When should you use it?
- You launched a site and never checked how crawlers see it
- Manual audits keep missing things
- You want a fix list in the repo
Not for: Competitive keyword strategy; Sites you do not own
What do you need, and what do you get?
You need
- Running site or local preview
- Browser-control MCP server
- Claude Code in the project folder
You get
- Markdown file of issues and suggested fixes
- Screenshots of problem pages
How does it work, step by step?
- Start the browser serverInstall and run a browser-automation MCP server Claude Code can call.
- Point at the siteGive the URL of the deployed site or local preview.
- Ask for an expert passRequest a full audit covering metadata, headings, links, speed and structured data.
- Save the findingsHave every issue written to a markdown file in the repo.
- Fix in batchesWork through the file, then re-run the audit to confirm.
The prompt
The original prompt by Alexander Opalic, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude Code and Claude. Values in lime are placeholders.
Original prompt by Alexander Opalic
You are a SEO expert your name is John Wick. I gave you so much money now you have to do a SEO audit for this blog. When you are done write down everything into a own markdown file so I can solve the problems later. Use Puppeteer MCP, the server is already running.
Exactly as published by Alexander Opalic in How I Use Claude Code for Doing SEO Audits | alexop.dev.
Our adapted version (optional)
Act as a technical SEO reviewer. Use the browser tool to load [site URL] and its main templates: home, a post, a tag page and the 404 page. Check titles, meta descriptions, heading order, canonical tags, internal links, image alt text, structured data, robots and sitemap, and page load. Save every issue with the page, the problem and a suggested fix to seo-audit.md in this repo. Do not change any code.
What can go wrong?
- An audit of a local preview can miss production settings such as redirects.
- Treat speed numbers from one run as indicative only.
Our take
We like this because it is honest about how simple the prompt was; leverage comes from the browser tool, not prompt craft. Writing findings to a file in the repo is the key habit, since the next session can continue from evidence. Alexander's setup gives Claude Code a real browser through a Puppeteer MCP server, so the audit checks the rendered page rather than guessing from source files. Ask for a pass covering metadata, headings, links, speed and structured data, and have every issue written to a markdown file in the repo; that file becomes the fix list and the record for the next session. Work through it in batches and rerun the audit to confirm each fix landed. Audit the deployed site rather than only a local preview, because redirects and production settings can differ. Treat speed numbers from a single run as rough. This suits sites you own and checks how crawlers see them; it is not a keyword strategy or a competitor analysis, and only point it at sites you control.
Where the time goes back: A tedious checklist walk-through becomes a saved to-do file you can work from at your own pace.
FAQ
Why a real browser?
Was the prompt fancy?
Source and credit
The original prompt on this page is by Alexander Opalic, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- How I Use Claude Code for Doing SEO Audits | alexop.dev
- Creator
- Alexander Opalic
- Published on
- alexop.dev
- Original date
- Jun 26, 2025
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.