Zyntlox

Method and limits

How Zyntlox reaches its results

The Zyntlox Generative Index (ZGI) is a number from 0 to 100 for how reachable and machine-readable a site is for AI search and answer engines. It is computed by fixed arithmetic from test results. No AI model writes a score or a finding. This page is current for ZGI version 2.7.

How the score is calculated

  1. Every test returns one of six states: pass, warn (partial credit), fail, inconclusive (could not be determined), not applicable or not tested.
  2. A test counts toward the score only if it has a weight above zero, applies to the site, and produced pass, warn or fail. Inconclusive, not tested and not applicable tests are left out and shown as coverage. They are never counted as passed.
  3. Inside a category, the category score is the weighted share of credit earned: Σ(test weight × credit) ÷ Σ(test weight), over the tests that counted.
  4. The ZGI is Σ(category weight × category score). If a whole category has nothing to score, the others are rescaled to 100.
  5. The points shown next to each test add up to the ZGI.

Every report states the formula version and the time the tests ran. Any change to a weight, severity, test, threshold or crawler list bumps the version, so a score can always be traced to the formula that produced it. Scores from different versions may not be comparable.

Categories and weights

The category weights are product decisions, not measurements. A site that only leaves crawlers allowed earns most of Crawler access; that is intended, because access is the precondition, not the whole score.

CategoryWeightScored testsWhat it covers
Crawler access3015Whether AI and search crawlers are permitted and able to fetch the site.
Entity graph355Whether the site states, in machine-readable form, who or what it is.
Machine context207Files and page elements that help machines discover and understand the site.
Citability151How much concrete, quotable data the page text contains.

Every test (61)

28 tests are scored and 33 are reported only. Severity is fixed per test and is never chosen by a model. Open a category to see what each test expects and what counts as a pass.

Crawler access25 tests · 30% of the score
GEO-106-GOOGLEBOTGooglebot (Search & AI Indexing)Criticalweight 4

Googlebot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for Googlebot, or the site has no robots.txt (HTTP 4xx).

GEO-102-OAI-SEARCHBOTOpenAI OAI-SearchBot (ChatGPT Search)Highweight 3

OAI-SearchBot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for OAI-SearchBot, or the site has no robots.txt (HTTP 4xx).

GEO-108-BINGBOTMicrosoft Bingbot (Bing & Copilot discovery)Highweight 3

Bingbot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for Bingbot, or the site has no robots.txt (HTTP 4xx).

GEO-120-SIMULATED-ACCESSSimulated crawler requests (search & retrieval bots)Highweight 3

The server answers crawler user agents the way it answers a browser.

Pass: Every considered crawler request returns 2xx (redirects allowed).

GEO-505-PAGE-RESPONSEPage responds successfully with HTMLHighweight 3

The final response is HTTP 2xx with an HTML content type.

Pass: HTTP 2xx and a text/html (or XHTML) content type.

GEO-605-NOINDEXPage is not marked noindexHighweight 3

Neither the HTML nor the headers tell crawlers to keep the page out of their index.

Pass: No noindex/none directive was found.

GEO-105-CLAUDE-SEARCHBOTClaude-SearchBot (Claude search)Highweight 2

Claude-SearchBot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for Claude-SearchBot, or the site has no robots.txt (HTTP 4xx).

GEO-109-PERPLEXITYBOTPerplexityBot (Perplexity search)Highweight 2

PerplexityBot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for PerplexityBot, or the site has no robots.txt (HTTP 4xx).

GEO-501-TLSTLS / HTTPSMediumweight 2

The page is served over HTTPS with TLS 1.2 or 1.3.

Pass: TLS 1.2 or 1.3 was negotiated.

GEO-502-TLS-CERTTLS certificate validityMediumweight 2

The certificate chain is trusted and valid for at least 14 more days.

Pass: Trusted certificate with 14 or more days left.

GEO-503-HTTPS-REDIRECTHTTP redirects to HTTPSMediumweight 2

Plain HTTP requests are permanently redirected (301 or 308) to HTTPS.

Pass: http:// redirects to https:// with a permanent redirect.

GEO-504-REDIRECT-CHAINRedirect chain lengthMediumweight 2

The page is reached with at most 1 redirect and no loop.

Pass: 0 or 1 redirect.

GEO-103-CHATGPT-USERChatGPT-User (user-initiated fetch)Mediumweight 1

ChatGPT-User is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for ChatGPT-User, or the site has no robots.txt (HTTP 4xx).

