Sample report

A real audit report, run on a demonstration site.

Our audit engine produced this report for Brightwater Plumbing Co., a made-up business on a demonstration site we built for this purpose. The scores, findings and fixes below are the report's own words, unchanged. Your report covers your website the same way.

  • 39 checks ran on this site
  • 14 fails, 4 warnings, 20 passes, 1 unknown
  • One-time payment, no subscription

This is a sample. Brightwater Plumbing Co. is not a real business, and its website exists only so the audit has something to read. It is hidden from search engines on purpose, which is why the report fails it on indexing. The report you buy is a PDF, and a link to it is emailed to you; this one was 24 pages.

01 / Overview

Score summary

Brightwater Plumbing Co. (demonstration site)

49/ 100Overall score
69SEO
16Maps SEO
55AEO

Each check is weighted by how much it matters. A pass earns its full weight, a warning half, a fail none. Unknown checks and checks this version does not run are left out of the score. The overall score is SEO 40%, Maps SEO 30% and AEO 30%; if a whole section has no usable data, its share is spread across the others. The lab speed test (SEO-16) and the page-weight check (SEO-19) count inside SEO only; the speed page shows the lab detail.

AEO readiness

AEO readiness from on-site signals only (structured data, robots AI-bot rules, llms.txt, FAQ heuristics). 6 pass / 3 warn / 4 fail / 0 unknown among AEO checks that ran. No live answer-engine probes in this report version.

How to read your scores

Scores are out of 100 and only count checks that ran on your public pages. If a check couldn't get the data it needs, it's marked unknown and left out of the score, never guessed. Checks this version doesn't run are listed under Not checked.

02 / Findings

Findings per check

Each finding shows the record the audit made on the page (the evidence), why the check matters and what to change.

14 checks failed

MAPS-04 / MAPS SEOFail

Service-area page setup

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"pages":[],"linkedFromHome":false}

Why it matters

You should have a clear service-area page that is linked from the main navigation or footer.

The fix

No service-area page showed up. Ask your web person to publish a clear service-area page and link it from the main navigation or footer.

AEO-02 / AEOFail

FAQPage markup

Evidence

{"faqPageBlocks":0}

Why it matters

FAQ markup should match the questions people can already read on the page.

The fix

Add FAQPage JSON-LD that mirrors the visible FAQ text. Ask your web person to generate valid Question/Answer markup from the on-page FAQ — not placeholder content.

MAPS-02 / MAPS SEOFail

Maps / profile link on site

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"urls":[]}

Why it matters

The site should link to your Google Business Profile or Maps place so people can confirm it is you.

The fix

No Google Business Profile or Maps place link/embed showed up. Ask your web person to add a clear link (or official Maps embed) on the homepage or contact page so people can confirm the profile is yours.

MAPS-03 / MAPS SEOFail

On-site review signals

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"aggregateOrReviewSchema":false,"widgetHint":false,"testimonials":0}

Why it matters

Shoppers should see real review proof on the site — a widget, named testimonials, or review markup.

The fix

No on-site review proof showed up. Ask your web person to add a review widget, named testimonials, or valid review/rating markup — with attribution, not anonymous praise.

SEO-11 / SEOFail

Indexability signals

Evidence

{"metaRobots":"noindex, nofollow","xRobotsTag":"noindex, nofollow"}

Why it matters

Your homepage must allow search engines to index it.

The fix

The homepage is marked noindex. Ask your web person to remove noindex from the meta robots tag and any X-Robots-Tag header on that page so search can include it.

AEO-04 / AEOFail

Organization identifying fields

Evidence

{"organization":false}

Why it matters

Business markup should clearly identify your name and site (and ideally phone or known profiles).

The fix

Organization markup is missing. Ask your web person to add Organization JSON-LD with your official name and site URL (and phone or known profile links when you have them).

MAPS-05 / MAPS SEOFail

Organization phone/address schema

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"organization":false}

Why it matters

Business markup should include your phone and address fields so machines can match your entity.

The fix

Organization markup is missing phone and address fields. Ask your web person to add telephone and postal address properties to your Organization JSON-LD.

SEO-06 / SEOFail

Title presence

Evidence

{"count":1,"length":4}

Why it matters

Your page title should name the business and trade without being cut off or empty in search snippets.

