{"slug": "your-site-audit-found-400-issues-you-ll-fix-four", "title": "Your Site Audit Found 400 Issues. You'll Fix Four.", "summary": "A developer built ContextBolt SEO, a hosted MCP server that lets Claude run real site audits by reading sitemaps and fetching batches of pages, revealing cross-page issues invisible from single-page checks. The tool focuses on the second audit run—the one that measures whether fixes worked—rather than the first run's overwhelming 400-issue report that nobody finishes.", "body_md": "Ask Claude to audit a page and it does a genuinely good job. Ask it to audit your site and something quietly goes wrong. It reads your homepage, tells you the title is a bit long, and calls that a site audit.\n\nYou have not audited a site. You have audited one page and rounded up.\n\nThey live in the pattern. Forty posts sharing one meta description because the template forgot to fill it in. Every product page rendering three H1s. A sitemap full of URLs that redirect.\n\nNone of that is visible from inside one page, because the bug is the relationship between pages, not the page itself.\n\nFour kinds of problem only show up when you look at many pages together.\n\nHand Claude a URL and it fetches that page. That is the whole behavior. No crawler, no sitemap parser, no memory of the last forty pages it read. So when you say \"audit my site,\" it does the only thing it can.\n\nThis is the same limitation behind every other SEO job. Claude is excellent at judgment and blind to live data. MCP is how you close that gap. An SEO MCP server gives Claude a tool that takes a domain, reads its sitemap, fetches a batch of pages, and returns structured data instead of a wall of HTML.\n\nOnce that tool exists, \"audit my site\" becomes a real instruction.\n\nHere is the uncomfortable part, and it applies to nearly every audit product on the market, mine included until I built the thing that fixes it.\n\nRun a classic site audit and you get a number. 400 issues found. It feels thorough. It is also the most useless output in SEO, because nobody has ever fixed 400 issues. You skim it, fix the four that look easy, promise to come back, and never do.\n\nThe scary first-run number is a marketing asset. It sells the subscription. It does not improve the site.\n\nThe run that improves the site is the second one. You fix a template, you re-audit, and you find out whether the number moved. That loop is where the work happens, and it is the part almost nothing is designed for. Most tools return you to a static report from last Tuesday, or worse, silently crawl a fresh set of pages so the comparison is meaningless.\n\n**An audit you run once is a to-do list. An audit you run twice is a system.**\n\nIf your audit cannot answer \"did my fix work,\" it is a report, not a tool.\n\nThe instinct is to crawl everything. Resist it.\n\nAlmost every site is a handful of templates wearing different content. Audit 25 pages chosen across those templates and you find nearly every repeating problem the site has. Auditing 5,000 finds the same ten problems five hundred times each and buries the two genuinely unique ones.\n\nGoogle puts the crawl-budget threshold at roughly a million pages changing weekly. If that is you, a dedicated crawler earns its place. For everyone else, the twenty-sixth page rarely tells you anything the first twenty-five did not.\n\nThere is a second reason. A fix list you can finish is worth more than a complete one you will not start.\n\nFull disclosure, I build one of these. [ContextBolt SEO](https://contextbolt.com/seo/) is a hosted SEO MCP server. You get one URL, you paste it into Claude Code, Claude Desktop, Cursor, or Codex, and your agent can run both audits. `page_audit`\n\ncovers one URL, `site_audit`\n\ncovers the site.\n\nIt reads the sitemap, picks the structurally important pages, checks titles over 60 characters, descriptions outside 120 to 155, missing or multiple H1s, thin content, broken pages, redirecting sitemap entries, canonicals pointing nowhere, and missing alt text, then hands back a score out of 100 with a fix list sorted worst first. Cross-page duplicates come free, because it holds every page at once. The default run is 25 pages. It costs $35 a month.\n\nThe part I care about is the second run. Ask again and it re-checks the pages already in your report, least recently checked first, and leads with the delta rather than a fresh report. It never quietly audits new pages and bills you for it.\n\nEvery run writes to one living report per site at `./seo-findings/audits/`\n\nas plain markdown, growing in place rather than spawning a new file each time. The audit trail sits in the repo next to the code it is grading.\n\nIf you would rather not pay for anything, you still get most of the way there. Search Console flags indexing problems across your whole site for free and it is your own data, which makes it the most trustworthy source you have. A free desktop crawler covers a few hundred URLs. The method works either way.\n\nThe longer walkthrough, with the full check list and the page-level companion, is in my [site audit with Claude](https://contextbolt.com/blog/site-audit-with-claude/) guide.\n\n**The version of a site audit worth running is not the one that finds the most problems. It is the one you run twice.**", "url": "https://wpnews.pro/news/your-site-audit-found-400-issues-you-ll-fix-four", "canonical_source": "https://dev.to/david_hamilton/your-site-audit-found-400-issues-youll-fix-four-3p7j", "published_at": "2026-07-22 10:34:38+00:00", "updated_at": "2026-07-22 11:00:27.923454+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "artificial-intelligence"], "entities": ["Claude", "ContextBolt SEO", "Cursor", "Codex"], "alternates": {"html": "https://wpnews.pro/news/your-site-audit-found-400-issues-you-ll-fix-four", "markdown": "https://wpnews.pro/news/your-site-audit-found-400-issues-you-ll-fix-four.md", "text": "https://wpnews.pro/news/your-site-audit-found-400-issues-you-ll-fix-four.txt", "jsonld": "https://wpnews.pro/news/your-site-audit-found-400-issues-you-ll-fix-four.jsonld"}}