Site Audit

A content audit tool that tells you what to fix first

A real crawl of your domain, your own Search Console numbers alongside it, and a fix list ordered by what's actually likely to move rankings.

Audit your site →
Whole-domain crawlSearch Console dataSeverity-ranked fixesPlain-English explanations
example.com · site audit
232
issues found
1,248
pages crawled
  • Canonicalised elsewhere (not audited)34 pagesFix this
  • Broken internal link21 pagesFix this
  • Duplicate title18 pagesFix this
  • Thin content (under 300 words)63 pagesWorth fixing
  • Missing meta description96 pagesLow priority

Most website content audits die in a spreadsheet. A tool exports four hundred rows, every row is technically a finding, and nobody can tell which twelve of them are costing traffic. The audit gets filed, the site stays the same, and six months later someone exports it again.

The problem is not detection; crawlers have been good at detection for a decade. The problem is ordering. A missing meta description on a page nobody visits and a canonical tag quietly deindexing your best-converting article are not the same emergency, and a list that treats them alike is a list you cannot work.

So this audit does two things beyond the crawl: it explains every issue in plain English, and it reads your own Search Console data so the pages with something to lose come first.

Crawl

A crawl, not a checklist

The audit runs DataForSEO's OnPage crawler across your domain and reports what it found on your live pages: response codes and redirect chains, canonical and indexability problems, duplicate or missing metadata, duplicated body content, broken internal links. It is the same crawl engine agencies license directly, pointed at your site and read for you.

  • ✓Runs over the whole domain, not URL by URL
  • ✓Every run is priced before you start it
  • ✓Results are stored, so re-opening an audit costs nothing
  • ✓Runs are never overwritten, so two crawls can be compared
82
A crawl, not a checkli score
Prioritize

Every issue explained, in order of severity

Findings arrive sorted by how much damage they're doing, and each one is written out: what it is, why it matters, and the steps to fix it. No error codes to go and look up somewhere else, and no assumption that the person reading has done a hundred audits before. A junior can work this list; a specialist can work it faster.

  • ✓What / why / how for every issue type
  • ✓Severity-ranked so the first hour is the useful one
  • ✓Tick issues off as your team works through them
  • ✓Filter by issue type when one fix pattern covers many pages
82
Every issue explained, score
Connect

Your own Search Console numbers, alongside

Connect Google Search Console and the audit reads your real queries, positions and impressions. That's what turns a generic issue list into a prioritised one. A broken canonical on a page holding position 4 for a commercial query outranks fifty cosmetic warnings on pages with no impressions at all.

  • ✓One OAuth connection, revocable any time
  • ✓Ranked keywords and positions per page
  • ✓Gap keywords your competitors rank for and you don't
  • ✓Impressions and clicks read straight from your property
82
Your own Search Consol score
Re-run

Proof the fixes landed

An audit is a claim about the site on a particular day. After your team ships a batch of fixes, run it again. The old crawl stays where it is and the new one sits beside it, so 'we fixed the redirect chains' becomes something you can show rather than something you assert.

  • ✓Old audits are kept, not replaced
  • ✓Compare two runs to see exactly what moved
  • ✓Re-open any stored audit for free, as often as you like
  • ✓One workspace per domain, so client sites stay separate
82
Proof the fixes landed score

How does it work?

01

Add your domain

Point the crawler at the site you want checked.

02

Run the crawl

See the cost first, then get the findings.

03

Work the list

Fix top-down; every issue explains itself.

04

Re-run and compare

Old audits stay put, so you can see what changed.

What a website content audit should cover

A content audit and a technical audit get sold as separate products, which is a marketing distinction rather than a real one. The reason a page underperforms is rarely purely editorial or purely technical: an excellent article can be canonicalised to another URL, and a technically perfect page can be four hundred words short of every result above it.

