Complete captured set
Inspect each stored crawl URL with its captured HTTP status, declared canonical, indexability signals, depth and internal links, then filter or export supported fields.
Crawl Explorer
Inspect every URL captured in your project crawl, and turn each supported technical finding into an action.
Crawl Explorer lays out every URL captured within the project crawl's discovery, permission and plan limits, including status, depth, metadata and health signals. The stored result set is not sampled, and the same captured crawl feeds the rest of Novaverb.
Why it is useful
A clear decision, with the supporting evidence close by
SEO problems hide in the gap between what a page claims and what a crawler actually retrieves, and most audits flatten that into a single score you can't act on. Crawl Explorer reads your site's own crawl page by page, so every title, canonical, directive, and rendering signal is evidence you can open, filter, and export.
Evidence-backed findings
Duplicate clusters, render evidence and data-quality states are shown when the required crawl fields are available.
Evidence you own
Each crawl is a timestamped record you keep, compare scans over time and use a later detector run to check whether a supported issue remains.
Data and evidence
See the evidence behind each result
Crawl Explorer reads one source: your own crawl of your own site. Every title, canonical, directive, status code and rendering signal it shows was retrieved from your pages, not modelled or estimated. Where the crawl could not retrieve a signal it says so, so a page that was never fetched is never presented as a page that passed.
Primary input
NovaCrawl page captures
Product layer
18 evidence workbenches
Primary output
Filterable URL fix queue
How to read this result
Page signals come from the selected project crawl; Search Console views activate after the property is connected.
Core capabilities
What you can do with Crawl Explorer
Eighteen focused cockpits let you interrogate a crawl from one angle at a time: status class and redirect health, title and description duplication, H1 state, canonical relationships and the status of what they point at, duplicate and render risk. Each cockpit filters to the affected URLs, so a finding is always a list of pages you can open.
01
Eighteen focused intelligence cockpits
One crawl feeds eighteen grouped tabs, each a purpose-built workbench for a single decision: titles, meta descriptions, H1s, content depth, images, canonicals, indexation directives, hreflang, structured data, internal links, JavaScript, security, URL hygiene, performance, redirects, HTTP status, sitemaps, and Search Console overlay. Every tab carries its own filters, quick-stat drill tiles, priority lanes, and a click-to-open drawer that ties each finding to a what/why/how fix card. You never leave for a second tool to answer a title, canonical, or directive question.
- Title state: missing, duplicated, too short, too long, weak
- Meta description length band (healthy 120-160) and duplication
- H1 count, duplicate H1, and title-mismatch flags
- Canonical relationship: self, cross, or missing plus target health
02
Data quality that never fakes clean
The bundled Data Quality view runs seven trust checks live over your crawl and leads with evidence coverage, how many checks it can actually run, instead of a made-up cleanliness score. Crawl-provable checks like soft-404 inferred, thin content, and needs-recheck return real counts; checks that require Search Console, a render pass, or Google's selected canonical are marked insufficient, never green by absence. A page is only called clean when a check actually ran and passed.
- Evidence coverage shown as N of 7 checks runnable
- Soft-404 inferred: 200 status with almost no extractable content
- Thin content and needs-recheck from word count and extraction
- GSC render gap, index mismatch, canonical shadow gated as insufficient
03
Duplicate and render risk, bundled
Duplicate Clusters groups pages that share an exact title, meta description, or H1, then risk-ranks each cluster by canonical posture, competing versus already-consolidated, and suggests the safest primary URL to keep. JS Render Health proves render-blocking load per page and the server-rendered text already in your initial HTML, and stays honest that raw-versus-rendered delta needs a render pass. Both are exact-match and crawl-derived, so body-level near-duplicate and rendered-only claims are surfaced as insufficient rather than asserted.
- Exact title, meta, and H1 clusters with unique URLs affected
- Canonical posture: consolidated, competing, missing, mixed
- Suggested primary URL from indexability, inbound links, depth
- Render-blocking resource count and server-rendered word count
How the work moves
From available evidence to a reviewable next action
Run a crawl, open the cockpit that matches the question you have, filter down to the affected URLs, then fix or export them. The crawl that produced a finding stays attached to it, so when a page changes you re-crawl and compare rather than trusting that the earlier list is still true.
- 01
Run a crawl
Point a project at your domain and Novaverb crawls it, capturing status, content, directives, links, and rendering signals into the latest scan.
- 02
Open a cockpit
Pick the tab for the decision at hand and read its KPI strip, priority lanes, and drill tiles scoped to that scan.
- 03
Filter and drill
Use the smart-filter dropdowns, status facets, and issue chips to narrow to the exact URLs that prove a problem.
- 04
Fix or export
Open any row's drawer for a diagnosis and fix steps, or export the current tab and filters as CSV for your team.
Built around real work
Useful for teams who need to move from evidence to delivery
In-house SEO teams
Triage a large site by opening the exact tab and filter for a title, canonical, or indexation issue instead of scrolling one giant report.
Technical SEO consultants
Hand clients an evidence-backed URL list per problem, exported to CSV, with the canonical or directive signal that proves it.
Content and editorial leads
Find thin, duplicate-title, or weak-H1 pages and see the fix guidance in the same drawer before rewriting.
Connected outcomes
Continue from this product into a complete customer workflow
Fix & Improve
How Can I Help Search Engines Discover New Pages Safely?
Make new pages reachable through clean crawl paths, accurate sitemaps, indexable directives and supported submission methods.
Open workflowFix & Improve
Which Technical SEO Issues Should I Fix First?
Fix the issues that combine verified severity, meaningful reach and clear affected URLs before lower-impact cleanup.
Open workflowDiscover & Diagnose
Why Can't Search Engines Find Some of My Pages?
Pages become hard to discover when internal links, crawl depth, sitemaps or indexability signals leave no clear path.
Open workflowFix & Improve
Why Do Important Pages Have No Internal Links?
Important pages become isolated when navigation, hubs and contextual links fail to connect a real source URL to the target.
Open workflowMeasure & Prove
How Can I Prove SEO Work Was Actually Completed?
Compare timestamped crawl evidence from before and after the change, then verify that the failing condition is gone.
Open workflowDiscover & Diagnose
How Do I Audit a Large Website Without Losing URL-Level Detail?
Keep every sitewide finding linked to the exact affected URLs, source fields and crawl scope.
Open workflowResources
Read more about Crawl Explorer
Written by the team that built it, and free to read without an account.
Guides
Step-by-step walkthroughs, five minutes each.
Definitions
What the terms on this page actually mean.
- What Is Crawling in SEO? How Search Engines Find Pages
- What Is a Search Engine Crawler? How Web Crawlers Work
- What Is Crawlability in SEO? Access, Rules and Testing
- What Is Crawl Depth in SEO? Levels, Impact and Examples
- How Do Search Engines Discover URLs? Links, Sitemaps & More
- What Is a Canonical Tag? rel=canonical Explained
Try it free
Run the idea on a real URL, no account needed.
In the app
How this works once you are inside a workspace.
Connected products
Keep the work moving without losing the source
Frequently asked questions
Crawl Explorer FAQ
Clear answers about data, availability and how the product fits into the wider workflow.
Do I need to connect anything to start?
No. Crawl Explorer works entirely from your own crawl, though checks that need Google-selected canonical, index coverage, or a render pass stay marked insufficient until you connect Search Console or run rendering.
What does an insufficient or needs-evidence label mean?
It means the check could not be proven from the signals captured, so Novaverb refuses to call it pass or fail. The URLs are neither confirmed clean nor flagged until the missing evidence lands.
Can I export what I am looking at?
Yes. Every tab streams the current tab plus its active filters to CSV, so the export matches exactly what is on screen.
How does it handle JavaScript-rendered content?
The static crawl proves render-blocking load and the text already present in your initial HTML. Raw-versus-rendered delta, render timing, and rendered-only content are shown as insufficient until a render pass runs, rather than guessed.
Technical SEO & Crawl
Put Crawl Explorer to work on your own evidence.
Start with a real project, keep unavailable data visible and follow the connected workflow when the result is ready for action.