GEO-110-CLAUDE-USERClaude-User (user-initiated fetch)Mediumweight 1

Claude-User is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for Claude-User, or the site has no robots.txt (HTTP 4xx).

GEO-604-CANONICALCanonical URL declared and consistentLowweight 1

The page declares a canonical URL that points to itself (or to another page of the same site, deliberately).

Pass: A canonical link is present and matches the page URL.

GEO-101-GPTBOTOpenAI GPTBot (model training)Informationalnot scored

GPTBot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for GPTBot, or the site has no robots.txt (HTTP 4xx).

GEO-104-CLAUDEBOTAnthropic ClaudeBot (model training)Informationalnot scored

ClaudeBot is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for ClaudeBot, or the site has no robots.txt (HTTP 4xx).

GEO-107-GOOGLE-EXTENDEDGoogle-Extended (control token)Informationalnot scored

Google-Extended is permitted to fetch "/".

Pass: The matching robots.txt group allows "/" for Google-Extended, or the site has no robots.txt (HTTP 4xx).

GEO-506-RESPONSE-TIMEResponse time (time to first byte)Informationalnot scored

The median time to first byte is at most 800 ms.

Pass: Median at most 800 ms.

GEO-507-COMPRESSIONResponse compressionInformationalnot scored

The HTML is served compressed (gzip, br, zstd or deflate).

Pass: A compression Content-Encoding is present.

GEO-508-CACHE-HEADERSCache headers presentInformationalnot scored

The response carries at least one cache validator or directive.

Pass: At least one of Cache-Control, ETag, Last-Modified.

GEO-509-ROBOTS-SIZErobots.txt is within Google's size limitInformationalnot scored

The file is no larger than 500 KiB.

Pass: The file is 500 KiB or smaller.

GEO-510-404-HANDLINGMissing pages return a real 404Informationalnot scored

A page that does not exist answers 404 or 410.

Pass: The made-up path answers HTTP 404 or 410.

GEO-602-INITIAL-HTMLContent present in the server's HTMLInformationalnot scored

The page's main text is present in the HTML as the server sends it.

Pass: At least half of the rendered text is already in the served HTML (or, with no rendering to compare, the served HTML holds a substantial amount of text and no empty app shell).

GEO-606-SNIPPET-CONTROLSPage allows text snippetsInformationalnot scored

Neither the HTML nor the headers forbid text snippets.

Pass: No nosnippet or max-snippet:0 directive was found.

Entity graph11 tests · 35% of the score
GEO-301-ORG-SCHEMAOrganization structured dataMediumweight 5

The page declares the organization behind the site in JSON-LD.

Pass: An Organization/Corporation entity is present in valid JSON-LD.

GEO-302-SAMEASsameAs profile linksLowweight 3

The entity links to its other public profiles.

Pass: At least one sameAs reference is present in the JSON-LD.

GEO-304-JSONLD-VALIDStructured data (JSON-LD) is validMediumweight 2

Every JSON-LD block is syntactically valid JSON.

Pass: All JSON-LD blocks parse.

GEO-303-FAQ-SCHEMAFAQPage structured dataLowweight 1

Question-and-answer content is marked up when the page has any.

Pass: FAQPage markup is present.

GEO-305-ORG-PROPERTIESOrganization data names the organizationLowweight 1

The Organization declares a name, a url and a logo.

Pass: name, url and logo are all present.

GEO-306-ENTITY-IDOrganization has a stable @idInformationalnot scored

The Organization has an @id (a stable identifier other entities can refer to).

Pass: An @id is present.

GEO-307-ENTITY-CONSISTENCYSingle consistent Organization entityInformationalnot scored

The page describes one organization.

Pass: At most one distinct Organization entity.

GEO-308-SCHEMA-TYPESStructured data types presentInformationalnot scored

Reported for information.

Pass: At least one schema.org type was found.

GEO-309-AUTHOR-PERSONArticles declare an authorInformationalnot scored

The article names an author and links to a profile.

Pass: Every article declares an author with a name and a url or sameAs link.

GEO-710-ABOUT-CONTACTAbout and Contact pages are linkedInformationalnot scored

The page links to an About page and a Contact page.

Pass: Both links were found.

GEO-711-BRAND-CONSISTENCYBrand name appears consistentlyInformationalnot scored

The Organization name appears in the title, og:site_name or H1.

Pass: The name appears in at least one of them.

