Skip to main content
VaultDevLabs
Evidence guide

WordPress pages not showing in Google

A practical checklist for WordPress pages that are public but not appearing in Google search results.

Use Search Visibility ScannerRequest Site Rescue Review
Evidence before edits
No automatic changes
Clear next action
Decision map

01 · Observed signal

A published page loads in the browser but does not appear for a site: search or exact title search.

02 · Evidence to inspect

Check noindex, robots.txt, HTTP status, redirects, canonical tags, sitemap inclusion, and internal links.

03 · Safe next move

Run the relevant diagnostic tool first so you have evidence before changing live site settings.

Start here

Understand the problem before changing the system.

When WordPress pages are not showing in Google, the cause can be technical discovery, indexing signals, redirects, canonical tags, robots rules, sitemap gaps, thin duplicate content, or simply not enough crawl time. The useful first step is to separate discoverability problems from ranking expectations.

Signals

What the issue can look like.

  • 01A published page loads in the browser but does not appear for a site: search or exact title search.
  • 02Search Console reports crawled, discovered, excluded, duplicate, noindex, or alternate canonical states.
  • 03New or updated pages are missing while older parts of the site appear normally.
  • 04Only certain templates, products, categories, or landing pages are affected.

Possible causes

What may have interrupted the expected path.

  • The page is noindex, blocked, redirected, canonicalized elsewhere, or missing from internal links and sitemaps.
  • Sitemap or internal linking paths do not expose the page clearly.
  • A migration, staging setting, SEO plugin change, or template rule changed indexability.
  • Google has not crawled the page yet, or it has crawled it but chosen not to index it.

Evidence checks

What to verify first.

  • Check noindex, robots.txt, HTTP status, redirects, canonical tags, sitemap inclusion, and internal links.
  • Compare affected URLs with similar URLs that already appear in Google.
  • Use Search Console URL Inspection where available to separate crawl, index, and canonical signals.
  • Use the Search Visibility Scanner to collect a first-pass view of pages search engines may not discover.

What not to do

  • Do not assume every missing page is a technical fault; some pages may be crawled but not selected for indexing.
  • Do not promise rankings, traffic, or indexing after a single settings change.
  • Do not submit URLs repeatedly without checking noindex, canonical, sitemap, redirect, and internal link evidence.
  • Do not make site-wide SEO plugin changes until you know whether the issue is page-level or template-level.

Decision path

Move from signal to evidence to action.

Use the smallest safe step that resolves uncertainty. Implementation comes after the evidence is clear.

  1. 01Run the relevant diagnostic tool first so you have evidence before changing live site settings.
  2. 02Request a Site Rescue Review if the evidence is unclear, recurring, or affects pages that matter commercially.
  3. 03Custom fix work is quoted after review, once the likely cause and scope are clear.

Quick answer

What does this usually mean?

When WordPress pages are not showing in Google, the cause can be technical discovery, indexing signals, redirects, canonical tags, robots rules, sitemap gaps, thin duplicate content, or simply not enough crawl time. The useful first step is to separate discoverability problems from ranking expectations.

First check

What should be checked first?

Check noindex, robots.txt, HTTP status, redirects, canonical tags, sitemap inclusion, and internal links.

Need a human decision?

Check the evidence before changing a live system.

Start with the Search Visibility Scanner to gather indexability and discovery signals. If the evidence is unclear or commercially important pages are affected, request a Site Rescue Review before broad SEO changes.

Use Search Visibility ScannerRequest Site Rescue Review