Reading your audit

What the findings mean, why each one cites a rule, and how to tell a partial crawl from a clean one.

After a crawl finishes, Noverva audits every page it managed to read and raises findings. This page explains how to read them.

Every finding cites its rule

A finding is not an opinion. Each one carries:

The rule that raised it, by identifier, so you can see exactly what was checked.
The evidence — the actual value found on the page, not a paraphrase.
An explanation of why it matters.
A recommendation, which is the smallest change that would clear it.
The page, linked, so you can go and look.

If a finding cannot explain itself, it does not ship. The database rejects one with an empty explanation, which is a deliberate constraint rather than a convention somebody might forget.

Scope: site or page

Findings are either about a single page or about the site as a whole. A missing meta description belongs to a page. A site with no sitemap belongs to the site. The distinction matters when you are deciding what to fix first: a site-scope finding usually costs one change and clears everything at once.

Partial crawls are reported as partial

If Noverva could not fetch every page it intended to, the run is marked partial, and the pages it missed are excluded from the counts rather than counted as healthy.

This matters more than it sounds. A crawl that reached 30 of 100 pages and found no problems has not told you the site is clean — it has told you that 30 pages are clean and 70 are unknown. A tool that reported "0 issues" there would be lying by omission.

The run summary always shows what was fetched, what failed, and what was skipped.

What the audit does not check

Anything requiring JavaScript execution. Noverva reads the HTML your server returns. A page whose content is assembled entirely in the browser will look thin, and that is a real finding rather than a false one — most crawlers see the same thing.
Anything off your own site. Noverva crawls only domains you have connected. It does not fetch competitor pages.
Rankings. An audit says what is wrong with a page, not where it sits in a result list.

Re-crawling

Sites can re-crawl on a schedule, and the interval available depends on your plan. A re-crawl produces a new audit and keeps the old one: page captures are never overwritten, so a finding that disappears can be traced to the change that cleared it.

Every finding cites its rule

A finding is not an opinion. Each one carries:

The rule that raised it, by identifier, so you can see exactly what was checked.

The evidence — the actual value found on the page, not a paraphrase.

An explanation of why it matters.

A recommendation, which is the smallest change that would clear it.

The page, linked, so you can go and look.

If a finding cannot explain itself, it does not ship. The database rejects one with an empty explanation, which is a deliberate constraint rather than a convention somebody might forget.

Scope: site or page

Partial crawls are reported as partial

If Noverva could not fetch every page it intended to, the run is marked partial, and the pages it missed are excluded from the counts rather than counted as healthy.

The run summary always shows what was fetched, what failed, and what was skipped.

What the audit does not check

Anything requiring JavaScript execution. Noverva reads the HTML your server returns. A page whose content is assembled entirely in the browser will look thin, and that is a real finding rather than a false one — most crawlers see the same thing.

Anything off your own site. Noverva crawls only domains you have connected. It does not fetch competitor pages.

Rankings. An audit says what is wrong with a page, not where it sits in a result list.