Site audit
Find what’s holding your site back. Fix the right things first.
Crawl every page for technical errors, on-page gaps and AI-readiness problems. Each crawl is compared with the last, so you see what got fixed, what broke and what’s new.
Ask Brigham.aiAudit DEV.co and tell me the five issues most likely costing us traffic, in the order I should fix them.- Broken internal links42
- Missing meta descriptions118
- Pages blocked from AI crawlers0
- Duplicate title tags17
- Fixed since last crawl64
- 3
- Issue families
- Crawl vs. crawl
- Every run compared
- GSC
- Search Console connected
- $20
- Per month, all tools
Why audit
Most sites don’t have a content problem. They have a plumbing problem.
- Covers
- Technical, on-page, AI-readiness
- Compare
- Every crawl vs. the last
- Data
- Crawl + Search Console + GA4
A strong page can still underperform if search engines can’t reach it, read it or tell it apart from three near-duplicates. Broken links, redirect chains, slow templates and missing tags quietly drain the value of everything you publish.
The search.co site audit crawls your site the way a search engine does, groups what it finds into technical, on-page and AI-readiness issues, and ranks each one by how many pages it touches and how much traffic those pages carry. You start with the fix that matters most, not the longest list.
Where the problems live
See issues by section of your site.
The crawl map groups pages by folder, so a template bug shows up as one fix instead of three hundred rows.
01
Template-level view
When one template causes an issue on every page, you see it once with the count.
02
Traffic-weighted
Search Console clicks are attached to each page so busy pages rise to the top.
What we check
Three families of issues, one crawl.
Technical
5 checks- Status codes, broken links and redirect chains
- Canonical tags and duplicate pages
- Robots.txt, noindex and sitemap coverage
- Page speed signals and heavy assets
- Mobile rendering and viewport
On-page
5 checks- Titles and meta descriptions
- Heading structure
- Thin and duplicate content
- Image alt text
- Internal links and orphan pages
AI-readiness
4 checks- Whether AI crawlers are allowed
- Structured data coverage
- Clear answers near the top of the page
- Content readable without scripts
Crawl over crawl
Know what changed since last time.
An audit is only useful if you can tell whether things are getting better. Every crawl is compared with the previous one, so you see fixed issues, new issues and regressions as separate lists.
If a release breaks canonical tags on 200 pages, it shows up as new the next morning, with the pages listed.
Fixed
Issues that were present last crawl and are gone now.
New
Issues that appeared since the last run, often tied to a release.
The change log
Every regression, with the pages attached.
| Issue | Last crawl | This crawl | Status |
|---|---|---|---|
| Canonical points elsewhere | 0 | 38 | New |
| Broken internal links | 57 | 42 | Improving |
| Missing meta description | 131 | 118 | Improving |
| Redirect chains | 14 | 0 | Fixed |
01
Release-aware
Spikes line up with the date they appeared, so you can match them to a deploy.
02
Exportable
Download any list as CSV or send it to a report.
- 3
- Issue families
- Technical, on-page, AI-readiness
- Every
- Crawl compared
- Fixed, new and regressed
- GSC + GA4
- Connected data
- Real clicks and conversions
AI-readiness
Make sure AI assistants can read you.
ChatGPT, Perplexity, Gemini and Google AI Overviews can only cite what they can fetch and understand. The AI-readiness checks look for blocked crawlers, missing structured data and pages that bury the answer under scripts.
Ask Brigham
Skip the 400-row export. Ask what to fix.
Brigham reads the crawl, your Search Console data and the change log, then ranks fixes by impact.
Likely yes. The last crawl found 38 blog posts now canonicalizing to the blog index after Tuesday’s template update. Those posts had 22% of blog clicks last month in Search Console. Nothing else changed on those pages.
Recommended fixes
Sorted by impact
- 1
Restore self-referencing canonicals
15 minThe blog template now points every post to /blog. Revert that one line.
- 2
Fix 42 broken internal links
30 minMost point to an old /services URL. One redirect rule covers 36 of them.
- 3
Add Article schema to posts
1 hrOnly 9% of posts carry it. Adding it to the template helps AI answers read them.
How it works
From crawl to fix list in four steps.
- 01
Add your domain
Set crawl limits, include or exclude folders, and connect Search Console.
- 02
Crawl
We fetch your pages as a search engine would and record every issue.
- 03
Prioritize
Issues are ranked by pages affected and traffic at risk.
- 04
Re-crawl
Schedule repeat crawls and watch fixed and new issues side by side.
The difference
An audit you can act on.
A typical audit tool
- Hundreds of issues, all flagged the same
- No link to real traffic
- Each crawl stands alone
- AI crawlers not considered
search.co site audit
- Issues ranked by traffic at risk
- Search Console clicks on every page
- Fixed, new and regressed per crawl
- AI-readiness checks built in
How many pages can you crawl?
You set the crawl limit per project. Crawls use credits, so most people crawl the full site once and then schedule smaller repeat crawls of the sections that change most.
Do I need to connect Search Console?
No, but it helps. With Search Console and GA4 connected, each issue shows the clicks and conversions on the affected pages, which makes prioritizing much easier.
What does AI-readiness mean?
It checks whether AI assistants can fetch and understand your pages: crawler access, structured data, clear answers and content that renders without scripts.
Can I share the audit with a developer?
Yes. Add the audit to a branded report or send a live share link. Each issue lists the affected URLs so a developer can work from it directly.
Find the fix that matters most.
Run your first crawl today. Start the 7-day trial, add your domain and get a ranked fix list in minutes.
Crawl my site and give me the top five technical fixes ranked by traffic at risk.