Your service page opens normally, but a customer cannot find it on Google. Rewriting the headline or submitting the URL repeatedly may address the wrong problem. First establish whether Google can access the intended page, whether indexing is permitted and which version Google has selected.

This guide is for a business owner commissioning a focused diagnosis. It does not replace a full SEO assessment or promise indexing, rankings or enquiries. Use the exact missing URL, not just the website's homepage.

The illustration separates crawl, indexing and canonical controls conceptually. It is not a screenshot of Google Search Console.

Collect one evidence pack before changing anything

Write down the full URL, the business purpose of the page, when it was published or moved and the date the problem was noticed. Save the relevant Search Console status and last-crawl information. Ask what changed recently: a release, an SEO plugin setting, a domain move or a hosting rule.

For example, a page that moved last week needs its old and new addresses checked together. A newly created page with no internal links needs a different investigation. Treat these as hypotheses until the response and inspection evidence support them.

Separate Google's stored view from today's page

Google's URL Inspection documentation distinguishes indexed information from a live test. Inspect the exact address in the appropriate Search Console property, record the reported reason and then compare it with the current live result. A passing live test does not guarantee indexing, and it does not predict Google's chosen canonical.

Ask the reviewer to state both dates: when Google last assessed the indexed version and when the current page was tested. Otherwise a fixed release can appear broken in an older report, or an older successful crawl can conceal a new production error.

Check the production response, including headers

A page visible to a signed-in editor may be inaccessible to a public visitor. Check the final address, redirects, HTTP response and returned page content. An error page that looks polished is still an error, and a login screen is not the intended service page. Review the production hostname rather than a staging preview.

Google documents two noindex mechanisms: page metadata and the HTTP X-Robots-Tag header. Both need checking. A correct HTML template does not cancel a conflicting response header. The same documentation explains that robots.txt must allow access for Google to discover a noindex rule; robots.txt itself is not a supported place to declare noindex.

Do not remove every exclusion across the website. Private pages, preview environments and deliberately excluded content may need those controls. Approve a change for the intended public URL and confirm its scope before deployment.

Resolve duplicate signals without creating more pages

Google's canonical guidance explains how redirects, canonical declarations and sitemap inclusion signal a preferred URL. Review these together with internal links. An old service address in navigation and a new one in the sitemap send inconsistent signals.

For a genuine duplicate, decide which address should remain the public destination and implement a coherent plan. Do not create another near-identical page to escape the report. For distinct services, make the difference useful and clear rather than forcing them into one page merely because their keywords overlap.

A focused technical SEO review of the missing page and its indexing signals can establish the next step. Request a Page Indexing Diagnosis with the exact URL and the reported Search Console reason.

Match the response to the reported problem

  • Access or fetch failure: resolve the actual delivery issue, then retest the final public page.
  • Unexpected noindex: locate the responsible template, plugin or header rule and change only the intended scope.
  • Alternate or duplicate: compare the chosen version with the intended version before changing canonicals.
  • Accessible but still not indexed: review discovery, duplication and the page's usefulness. Another indexing request alone is not a content strategy.

This is a triage sequence, not a claim that each Search Console label has one universal fix. Keep a record of what was observed, what was changed and what remains uncertain.

Validate the release and follow the evidence

After an approved fix, retest the live response and relevant internal links. Keep the sitemap aligned with the intended canonical URL. Use the website move and redirect checklist when a relocation is involved. Request indexing where appropriate, then monitor the outcome without promising a specific recrawl date.

The useful deliverable is a diagnosis and verified implementation, followed by observed search behaviour. Those are different stages. Until Search Console or other verified data shows a change, do not report improved visibility, traffic or leads.

Request a Page Indexing Diagnosis to discuss the missing page, recent changes and evidence available from Search Console. The form below preserves this article's context; never send account passwords or private verification tokens.

Official Google documentation reviewed 20 October 2026. Examples and the evidence-pack method are editorial guidance, not a diagnosis of your website.