The fix

The homepage title is missing, empty, or far outside a useful length. Ask your web person to set one title that names the business and the trade in plain language.

SEO-15 / SEOFail

Structured data

Evidence

{"blocks":0,"parseErrors":0,"relevantTypes":[]}

Why it matters

Machine-readable business markup helps search and answer engines understand who you are and what you offer.

The fix

No usable business structured data showed up. Ask your web person to add valid JSON-LD for your organization and, where it fits, your services or FAQs.

AEO-12 / AEOFail

Entity name clarity

Evidence

{"title":true,"h1":true,"orgName":null}

Why it matters

Your business name should match across the title, main headline, and business markup.

The fix

The business name disagrees across the title, main headline, and Organization markup. Ask your web person to use one official name in all three places.

SEO-05 / SEOFail

Canonical hints

Evidence

{"canonicals":[]}

Why it matters

We check that the page points crawlers at one preferred URL.

The fix

Add one absolute canonical link tag on the homepage that points at the preferred URL, and remove duplicates. Ask your web person to set this in the page head.

AEO-11 / AEOFail

llms.txt presence

Evidence

{"status":404}

Why it matters

An llms.txt file helps AI agents find the useful pages on your site (proposal: https://llmstxt.org/).

The fix

Add an `/llms.txt` file at the site root with a markdown H1 naming the business and links to useful pages. Ask your web person to follow the llms.txt proposal: https://llmstxt.org/

SEO-07 / SEOFail

Meta description

Evidence

{"count":0,"length":0}

Why it matters

Your meta description should give search a clear, readable summary — not blank and not a wall of text.

The fix

Add a meta description on the homepage. Ask your web person to write one clear sentence about who you help and what you do.

SEO-13 / SEOFail

Image alt text

Evidence

{"sampled":1,"withAlt":0}

Why it matters

Important photos should include text descriptions so assistive tech and crawlers understand them.

The fix

Most sampled images are missing alt text. Ask your web person to add short descriptions to important photos (trucks, crews, finished jobs).

4 warnings

AEO-01 / AEOWarn

Visible FAQ content

Evidence

{"pairs":2,"sources":{"home":true,"faqPage":false}}

Why it matters

Your site should answer common homeowner questions in plain FAQ form.

The fix

Only a thin FAQ showed up. Ask your web person to expand it with more common questions (pricing ranges, timelines, what you handle) in plain language.

AEO-03 / AEOWarn

Service schema

Evidence

{"serviceSchema":0,"htmlServicesHint":true}

Why it matters

Machines should be able to read what services you offer.

The fix

Services appear in plain HTML only, or markup is incomplete. Ask your web person to add named Service structured data that matches the services you sell.

AEO-13 / AEOWarn

Citation-worthy facts

Evidence

{"citeableCandidates":1,"vagueOnly":0,"note":"Heuristic only; accuracy not verified"}

Why it matters

Prefer concrete, citeable facts on the page over vague superlatives. We do not fact-check accuracy in this report.

The fix

Only a couple of citeable facts showed up. Ask your web person to add a few more concrete, specific statements buyers and answer engines can quote.

MAPS-06 / MAPS SEOWarn

Click-to-call tel links

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"telLinks":[]}

Why it matters

Your phone number should be tappable on phones.

The fix

A phone number appears as plain text only. Ask your web person to make it a `tel:` link so callers can tap it on phones.

20 checks passed and 1 could not be read: show them

SEO-16 / SEOPass

Lab speed test (mobile)

Evidence

{"source":"Lighthouse CLI mobile lab","lcpMs":808,"cls":0,"tbtMs":3,"bands":{"lcp":"good","cls":"good","tbt":"good"},"note":"Lab speed test (mobile Lighthouse lab). INP needs real-user / field data; lab uses Total Blocking Time (TBT) as a stand-in. Not PageSpeed Insights or CrUX. Not real-user performance data.","citations":["https://developers.google.com/search/docs/appearance/core-web-vitals","https://developers.google.com/speed/docs/insights/v5/about"]}

Why it matters

We run a lab speed test on our machines with a phone preset (Lighthouse lab). We report lab load, layout stability, and how long the page stays busy (LCP, CLS, and Total Blocking Time). INP needs real-user / field data, so this lab speed test does not measure INP. This is not real-user performance data. Failures mean the lab run looked too slow on phones, jumpy while loading, or busy for too long.

