TECHNICAL SUITE · SITE AUDIT

Crawl every page. Know what's happening.

SEORCE Site Audit continuously crawls your entire site, not a sample, and shows what every page is doing across crawlability, indexability, rendering, links and redirects. Every discoverable URL, on a schedule, run after run.

You are here · the workflow

CRAWL → DIAGNOSE → PRIORITISE → FIX → VERIFY → MONITOR

The technical surface · this page covers

Crawl & discoveryIndexabilityRenderingRedirectsSchemaContentInternal linksPerformanceCrawlabilityAssets

Part of Technical Suite's six-stage loop. See the full system →

Common challenges

Most sites are only checked a few times a year.

  • An audit runs quarterly. For the other eleven weeks, nobody knows what's happening across the site.
  • A migration breaks tens of thousands of redirects. It surfaces six weeks later as a slope down in Search Console, not on the day it happened.
  • A crawl tool samples 5,000 pages on a 40,000-page site. Whatever's wrong outside the sample simply doesn't exist as far as anyone knows.
  • Nobody can say with confidence what "every page" looks like right now, only what a subset looked like the last time someone checked.

What needs to happen: coverage needs to be complete, not sampled, and it needs to repeat on a schedule rather than only when something's already gone wrong.

How SEORCE does it: every discoverable URL within crawl scope is crawled, on a schedule, run after run, not a sample. Crawlable, indexable and indexed status are reported separately, JavaScript-rendered content is checked against the raw server response, and crawl history is kept run over run, so a regression is a visible change, not something someone has to happen to notice.

Coverage

Not 5,000 pages. Not a sample. Your whole site.

Every discoverable URL within crawl scope gets crawled, run after run. A one-off audit tells you about the day it ran. A continuous crawl tells you what's true right now.

Discovered41,208
Crawled41,208
Indexable37,940
Indexed*35,120
Blocked / excluded3,268
Orphaned214

Discovered ≠ crawled ≠ indexable ≠ indexed. Each is a different failure point, reported separately.

*Crawlable and indexable are determined directly from the crawl. Indexed status reflects Search Console or another connected data source, where available.

Continuous, not periodic

A crawl that runs. Not a crawl that ran once.

A one-off audit gives you a snapshot: accurate the day it ran, stale the moment anything on the site changes. Site Audit runs on a schedule, continuously, so the gap between "something broke" and "something was found" is one crawl cycle, not one financial quarter.

ONE-OFF AUDIT
Audit runs. Site is accurate here. Drift, unmeasured, for months
CONTINUOUS CRAWL
Every run re-checks the whole site
Discovery, this crawlhow URLs get foundDemo data
Sitemap
Internal links
↓
41,208 URLs discovered
Cadencethis project

A full re-crawl runs on a set schedule, not triggered manually. Between runs, nothing about the site's technical state is assumed. Every page is checked again rather than only the ones someone remembered to look at.

Indexability, in detail

Crawlable. Indexable. Indexed. Not the same thing.

A page can be perfectly crawlable and still be blocked from indexing by its own canonical or a noindex tag. Collapsing the three into one status hides exactly where a page is failing.

Sample pages, this crawlcrawlable · indexable · statusDemo data
/product/running-shoe-aCrawlable, indexableHealthy
/product/running-shoe-bCrawlable, canonical points elsewhereNot indexable
/product/running-shoe-cBlocked in robots.txtNot crawlable
!3,268 pages are crawlable but not indexable. Most of them because a canonical points somewhere it shouldn't.
Rendering, in detail

What the server sends. What the browser shows.

For JavaScript-driven pages, content, links and metadata that only appear after a script runs are invisible to anything that only reads the server response.

Server response

  • →Title: "Product"
  • →No product links present
  • →No meta description

Rendered DOM

  • ✓Title: "Trail Runner 3 | Ledgerly"
  • ✓42 product links present
  • ✓Full description rendered

This page checks out fine once rendered. The gap matters most when it doesn't: content or links that never make it into the rendered version at all.

Crawl depth

How far a page sits from the homepage.

