SEOScrape
Run free audit
Sample report

See what the full AI SEO audit report looks like.

This is a complete, anonymized example for a fictional SaaS site (acme-saas.com). Same shape as a real audit: overall score, category breakdown, top issues, per-page findings, and a prioritized fix list.

seoscrape.com/report/acme-saas-com
66/ 100

Overall score

Average — fixable in a week

SEO71AI readiness52Structure78

Category scores

Crawlability
86
Technical SEO
70
Content clarity
49
AI readiness
41
Structured data
62

Top issues

  • criticalHomepage does not state who the product is for or what category it sells
  • highGPTBot, ClaudeBot and PerplexityBot disallowed in robots.txt — no AI citations possible
  • highSix product pages share the same meta description
  • mediumFAQ schema missing on pricing page (4 visible Q&A entries)
  • mediumArticle schema on blog posts has no datePublished or author
Every issue, explained

The full report opens every issue. Here are five examples.

Each issue includes evidence from your site, a plain-language explanation of why it matters, a concrete fix, and an estimate of how much it would lift the score.

criticalContent clarityLow effort · ~30 min

Homepage does not state who the product is for or what category it sells

Evidence

Hero headline: 'Grow faster with confidence.' Subhead: 'A better way for modern businesses.' Neither names the audience, the category, nor the outcome.

Why it matters

Search engines and AI engines cannot match this page to a query because no specific audience, product category, or outcome is named. A page that could be about anything matches no specific intent.

Recommended fix

Rewrite the hero in this shape: '[Product category] for [specific audience] who want to [specific outcome].' Example: 'Booking software for local tour operators who want to cut admin time by 40%.'

Estimated score impact

+12 overall, +18 content clarity, +9 AI readiness

highCrawlability & indexabilityLow effort · ~30 min

GPTBot, ClaudeBot and PerplexityBot disallowed in robots.txt — no AI citations possible

Evidence

robots.txt at /robots.txt contains: User-agent: GPTBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: PerplexityBot Disallow: /

Why it matters

AI answer engines respect robots.txt. While these directives are in place, your pages will never be cited in ChatGPT, Claude, or Perplexity answers — even when a user asks a question your site answers perfectly.

Recommended fix

Remove the AI crawler disallows unless you have a deliberate IP-protection reason to block them. Add explicit allow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and CCBot.

Estimated score impact

+14 AI readiness, +6 crawlability

highMetadata qualityMedium effort · ~2 hours

Six product pages share the same meta description

Evidence

Meta description on /products/a, /products/b, /products/c, /products/d, /products/e, /products/f is identical: 'Premium solutions for modern businesses.'

Why it matters

Duplicate meta descriptions signal to Google that pages are interchangeable, which leads to deduplication and lost rankings. They also collapse social shares into identical-looking cards.

Recommended fix

Write a unique 140–160 character description per product page. Lead with the specific benefit, follow with the proof, end with the action. Treat the description as the ad for that page.

Estimated score impact

+8 metadata quality, +3 overall

mediumStructured dataLow effort · ~30 min

FAQ schema missing on pricing page (4 visible Q&A entries)

Evidence

The /pricing page renders 4 visible question-answer pairs in an accordion, but the page source contains no FAQPage JSON-LD.

Why it matters

FAQ schema turns plain Q&A blocks into rich results that take additional SERP space and lift CTR. It also gives AI answer engines a clean unit to extract.

Recommended fix

Add FAQPage JSON-LD to /pricing with mainEntity entries that exactly match the visible question and answer text. Validate in Google Rich Results Test.

Estimated score impact

+6 structured data, +2 AI readiness

mediumStructured dataMedium effort · ~2 hours

Article schema on blog posts has no datePublished or author

Evidence

Article JSON-LD on /blog/* contains headline + mainEntityOfPage, but no datePublished, dateModified, or author fields.

Why it matters

Missing date fields weaken freshness signals. A missing author Person entity gives Google no expertise signal to attribute the article to.

Recommended fix

Add datePublished, dateModified, and author (Person with name, url, sameAs) to every Article block. Verify the visible byline on the page matches the author entity in JSON-LD.

Estimated score impact

+5 structured data, +3 entity signals

Per-page findings

The paid report scans your top pages individually.

On the full report we expand to your top 10 pages with page-specific findings — the issue that hurts your homepage often is not the one hurting your pricing page.

  • / (homepage)Hero copy fails the 5-second clarity test (no audience, no category, no outcome)critical
  • /pricingFAQ schema missing; pricing copy uses 'starting at' language without anchorhigh
  • /products/[slug]Identical meta description across 6 product pageshigh
  • /blog/[slug]Article schema present but missing datePublished + author Personmedium
  • /aboutNo Person schema for founder; only 'we' pronouns in body — entity signals weakmedium

Want your own report?

Free audit returns your real score in about a minute. If the breakdown is worth the $9.99, unlock the full report from there.