NovaBrain severity
Supported findings are ordered by the severity and confidence encoded in the active NovaBrain criterion, not by a promised ranking effect.
A source-aware technical checklist that prioritizes supported findings and records fresh rechecks.
Site Health Audit evaluates captured project URLs against supported NovaBrain SEO and AEO checks, orders findings by NovaBrain severity and records later evidence-based rechecks.
Why it is useful
A wall of red and green checks tells you something is wrong but not what to fix first or whether a green even means anything. Site Health Audit grades your crawl against a defined criteria library, keeps missing evidence separate from real pass and fail, and turns the result into a ranked work-list that jumps straight to the affected pages.
Supported findings are ordered by the severity and confidence encoded in the active NovaBrain criterion, not by a promised ranking effect.
A finding shows its captured evidence and available guidance; an AI draft is offered only when that action and model are configured.
A later crawl can re-run the same measured check. Findings update when the required fresh evidence is available.
Data and evidence
Site Health Audit reads your crawl and grades it against a defined criteria library. Its health percentage is calculated from graded checks only: where the crawl lacks the signal a criterion needs, that criterion is counted as needing evidence rather than as a pass. That separation is why a green here means something was measured.
Crawl, sitemap, optional GSC
Evidence-gated audit criteria
Severity-ranked repair plan
The health score uses graded checks only; checks awaiting another source remain in their own evidence state.
Core capabilities
The audit turns a crawl into a ranked work-list: errors, warnings and passes with a severity and an affected-page count per criterion, a fix-first queue that jumps straight to the page at fault, the sitemap view alongside it, and the history of earlier runs so a change can be seen rather than assumed.
The audit runs your crawl against the active NovaBrain criteria and grades each check as error, warning, or pass, with the health score computed only from checks that could actually be graded. Checks the crawl lacks evidence for are held out as needs-evidence, and offline-only or manual checks get their own states, so a green is always a real pass on captured data. The evidence strip shows exactly which sources, crawl, criteria, Search Console, and domain verification, back the grade.
Every graded issue is ranked by severity and number of affected pages into a single prioritized queue covering both crawl findings and criteria checks. Each row carries its evidence source and a link that opens the precise Crawl Explorer view, the missing-title list, the broken-status lane, the thin-content filter, so you go from problem to page in one click. The same builder powers the standalone Fixes tab, so the priority order never contradicts itself.
The Sitemaps tab fetches and parses your XML sitemap and cross-references it against the crawl to expose bad entries, indexable pages missing from the sitemap, and declared-but-uncrawled URLs, with a coverage percentage and lastmod freshness. The History tab keeps one row per crawl, date, duration, URLs crawled, errors, and trends health over time from the real run ledger. Both stay honest that Google submission and index coverage are not connected, so acceptance by Google is never implied.
How the work moves
Crawl the site, grade it against the criteria, work the queue from the top, then verify and track. Verification re-runs the same criterion against a fresh crawl, so a fix is closed by new evidence rather than by someone marking it done.
Novaverb crawls your project and captures the status, content, and directive signals every criterion reads.
The audit engine runs the active criteria library and grades each check, holding out anything it lacks evidence to judge.
Open the fix-first queue, start with the top blocker by affected pages, and click through to the exact URL list.
Re-crawl to confirm a fix, then watch the health score and issue counts trend on the History tab.
Built around real work
Run one audit each crawl and hand engineering a severity-ranked list where every item links to the pages to fix.
Track each client's health score and error trend across crawls and export the graded criteria list for reporting.
See the single top blocker and its affected page count without needing to interpret a full technical report.
Connected outcomes
Fix & Improve
Make new pages reachable through clean crawl paths, accurate sitemaps, indexable directives and supported submission methods.
Open workflowFix & Improve
Fix the issues that combine verified severity, meaningful reach and clear affected URLs before lower-impact cleanup.
Open workflowFix & Improve
SEO work fragments when research, crawl evidence, content decisions and reporting lose their shared project context.
Open workflowDiscover & Diagnose
Pages become hard to discover when internal links, crawl depth, sitemaps or indexability signals leave no clear path.
Open workflowMeasure & Prove
Compare timestamped crawl evidence from before and after the change, then verify that the failing condition is gone.
Open workflowDiscover & Diagnose
Interpret the change by metric, source and comparison window before deciding whether it is good, bad or only contextual.
Open workflowResources
Written by the team that built it, and free to read without an account.
Step-by-step walkthroughs, five minutes each.
What the terms on this page actually mean.
Run the idea on a real URL, no account needed.
How this works once you are inside a workspace.
Connected products
Frequently asked questions
Clear answers about data, availability and how the product fits into the wider workflow.
It is the percentage of graded checks that passed, where graded means error, warning, or pass. Checks the crawl could not provide evidence for are excluded, so the score never inflates by counting ungraded checks as passing.
A check is needs-evidence when the crawl did not capture the signal it reads, and manual when there is no automated detector for it. Both are shown as their own states rather than being forced into a pass or fail.
No. It cross-references your fetched XML sitemap against the crawl to find coverage gaps and bad entries, but it is explicit that Google submission and index-coverage state are not connected.
Yes. The Overview and Issue Explorer views export the graded criteria list, including status, group, severity, affected URLs, the evidence basis, and the exact pass condition, as CSV.
Technical SEO & Crawl
Start with a real project, keep unavailable data visible and follow the connected workflow when the result is ready for action.