Machine context24 tests · 20% of the score
GEO-202-SITEMAP-DIRECTIVESitemap declared in robots.txtMediumweight 2

robots.txt points crawlers to the site's sitemap.

Pass: At least one Sitemap: line is present.

GEO-203-SITEMAP-VALIDSitemap file is retrievable and well-formedMediumweight 2

The sitemap returns HTTP 200, is well-formed XML with a <urlset> or <sitemapindex> root, and lists at least one URL (at most 50,000 per file).

Pass: HTTP 200, well-formed XML, known root element, 1 to 50,000 URLs.

GEO-204-SITEMAP-URLSSampled sitemap URLs are healthyMediumweight 2

Sitemap URLs return HTTP 2xx directly (no redirect, no 404/410).

Pass: Every sampled URL with a decisive answer returned HTTP 2xx.

GEO-702-TITLEPage has a titleMediumweight 2

The page has a non-empty <title>.

Pass: A non-empty title is present.

GEO-205-SITEMAP-LASTMODSitemap lastmod dates are validLowweight 1

Every <lastmod> is a valid W3C Datetime (YYYY, YYYY-MM, YYYY-MM-DD or a full timestamp with a time zone).

Pass: All lastmod values present are valid.

GEO-703-META-DESCPage has a meta descriptionLowweight 1

The page has a non-empty meta description.

Pass: A non-empty meta description is present.

GEO-704-H1Page has one main heading (H1)Lowweight 1

The page has exactly one non-empty H1.

Pass: Exactly one H1.

GEO-201-LLMS-TXT/llms.txtInformationalnot scored

A /llms.txt file is published.

Pass: /llms.txt returns HTTP 200.

GEO-601-PAGE-WEIGHTPage weight for AI (estimated tokens)Informationalnot scored

Reported for information. No AI provider documents a size threshold.

Pass: The page HTML was measured.

GEO-607-HREFLANGhreflang annotations follow Google's rulesInformationalnot scored

Every hreflang code is well formed, the page lists itself, and no code points to two different URLs.

Pass: All codes are well formed, the page references itself, and there are no conflicts.

GEO-705-HEADINGSHeading hierarchy is soundInformationalnot scored

No empty headings and no skipped levels.

Pass: No empty headings and no skipped levels.

GEO-706-IMAGE-ALTImages have alt attributesInformationalnot scored

Every image has an alt attribute.

Pass: Every image has an alt attribute.

GEO-707-SEMANTIC-HTMLSemantic HTML elements usedInformationalnot scored

The page uses <main> or <article> to mark its main content.

Pass: <main> or <article> is present.

GEO-708-LINK-TEXTLinks have descriptive textInformationalnot scored

Links are described by their text.

Pass: No generic or empty link text.

GEO-709-CONTENT-LENGTHAmount of readable textInformationalnot scored

Reported for information.

Pass: At least 150 words of readable text.

GEO-712-TEXT-BLOCKSText is divided by headingsInformationalnot scored

No stretch of text runs longer than 300 words without a heading.

Pass: Every stretch between headings is 300 words or fewer.

GEO-713-ANSWER-AFTER-H1A short summary follows the main headingInformationalnot scored

A paragraph of 20 to 100 words follows the H1.

Pass: The first paragraph after the H1 is 20 to 100 words long.

GEO-801-INTERNAL-LINKSInternal links lead to working pagesInformationalnot scored

Internal links lead to pages that exist.

Pass: No crawled internal link answered 404 or 410.

GEO-802-INTERNAL-REDIRECTSInternal links avoid redirectsInformationalnot scored

Internal links point straight at the final URL.

Pass: No crawled internal link redirects.

GEO-803-CANONICAL-CONSISTENCYCanonical URLs are consistent across pagesInformationalnot scored

Each page declares itself as its canonical URL.

Pass: Every crawled page with a canonical points to itself.

GEO-804-DUPLICATE-URLSOne URL per pageInformationalnot scored

Each page is linked under a single URL.

Pass: No page is linked under more than one spelling.

GEO-805-ORPHAN-PAGESSitemap pages are linked from the siteInformationalnot scored

Every page in the sitemap is linked from another page.

Pass: Every sitemap URL was found as a link.

GEO-806-SITEMAP-INDEXABLESitemap pages are indexableInformationalnot scored

Pages in the sitemap can be indexed.

Pass: No crawled sitemap page carries noindex.

GEO-807-QUERY-LINKSInternal links avoid query-parameter URLsInformationalnot scored

Few internal links carry query parameters, or those pages declare the clean URL as canonical.

