Website report
Visit sitehttps://zergai.com/
AI automation for the systems your business depends on. Build integrations, modernize software, and automate operations with results you can verify.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Fly.io
Analysed Nov 7, 2026 · 15 categories · 97 passed · 26 warnings · 5 issues · 22 informational
Audit score
F46/100
Needs work
- Agentic
- 100
- SEO
- 46
What we found
5Needs a fix26Could be better97Looks good22Informational- 1.Needs a fix: No placeholder text: needs fixing. see checkUseful, specific content gives visitors answers and a reason to stay.
- 2.Needs a fix: llms.txt follows the spec: needs fixing. see checkClear, accessible information helps AI assistants understand and cite your website.
- 3.Could be better: Sampled URLs have aligned indexability signals: needs attention. see checkSearch engines need clear access and indexing instructions to list your pages.
- 4.Could be better: Images are missing size information. see checkDeclared dimensions keep content from jumping while images load.
- 5.Could be better: Lazy loading: needs attention. see checkImages affect page speed and accessibility.
Built with 2 technologies· detected stack
Read from the public source and response headers of the sampled pages.
How it fits together
NuxtFramework- Fly.ioHosting / edge
- Fly.ioHosting / edge
- NuxtFramework
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata11Looks good
100/100Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "Zerg | AI Automation for Mission-Critical Work"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 46 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "Zerg | AI Automation for Mission-Critical Work" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "AI automation for the systems your business depends on. Build integrations, modernize soft…"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description length
Looks good · Metadata · Review suggested
Observed evidence
Description is 148 characters and inside this audit's 70–160 preview range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 9 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing2Could be better14Looks good
68/100Could be better: Sampled URLs have aligned indexability signals1 sampled URL(s) have conflicting indexability signals: https://zergai.com/onboarding (applicable meta/header noindex, sitemap URL redirects to an unlisted final URL).
Could be better · Indexing · Measured on your pageCritical
Observed evidence
1 sampled URL(s) have conflicting indexability signals: https://zergai.com/onboarding (applicable meta/header noindex, sitemap URL redirects to an unlisted final URL).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.
Recommended fix
Keep submitted sitemap URLs successful and intended for indexing. Remove accidental noindex, list the preferred canonical URLs, and replace stale redirecting entries. A useful page does not have to appear in a sitemap.
Affected pages (1)
- https://zergai.com/onboarding
Could be better: Sitemap declared in robots.txtrobots.txt doesn't declare the sitemap.
Could be better · Indexing · Review suggested
Observed evidence
robots.txt doesn't declare the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.
Recommended fix
Add "Sitemap: https://zergai.com/sitemap.xml" to robots.txt so every crawler finds it without Search Console.
Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. No matching group; crawling is permitted by default.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://zergai.com/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 89 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical URL set
Looks good · Indexing · Measured on your page
Observed evidence
Canonical set: https://zergai.com/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (zergai.com).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (28 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 10 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content1Needs a fix1Could be better8Looks good1Informational
43/100Needs a fix: No placeholder textPlaceholder text found: "coming soon".
Needs a fix · Content · Review suggestedCritical
Observed evidence
Placeholder text found: "coming soon". First occurrence: "…d before production. Andesite Coming soon Supporting work on synthetic data, eva…" on https://zergai.com/contact.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. Right now the sampled pages don't provide it.
Recommended fix
Replace every placeholder before anything else on this list. Published placeholder text tells a reader the page is unfinished, and AdSense reviewers treat it the same way.
Affected pages (2)
- https://zergai.com/contact
- https://zergai.com/case-studies
Could be better: Text-to-HTML ratioVisible text is 3.6% of the HTML markup (scripts and styles excluded).
Could be better · Content · Review suggested
Observed evidence
Visible text is 3.6% of the HTML markup (scripts and styles excluded).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.
Recommended fix
Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.
Not measured: ReadabilityFlesch reading ease ≈ 40.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 40.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 707 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 707 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: automation, mission, critical, work.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 8 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
5 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 9 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured dataNot measured
Not measuredCould be better: JSON-LD presentNo JSON-LD structured data on the homepage.
Could be better · Structured data · Review suggested
Observed evidence
No JSON-LD structured data on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.
Could be better: Organization or WebSite schemaNo Organization, WebSite or Person schema found.
Could be better · Structured data · Review suggested
Observed evidence
No Organization, WebSite or Person schema found.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.
Recommended fix
Add an identity node so search engines and AI assistants can attribute your content to a real entity.
Not applicable: JSON-LD parsesNo JSON-LD blocks were found, so there is no syntax to validate.
Not applicable · Structured data · Measured on your page
Observed evidence
No JSON-LD blocks were found, so there is no syntax to validate.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.
Not applicable: Content-specific schemaNo content-specific schema (Article, Product, FAQPage…) detected.
Not applicable · Structured data · Measured on your page
Observed evidence
No content-specific schema (Article, Product, FAQPage…) detected.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.
Recommended fix
If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.
Headings7Looks good
100/100Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "AI automation for mission-critical work."
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Single H1
Looks good · Headings · Measured on your page
Observed evidence
Exactly one H1 on the homepage.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Heading levels don't skip
Looks good · Headings · Measured on your page
Observed evidence
Heading hierarchy is sequential across 31 headings.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "AI automation for mission-critical work.".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
31 headings, averaging 4.5 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
12 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Element IDs are unique per document
Looks good · Headings · Measured on your page
Observed evidence
All inspected element IDs are unique within their documents.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images2Could be better1Looks good1Informational
64/100Could be better: Width/height attributes4 of 7 visible images lack width and height attributes: (inline data image), (inline data image), (inline data image), ….
Could be better · Images · Review suggested
Observed evidence
4 of 7 visible images lack width and height attributes: (inline data image), (inline data image), (inline data image), ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Set explicit width and height so the browser reserves the space before the image loads. Without them the page shifts as images arrive, which is what Cumulative Layout Shift measures. next/image sets them for you.
Could be better: Lazy loadingNone of the 7 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).
Could be better · Images · Review suggested
Observed evidence
None of the 7 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Add loading="lazy" to below-the-fold images so the initial render doesn't wait on them. Keep the hero image eager.
Not applicable: Modern image formatsNo raster images with a recognizable file extension were found.
Not applicable · Images · Measured on your page
Observed evidence
No raster images with a recognizable file extension were found.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.
Recommended fix
Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 7 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links6Looks good
100/100Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Anchor text is meaningful
Looks good · Links · Measured on your page
Observed evidence
65 of 65 links have descriptive text or labels.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 25 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
4 same-page fragment link(s) have source targets.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile4Looks good2Informational
100/100Not applicable: Responsive image markupNone of the 7 images use srcset.
Not applicable · Mobile · Measured on your page
Observed evidence
None of the 7 images use srcset.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Interactive controls have source labels
Looks good · Mobile · Measured on your page
Observed evidence
682 source controls have detectable names. Browser accessibility and CSS visibility were not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: ARIA references point to source elements
Looks good · Mobile · Measured on your page
Observed evidence
41 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding1Looks good3Informational
100/100Not measured: Apple touch iconNo apple-touch-icon link.
Not measured · Branding · Not established
Observed evidence
No apple-touch-icon link.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.
Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (/favicon-light.png).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| HTML payload size | 1122 KB | Could be better: needs attentionThe page's HTML is 1122 KB uncompressed. |
| Inline styles are bounded | 416 KB | Could be better: needs attention416 KB of inline <style> in the page. |
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| Server response time | 688 ms | Looks good: goodThe audit received response headers after 688 ms from one test location. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Script/stylesheet count | — | Looks good: good5 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 1121.6 KB | Informational: measured source, not transferred bytes1121.6 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: Content Security PolicyA CSP is present but its script or object restrictions need review.
Could be better · Security · Review suggested
Observed evidence
A CSP is present but its script or object restrictions need review.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Restrict script origins, use nonces or hashes for inline scripts, avoid unsafe evaluation, and set object-src 'none'.
Could be better: Server technology disclosureThe X-Powered-By header advertises "Nuxt".
Could be better · Security · Review suggested
Observed evidence
The X-Powered-By header advertises "Nuxt".
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
You can remove it (in Next.js: poweredByHeader: false; in Express: app.disable('x-powered-by')). It adds bytes to every response and tells scanners what to probe; it is not a vulnerability by itself.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=31536000; includeSubDomains.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Frame embedding protection
Looks good · Security · Measured on your page
Observed evidence
Response headers restrict cross-origin framing (frame-ancestors 'self').
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
Referrer-Policy is strict-origin-when-cross-origin.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Browser feature permissions
Looks good · Security · Measured on your page
Observed evidence
A Permissions-Policy disables at least one sensitive browser feature.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Review remaining features and allow only origins the application needs.
Looks good: X-Content-Type-Options
Looks good · Security · Measured on your page
Observed evidence
nosniff is set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
2 declared form(s) submit over HTTPS to this site. Runtime submission behavior is untested.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Needs a fix: llms.txt follows the specllms.txt is missing a blockquote summary under the H1, markdown links in the form [name](url).
Needs a fix · AI answer readiness · Published platform rule
Observed evidence
llms.txt is missing a blockquote summary under the H1, markdown links in the form [name](url).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. Right now the sampled pages don't provide it.
Recommended fix
Follow the published structure: a single H1, a blockquote summary, then H2 sections whose lists use [name](url): short note. Parsers read the H1 and the link lists.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.
Could be better: Question-style headingsOnly 3% of 94 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 3% of 94 H2/H3 headings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "Built for mission-critical systems…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "Built for mission-critical systems…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: Freshness signalsNo dateModified schema or visible 'updated' dates found.
Could be better · AI answer readiness · Review suggested
Observed evidence
No dateModified schema or visible 'updated' dates found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
For content where dates matter, show the actual update date and mirror it in dateModified. Do not invent dates or change them without a substantive update. Missing dates alone do not prove stale content.
Could be better: llms.txt links resolve to this sitellms.txt contains no Markdown links to discoverable pages.
Could be better · AI answer readiness · Measured on your page
Observed evidence
llms.txt contains no Markdown links to discoverable pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add Markdown links such as [Pricing](/pricing) for the pages an answer engine should retrieve first.
Affected pages (1)
- https://zergai.com/
Could be better: Question headings have concise answers2/3 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Could be better · AI answer readiness · Measured on your page
Observed evidence
2/3 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.
Affected pages (1)
- https://zergai.com/use-cases
Could be better: Machine-readable provenance signalsOnly 3 of 4 provenance signal types were found: contact, date, author.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Only 3 of 4 provenance signal types were found: contact, date, author.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.
Affected pages (9)
- https://zergai.com/
- https://zergai.com/contact
- https://zergai.com/privacy
- https://zergai.com/products
- https://zergai.com/bot
- https://zergai.com/apps
- https://zergai.com/use-cases
- https://zergai.com/solutions
- https://zergai.com/case-studies
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /contact.md or /index.html.md.
Could be better · AI answer readiness · Measured on your page
Observed evidence
No markdown copy answered at /index.md or /contact.md or /index.html.md.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.
Affected pages (2)
- https://zergai.com/
- https://zergai.com/contact
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density21 concrete figures across 982 words.
Not measured · AI answer readiness · Not established
Observed evidence
21 concrete figures across 982 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html;charset=utf-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html;charset=utf-8.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: llms.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt exists (3650 chars of markdown).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Semantic HTML structure
Looks good · AI answer readiness · Measured on your page
Observed evidence
Semantic structure present: main×1, article×17, section×10, nav×1, header×1, footer×1.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 13 words, lists present — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
57 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "Zerg".
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Entity identity agrees across signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
The site is consistently named "Zerg" and 2 identity URL(s) stay on zergai.com.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 18/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: No "coming soon" or placeholder pages9 sampled page(s) still read as unfinished — found "coming soon".
Needs a fix · AdSense policy · Review suggestedCritical
Observed evidence
9 sampled page(s) still read as unfinished — found "coming soon".
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Finish those pages, or redirect, noindex or remove them. Google policy prohibits ads on screens under construction.
Affected pages (9)
- https://zergai.com/
- https://zergai.com/contact
- https://zergai.com/privacy
- https://zergai.com/products
- https://zergai.com/bot
- https://zergai.com/apps
- https://zergai.com/use-cases
- https://zergai.com/solutions
- https://zergai.com/case-studies
Needs a fix: Latest article has real depthThe newest article has 71 words of body text.
Needs a fix · AdSense policy · Measured on your pageCritical
Observed evidence
The newest article has 71 words of body text.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Publish articles that answer the question fully — under a few hundred words a page rarely carries more than a restated headline. Depth is measured here in words of body copy, not in padding.
Affected pages (1)
- https://zergai.com/blog/category/case-studies
Needs a fix: Latest article names an author and a dateThe newest article shows neither an author nor a publication date.
Needs a fix · AdSense policy · Measured on your pageCritical
Observed evidence
The newest article shows neither an author nor a publication date.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Put a named author and a visible date on every article, and repeat both in Article JSON-LD. Reviewers look for a person who stands behind the page.
Affected pages (1)
- https://zergai.com/blog/category/case-studies
Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks cookie/storage, advertising or Google disclosure signals.
Could be better · AdSense policy · Published platform ruleCritical
Observed evidence
Fetched privacy policy lacks cookie/storage, advertising or Google disclosure signals.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Describe data collection, sharing, and cookie use by Google and other third-party ad vendors.
Affected pages (1)
- https://zergai.com/privacy
Could be better: Sampled publisher-content coverage2/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 2750 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
2/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 2750 publisher words in total. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (2)
- https://zergai.com/onboarding
- https://zergai.com/case-studies
Could be better: About pageNo about page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No about page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add an About page that identifies the publisher, site purpose, and relevant experience. This supports content transparency but is not a standalone AdSense requirement.
Could be better: Tool pages expose explanatory content3/10 tool-style screen(s) expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
3/10 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.
Affected pages (3)
- https://zergai.com/contact
- https://zergai.com/onboarding
- https://zergai.com/case-studies
Could be better: Policy pages linked site-wide1/10 crawled pages don't link to the privacy policy.
Could be better · AdSense policy · Review suggested
Observed evidence
1/10 crawled pages don't link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.
Affected pages (1)
- https://zergai.com/onboarding
Not measured: ads.txtNo ads.txt yet.
Not measured · AdSense policy · Not established
Observed evidence
No ads.txt yet.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Not measured: Latest article reads as edited workThe newest article has only 71 words, too few to measure style reliably.
Not measured · AdSense policy · Not established
Observed evidence
The newest article has only 71 words, too few to measure style reliably.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
The depth check covers length. Style signals need a few hundred words before they mean anything.
Affected pages (1)
- https://zergai.com/blog/category/case-studies
Looks good: Privacy policy page
Looks good · AdSense policy · Measured on your page
Observed evidence
Privacy policy found: https://zergai.com/privacy
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Terms page
Looks good · AdSense policy · Measured on your page
Observed evidence
Terms page found: /terms
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Contact method
Looks good · AdSense policy · Measured on your page
Observed evidence
Contact page found: https://zergai.com/contact
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: First-party contact email
Looks good · AdSense policy · Measured on your page
Observed evidence
First-party contact email found: hello@zergai.com.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
6/8 editorial pages clear the audit's publisher-content triage threshold. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 6 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: Article-style content exists
Looks good · AdSense policy · Measured on your page
Observed evidence
Article-style content detected.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | zergai.com |
|---|---|
| Hosting | Fly.io |
| IP addresses | 66.241.125.142, 2a09:8280:1::15a:e45b:0 |
| DNS A | 66.241.125.142 |
| DNS AAAA | 2a09:8280:1::15a:e45b:0 |
| DNS NS | ns19.domaincontrol.com · ns20.domaincontrol.com |
| DNS MX | 1 aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com · 10 alt3.aspmx.l.google.com · 10 alt4.aspmx.l.google.com |
| TLS | TLSv1.3TLS_AES_256_GCM_SHA384 |
| Certificate issuer | Let's Encrypt / YE1 |
| Certificate valid until | Jan 4 23:53:34 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
707 publisher words
Page structure
html content
Observed discovery
Depth 0 · 8 incoming links
HTTP 200 · 1121.6 KB source
Source interactions
77 controls · 0 unnamed
2 script / 3 stylesheet references
- Canonical declaration
- https://zergai.com/
- Schema types
- None observed
- Outgoing links in sampled graph
- /products · /products/zerg · /products/ztc · /products/zde · /cloud · /bot · /apps · /use-cases · /use-cases/data-connectors · /use-cases/code-migration · /use-cases/cve · /use-cases/etl-pipelines · /use-cases/operations-workflows · /solutions · /case-studies · /case-studies/durable-javascript-to-typescript-migration · /case-studies/andesite · /platform · /blog · /help · /contact · /security · /for-ai · /privacy · /terms
Routes: / · /contact · /privacy · /products · /onboarding · /bot · /apps · /use-cases · /solutions · /case-studies
Resource origins 3
Resources associated with your website. External resources may belong to the same organization.
- https://zergai.com/stylesheet, script, image · 26 references · same origin
- https://zerglytics-epoch.fly.dev/script · 10 references · cross origin
- https://du9qsjxy0qfg8.cloudfront.net/image · 6 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | Declared policy for this page. |
| Googlebotsearch | /contact | allowed | Declared policy for this page. |
| Googlebotsearch | /privacy | allowed | Declared policy for this page. |
| Googlebotsearch | /products | allowed | Declared policy for this page. |
| Googlebotsearch | /onboarding | allowed | Declared policy for this page. |
| Googlebotsearch | /bot | allowed | Declared policy for this page. |
| Googlebotsearch | /apps | allowed | Declared policy for this page. |
| Googlebotsearch | /use-cases | allowed | Declared policy for this page. |
| Googlebotsearch | /solutions | allowed | Declared policy for this page. |
| Googlebotsearch | /case-studies | allowed | Declared policy for this page. |
| bingbotsearch | / | allowed | Declared policy for this page. |
| bingbotsearch | /contact | allowed | Declared policy for this page. |
| bingbotsearch | /privacy | allowed | Declared policy for this page. |
| bingbotsearch | /products | allowed | Declared policy for this page. |
| bingbotsearch | /onboarding | allowed | Declared policy for this page. |
| bingbotsearch | /bot | allowed | Declared policy for this page. |
| bingbotsearch | /apps | allowed | Declared policy for this page. |
| bingbotsearch | /use-cases | allowed | Declared policy for this page. |
| bingbotsearch | /solutions | allowed | Declared policy for this page. |
| bingbotsearch | /case-studies | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | / | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /contact | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /products | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /onboarding | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /bot | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /apps | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /use-cases | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /solutions | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /case-studies | allowed | Declared policy for this page. |
| PerplexityBotsearch | / | allowed | Declared policy for this page. |
| PerplexityBotsearch | /contact | allowed | Declared policy for this page. |
| PerplexityBotsearch | /privacy | allowed | Declared policy for this page. |
| PerplexityBotsearch | /products | allowed | Declared policy for this page. |
| PerplexityBotsearch | /onboarding | allowed | Declared policy for this page. |
| PerplexityBotsearch | /bot | allowed | Declared policy for this page. |
| PerplexityBotsearch | /apps | allowed | Declared policy for this page. |
| PerplexityBotsearch | /use-cases | allowed | Declared policy for this page. |
| PerplexityBotsearch | /solutions | allowed | Declared policy for this page. |
| PerplexityBotsearch | /case-studies | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | / | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /contact | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /privacy | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /products | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /onboarding | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /bot | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /apps | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /use-cases | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /solutions | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /case-studies | allowed | Declared policy for this page. |
| GPTBottraining | / | allowed | Declared policy for this page. |
| GPTBottraining | /contact | allowed | Declared policy for this page. |
| GPTBottraining | /privacy | allowed | Declared policy for this page. |
| GPTBottraining | /products | allowed | Declared policy for this page. |
| GPTBottraining | /onboarding | allowed | Declared policy for this page. |
| GPTBottraining | /bot | allowed | Declared policy for this page. |
| GPTBottraining | /apps | allowed | Declared policy for this page. |
| GPTBottraining | /use-cases | allowed | Declared policy for this page. |
| GPTBottraining | /solutions | allowed | Declared policy for this page. |
| GPTBottraining | /case-studies | allowed | Declared policy for this page. |
| ClaudeBottraining | / | allowed | Declared policy for this page. |
| ClaudeBottraining | /contact | allowed | Declared policy for this page. |
| ClaudeBottraining | /privacy | allowed | Declared policy for this page. |
| ClaudeBottraining | /products | allowed | Declared policy for this page. |
| ClaudeBottraining | /onboarding | allowed | Declared policy for this page. |
| ClaudeBottraining | /bot | allowed | Declared policy for this page. |
| ClaudeBottraining | /apps | allowed | Declared policy for this page. |
| ClaudeBottraining | /use-cases | allowed | Declared policy for this page. |
| ClaudeBottraining | /solutions | allowed | Declared policy for this page. |
| ClaudeBottraining | /case-studies | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | / | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /contact | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /privacy | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /products | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /onboarding | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /bot | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /apps | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /use-cases | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /solutions | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /case-studies | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /contact | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /products | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /onboarding | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /bot | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /apps | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /use-cases | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /solutions | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /case-studies | allowed | Declared policy for this page. |
Advertised APIs and machine interfaces
documentation · declared
https://apps.zergai.com/developers
This interface was advertised; its runtime behavior remains unverified.
Public DNS and TLS endpoint
zergai.com · observed · 66.241.125.142, 2a09:8280:1::15a:e45b:0
- A
- 66.241.125.142
- AAAA
- 2a09:8280:1::15a:e45b:0
- CNAME
- Unavailable for this exact hostname
- NS
- ns19.domaincontrol.com · ns20.domaincontrol.com
- MX
- 1 aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com · 10 alt3.aspmx.l.google.com · 10 alt4.aspmx.l.google.com
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Let's Encrypt / YE1
Certificate valid until: Jan 4 23:53:34 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Replace every placeholder text
Replace Lorem ipsum and 'coming soon' with publisher content before sending users or ad reviewers to the page.
- 02
Your top fixes list is the priority order — clear the red items before creating more content.
- 03
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
- 04
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://zergai.com/
- https://zergai.com/contact
- https://zergai.com/privacy
- https://zergai.com/products
- https://zergai.com/onboarding
- https://zergai.com/bot
- https://zergai.com/apps
- https://zergai.com/use-cases
- https://zergai.com/solutions
- https://zergai.com/case-studies