serpName the stage before prescribing a fix
When someone says a page is not on Google, ask what evidence they have. A page that Google has not discovered presents a different problem from one that was fetched but not indexed, and both differ from an indexed page with little visibility.
Build a short investigation note with three questions: is the URL discoverable, what does Google report about its indexed state, and does it receive relevant search exposure? The sequence prevents a ranking complaint from turning into unnecessary sitemap edits or an inaccessible page from receiving a purely editorial rewrite.
Check discovery with the website's own structure
Start from a visitor's path. Can a person reach the page through relevant navigation or contextual links? Is it present in the intended public content inventory? A page that exists only because someone knows its exact address has a weak place in the site.
Review the sitemap as an additional discovery aid, then inspect the actual response. A link to a broken or private page does not make the content usable. Keep the discovery check concrete: source page, link destination, final response, and visible content. That record helps developers reproduce the condition.
Hypothetical example: an isolated resource
Suppose a team publishes a detailed template library but never links it from the website. The URLs appear in an export, yet the main navigation and relevant guides still point to an older resource. The team initially plans to rewrite every template introduction.
A review reveals the more immediate problem: the new library has little meaningful connection to the public site. The team adds contextual routes from relevant guides, verifies the responses, and monitors discovery. Rewriting the introductions might still help later, but it would not address the first failure in the chain.
Treat indexed visibility as an editorial question too
Once a page is indexed and technically accessible, ask whether it is the best destination for the queries you want. Does it answer the task clearly? Does it provide evidence, examples, or useful detail that a generic summary lacks? Are the title and page purpose aligned?
Do not infer a penalty from a page's lack of clicks. New content, limited demand, poor fit, and competition can all require investigation. State what is known and what remains uncertain. That discipline is especially important when an automated report offers a confident diagnosis from very little evidence.
Assign the next action to the right owner
Discovery and routing issues usually need publishing or development changes. An intentional exclusion may need no action. Weak content fit requires editorial work. Measurement questions may require better segmentation rather than any page change at all.
Use these distinctions in status reports. Instead of saying SEO is fixed, describe the completed stage and the next observable outcome. A successfully fetched page is not automatically indexed, and an indexed page is not guaranteed relevant traffic. Clear stages make progress visible without promising outcomes outside the team's direct control.
Diagnose the stage first so the proposed fix addresses the actual failure.
Sources & further reading
Official documentation informs this guide. Examples are illustrative, and product interfaces or limits can change.
From search signals to a useful first draft.
SERP.so is in development. Join the waitlist for a workspace that connects research, content review, and publishing.
Join early access ↗