Pass: Fewer than 5 internal URLs, or fewer than 20% of them, carry query parameters.

Citability1 tests · 15% of the score
GEO-401-STAT-DENSITYQuantitative figures in page textLowweight 1

The page contains concrete figures that can be quoted.

Pass: 5 or more figures. Fewer earns proportional credit (n ÷ 5).

The crawlers Zyntlox simulates

For each crawler below, the audit sends one request with that crawler's user-agent string and compares the answer with a request from a normal browser. The details come from each provider's own documentation, last checked 2026-11-07.

  • GPTBot · OpenAIProvider documentation

    Crawls content that may be used to train OpenAI's generative AI foundation models.

    User-agent string follows an example in the provider's documentation.

  • OAI-SearchBot · OpenAIProvider documentation

    Surfaces websites in ChatGPT's search features. Controls search eligibility, separately from GPTBot.

    The exact string was not published, so it is built from the provider's token and naming convention; the real crawler's version number may differ.

  • ChatGPT-User · OpenAIProvider documentation

    Fetches a page when a ChatGPT user or Custom GPT action asks for it. Not an automatic crawler.

    User-agent string follows an example in the provider's documentation. This fetcher acts on a person's request and may ignore robots.txt by design.

  • ClaudeBot · AnthropicProvider documentation

    Collects web content that could contribute to model training.

    The exact string was not published, so it is built from the provider's token and naming convention; the real crawler's version number may differ.

  • Claude-SearchBot · AnthropicProvider documentation

    Navigates the web to improve the quality of Claude search results.

    The exact string was not published, so it is built from the provider's token and naming convention; the real crawler's version number may differ.

  • Claude-User · AnthropicProvider documentation

    Retrieves a page when a Claude user asks a question that needs it. User-initiated.

    The exact string was not published, so it is built from the provider's token and naming convention; the real crawler's version number may differ.

  • Googlebot · GoogleProvider documentation

    Google Search crawler; its index also serves Google's AI search features.

    User-agent string follows an example in the provider's documentation.

  • Bingbot · MicrosoftProvider documentation

    Bing's crawler; discovers and indexes pages for Bing Search, which also feeds Copilot.

    The exact string was not published, so it is built from the provider's token and naming convention; the real crawler's version number may differ.

  • PerplexityBot · PerplexityProvider documentation

    Surfaces and links websites in Perplexity search results. Perplexity states it is not used to crawl content for foundation models.

    User-agent string follows an example in the provider's documentation.

What the score does not say

  • Crawler access is what robots.txt permits, plus a simulation. It does not show that any AI engine visits, indexes or cites the site.
  • The simulation cannot detect firewall rules that check a crawler's IP address against the provider's published ranges, so a real crawler may be treated differently from a simulated request.
  • Structured data does not guarantee citations or rankings.
  • When a page could only be fetched without running scripts, structured data added by scripts is invisible. In that case a missing Organization or FAQ entry is reported as inconclusive, not as a failure.
  • Signals that no major AI engine has confirmed it uses, such as /llms.txt, are checked and shown but never scored.
  • Blocking training crawlers (GPTBot, ClaudeBot, Google-Extended) is reported but does not lower the score. It is a site owner's choice.

Judgement calls we made

These are Zyntlox's choices, not facts about any AI engine. They are stated so you can disagree with them.

  • The category weights, each test's weight and each severity.
  • Full credit for quantitative figures at 5 figures in the page text.
  • A text block is flagged above 300 words without a heading.
  • A short summary after the main heading should run 20 to 100 words.
  • Query-parameter links are flagged at 5 URLs or 20% of the pages tested.

How Zyntlox scans a site

  • The audit requests the page you enter, /robots.txt, /llms.txt, the sitemap, and a sample of linked pages (25 by default, 50 at most), fetched without running scripts. Where possible the main page is loaded in a headless browser so that content added by scripts is visible; if that is slow or unavailable, it is fetched without scripts instead.
  • Its own checks identify themselves with the user agent Mozilla/5.0 (compatible; ZyntloxAudit/x.y; +https://zyntlox.com), where x.y is the version of that check. The simulated-access test sends each crawler's own string, listed above.
  • Each audit is bounded: a fixed number of requests and a time budget, and audits are rate limited per visitor. Private, internal and local addresses are refused, including when a redirect leads to one. Zyntlox does not log in to sites.
  • If you run a site and want us to stop scanning it, write to hello@zyntlox.com.