Technical SEO audit
Inspect the title, description, canonical URL and indexing instructions in the HTML your server sends. Each result identifies the page and the value that prompted it.
Find a conflicting canonical
Two branches of a clinic have different opening hours. A patient searches for the north branch but lands on the south branch page. Start with the north URL and review its final address, HTML title and canonical link. If that link names the south branch, confirm which address should represent the north branch before editing the template.
The report also records generic robots meta directives and the returned X-Robots-Tag. A deliberate noindex on a duplicate page can be the correct choice.
Compare neighboring pages
A standard scan checks one public page. On extended-scan hosts, look at the titles and descriptions of distinct pages in the sample. Two matching descriptions can reveal a shared template that says little about either branch. JSON-LD checks report syntax and observed types. Rich-result eligibility depends on additional requirements.
Verify the fix at its source
After publishing, scan the same URL again and compare the evidence. In CiteMaybe’s documented three-page self-audit, warnings fell from nine to three after edits including page-specific descriptions and canonical links. That comparison measured rule outcomes. Google’s indexing and display decisions require separate observation.
Run an audit
Start with a public HTTPS page that a customer would use. The free report records which checks ran and the evidence behind each finding.