SEO Audit with Claude

Decide what the audit covers

An audit without a scope grows until it is useless. Pick the pages that matter: the home page, the main service or product pages, and the pages that already bring traffic or should bring traffic. For each page, note its target keyword and the action you want the visitor to take. A page without a target keyword or a purpose is itself a finding.

Gather the basic data before you start: the page text, title, and description, plus any data you already have, such as which pages get visits and which pages never get any. Paste pages into Claude one at a time, or in small groups, so the review stays focused. A giant paste of an entire site produces a vague audit.

Check the technical basics first

Ask Claude to check each page against a short technical list: a unique title that describes the page, a description that matches the content, one main heading, headings in logical order, working internal links, and images with useful descriptions. These basics are unglamorous and they matter, because search engines and visitors both rely on them to understand a page.

Also check for duplicate titles and descriptions across pages, pages that say almost the same thing, and pages that are very thin. Two pages competing for the same keyword split the result between them. In an audit, that overlap is usually more important than any single missing keyword.

Review content against search intent

For each page, ask what a person searching its keyword actually wants. Someone searching a how-to phrase wants steps. Someone searching a service in a town wants to know what is offered, where, and how to book. Compare the page against that intent. If the page answers a different question than the searcher asked, it will struggle no matter how well written it is.

Read the page as a visitor. Is the main answer near the top? Is the next step obvious? Is anything promised that the page does not deliver? Claude can help by summarising the page's argument and listing what it does not cover, which often reveals gaps the author stopped seeing.

Turn findings into a fix list

An audit is only useful if it ends in actions. Group findings by type, then order them by impact and effort: quick fixes that help many pages first, then larger content rewrites, then technical work that needs a developer. Each item needs a page, a problem, and a specific fix. Vague items like improve SEO do not get done. Specific items like rewrite the title of the services page to name the service and town do.

Keep the original findings alongside the fixes. When you re-check in a month, you can see which fixes worked and which problems remain, instead of running a fresh audit from scratch each time.

What Claude cannot audit alone

Claude cannot see your live server settings, your private search analytics, or your backlinks unless you supply that data. It also cannot guarantee rankings, and anyone promising a specific ranking from an audit is selling certainty that does not exist. Use Claude to organise and prioritise, use your own data for the facts, and judge the result by traffic and enquiries over time, not by a single score.

Audit this web page for SEO.
Page URL: [paste the URL]
Target keyword: [keyword]
Visitor goal: [what the visitor should understand or do]

Checklist:
1. Title: is it unique and does it describe the page?
2. Description: does it match the content?
3. Headings: is there one main heading, in logical order?
4. Content: does it answer the search intent for the keyword?
5. Overlap: does it duplicate another page on this site?
6. Next step: is the visitor's next action obvious?

For each issue, give the page section, the problem, and one specific fix.
Order the fixes by impact, highest first.

Page content:
[Paste the page text here]

Frequently asked questions