Site Audit.
Understand what your site is telling search engines.
SEONova crawls the pages in your project and turns the technical evidence into a health score, prioritized issues, page-level details, and audit history. Set the crawl scope and schedule that fit your site and plan.
Site Audit
Illustrative audit workspace
Health score
Priorities
Scope
Open an issue to inspect the evidence
Review affected URLs, severity, category, crawl facts, and the recommended next step.
Audit evidence
Stored by runTrace every score back to its evidence.
Every result is tied to a crawl run and the pages it examined, so your team can understand both the finding and the limits of the crawl behind it.
How pages are found
Internal links, robots.txt, and XML sitemap discovery help establish the crawl scope.
What is recorded
URL status, redirect hops, click depth, indexability, page analysis, and issue evidence.
How findings are grouped
Issues are categorized by severity and by crawlability, security, on-page, content, performance, mobile, and structured-data areas.
What persists
Audit snapshots retain scores, issue counts, crawl statistics, and changes from prior audit runs.
What it actually does.
Review crawlability, page metadata, content, performance signals, mobile fundamentals, security headers, and structured-data signals in one project-level audit.
A connected technical crawl
The crawler follows in-site links, records response status and redirect paths, respects robots.txt when enabled, reads sitemap signals, and maps click depth and internal-link evidence.
Page metadata
Titles, descriptions, headings and canonicals
Page delivery
HTML size, response time and compression
Discoverability
Indexability, links, redirects and click depth
Experience signals
Mobile metadata and PageSpeed data when available
Page-level SEO and performance evidence
For fetched HTML pages, SEONova checks titles, descriptions, headings, canonicals, content depth, images, page weight, response time, compression, DOM size, rendering scripts, mobile metadata, and more.
Audit comparison
Compare stored audit snapshots rather than relying on a single crawl.
Compare audit snapshots over time
Each completed audit keeps its score, issue counts, category scores, crawl statistics, and a new-versus-fixed issue comparison. Use issue lifecycle and audit history to investigate changes between runs.
Crawl schedule
Manual, daily, weekly, or monthly
Crawl scope
Page, depth, and URL-pattern controls
Email updates
Completion and regression notifications
Control the crawl scope
Run an audit when you need it. Configure page and depth caps, include or exclude URL patterns, and choose how robots.txt should be handled.
Three steps. Zero setup tax.
Start with a project URL, decide how much of the site to crawl, then use the evidence in the audit workspace to prioritize the next fix.
Set your crawl scope
Choose the maximum page count and click depth for the audit. Keep robots.txt enabled by default, and add include or exclude patterns when parts of the site should be out of scope.
Run the audit
Start a manual audit when you need an answer. The available crawl volume is governed by your current plan limit.
Investigate the pages behind each issue
Start with the health score and prioritized issues, then drill into affected URLs, crawl facts, recommendations, Core Web Vitals data when available, and changes from prior audits.
The questions every buyer asks.
What SEONova audits, what you can configure, and where to find the resulting evidence.
The audit evaluates crawlability, HTTPS and response security, on-page SEO, content, performance signals, mobile metadata, and structured-data and social signals. Examples include response errors, broken internal links, redirects, robots and sitemap discovery, indexability, titles, meta descriptions, headings, canonicals, duplicate signals, image alt text, response time, viewport setup, JSON-LD, and Open Graph metadata.
Turn a crawl into a clear fix list.
Set up the site you want to inspect, run the crawl within your plan capacity, and work from page-level evidence instead of a vague technical checklist.