example.com

Checked: 2026-08-08 Β· seo-v1+geo-v1 Β· 1 pages

This check is more than 30 days old, so it may no longer reflect the site.

β€”
Overall
76
SEO hygiene
coverage 76%
62
GEO readiness
coverage 100%
β€”
AI exposure

Not enough coverage for a combined score

What robots.txt tells each crawler

OAI-SearchBotAI search β€” counts towards GEO readinessAllowedβ€”
ChatGPT-UserUser-triggered retrieval β€” diagnostic onlyAllowedβ€”
GPTBotModel training β€” reported, never scoredAllowedβ€”
Claude-SearchBotAI search β€” counts towards GEO readinessAllowedβ€”
Claude-UserUser-triggered retrieval β€” diagnostic onlyAllowedβ€”
ClaudeBotModel training β€” reported, never scoredAllowedβ€”
PerplexityBotAI search β€” counts towards GEO readinessAllowedβ€”
Perplexity-UserUser-triggered retrieval β€” diagnostic onlyAllowedβ€”
Google-ExtendedModel training β€” reported, never scoredAllowedβ€”
CCBotModel training β€” reported, never scoredAllowedβ€”
GooglebotOrdinary web searchAllowedβ€”
BingbotOrdinary web searchAllowedβ€”

What was observed

SEO hygiene

Links not checked

unknown

No internal links were sampled within the budget.

No canonical URL

warn

Without a canonical, duplicate addresses of the same page compete with each other.

Canonical targets not checked

unknown

No sampled page declared a canonical URL.

Little content in the served HTML

fail

Only 19 words are present in the served HTML β€” the page most likely renders its content in the browser.

Description length not checked

not_applicable

There is no description to measure.

No meta description

warn

Search engines will compose their own snippet from page text.

Exactly one H1 on the homepage

pass

One top-level heading was found in the served HTML.

  • Example Domain

Heading levels follow their order

pass

Observed heading sequence on the homepage; visual styling is not judged here.

Homepage responds

pass

The homepage returned HTTP 200 to an ordinary GET request.

  • HTTP 200

No hreflang alternates

not_applicable

Single-language sites do not need them; this is not counted against the score.

Served over HTTPS

pass

The address that was actually served after redirects was checked.

  • https://example.com/

No images on the homepage

not_applicable

Nothing to describe.

No noindex directive on the homepage

pass

Neither the robots meta tag nor the X-Robots-Tag header blocks indexing.

Few internal links on the homepage

warn

0 same-origin links were found in the served HTML.

No structured data

warn

No JSON-LD was found on the homepage.

Document language declared

pass

The html element declares the document language.

  • en

No robots.txt

warn

Crawlers assume everything is allowed, which is usually fine but leaves no place to declare a sitemap.

  • HTTP 404

Search crawlers may fetch the homepage

pass

robots.txt does not disallow ordinary web search crawlers here.

No sitemap found

warn

Neither robots.txt nor /sitemap.xml pointed at one.

Sitemap parses

pass

0 URLs read from the sampled sitemap documents.

No OpenGraph or Twitter tags

warn

These control how a link renders when shared, not how it ranks.

Title length is outside the usual range

warn

14 characters. This is a recommendation about how results are rendered, not a ranking claim.

  • Example Domain

Title present

pass

The homepage declares a title element.

  • Example Domain

Title uniqueness not checked

unknown

Fewer than three pages were sampled, so uniqueness says nothing yet.

Viewport declared

pass

Mobile rendering depends on this declaration.

GEO readiness

No about, contact or policy pages linked from the homepage

warn

These pages are how both people and models establish who is behind a claim.

AI search crawlers may fetch the homepage

pass

3 AI search crawlers are allowed by robots.txt. A CDN or WAF can still block them at request time β€” robots.txt is only the declared policy.

  • OAI-SearchBot
  • Claude-SearchBot
  • PerplexityBot

No obvious question-and-answer structure

warn

Short, self-contained passages are the parts an assistant can quote without distorting them.

No author or date signals

warn

Assistants weigh statements they can attribute and date more highly than anonymous, undated text.

No paywall or consent wall observed

pass

No gate wording was found in the served text.

No entity markup

warn

Without Organization, Product, Article or similar JSON-LD, a machine has to guess who this page belongs to.

No machine-readable date

warn

Nothing on the homepage states when the content was published or updated.

Declared language is consistent

pass

Language declarations should agree with each other.

No llms.txt

warn

An emerging convention, deliberately weighted low: extractable content matters far more than this file.

Real page served to a plain request

pass

The response was the site itself, not a challenge or verification screen.

Content appears only after JavaScript runs

fail

The served HTML carries 19 words. Assistants that fetch a URL without executing scripts will see an effectively empty page.

No canonical address

warn

A citation needs one address that stays valid.

Training crawler preference, for information

info

Whether model-training crawlers are allowed is a policy choice. It is reported here and has no effect on the score.

  • GPTBot: allowed
  • ClaudeBot: allowed
  • Google-Extended: allowed
  • CCBot: allowed

User-triggered retrieval, for information

info

These fetch a page because a person asked for that page. Reported as a diagnostic and never scored.

  • ChatGPT-User
  • Claude-User
  • Perplexity-User

Is this your domain?

Owner verification, the full report with exact evidence, and paid remediation are being built. For now the free check and this card are the whole product β€” we would rather say that than promise a dashboard that does not exist.

Run the check again

Something wrong here?

Corrections and removals are free and do not require an account. A disputed card leaves the ranking immediately, before anyone reviews it, and personal or non-commercial domains are removed on request without argument.

Request a correction or removal