WordPress Pages Not Indexed: A Practical Google Search Console Guide

First separate discovery, crawling and indexing

A page can be missing from Google for different reasons. Google may not know its URL, may not have crawled it yet, or may have crawled it and decided not to include it in Search. Those situations need different evidence, so start with a few specific URLs instead of changing the whole site.

A site: search can show some results, but Google says search operators have retrieval limits. An empty result is not a reliable diagnosis. For a page you manage, use Search Console URL Inspection to see what Google reports about that exact URL and to test whether the live page is accessible to Google.

Read the URL Inspection result before editing WordPress

Open the correct Search Console property and enter the complete page URL, including the preferred protocol and hostname. Compare the indexed result with the live test. Note whether Google reports that it has crawled the URL, whether indexing is allowed, and which canonical URL it selected. Save the exact status and any explanation shown.

A live test answers a narrower question than “is this page indexed?” It checks what Google can access now; it does not prove that the page is already in Google Search. Requesting indexing for an individual URL is available in Search Console, but submission is a request and does not guarantee inclusion or a particular timing.

Check the site wide picture and the page itself

Use the Page Indexing report for the site wide pattern and the URL Inspection report for individual pages. The report does not include URLs Google does not know about, so a short list of affected pages can help you identify whether the issue concerns one template, one section, or the whole site.

Ask a WordPress developer to review the page’s HTTP response, robots directives, canonical URL, internal links and rendered content. Confirm that the preferred version is reachable without a login and that the page contains the content visitors expect. A robots.txt rule and a noindex directive work differently; the developer should identify the actual signal before changing settings.

Treat sitemaps as discovery help, not an indexing switch

Check that the sitemap lists the preferred, public URLs and that the sitemap can be fetched. Useful internal links also help crawlers find important pages. Google describes sitemaps as a way to help discovery, while making clear that a submitted URL is not guaranteed to be crawled or indexed.

Avoid repeatedly resubmitting the same unchanged sitemap or making several SEO changes at once. Record what was changed and when, then monitor the relevant Search Console reports. A delay alone does not show that a WordPress plugin is broken, and adding a plugin cannot determine why Google chose not to index a page.

Prepare a useful brief for diagnosis

List a few affected URLs, when the problem began, the exact URL Inspection messages, and any recent site or content changes. Note whether all pages share a template or category. Do not send passwords or customer data in an initial contact form.

For a technical review, ask the developer to explain the evidence, proposed change and acceptance check before touching the live site. Changes to WordPress settings or theme code should be evaluated and tested on a staging copy first, then checked on the public URL and in Search Console. Store Armory can scope that investigation and quote the work before it starts.

Practical checklist

• List a small set of exact affected URLs and the correct Search Console property
• Save the URL Inspection indexed result and live test details for each example
• Check sitemap access and whether the preferred URLs are linked internally
• Record recent publishing, migration or configuration changes and their dates
• Ask for a staging test plan and a clear check for each proposed change

Need help applying this to your website?

Request a tailored quote