4 Hours to 30 Minutes: Automating High-Impact SEO Audits with Claude Code

In this talk, John will demonstrate how Claude Code can compress a full technical SEO audit from a 4-hour manual process into under 30 minutes.

He'll walk through the exact automation workflow, show real outputs, and give attendees a replicable framework they can deploy on their own client sites immediately.

Transcript

2. Hi, I'm John. 12 years in SEO: agency & in-house some of the brands behind the work
3. I audit large ecommerce sites for a living.
4. By the end of this talk, an audit will have run itself.
5. 4 hours One technical audit. One site. Done properly, by hand. crawl config · exports · spreadsheet joins · analysis · writeup
6. The first 30 minutes: configuration 0:30 01 Crawl mode: text vs JS 02 Crawl speed & politeness 03 XML sitemap discovery 04 GSC, GA4 + API connections 05 Include / exclude rules 06 Custom extractions & searches 07 Page-type segmentation
7. The anatomy of a manual audit Setup Crawl Analysis & joins Deliverable 0:30 0:30–2:00+ 1:00–2:00 1:00 ≈ 4 hours. Every audit. Every site.
8. And again next month. And for the next client.
9. So I automated it. Badly.
10. Eighteen scripts.
11. One check each. Fifteen minutes of babysitting.
12. xkcd.com/1319 CC BY-NC 2.5
13. The problem was never the audit. It was me.
14. Claude Code didn't speed up the job. It took the job.
15. It builds the audit. Then it joins the audit.
16. What you'll see today ≈ 1 min a fast sampling audit, built for this talk any Shopify store: 9 modules, 50+ checks free at audit.johncaiozzo.com A gateway to the full audit, not the full audit.
17. What runs for clients ≈ 30 min dedicated front-end + back-end apps full-site crawl, JS rendering on every template daily and weekly checks, reports, Slack alerts Sections 1 to 3 are this system. Section 4 is the gateway to it.
18. 01 Build one audit
20. Target: every collection page on the store
21. What I find on Shopify stores. Every time. × Orphaned collections: live, indexed, no internal links HIGH × Forgotten collections: still live, zero products CRITICAL ! Sitemap URLs that redirect or 404 MEDIUM × Broken header or footer links HIGH × Product schema missing, or injected only by JavaScript HIGH ! No agentic-commerce (ACP) context, e.g. product_type MEDIUM None of these are hard to find. They're hard to remember to look for.
22. You describe the audit in English
23. It plans before it codes
24. Then it writes the collector
25. Three files. Every audit. collector fetch + check + persist → router query + filter + export → Every audit. Same three files. page chart + alerts + table
26. One config file per client the only thing that changes
27. First run
29. 02 Then build all of them
30. Adding a check became mechanical.
31. 65+ rules across 18 modules and growing weekly the client build, multiple storefronts · today's free tool: 9 modules, 50+ checks
32. Sitemaps
33. Collections
34. Agentic commerce
35. Every Monday. By itself.
36. It tells you what changed
38. 03 Checks only an LLM can do
39. Crawlers read HTML. Google reads the render.
40. The agent reads the diff
41. Ranking #3. Getting #9's clicks.
42. One template fix. Four hundred pages.
43. It posts to Slack before I've had coffee
45. 04 Zero to audit in one minute
46. What happens when you hit Run 01 robots.txt crawl rules, declared sitemaps, AI-bot access 02 sitemaps 03 04 page types checks sample each template 9 modules, 50+ checks, scored and ranked → the URL inventory: → classify every URL, → collections, products, pages No crawler to configure. The store tells the tool how to audit it — the same four steps for every storefront, every run.
47. Watch it work
48. Done. Scored. Prioritized.
49. Client-ready, not a data dump
50. 39.3s 131 requests · 30 pages · zero babysitting the hosted sample audit — the full local run with rendering checks: under 30 minutes
51. But speed isn't the win.
52. The win: nobody has to remember to run it.
54. 05 Steal this
55. The whole framework collector fetch + check + persist → router query + filter + export → page chart + alerts + table config — the only per-client file Three files per audit. One config per client. That's the framework. In the open-source engine the same idea is one module per check family — plus one config.
56. CLAUDE.md is your agent's onboarding doc conventions live here so every new check matches
57. Try it right now. The live tool — 50+ checks, including agentic-commerce (ACP) readiness. Free. audit.johncaiozzo.com github.com/caiozzo-consulting/shopify-seo-audit audit a store now
58. MONDAY Automate your link checker > claude "check every nav and footer link on mysite.com, flag anything that isn't a clean 200"
59. TUESDAY Sitemap health > claude "parse my sitemap index, check every URL's status, flag redirects and 404s in the sitemap"
60. WEDNESDAY Schema validation > claude "validate Product and CollectionPage schema on these templates against Google's requirements"
61. Automate one check this week.
62. Thank you. Run it on your own store at the link. Come say hi — I love talking shop. @johncaiozzo · johncaiozzo.com github.com/caiozzo-consulting/shopify-seo-audit audit.johncaiozzo.com