This crawl reports what is on your live pages, which is the layer both problems show up in.

  • Response codes and redirect chains, including the ones that only appear at scale
  • Canonical tags pointing somewhere else, and pages excluded from indexing
  • Duplicate or missing titles and meta descriptions
  • Body content duplicated across URLs
  • Broken internal links and the pages they sit on

Why Search Console data changes the order of the list

Severity alone is a property of the issue. Priority is a property of the issue *and* the page it is on, and that second half is not in the crawl. It is in your Search Console property.

Once the connection is made, the audit knows which URLs hold impressions, what they rank for and where. A thin-content flag on a page sitting at position 11 for a term with commercial intent is a genuine opportunity: one position of movement is the difference between page two and traffic. The same flag on a page with no impressions in three months is a note, not a task.

The connection is a single OAuth grant, revocable at any time from your Google account, and it is optional: the crawl runs without it. It just runs less usefully.

Who this fits, and what it deliberately does not do

The audit is built for the people who have to act on it: freelance SEO consultants working several client sites, small agencies who need a finding explained well enough to forward to a client's developer, and in-house teams who want the fix list ordered rather than exhaustive.

It does not change your site. It tells you what is wrong, why it matters and what the fix is; the change happens in your CMS or your codebase, by someone who can see it first. Anything that quietly edits live pages on your behalf is a worse deal than it sounds, and the first time it is wrong it is very wrong.

It also does not run on a schedule. Crawls cost money, and nothing here spends yours in the background. A run happens when you press the button, and you see the price before you do.

Perfect workflow

One platform. One workflow. The full content loop.

01
Find the gaps
Keyword Clustering →

Real keyword data from your competitors, filtered and clustered into briefs.

02
Write & optimize
SEO Content Editor →

Write to targets measured from the pages already ranking.

03
Fix what's broken
Content Audit →

Crawl the domain and work a fix list ordered by impact.

04
Check the answers
AI Visibility Tracker →

See whether ChatGPT, Gemini, Perplexity and Claude name you.

Frequently asked questions

What does the crawl actually check?+

It's DataForSEO's OnPage crawler, the same engine agencies license directly. It reports what's on your live pages: response codes, redirect chains, canonical and indexability issues, duplicate or missing titles and descriptions, duplicated body content, and broken internal links.

Do I need Google Search Console?+

No, the crawl runs without it. Connecting GSC adds your own query, position and impression data alongside the crawl, so you can see which pages the issues are actually costing you. It does not change how the audit orders its findings — that is still by severity.

Is this a content audit or a technical SEO audit?+

Both, because the split isn't real. The crawl reports the technical state of your live pages, and the Search Console data tells you which of those pages are worth editorial attention. If a page needs rewriting rather than repairing, it opens straight into the Content Editor with targets from the live SERP.

How big a site can it crawl?+

It runs across the whole domain rather than URL by URL, and the price you're shown before the run scales with the size of the crawl, so a large site is a larger number on the confirmation, not a silently truncated report.

Does opening an old audit cost anything?+

No. Every audit is saved the moment it runs, and re-opening it reads the stored result. Only pressing Run buys new data, and you see the price before you press it.

How often should I re-run it?+

After you've shipped a batch of fixes, rather than on a schedule. Runs are never overwritten, so a fresh crawl sits next to the last one and you can see exactly what moved.

Will it fix things for me?+

No. It tells you what's wrong, why it matters and what the fix is. The change still happens in your CMS or your codebase. Anything that edits your live site without you seeing it first is a worse deal than it sounds.

Can I keep client sites separate?+

Yes. Each domain gets its own workspace, and audits, documents and visibility runs are filed against it, so nothing from one client's site turns up in another's report.

Explore the rest of the platform

SEO content editor →

Rewrite the pages the audit flags as thin.

Content gap analysis →

In progress — the keywords rivals rank for and you don't.

AI visibility tracker →

Check whether assistants cite the pages you just fixed.

Your brand deserves to be seen, everywhere.

AI is shaping decisions. If you're not in the answers, you're not even considered. Win the next wave of search.

Get started now →