The fix

No change required for this check based on what we could measure.

SEO-03 / SEOPass

Homepage HTTP status

Evidence

{"status":200,"redirects":0,"chain":[{"url":"https://rt-demo-site.vercel.app/","status":200}]}

Why it matters

Your homepage should load cleanly without a long bounce through redirects.

The fix

No change required for this check based on what we could measure.

AEO-06 / AEOPass

Concise answer blocks

Evidence

{"questions":2,"withAnswer":2,"concise":2}

Why it matters

Under each question, lead with a short direct answer before the longer explanation.

The fix

No change required for this check based on what we could measure.

SEO-01 / SEOPass

Robots access

Evidence

{"status":200,"sitemapCount":1,"groups":1}

Why it matters

We look for a working robots file that tells crawlers what they may read.

The fix

No change required for this check based on what we could measure.

SEO-02 / SEOPass

XML sitemap

Evidence

{"linked":true,"url":"https://rt-demo-site.vercel.app/sitemap.xml","isUrlset":true,"isIndex":false,"urlCount":4}

Why it matters

We check whether your site publishes a sitemap so crawlers can find your pages.

The fix

No change required for this check based on what we could measure.

SEO-04 / SEOPass

HTTPS preferred host

Evidence

{"protocol":"https:","mixedContentHints":0}

Why it matters

Your main site address should load securely (padlock / HTTPS).

The fix

No change required for this check based on what we could measure.

AEO-05 / AEOPass

Question-shaped headings

Evidence

{"questionHeadings":2,"samples":["What we do","Why people choose us"]}

Why it matters

Some headings should read like real questions homeowners ask.

The fix

No change required for this check based on what we could measure.

AEO-07 / AEOPass

GPTBot robots stance

Evidence

{"bot":"GPTBot","stance":"none"}

Why it matters

Your robots file should not blanket-block OpenAI’s GPTBot if you want that crawler to read the site.

The fix

No change required for this check based on what we could measure.

AEO-08 / AEOPass

OAI-SearchBot robots stance

Evidence

{"bot":"OAI-SearchBot","stance":"none"}

Why it matters

Your robots file should not blanket-block OpenAI’s search crawler (OAI-SearchBot).

The fix

No change required for this check based on what we could measure.

AEO-09 / AEOPass

PerplexityBot robots stance

Evidence

{"bot":"PerplexityBot","stance":"none"}

Why it matters

Your robots file should not blanket-block PerplexityBot if you want to appear in that product’s results.

The fix

No change required for this check based on what we could measure.

SEO-08 / SEOPass

Single clear H1

Evidence

{"count":1,"sample":["Plumbing done right"]}

Why it matters

The homepage needs one clear main headline that states what you do.

The fix

No change required for this check based on what we could measure.

SEO-12 / SEOPass

Internal links to key paths

Evidence

{"sameHostLinks":9,"contactish":2}

Why it matters

Visitors should be able to reach a contact or quote path from the homepage.

The fix

No change required for this check based on what we could measure.

SEO-14 / SEOPass

Homepage substance

Evidence

{"visibleChars":849}

Why it matters

The homepage needs real substance — not just a logo and a form.

The fix

No change required for this check based on what we could measure.

SEO-17 / SEOPass

Sitemap URL sample status

Evidence

{"sampled":4,"bad":0,"softRedirects":0}

Why it matters

Pages listed in your sitemap should actually load.

The fix

No change required for this check based on what we could measure.

SEO-19 / SEOPass

Page weight / asset heuristics

Evidence

{"htmlBytes":1591,"blockingScriptsInHead":0,"imgsMissingDimensions":0,"note":"Page-weight heuristics from our fetch — not the lab speed test; not real-user data"}

Why it matters

We check whether the page looks heavy on phones — large page download, oversized images, or scripts that block first paint — using our own fetch. This is a page-weight check from our fetch, not the lab speed test and not real-user data.

The fix

No change required for this check based on what we could measure.

AEO-10 / AEOPass

Google-Extended robots stance

Evidence

{"bot":"Google-Extended","stance":"none"}

Why it matters

We report whether Google-Extended is allowed; this is separate from Google Search ranking.

The fix

