Example result

Wraycroft Creamery, before the repairs: 3 verified problems

This is the EdenLens free check, run on an invented business and published as it came out, so you can read a whole result without running one. Checked 6 October 2026; 10 of 40 criteria read from one page, robots.txt and the sitemap.

An invented business. The result is the engine's own output for its fixture page; the domain is a display name. It is not a client.

Run the same check on your site

The quick check found 3 verified problems.

Each one is computed from your own site and cites the evidence it rests on.

  1. AI answer crawlers blocked (OAI-SearchBot, PerplexityBot)

    robots.txt blocks OAI-SearchBot, PerplexityBot. Assistants that respect these rules cannot fetch this site to cite it, whatever the content quality. robots.txt also names GPTBot, which govern training corpora rather than live citation. That is a documented choice, not a fault, and it does not affect this gate.

    Evidence EV-022, EV-026, EV-027

    The repair, step by step ›

  2. No machine-readable business identity

    The homepage carries no Organization or LocalBusiness node. Search and AI systems have no machine-readable statement of who this business is, where it is or how to reach it, so they must infer it from the page text or from what third parties say. A telephone number is published on the page (01632 960142, found in page text), but nothing marks it as belonging to this business, so a machine can read the digits without knowing whose they are.

    Evidence EV-033, EV-034, EV-035

    The repair, step by step ›

  3. No XML sitemap

    The sitemap request answered HTTP 404. Search engines can still crawl the site, but discovery of new and changed pages is slower and less complete.

    Evidence EV-006

    The repair, step by step ›

Four foundations

Each one is a gate: if it fails, nothing downstream can work, however good the page is.

  • Pass The site is served securely

    The homepage loads over HTTPS and plain http requests are redirected to it.

    Evidence EV-031, EV-032

  • Pass Search engines can reach and index the site

    The homepage answers with HTTP 200, carries no noindex directive, and robots.txt does not block Googlebot or Bingbot.

    Evidence EV-001, EV-019

  • Fail AI assistants are allowed to read the site

    robots.txt blocks OAI-SearchBot, PerplexityBot. Assistants that respect these rules cannot fetch this site to cite it, whatever the content quality. robots.txt also names GPTBot, which govern training corpora rather than live citation. That is a documented choice, not a fault, and it does not affect this gate.

    Evidence EV-022, EV-026, EV-027

  • Pass Content is readable without running JavaScript

    The initial HTML carries 224 visible words, so crawlers that do not execute JavaScript still see the content.

    Evidence EV-002

Who machines think this is

Fail The homepage carries no Organization or LocalBusiness node. Search and AI systems have no machine-readable statement of who this business is, where it is or how to reach it, so they must infer it from the page text or from what third parties say. A telephone number is published on the page (01632 960142, found in page text), but nothing marks it as belonging to this business, so a machine can read the digits without knowing whose they are.

Evidence EV-033, EV-034, EV-035

Three readiness readings

Each reading is its signals counted against the number tested. There is no band, no total and no percentage; the count is the result.

SEO: 3 of 5

Can search engines find, fetch and file these pages?

  • Yes the pages can be indexed
  • No a sitemap lists more than the homepage
  • Yes a canonical URL points at this site
  • Yes the title says which page and which business this is
  • No the description says something the title does not

Evidence EV-004, EV-012

AEO: 3 of 4

Can a clear answer be lifted from this page?

  • Yes one clear top-level heading names the page
  • Yes enough section headings for a machine to lift one part
  • No the description offers an answer, not a greeting
  • Yes facts are in text, not locked inside images

Evidence EV-037, EV-038, EV-018

GEO: 0 of 4

Can an assistant identify this business and corroborate it?

  • No the crawlers that fetch pages for answers are allowed
  • No a business node identifies the organisation
  • No that node carries the facts an answer needs
  • No declared profiles connect the business to where else it appears

Evidence EV-033, EV-034, EV-022

What this check could not see

  • Site-wide consistency beyond the homepage
  • Whether pages answer the questions customers actually ask
  • Whether the business identity agrees across the registers, maps and profiles where it appears
  • Whether search engines and assistants actually reach the site, which needs server logs
  • Whether assistants mention or cite the business today

This free check reads one page, robots.txt and the sitemap. It reports readiness signals only and does not measure live visibility in AI answers. Anything it could not see is left unassessed, never counted as a failure.

Evidence appendix (46 facts)
IdFactValue
EV-001HTTP status of the public homepage fetch200
EV-002Visible words in initial HTML (pre-JavaScript)224
EV-003JSON-LD @types parsed from initial HTMLnone
EV-004Canonical link declaredhttps://wraycroftcreamery.co.uk/
EV-005robots.txt HTTP status200
EV-006XML sitemap HTTP status404
EV-007Business name as discoveredWraycroft Creamery
EV-008Postal address as discoverednone
EV-009Telephone as discovered01632 960142
EV-010Description/category as discoverednone
EV-011Facebook profile linked from page linkhttps://www.facebook.com/yourpage
EV-012Page <title> text and lengthWraycroft Creamery (18 chars)
EV-013Meta description present and lengthno
EV-014H1 headings found on the pageWelcome to Wraycroft Creamery
EV-015Viewport meta tag present (mobile readiness signal)yes
EV-016Open Graph title/description presentno
EV-017Hreflang alternates declaredno
EV-018Image alt-text coverageno <img> elements in initial HTML
EV-019noindex directive present in initial HTMLno
EV-020robots.txt names Googlebotnot named (wildcard rules apply)
EV-021robots.txt names Bingbotnot named (wildcard rules apply)
EV-022robots.txt names OAI-SearchBotDisallow: /
EV-023robots.txt names ChatGPT-Usernot named (wildcard rules apply)
EV-024robots.txt names ClaudeBotnot named (wildcard rules apply)
EV-025robots.txt names Claude-Usernot named (wildcard rules apply)
EV-026robots.txt names PerplexityBotDisallow: /
EV-027robots.txt names GPTBotDisallow: /
EV-028robots.txt names Google-Extendednot named (wildcard rules apply)
EV-029robots.txt names CCBotnot named (wildcard rules apply)
EV-030Wildcard 'Disallow: /' blocking all agentsno
EV-031Homepage served over HTTPSyes
EV-032Plain http request redirects to httpsyes (HTTP 301)
EV-033Organization or LocalBusiness node in structured datano
EV-034Identity fields present on the business nodeno business node
EV-035Required identity fields missing from the business nodename, address, contact, url
EV-036sameAs profile links declared in structured datano
EV-037Level-one headings in the initial HTMLWelcome to Wraycroft Creamery
EV-038Section headings (h2, h3) outside navigation3
EV-039Meta description textno
EV-040Email address as discoverednone
EV-041robots.txt names Claude-SearchBotnot named (wildcard rules apply)
EV-042robots.txt names Perplexity-Usernot named (wildcard rules apply)
EV-043robots.txt names Applebot-Extendednot named (wildcard rules apply)
EV-044Share title (og:title)none
EV-045Share description (og:description)none
EV-046Share picture (og:image)none

The other examples

How the free audit works · The fix library · The method