Every GEO check the scanner runs

If a crawler cannot read the page, nothing else on this list can matter. This is the only dimension where a failure makes the rest of the score moot.

• 2 ptrobots.txt is served

  A request for /robots.txt returns HTTP 200 with a non-empty body.

• 6 ptNo AI crawler is blocked

  Parsing robots.txt into user-agent groups, none of gptbot, claudebot, perplexitybot, oai-searchbot or google-extended is disallowed from /, AND the homepage served a crawler-shaped request with HTTP 200.

• 1 ptrobots.txt declares a sitemap

  robots.txt contains a Sitemap: line.

• 2 ptHomepage returns HTTP 200

  The homepage returns HTTP 200 to a non-browser request that identifies itself honestly.

• 2 ptHomepage is marked noindex

  The homepage has no meta robots directive containing noindex.

• 3 ptsitemap.xml is present and well-formed

  /sitemap.xml returns a body containing <urlset> or <sitemapindex>.

• 1 ptrobots.txt states a content policy

  robots.txt contains a Content-Signal directive with a value on the same line, for example `Content-Signal: search=yes, ai-input=yes, ai-train=no`.

JSON-LD is how a model binds your brand name, domain and product into one entity instead of inferring three unrelated strings.

• 5 ptValid JSON-LD is present

  At least one <script type="application/ld+json"> block parses as JSON and declares at least one @-keyword (@context, @type, @graph or @id).

• 4 ptAn entity node is declared

  Parsed JSON-LD contains an @type of Organization, WebSite, Person or LocalBusiness.

• 3 ptContent-type schema is present

  Parsed JSON-LD contains an @type of FAQPage, Article, BlogPosting, HowTo, Product, SoftwareApplication or BreadcrumbList.

Generative engines select sources that answer a question thoroughly. Thin pages are rarely retrievable regardless of how well they are marked up.

• 5 ptSubstantial body text

  Visible text, after removing script, style and comment content, contains at least 800 word tokens.

• 3 ptContent is divided into sections

  The page contains at least 4 H2 elements.

• 3 ptLists and tables are present

  The page contains both a <ul>/<ol> and a <table>.

Statistics, quotations and cited sources are the interventions with the largest measured effect in the published GEO research.

• 4 ptQuantified claims are present

  Body text contains at least 5 numeric claims: percentages, currency amounts, multipliers of the form 3.2x, thousands-separated figures, or raw numbers of five digits or more.

• 3 ptDirect quotations are present

  The page contains at least one <blockquote> element.

• 3 ptExternal authoritative sources are cited

  The page links to at least 2 external hosts on the authority list: arxiv.org, doi.org, nature.com, science.org, acm.org, ieee.org, springer.com, sciencedirect.com, any .gov or .edu host, wikipedia.org, github.com, developer.mozilla.org, ...

• 1 ptCanonical URL is declared

  The page declares a rel=canonical link.

Answers are extracted as spans, not pages. A question-shaped heading followed by an immediate answer is the easiest thing for a retrieval system to lift intact.

• 4 ptHeadings are phrased as real questions

  At least 3 H2 or H3 headings either end with a question mark or begin with how, what, why, which, when, who, where, is, are, do, does, can, should or will.

• 3 ptFAQPage schema is present

  Parsed JSON-LD contains a FAQPage node.

• 3 ptHeadings are followed by a direct answer

  Of the first 30 heading-then-paragraph pairs (H2/H3 optionally followed by wrapper elements then a <p>), at least 60% have an opening paragraph of 80 words or fewer.

E-E-A-T signals decide whether a model treats a claim as safe to repeat rather than something it should hedge.

• 2 ptServed over HTTPS

  The homepage was retrieved over https://, rather than only over plain http://.

• 3 ptAbout and contact paths are linked

  Hrefs on the page include both an about-style path (about, company, team, who-we-are) and a contact-style path (contact, support) or a mailto: link.

• 3 ptAuthorship is attributed

  Authorship is signalled by any of: a Person node in parsed JSON-LD, an author property with a non-empty value in parsed JSON-LD, rel="author", or a visible byline matching "by Firstname Lastname".

• 2 ptEntity is cross-referenced

  Parsed JSON-LD contains a sameAs property with a non-empty value.

Heading hierarchy and landmark elements are how a parser locates section boundaries at all.

• 3 ptExactly one H1

  The page contains exactly one non-empty <h1>.

• 3 ptSemantic landmarks are used

  At least 3 of main, article, section, header, nav and footer appear as elements.

• 2 ptMain content is in the HTML

  The raw server response contains at least 100 words of visible text without executing JavaScript.

Title, description and canonical control what a search or answer surface can show about the page.

• 3 ptTitle length is in range

  <title> is between 15 and 65 characters long.

• 2 ptMeta description length is in range

  The meta description is between 50 and 160 characters long.

• 1 ptOpen Graph tags are present

  At least one meta property beginning with og: is present.

• 1 ptDocument language is declared

  The <html> element carries a lang attribute.

A cheap and optional signal. Google has stated it does not use llms.txt in Search, and crawler support is inconsistent.

• 4 pt/llms.txt is present and structured

  /llms.txt returns more than 20 bytes and contains an H1, a > summary line and at least 3 markdown links.

• 1 ptA crawler policy is published

  robots.txt is readable, so a crawler policy is published.

• 1 ptA markdown alternate is declared

  The document head contains a <link> with rel="alternate" and type="text/markdown", in either attribute order.

Dated content is deprioritised in generated answers, and an undated page gives an engine nothing to reason about.

• 3 ptA machine-readable date is present and recent

  A machine-readable date is found in dateModified, datePublished or article:modified_time.

• 2 ptA current year appears in the content

  The current calendar year appears in the visible body text.

Language and region markup decides which language market a page can be retrieved in at all.

• 2 ptAlternate language versions are declared

  At least 2 distinct hreflang language codes are declared.

• 1 ptA region-specific locale is declared

  A language tag carrying a region subtag appears in <html lang>, in og:locale or in an hreflang attribute - for example en-GB, en_GB or de-AT.

A slow or non-mobile-readable page is dropped before any content analysis happens.

• 1 ptViewport meta tag is present

  A meta viewport tag is present.

• 1 ptHTML payload is reasonable

  The uncompressed HTML response is under 500 KB.