The website audit that grades you for 2026 search, not 2015.

What a website audit should produce

A website audit is only useful if it ends in a backlog. A score by itself is decoration. Our audit outputs a prioritized findings list with the exact URL, the offending HTML or header, the rule it violates, and a fix you can hand to an engineer or paste into a ticket.

The 45 checks, in eight dimensions

Foundational, Technical, On-page, AI Overviews, GEO, Local, E-E-A-T, Performance. See the full check list on the methodology page.

What makes this audit different

Three things. First, we grade the AI-search surface, not just Google. Second, every finding ships with raw evidence (the literal HTTP headers, JSON-LD blocks, content excerpts). Third, the audit's output is a 30/60/90 action plan written for humans, not a 200-row CSV that requires an SEO consultant to interpret.

Why the AI-search surface matters

Position-1 CTR drops 58% when an AI Overview is present [4]. Even if your classic SEO is perfect, a #1 ranking now leaks more than half its clicks if you're not cited inside the AI Overview. And 80% of LLM citations come from URLs not ranking in Google's top 10 - which means AI visibility and classic ranking are correlated but distinct disciplines.

Crawl scope and limits

Free tier: up to 50 pages, one audit at a time, shareable public URL. Paid tiers raise the crawl ceiling, add monitoring, scheduled re-audits, PDF export, and unlimited private audits. See pricing.

What you'll do with the report

• Hand the executive brief to a stakeholder.
• Paste the technical findings into engineering tickets.
• Use the 30/60/90 plan to sequence work across two sprints.
• Share the public URL in a Slack channel or a sales proposal.
• Re-run after each fix to track score lift.

The 6-point pre-audit checklist

1. Confirm OAI-SearchBot, ClaudeBot and PerplexityBot are not blocked at WAF or robots.txt.
2. Ship Article schema with datePublished and dateModified on long-form pages.
3. Add Person schema to every byline with a LinkedIn sameAs edge.
4. Make sure the first 200 words of every page directly answer the page's primary question.
5. Confirm an llms.txt exists at the domain root.
6. Test render parity — what the crawler sees without JS should already contain the answer.