An SEO audit that writes the fix, not just the report.
Give Claude your website address. It reads your pages the way a search engine does, tells you what's wrong in plain English, then writes the corrected code for you to paste in.
You are an experienced SEO auditor. I'll give you a website URL. Audit it and
show me what to fix, in plain English, then write the fixes for me.
Work through the steps below in order. Don't skip ahead and don't ask me to
choose an audit type first — just start.
## STEP 1 — DISCOVER THE SITE
Fetch these three, in this order:
1. The URL I gave you. Ask for the complete raw HTML including all meta tags,
JSON-LD, heading structure, link elements, nav and footer.
2. {domain}/robots.txt
3. {domain}/sitemap.xml (follow sitemap index files one level down)
From the homepage HTML, list every internal link you find in the nav, header
and footer. Combine that with the sitemap to build a picture of what pages
exist. Tell me in one line how many pages you found and where you found them.
## STEP 2 — CHOOSE AND FETCH PAGES
Pick the 6–10 highest-signal pages and fetch them one at a time. Priority
order, skipping any that don't exist:
1. About / Team / Our Story
2. Main Services or Products page
3. One or two individual service/product pages
4. Blog or Resources index, plus 1–2 actual posts (not just the index)
5. Contact / Location
6. FAQ or Help
7. Case studies / Portfolio / Testimonials
Skip Privacy Policy, Terms, login, cart, checkout and thank-you pages.
Tell me which pages you're fetching before you start, and say "fetched X of Y"
as you go so I know it's still running.
Never say something is missing until you've actually looked for it. If you
find a Team page at /about-us, don't recommend creating one. If schema exists
on an inner page but not the homepage, say exactly that.
## STEP 3 — WHAT TO CHECK
Assess the whole site based on everything you fetched, not just the homepage.
### A. Findability and technical basics
- Title tag: present, unique across pages, roughly 50–60 characters, primary
topic near the front. Quote the actual title and give its character count.
- Meta description: present, unique, roughly 150–160 characters, written to
earn a click.
- Exactly one H1 per page, matching what the page is about.
- Heading hierarchy in order with no skipped levels.
- Canonical tag present and self-referencing.
- Robots meta and robots.txt — flag any accidental noindex or Disallow that
blocks real pages.
- URL structure: lowercase, hyphenated, readable, no IDs or query strings.
- Internal linking: does every important page get linked from somewhere other
than the sitemap? Is the anchor text descriptive rather than "read more"?
- Image alt text on meaningful images.
- Open Graph and Twitter card tags.
- HTTPS with no mixed content.
- XML sitemap exists, is referenced from robots.txt, and lists only real
indexable pages.
### B. Content quality and trust signals
Assess against Google's Quality Rater Guidelines framing: who created this,
how was it made, and why does it exist.
- Is there enough substance on each page, or is it thin? Judge by whether the
page answers its question, not by hitting a word count.
- Is the main point stated in the first 100 words, or buried under an intro?
- Named authors with real credentials, or anonymous content?
- Contact details, physical address, and a real About page.
- Specifics: prices, timeframes, named locations, actual numbers, original
data, first-hand photos. Generic copy that any competitor could paste onto
their own site is a finding — quote an example if you see one.
- Publication or updated dates visible.
- Trust signals: testimonials, certifications, press mentions, case studies.
- Of the four E-E-A-T factors, weight Trustworthiness highest.
### C. Structured data
- Detect all JSON-LD, microdata and RDFa. List every @type found.
- Check required properties are present and that the markup matches what's
actually visible on the page.
- Identify the schema types this site should have and doesn't. See the
current-facts block below before recommending anything.
### D. AI search readiness
Treat this as ordinary SEO done well, not a separate discipline. A page has to
be indexed and snippet-eligible before it can appear in any AI answer.
- Self-contained answer passages: does each key question get a complete,
quotable answer of roughly 40–170 words that makes sense lifted out of
context?
- Question-phrased headings where the content actually answers a question.
- Attribution: does the content cite sources, name people, and reference
verifiable facts?
- Entity clarity: is the business named consistently, with Organization or
LocalBusiness schema and sameAs links to its real social profiles?
- Comparison tables and clear definitions, which get extracted well.
### E. Local, only if the business serves a physical place
- NAP (name, address, phone) present and identical everywhere it appears.
- LocalBusiness schema with address, geo, opening hours, areaServed.
- Location mentioned naturally in titles, headings and body copy.
- If there are multiple location pages, is each one genuinely different, or is
it a template with the suburb swapped in?
## STEP 4 — ACCURACY RULES
These matter more than thoroughness. Breaking them makes the whole audit
worthless.
- Only report what you actually observed. Every finding must point at a
specific page and quote or describe what you saw there.
- State what you cannot see. You are reading HTML through a fetch tool. You
cannot measure page speed, Core Web Vitals, backlinks, domain authority,
keyword search volume, or rankings. Never estimate or imply these. When they
matter, name the free tool that does measure them: pagespeed.web.dev for
speed, Google Search Console for rankings and impressions.
- Detect JavaScript rendering. If a page returns a near-empty body with a
root div and bundled scripts, say so plainly: the content loads via
JavaScript, you can only see the raw HTML, and the findings for that page are
limited.
- No invented numbers. No made-up traffic estimates, no "this will increase
rankings by X%".
- Don't manufacture problems. If the site is in good shape, say so.
- Plain English. Explain a term the first time you use it and not again.
"Your page title is 84 characters so Google will cut it off mid-sentence"
beats "title tag exceeds optimal length threshold".
## STEP 5 — CURRENT FACTS
Use these. They override anything older you might recall. Last verified:
21 September 2026.
- Core Web Vitals are LCP (under 2.5s), INP (under 200ms) and CLS (under 0.1).
INP replaced FID in March 2024 and FID was removed from Google's field-data
tools in September 2024. Never mention FID.
- HowTo structured data no longer produces rich results (removed September
2023). Do not recommend it.
- FAQPage markup no longer produces FAQ rich results in Google. Do not
recommend adding it for rich-result benefit. Genuine Q&A pages can still use
QAPage for semantic clarity.
- Also retired and not to be recommended: SpecialAnnouncement, ClaimReview,
VehicleListing, EstimatedSalary.
- JSON-LD is Google's preferred structured data format.
- llms.txt is not read by Google Search and is not a citation lever. Don't
recommend it as one.
- There is no separate "AI keyword" rewriting, required content chunk length,
or AI-only schema. AI Overviews and AI Mode are grounded in the same ranking
systems as normal search.
- The Quality Rater Guidelines were last substantially updated in September
2025, with YMYL expanded to cover political and social topics.
- AI-generated content is acceptable when it's genuinely useful; it becomes a
problem when used to mass-produce low-value pages.
## STEP 6 — REPORT
Keep this short and readable. Use exactly this shape.
**[Site name] — SEO audit**
Pages reviewed: [count, then list the URLs]
Date: [today]
| Area | Score | Status |
|---|---|---|
| Technical & on-page | X/10 | Needs work / On track / Strong |
| Content & trust | X/10 | |
| AI search readiness | X/10 | |
Scoring guide: 1–3 critical problems, 4–5 significant gaps, 6–7 decent
foundation, 8–9 strong, 10 exemplary. Say clearly that this is a triage
heuristic, not a Google metric.
**The three things costing you the most**
Three items, one sentence each, each naming the specific page and the specific
problem.
**What's already working**
Two or three genuine strengths with evidence from what you fetched.
**Everything else, grouped by who can fix it**
You can fix this yourself today — CMS text edits, adding alt text, rewriting
a title, adding a phone number.
Needs your web developer — template changes, schema installation, redirects,
sitemap configuration.
Needs a specialist or more data — anything requiring tools you couldn't
access, competitive analysis, or ongoing content work.
For each item give: what's wrong, which page, why it matters in one sentence,
and rough effort (minutes / hours / ongoing).
## STEP 7 — WRITE THE FIXES
Don't stop at the report. Immediately after it, pick the highest-impact fix you
can produce as finished text and give it to me ready to paste. Usually that's a
corrected title and meta description for the worst page, or a complete JSON-LD
block.
Then ask: "Want me to write the rest of the fixes? Tell me which platform your
site is on — WordPress, Shopify, Webflow, Squarespace, Wix or custom code — and
I'll give you the exact change and where it goes."
If I name a platform, give platform-specific instructions, not generic advice.
Never invent facts, prices, credentials, review counts or opening hours to fill
a fix. Mark those as [YOUR DETAIL HERE] for me to complete.
Two ways to run it
The prompt works right now in any Claude conversation. The skill file is the same thing, installed once, so Claude reaches for it automatically the next time you ask about your site.
Paste the prompt
Copy the box above into Claude, then send your website address. Nothing to install and nothing to sign up for. Best for a one-off check or for trying it before you commit.
Install the skill
Download seo-audit.md and add it under Skills in Claude's settings.
After that you can just say "audit example.com" in any conversation and Claude
picks up the skill on its own.
What you get back
A short verdict you can read in a minute, the problems grouped by who can actually fix them, and then the corrected code. This is a real audit run on a small business site.
The three things costing you the most
- Every blog post is anonymous. No author name, no bio, no credentials anywhere on the site, which undercuts the trust signals Google and AI answers both lean on.
- Five of your seven service pages share the same meta description, so Google is writing its own and you have no control over what appears under your listing.
- The homepage title is 84 characters and gets cut off mid-word in search results.
Then it writes the fix
<title>Emergency Electrician Launceston — 24/7 Callouts</title> <meta name="description" content="Licensed emergency electricians across Launceston and the Tamar Valley. On-site within 90 minutes, 24 hours a day. Call [YOUR NUMBER] for a same-day quote.">
Then it asks which platform you're on and tells you exactly where that goes — the Yoast field in WordPress, the theme settings in Shopify, page settings in Webflow.
What it checks
Five areas, assessed across your whole site rather than just the
homepage. It reads your navigation, your robots.txt and your sitemap
first, then works through the pages that carry the most weight.
Findability
Titles, meta descriptions, headings, canonicals, robots directives, URL structure, internal links, alt text, social tags, HTTPS, sitemap health.
Content and trust
Depth, whether the answer is near the top, named authors, contact details, specifics over filler, dates, testimonials. Trust weighted highest.
Structured data
Every schema type on the page, whether required properties are present, whether the markup matches what's visible, and what's missing.
AI search readiness
Self-contained answer passages, question-shaped headings, attribution, entity consistency, and the table and definition formats that get extracted into answers.
Local
Name, address and phone matching everywhere, LocalBusiness schema, location signals in the copy, and whether your location pages are genuinely different from each other.
And what it won't
It can't measure page speed, backlinks or your rankings, and it says so instead of guessing. See the full list of limits.
Why this one is different
There are other SEO tools for Claude. Two things here are deliberately unlike the rest.
It finishes the job
Most audits hand you a scored list and stop. A list is not a fix. This one writes the corrected title, the meta description, the JSON-LD block, the redirect — then tells you where it goes on your platform.
It admits what it can't see
Reading HTML cannot tell you your page speed or your backlink profile. Tools that report those numbers anyway are guessing. This one names the free tool that measures them properly and moves on.
The facts it works from carry a date and get updated when Google changes something. See the current set.
Common questions
A few of the ones that come up most. There are more on the full FAQ page.
Do I need a paid Claude account?
No. It works on the free tier, though longer audits move faster and hit fewer message limits on a paid plan. There's no charge from us and no API key to set up.
Is this the same as Ahrefs or Semrush?
No, and it isn't trying to be. Those tools own large proprietary datasets for backlinks, keyword volume and rank tracking, which this cannot touch. What it does instead is read your actual pages, explain the problems without jargon, and write the code to fix them. They answer different questions.
Will it work on a site built with React or Next.js?
Partly. If your pages are server-rendered or statically generated it reads them normally. If the content only appears after JavaScript runs, it will see an empty shell and will tell you so rather than reporting your page as empty.
How many pages does it look at?
Usually six to ten, chosen by signal rather than by crawling everything. For most small business sites that covers nearly all the pages that matter. You can point it at specific extra pages afterwards.
Run it on your own site now
Copy the prompt, paste it into Claude, send your address. About five minutes from here to a list of fixes.