Depth isn't decoration. Pages buried deep get crawled less often and pass less authority. This is where the site's own structure works against it.

Depth 0 · Homepage1
Depth 1 · Categories42
Depth 2 · Subcategories, listings3,940
Depth 3 · Product & article pages34,120
Depth 4+ · Filtered & paginated3,105

3,105 pages sit four or more clicks from the homepage, mostly filter and pagination combinations, the least likely to get recrawled often.

Everything inspected

Not a summary score. Every signal, per page.

Discovery

Crawl mechanics

  • Status codes (2xx/3xx/4xx/5xx)
  • Crawl depth from homepage
  • Internal link count, in and out
  • Orphan pages: zero inlinks
Indexability

Can it be indexed

  • Canonical tag, self or cross-page
  • Noindex directives, meta or header
  • Sitemap presence and coverage
  • robots.txt rule matching, per bot
Rendering

What's there

  • Raw HTML vs rendered DOM diff
  • Rendered title, meta and canonical
  • Links only present after JS runs
  • Content that fails to render
Status codes

Every response, across 41,208 URLs.

Status code distributionthis crawlDemo data
200 · OK37,940
301 · Redirect2,860
404 · Not found312
302 · Temporary redirect78
5xx · Server error18
What you'll see

Inside every crawl.

Coverage

Every URL, not a sample

  • Every crawled URL, not a sample
  • Status codes, crawl depth, robots.txt matching per bot
Indexability & rendering

What a page is

● Crawlable ● Indexable ● Rendered
  • Crawlable, indexable and index status per page
  • Raw HTML vs rendered DOM, for JavaScript-driven pages
Structure & history

How it changes over time

  • Orphan pages and internal link count
  • Crawl history, run over run, for comparison

What is Site Audit?

Site Audit is the full-site crawl inside SEORCE Technical Suite. It crawls every discoverable URL within crawl scope on a schedule, not a sample, and reports crawlable and indexable status for every page directly from the crawl, plus index status where Search Console or another connected data source confirms it. For JavaScript-driven pages, it compares the raw server response against the rendered DOM, since content and links that only appear after a script runs are invisible to a crawler that only reads the server response. It also maps internal links across the site to find orphan pages, ones with zero links pointing to them. Crawl history is kept run over run, so what changed between crawls is visible as a comparison, and everything this crawl finds feeds directly into diagnosis, prioritisation and AutoFix.

Key facts

  • Crawls every discoverable URL on a schedule, not a one-off audit or a sample
  • Reports crawlable, indexable and indexed status separately per URL
  • Compares raw HTML against the rendered DOM for JavaScript-driven pages
  • Finds orphan pages by mapping internal links across the whole site
  • Crawl history is kept run over run for comparison

Last reviewed 15 October 2026 by the SEORCE team.

Common questions

Frequently asked about Site Audit.

Updated 18 September 2026

The whole site. Every discoverable URL within crawl scope is crawled on a schedule, not sampled once and left stale.

Crawlable means a bot can reach the page at all. Indexable means nothing on the page itself blocks indexing, such as a noindex tag or a canonical pointing elsewhere. Indexed means Search Console or the search engine has confirmed it, where that data is connected. SEORCE cannot claim index status from a crawl alone. A page can be crawlable without being indexable, and indexable without ever being indexed. Site Audit reports all three separately.

Yes. For JavaScript-driven pages, the crawl compares the raw server response against the rendered DOM, so content, links, metadata or canonicals that only appear after JavaScript runs are checked too.

The crawl maps internal links across the whole site as it runs, so a page with zero links pointing to it is flagged automatically, the same cycle it's discovered.

On a schedule, continuously, not as a one-off audit. Crawl history is kept run over run so what changed between crawls is visible as a comparison.

They're scored by impact and scale, then AutoFix applies the fix automatically for the class of issue with a single correct answer. Everything else is diagnosed with the exact fix already worked out.

Free to start

See what a full crawl finds on your site.

Every page, crawlable, indexable and rendering status included: not a sample, not a one-off scan.

3,000+ users · Free forever plan, no card needed