No change required for this check based on what we could measure.

MAPS-07 / MAPS SEOPass

Hours on site

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"hoursKind":"grid"}

Why it matters

Publish clear days and hours so callers know when you answer.

The fix

No change required for this check based on what we could measure.

SEO-09 / SEOPass

Heading outline

Evidence

{"h2":2,"h3":1}

Why it matters

The page should break into clear sections so people and answer engines can scan your services.

The fix

No change required for this check based on what we could measure.

SEO-10 / SEOPass

Mobile viewport

Evidence

{"viewport":"width=device-width, initial-scale=1"}

Why it matters

The site should be set up to display correctly on phones.

The fix

No change required for this check based on what we could measure.

SEO-18 / SEOPass

Contact path discoverable

Evidence

{"contactPages":["https://rt-demo-site.vercel.app/contact"],"telOrMailtoOnly":false}

Why it matters

Callers need an obvious path to contact you or request a quote.

The fix

No change required for this check based on what we could measure.

MAPS-01 / MAPS SEOUnknown

On-site NAP consistency

Maps SEO: based on what your website shows. We don’t read your Maps listing.

Evidence

{"surfaces":[{"label":"homepage","phones":[],"address":null,"names":["plumbing done right"]},{"label":"contact","phones":["5550100142"],"address":"100 Example Street","names":["contact"]},{"label":"footer","phones":[],"address":null,"names":[]}],"reason":"too few NAP surfaces"}

Why it matters

Your name, phone, and address line should match wherever they appear on the site.

The fix

We could not verify this check from public data alone. Re-run after the site is reachable, or supply missing public signals.

03 / SEO / SEO-16

SEO / Mobile speed

SEO-16 · Counted once in SEO · Lighthouse · mobile preset
Lab speed test · Not real-user data · TBT stand-in (INP needs field data)

0.808 sLCP PassGood: ≤ 2.5 s
Needs work: > 2.5–4 s
Poor: > 4 s
0CLS PassGood: ≤ 0.10
Needs work: > 0.10–0.25
Poor: > 0.25
3 msTBT PassGood: ≤ 200 ms
Needs work: > 200–600 ms
Poor: > 600 ms

Measurement context

Lab speed test (mobile Lighthouse lab). INP needs real-user / field data; lab uses TBT. No PageSpeed Insights / CrUX. Not real-user performance data.

Why it matters

On phones, a page that's slow to show its main content, jumps around while it loads, or stays busy before it responds loses calls and form fills.

The fix

Start with any metric above marked warn or fail. Compress and size large images, delay scripts the page doesn't need to show its content, and reserve space for images and embeds so the layout stays still. Then run a lab test again.

04 / Scope

Scope & next steps

Prioritized next steps

  1. Fix high-priority failures firstAddress: MAPS-04, AEO-02, MAPS-02, MAPS-03, SEO-11. Confirm the evidence on the live public pages, then re-check.
  2. Tighten warningsReview: AEO-01, AEO-03, AEO-13. These are partial signals, not full passes.
  3. Validate on the public siteAfter changes, confirm the same URLs still load over HTTPS and that machine-readable files remain reachable.

Not checked in this report

  • MAPS-08 Public Places / GBP match — Places API needs key + billing; out of v1 at zero spend
  • MAPS-09 Public review count / rating from Places — same dependency as MAPS-08
  • MAPS-10 Site ↔ profile URL agreement via Places — same dependency as MAPS-08
  • AEO-14 Answer-engine visibility probes — needs spend approval and Legal review

What this report is not

  • Not a guarantee of rankings, traffic, citations, or revenue
  • Not access to your Search Console, analytics, or Maps listing admin
  • Not legal, financial, or professional advice
  • Not real-user performance data (SEO-16 is a lab speed test only when it ran)
  • Not a Places / map-pack ranking report (MAPS-08–10 not checked in v1)

Attribution

This report comes from our own automated checks of your public pages. We fetched your pages, robots.txt, sitemap and llms.txt files, and ran a phone-preset lab speed test with Lighthouse, an open-source tool, on our own machines. We did not use your private accounts or any third-party data service. Naming a tool or company here does not mean it endorses this report.

Website audit

See this for your own website.

One payment, at the price shown at checkout. The report goes to the email you give at checkout.

Get your audit