A score is a summary. It is not an explanation.
You can learn more from one well-evidenced finding than from a hundred warnings that do not say where they came from. A useful SEO report should help you make a decision without opening a second tool, guessing at the cause or wondering whether the issue affects the page you care about.
Here is the standard to hold a report to.
1. A finding should show the evidence
“Missing meta description” is a label. The useful version is:
- Observed: the page has no
<meta name="description">tag. - Expected: a description of roughly 70–160 characters that represents the page.
- Affected page: the exact URL where the check failed.
- Why it matters: search and sharing surfaces have less context to work with.
- Recommended fix: add a description that is specific to the page.
Without the observed value, you cannot tell whether the checker saw the live page, a cached version, a redirect or a different URL. Without the expected result, you cannot tell what “fixed” looks like.
This is why nanoSEO findings are structured around evidence, the affected URL, the expected result and a recommended action. A finding should be verifiable, not just believable.
2. A finding should name the page
Site-wide issues are rarely site-wide in the same way. One page may have a duplicate title, another may have no H1, and a third may be blocked by a robots directive. Those are different problems with different fixes.
A report should show the affected URL beside each finding, and page-level results should make it possible to see which pages are healthy and which need attention. A summary without page context turns a useful audit into a scavenger hunt.
3. Priority should be visible
Not every issue deserves the same response.
A canonical conflict on a page you want indexed is more urgent than an image without declared dimensions. A missing meta description affects how a result appears; a missing favicon is usually polish. The report should make that distinction clear instead of flattening everything into one warning count.
Use priority as a starting order, not an instruction to ignore everything else. A low-priority issue can still be worth fixing when you are already editing the page.
4. The report should explain the categories
An overall score is easier to interpret when it is broken into sections. nanoSEO reports show category scores for technical health, content quality and search appearance, followed by the checks that contributed to them.
That structure helps you answer a practical question: is the page fundamentally inaccessible to search engines, or is it technically fine and simply under-explained?
The categories are not separate products. They are different views of the same page-level evidence.
5. The next action should be obvious
A report is finished when you know what to change.
For a small fix, that may be a direct instruction: update the canonical URL to the live page URL. For a larger issue, it may be a sequence: decide the preferred title, update it in the CMS, publish, then re-check the page.
nanoSEO reports include recommended fixes and a copy-ready prompt for an AI coding agent. The prompt gives an agent the report context, affected URLs, evidence and recommendations. It is still your responsibility to review the suggested change before publishing it.
6. Limitations should be stated plainly
A report should tell you what it did not inspect.
nanoSEO checks publicly reachable pages. It does not log in, bypass paywalls or access controls, and it cannot verify business information that is not on the page. It cannot promise rankings or traffic. If a check cannot be completed because the required data is missing, the report should not pretend the page passed or failed.
Clear limitations make the rest of the report more trustworthy. A tool that claims certainty everywhere is usually hiding an assumption.
A fifteen-minute review routine
When a new report lands, read it in this order:
- Open the high-priority findings and confirm the affected URL.
- Read the observed value against the expected result.
- Fix anything that prevents the page from being indexed or understood.
- Read the content and search appearance findings together.
- Assign the remaining fixes by effort and impact.
- Export the report before its retention window ends.
For a free check, that window is 2 days. For a paid audit, detailed report data is kept for 14 days.
Check the evidence, then act
The best SEO report does not make SEO sound complicated. It makes the next change obvious.
Run a free one-page check at nano-seo.com, or compare paid audits on the pricing section.