Start here / 03

What does my page inspection actually prove?

A finding is only as strong as the returned evidence. Separate an observed problem, a suggestion and a check that could not be completed.

Match the conclusion to the evidence

A missing title in successfully returned HTML is evidence about that response. It is not proof that Google has never found the page. “Could explain the price more clearly” is advice that needs your judgement, not a measured technical failure.

Use three working labels

These labels help you read a report. Preserve the plugin’s exact observation and limitation beside your own note.

The plugin uses categories such as confirmed, observed, review and unavailable. It also uses found, review and missing status labels. “Found” means present, not necessarily correct. Read the observation, not just its badge.

  • Confirmed problem: the checked material shows an error, such as JSON-LD that cannot be parsed. Keep the evidence and scope.
  • Suggestion: an improvement may help, such as a more descriptive heading. Check the business context before deciding.
  • Unavailable: the request failed or returned too little information for that check. Do not count it as passed, failed or fixed.

Know who is saying what

AI Visibility Studio inspection observations come from the checked response. ChatGPT interpretation explains what those observations might mean. General lessons and published blog articles provide education, not findings about your page. A plan revision is not a fresh inspection.

A detected link does not prove its destination works. Valid JSON-LD syntax does not prove that its facts are correct, that it satisfies Google’s requirements or that it earns an AI citation.

Choose a small action supported by the report

Address a confirmed access or content problem before polishing optional details. If the check is unavailable, recover the check or ask for help interpreting the response. Do not rewrite a complete page solely because a tool failed to read it.

Made-up example / Business coach

Three notes, three different conclusions

A fictional report finds malformed structured data, suggests a clearer service heading and cannot retrieve crawler rules. Repair the malformed code with your website person, review the heading as advice and keep crawl access marked unknown.

One thing to try

Try it on one public page

  1. Copy one observation and its exact evidence into your notes.
  2. Label it a confirmed problem, suggestion or unavailable check.
  3. Write one action that addresses that observation.
  4. State what evidence would show the action worked.

How to check the result

  • Compare the conclusion with the quoted evidence. Remove claims the evidence cannot support.
  • After a change, repeat the same check on the same address. A failed recheck cannot close an earlier finding.

Keep the page address, date and evidence. A page improvement is not a promise of rankings or AI citations.

Words in this guide

Only if you want to look them up.

Sources and further reading

Official documentation for the general guidance. These sources are not inspection findings about your page.

Published Studio article, for further reading: Your Website Has Three Viewers Now. You Do Not Build Three Websites.

Want help with your own website?

Tell us what you’re stuck on →