When should you use it?
- Your site content lives in a repo or CMS the agent can edit
- SEO recommendations keep stalling at execution
- You can review changes in batches
Not for: Publishing SEO edits without human review; Sites where strategy is not yet decided
What do you need, and what do you get?
You need
- An SEO audit with specific recommendations
- Repository or CMS access for the agent
- Approval gates before anything goes live
You get
- Meta title and description updates across many pages
- Contextual internal links added at scale
- Refreshed copy on underperforming pages
How does it work, step by step?
- Bring the audit, not vague goalsGive the agent concrete findings so it executes a plan rather than inventing one.
- Scope to a small batchStart with a limited set of pages where time savings are real and risk is low.
- Let it do the mechanical workHave it update tags, add links and restructure categories across the library.
- Keep strategy humanA strategist defines and reviews every change; the agent only executes.
- Approve before shippingNothing goes live until a person signs off on the batch.
The prompt
Our own prompt, inspired by Lawrence Hitches and written to work in Claude Code. Values in lime are placeholders.
Here is our SEO audit: [paste findings]. Working in our content repo, execute these changes as a pull request for a small batch of [N] pages first: update meta titles and descriptions to the recommendations, add relevant contextual internal links, and refresh the listed underperforming pages. Match our style guide, explain each link's relevance, and do not touch anything outside the listed pages.
Inspired by Lawrence Hitches: How to Use Claude Code for SEO Automation. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Scale makes mistakes scale too; batch the work and review before publishing.
- Internal links need relevance judgment, so skim the agent's choices rather than trusting them blindly.
Our take
Lawrence Hitches identifies the real bottleneck in SEO work: analysis is rarely the problem, execution is. Audits produce long lists of small, repetitive edits, and that is exactly what coding agents handle well. Keeping strategists in charge of what to change and approving each batch, while the agent grinds through the edits, is the right division. Bring the audit itself, with specific pages and recommendations, rather than vague goals like improve rankings, since a precise brief produces precise changes. Ship in small, supervised waves. A pattern that looks fine on paper can go wrong in practice, such as titles that truncate badly or internal links that all point to one page, and catching it on ten pages is far cheaper than on a thousand. Content refreshes need the most care, because agents can flatten a page's voice or introduce claims that are not accurate; have a writer review those. Record what changed and when, so ranking movements can be linked to specific batches. Keep client approval in the loop for anything visible to customers.
Where the time goes back: The gap where audits die, nobody has time to execute, closes because tedious changes become reviewable pull requests in minutes.
FAQ
What does the agent actually do?
Who decides strategy?
Source and credit
Inspired by Lawrence Hitches. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How to Use Claude Code for SEO Automation
- Creator
- Lawrence Hitches
- Published on
- studiohawk.com.au
- Original date
- May 12, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and 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 23, 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.