gaflow

AI Visibility Blueprint

example-client.com · measured 2026-08-25

This is a real report. It was produced by the same checks you would receive, against a live site, on the date shown. The only thing changed is the client's domain name. Nothing here is a mock-up — an invented sample would be exactly the kind of thing this audit exists to catch.
17
Effectively invisible
out of 100 · 6 checks

What we checked

NEEDS WORKAI crawler access

robots.txt returns 200 but is not text/plain (got "text/html"). Crawlers may not parse it.

FAILSitemap

No valid sitemap.xml. Assistants and search crawlers have no map of your pages.

FAILMachine-readable business facts

No JSON-LD structured data on the homepage. Assistants have to guess your name, location and services from prose.

NEEDS WORKQuotable content structure

1 H1 and 0 H2 headings. Assistants quote well-sectioned pages; flat pages get summarised away.

FAILTitle and description

No meta description.

FAILIndexable

Homepage sends "noindex,follow" — it is asking to be excluded entirely.

Your fix list, in priority order

  1. P1
    Serve robots.txt as text/plain. Right now it returns a page, which crawlers cannot read as rules.
  2. P1
    Add Organization or LocalBusiness JSON-LD with name, address, phone, hours, and areaServed.
  3. P1
    Remove the noindex meta tag from the homepage. Nothing else matters while it is there.
  4. P2
    Publish a valid sitemap.xml and reference it from robots.txt.
  5. P2
    Add a descriptive <title> and meta description naming the service and the place you serve.
  6. P3
    Use exactly one H1 and break the page into H2 sections that answer a real question each.
  7. P3
    Add FAQPage schema — question/answer pairs are the format assistants quote most directly.

Evidence

robots.txt  HTTP 200
sitemap.xml HTTP 200
JSON-LD blocks found: 0
JSON-LD types: none