Tools › Website & AI Search Readiness Audit › Sample report

Sample report: Website & AI Search Readiness Audit

This is a real, unedited run of the free audit (also called the Mega Analyzer) on our own home page, https://jwatte.com/, captured October 20, 2026 with the analyzer version dated 2026-10-20. We use our own site so you can check every finding yourself. The scan took 103 seconds.

Run the same audit on your site

At a glance

481 checks ran on this one page: 146 passed, 1 failed, 1 need a look, and 333 are information only (measured and reported, not scored).

Scores by area

Area	Score
SEO	98
Schema	100
E-E-A-T	100
Voice	not scored
Mobile	not scored
Perf + AI	100

"Not scored" areas (such as voice and the desktop/mobile comparison) are shown in the full report for information and do not change the grade. How every check is weighted: methodology.

What needs attention

Every failing or review item from this run, exactly as the report shows it, with the fix it suggests.

What each tab covered

Tab	Pass	Fail	Review	Info
SEO	105	0	1	219
Schema	4	0	0	15
E-E-A-T	13	0	0	34
Voice	0	0	0	9
Perf + AI	18	0	0	52
A11y (WCAG)	6	1	0	2
Indexing Hygiene	0	0	0	1
Retrieval (AEO)	0	0	0	1

SEO: examples of checks that passed

• Canonical URL set
• HTML lang attribute
• Mobile viewport (WCAG 1.4.4 zoom allowed)
• HTTPS
• Document encoding declaration

Schema: examples of checks that passed

• creator is a typed object, not a bare string
• No HTML-encoded ampersands in sameAs URLs
• No HTML-encoded entities in JSON-LD strings
• Google Business Profile share URL in sameAs

E-E-A-T: examples of checks that passed

• Social links point at real profiles (21 sameAs)
• llms.txt found
• llms-full.txt expansion found
• llms.txt mirror at /.well-known/llms.txt
• dateModified in JSON-LD

Perf + AI: examples of checks that passed

• llms.txt found at root
• llms-full.txt expansion at root
• Optional /.well-known/llms.txt mirror
• robots meta: max-image-preview:large
• Phone / email / ZIP fields open the right mobile keyboard (2)

A11y (WCAG): examples of checks that passed

• HTML lang attribute set: en
• Document title set
• All 13 images have alt attribute
• Heading hierarchy sequential
• All 7 form controls labeled

Information rows

Many rows report what the analyzer measured without grading it, because there is no single right answer (for example word counts, optional agent files, or crawler policies you may want either way). A few from this run:

• Content length and heading inventory: Measured 2525 words, 1 H1 headings and 7 H2 headings. Page purpose and heading semantics matter; no fixed word count or heading quota is required. Learn more: https://jwatte.com/tools/mega-analyzer/ Source:...
• Content length and heading inventory: Measured 2525 words, 1 H1 headings and 7 H2 headings. Page purpose and heading semantics matter; no fixed word count or heading quota is required. Learn more: https://jwatte.com/tools/mega-analyzer/ Source:...
• Indexable: Measured access and indexing choices are owner policy. Review the effect against the intended audience; differing named groups or blank lines do not prove a mistake. Learn more:...
• robots.txt found: Measured access and indexing choices are owner policy. Review the effect against the intended audience; differing named groups or blank lines do not prove a mistake. Learn more:...
• Trusted Types enforcement: Optional Trusted Types directives not declared. Learn more: Review this configuration. Source: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/require-trusted-types-for
• Integrity-Policy enforcement and reporting: Optional emerging Integrity-Policy not declared. Learn more: Review this configuration. Source: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Integrity-Policy
• Cookie flags and SameSite validity: No cookies were set in this anonymous response. JavaScript and post-login cookies were not sampled. Review cookie flags. <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie">Set-Cookie...
• Cookie prefixes and partitioned cookies: No cookies were set in this anonymous response. JavaScript and post-login cookies were not sampled. Review cookie flags. <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie">Set-Cookie...

The fix prompt

Every report ends with a prompt you can paste into Claude, ChatGPT or a coding agent. The start of this run's prompt:

[PERSONA]
You are a senior SEO + content + platform engineer.
Your expertise: SEO, schema.org, E-E-A-T entity modeling, accessibility, Core Web Vitals, crawl validation
Your approach: propose code-exact fixes, group by priority, call out deployment-layer caveats

[STAKES]
This single-URL audit is the blueprint for the next 90 days of fixes. Missing a critical issue means shipped regressions I have to find in production later.

[METHODOLOGY]
Take a deep breath. Work through this step by step:
1. Restate the problem in your own words.
2. Enumerate the constraints and success criteria.
3. Produce the answer.
4. Verify against each constraint before finalizing.

[TASK]
Review this measured page audit. The fix plan uses the actual score weights. Preserve owner-selected indexing, training and access restrictions. Optional adoption, editorial style, Voice and Mobile comparisons earn no points. Unknown evidence is not a defect.

Use each finding's own evidence and learn link. Reuse a reviewed template only within its stated scope. Request missing deployment details before proposing configuration. Do not invent identities, ratings, dates, prices, consumer requirements or score gains. Confirm applicability before changing a policy.

# Mega Analyzer actions

## 1. csp\_header

Resolves: csp\_header

Priority: 1\.5

Estimated gain: 0\.39 overall score points

### Effective Content\-Security\-Policy

1 enforced policy/policies parsed independently; first duplicate directive wins\. 0 inline script\(s\) do not match every enforced policy\. Every policy allows broad script execution; restrict sources with a staged rollout\. Strict nonce/hash, strict\-dynamic, object\-src and base\-uri profile is optional hardening; safe alternatives exist\. Hash and nonce matching does not establish nonce randomness or reuse\. Learn more: Review this configuration\. Source: http\[private reference removed\]

Learn: https://jwatte\.com/tools/csp\-strictness\-audit/

Reviewed template: Content\-Security\-Policy: OWNER\_REVIEWED\_VALUE

Owner\-managed final HTTPS response header configuration Review the policy for this site, configure the final HTTPS response, then repeat this row with complete header evidence\.

## referrer\_policy

State: pass

Source: https://jwatte\.com/

Observed: 2026\-10\-20T05:39:29\.260Z

Scope: page

Priority: Unranked

- Repeat this check with complete evidence afte…

What this report is and is not

• It checks one page and the site files around it (robots.txt, sitemap, llms.txt, security headers, DNS records), using the raw HTML the way most crawlers and AI agents fetch it. It does not run the page's JavaScript.
• It is automated. It points at things to look at; it is not legal, accessibility-compliance or security certification.
• A good grade on one page says nothing about the rest of the site. Run it on your important templates (home, a product or service page, an article).

Next steps

• Run the audit on your own page. Free, no sign-up.
• Get a free weekly email if your site goes down, picks up a noindex, blocks Google or AI crawlers, or its certificate is about to expire.
• Want a person to go through every page and help fix what it finds? Get in touch.