Site Audit
Point Kitbase at your site and it answers one question: what is wrong with it, and what should you fix first?
An audit crawls your pages, checks each one, and returns a single report — a score, a ranked issue list, and the table of every page it reached. It costs nothing per run beyond time: the crawler and the checks are ours, so you can run it as often as you like.
What makes this different from a generic SEO crawler
Broken links and missing meta descriptions are a solved commodity. The part worth your attention is the AI-readiness score — whether an AI engine can reach, parse and cite your pages. That is the headline of the report; the issue list is what makes it trustworthy.
Running an audit
Set your project's website on the Website page, then press Run audit. One audit runs at a time per project.
A run starts from your homepage and your sitemap, then follows internal links outward until it reaches its page limit. It respects robots.txt for our user agent, skips assets that are not pages, and holds itself to a polite request rate.
| Option | Default | What it does |
|---|---|---|
| Page limit | 100 | How many pages the crawl may fetch. Higher means longer, not more expensive. |
| Follow links | On | Off crawls only what your sitemap lists — faster, and blind to anything unlisted. |
While it runs you see the phase, the page counts, and the URLs it is crawling right now. Cancel stops it; everything already crawled keeps its results.
The report
Score
The AI-readiness score (0–100) and its three category scores: Crawler access, Machine readability and Analytics. This is the weighted verdict of the 16-item checklist, unchanged from before — a check that passes still counts, which is why the checklist keeps its own tab.
Tiles
Pages crawled, issues found by severity, average response time, and how many pages came back blocked, broken or erroring.
Issues
Every problem the audit found, grouped by severity and then by rule. Expanding a rule explains why it matters, what to do about it, and which pages it affects.
| Severity | Means |
|---|---|
| Critical | Costs traffic or indexing outright — unreachable, unreadable, or blocked. |
| Warning | Real damage, but the page still works. |
| Info | Worth knowing, not worth interrupting anything for. |
Rules come from several places, and each row is chipped with which:
- Crawl — what only a crawl can answer: blocked pages, server errors, broken pages, redirect chains and loops, duplicate meta descriptions, canonical conflicts, slow pages, buried pages.
- Scorecard — a checklist item that did not hold up. A failure on a heavily-weighted check (AI crawlers blocked at the root) is critical; a light one (no
llms.txt) is not. - Consistency — relational findings computed over the whole crawl: links pointing at pages that turned out to be broken, pages nothing links to, and pages publishing identical copy.
Orphan pages need a complete crawl
"Nothing links here" is a claim about everything, so it is only reported when the run followed links, read your whole sitemap, and did not stop at its page limit. A partial crawl says nothing about orphans rather than guessing.
Pages
Every page the crawl reached, with its status, title, H1 count, word count, images missing alt text, response time, crawl depth and issue count. Filter by status, search by URL, and sort by slowest, thinnest or deepest.
This is one run's snapshot. The site content pages screen remains the living inventory across runs, with history and freshness.
Checklist
The 16-item AI-readiness checklist, including the items that passed. Any single check can be re-run on its own with Re-check without starting a new audit.
Export
Export hands you the Issues or Pages tab as CSV or JSON, filtered exactly as the screen is.
When something is blocked
If bot protection turns our crawler away, the report says so plainly rather than reporting hundreds of phantom broken pages. Allowlist the user agent to fix it:
Mozilla/5.0 (compatible; KitbaseAuditBot/1.0; +https://kitbase.dev/audit-bot)Every AI crawler meets the same wall you put in front of ours, so this is worth fixing for its own sake. See Bot & Crawler Detection for what our crawler does and how to recognise it.
Older audits
Audits run before this release keep their score and checklist but have no issue list or page table — they were sampled, not crawled. The report names that rather than showing an empty issue list. Run a new audit for the full report.