SEO

How to investigate a page that is missing from Google Search

Work through the page, access, indexing and content questions before deciding what to fix.

By Graphic Core   /   Published
Monthly guide series: December 2021

A hand holding a magnifying glass over a grid of cards with one dark circular mark.

Define which page is missing

Start with the exact URL and the search outcome you expected. A page may be missing from the index, indexed but not visible for a particular query, or replaced in results by another version. Those are different situations. Search results vary, so a single search from one device does not establish the full status of a page.

Confirm that the page exists for a clear customer purpose and that it is intended to be public. A private document, old thank-you page or deliberately retired URL may not belong in search results. Record the address, intended audience and date of the check so a colleague can reproduce the investigation.

Open the page as a visitor

Visit the exact address in a normal browser and check that the final page loads, the content is readable and the main links work. Does the URL redirect elsewhere, ask for a login or display an error? A page that looks like an error but returns a success response can also be confusing; ask a developer to inspect the actual response where needed.

Check the public production domain rather than a staging address and make sure the page contains the information the visitor expects. If the destination is an intentional replacement, update internal links to it. If the page has recently moved, allow time for search engines to discover the change while confirming the technical route.

Check access and indexing instructions

Ask a developer to review robots.txt, page-level noindex instructions and relevant response headers. Google must be able to access a page to observe its contents and instructions. A blocked URL and a noindex page require different decisions. Removing a restriction is appropriate only when the page is meant to be public and eligible for search.

Authentication is an access control, not a search-indexing preference. Do not make confidential information public just to test an index report. If the page should remain private, keep the protection in place and remove it from public discovery routes where appropriate. Review the site’s launch settings for accidental restrictions.

Use Search Console as evidence

If you have access to the correct Search Console property, inspect the exact URL and read the current report in context. The tool can show information Google has recorded and offers a live test for certain checks. An indexed report and a live test may refer to different moments, so compare their dates and do not treat them as identical.

Look at the selected canonical, crawl or indexing information and any stated reason for exclusion, then follow the relevant documentation. A submission or recrawl request does not guarantee indexing or ranking. Avoid repeatedly requesting indexing without resolving an underlying access problem or assessing whether the page is genuinely useful.

Review duplication and discovery

Check whether the same or substantially similar content is available at another address and whether the sitemap, canonical annotation and internal links point consistently to the preferred version. A search engine can select a different canonical from the one the site suggests. Examine why before changing settings across the whole website.

Follow a route from the homepage or a relevant service page to the missing page. Is there a clear ordinary link with descriptive text? A sitemap can help communicate preferred URLs but does not replace a usable site structure. Review whether the page provides something distinct and valuable for the intended reader.

An illustrative triage record

Imagine a team reviews nine important URLs: four have an unintended noindex instruction, three correctly redirect to replacement pages and two return temporary server errors. The team should remove noindex only from the four pages intended for public search, update its records for the three valid replacements and ask the host to investigate the two errors.

These numbers are an illustrative example, not measured results. They are categories in a small fictional review, not traffic or ranking data. The actual causes can differ, and a page may have more than one issue. Prioritise the URLs whose resolution will help real customers complete an important task.

ILLUSTRATIVE CHART

Example review of nine URLs

  • Unintended noindex4 URLs
  • Valid redirects3 URLs
  • Server errors2 URLs
Illustrative example, not measured results. Each bar represents one category in a fictional review.

Compare the report with the live page

Write down whether the report describes an indexed record or a live test, and note when each was captured. A live page can be repaired before an older indexed report changes, while a page that once worked may now return an error. Check both observations against the deployment history instead of assuming the two views must immediately agree.

If another URL is selected as canonical, inspect both destinations and their content. Look for inconsistent internal links, redirects, sitemap entries or duplicate content, then decide whether the selected version is actually a problem for visitors. Avoid changing every page based on one ambiguous report.

Prioritise a small investigation

Start with pages that support an active service or answer an important customer question. For each one, record its intended URL, observed response, access rules, internal link and the person who can fix the issue. Group similar causes only after checking a representative example; different templates can have different settings.

After an agreed fix, verify the live outcome and allow time for reports to update. If the page is accessible but offers little distinct help, improving its content may be more useful than resubmitting it. Keep expectations clear: discovery and indexing decisions are made by the search engine.

Decide, fix and recheck

Write down the observed problem, the person responsible, the agreed change and how it will be verified. Fix one issue at a time where possible, then test the public page and monitor the appropriate report after the search engine has had time to recrawl. Keep a record of the previous setting so an incorrect change can be reversed.

Before concluding, ask whether the page is useful, accessible, intended for indexing and connected from relevant pages. A technically correct page still may not be selected or rank for a particular search. The goal is a clear, honest investigation rather than a promise that every URL will appear immediately.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION