A WordPress page can be missing from Google for several different reasons. It may be blocked by a noindex directive, point to the wrong canonical URL, return an error to crawlers, remain undiscovered, or provide too little unique value to justify inclusion in search results.
The fastest way to find the cause is to inspect the exact URL in Google Search Console, then work through the technical and content checks below. Requesting indexing should be the final step, not the first one.
1. Check whether Google has indexed the page
Begin with a site-specific Google search:
site:example.com/your-page/
Replace the example with your domain and page path. If the page does not appear, that is a useful clue, but it does not explain the cause by itself.
Next, open Google Search Console, select the correct property, and use URL Inspection. Enter the complete published URL. The report may show that the page is indexed, excluded, discovered but not crawled, or affected by a technical problem.
Check that you inspected the correct version of the URL. HTTP and HTTPS versions, URLs with or without a trailing slash, staging addresses, and parameterized URLs can all produce different results.
2. Remove accidental noindex directives
A noindex directive tells search engines not to include a URL in their search results. WordPress SEO plugins can add it at the page level or through global settings for pages, posts, archives, or custom post types.
Review the page settings
Edit the page and open your SEO plugin’s advanced or robots settings. Confirm that the page is allowed to appear in search results. Depending on the plugin, this may be labelled “Index,” “Allow search engines to show this page,” or “Robots.”
Also confirm that the page is published and public. Drafts, private pages, password-protected pages, and pages awaiting review are not normally available for public indexing.
Inspect the published HTML
View the page source and search for a directive like:
<meta name="robots" content="noindex">
Look for an HTTP response header as well:
X-Robots-Tag: noindex
An X-Robots-Tag may come from server configuration, a security plugin, a caching system, or custom code. If you recently changed a global SEO setting, review those rules too. A site-wide setting can override an individual page’s intended status.
3. Verify the canonical URL
A canonical link identifies the preferred URL when similar or duplicate versions exist. For a standalone page, it will usually point to that page’s own preferred address:
<link rel="canonical" href="https://example.com/your-page/">
Investigate if the canonical points to the homepage, an old URL, a category archive, a staging domain, or another page with different content. Google may choose to index the canonical target rather than the URL you inspected.
Check canonical settings in your SEO plugin, redirection plugin, theme, and custom templates. Make sure the HTML contains one clear canonical tag, then clear WordPress, server, CDN, and browser caches before testing again.
4. Test crawlability and robots.txt
Google needs to fetch a page before it can evaluate it. Confirm that the URL returns a successful public response rather than a 403 or 404 error, redirect chain, login prompt, maintenance screen, or server error.
Open the page in a private browser window while logged out. This can reveal membership restrictions, password protection, security challenges, or other conditions that are not visible to an administrator.
Then review your robots.txt file at https://example.com/robots.txt. Make sure it does not disallow the page path or a folder containing important resources. Robots.txt controls crawling; it is not a reliable way to remove a URL that Google already knows about.
For a more detailed process, see How to Fix WordPress Robots.txt Problems. Security plugins and host-level firewalls deserve particular attention if they block Googlebot or display repeated challenge pages.
5. Check internal links and the XML sitemap
Google can discover a page through internal links, XML sitemaps, external links, and other known URLs. Link to important pages naturally from relevant content, navigation, or other useful sections of the site.
Open your XML sitemap and confirm that the page is listed. Common locations include /sitemap_index.xml and /wp-sitemap.xml. If the URL is missing, check whether your SEO plugin excludes that post type, page, taxonomy, or content status.
A sitemap helps with discovery but does not guarantee indexing. It should contain only public, canonical, indexable URLs. Do not add pages to a sitemap while they still have a noindex directive or point to another canonical URL.
6. Assess the page’s content and usefulness
If the technical signals are correct, the page may simply offer too little distinct value. This often affects short service pages, near-duplicate location pages, thin product variations, tag archives, and pages created mainly to target a keyword.
Review the page from a visitor’s perspective. Does it answer a specific question or support a clear task? Add original details, practical examples, relevant context, and useful next steps. Remove repeated sections and make the title and opening paragraphs accurately describe what the page provides.
Use internal links where they help readers, but avoid forcing the target keyword into every heading or paragraph. Search visibility depends on the overall quality and relevance of the page, not on repeating one phrase.
Inspect the published output
On page-builder sites, check the published page rather than relying only on the visual editor. Look for broken links, duplicate sections, inaccessible content, poor mobile rendering, and important information that appears only after JavaScript runs.
7. Request indexing after the fix
Once the page is public, crawlable, indexable, correctly canonicalized, internally linked, and useful, return to URL Inspection and select “Request indexing” if the option is available.
The request asks Google to recrawl the URL; it does not guarantee inclusion or an immediate result. Monitor the URL in Search Console after making changes, and avoid repeatedly submitting the same unchanged page. Repeated requests do not replace fixing the underlying problem.
A practical troubleshooting checklist
- The page is published, public, and returns a successful response.
- No page-level or HTTP-header
noindexdirective is present. - The canonical URL matches the preferred public URL.
- Robots.txt and security tools do not block crawling.
- The page appears in the XML sitemap when appropriate.
- Relevant pages link to it internally.
- The content is original, useful, and not a thin duplicate.
- Google Search Console has been checked after the changes.
When a deeper WordPress audit is worthwhile
Some indexing problems come from interactions between SEO plugins, custom post types, page-builder templates, redirects, caching rules, and server configuration. In those cases, changing one setting at a time can leave the underlying conflict in place.
This guide to WordPress maintenance retainers explains one approach to ongoing site support. A technical audit can also help identify conflicting directives, incorrect templates, or server responses that are difficult to spot from the WordPress editor.
Frequently asked questions
How long does Google take to index a corrected WordPress page?
There is no fixed timeframe. Google must recrawl and evaluate the URL, and submitting a request does not guarantee inclusion. Keep the page accessible and monitor its status in Search Console.
Can a page be indexed if robots.txt blocks it?
A robots.txt rule can prevent Google from crawling the page. Google may still know that the URL exists through links or other signals, so robots.txt should not be treated as a complete removal method.
Should every WordPress page be indexed?
No. Utility pages, duplicate archives, internal search results, and private or low-value pages may not need search visibility. Indexing decisions should reflect the page’s value and role in the site structure.
What does “Crawled – currently not indexed” mean?
It means Google crawled the URL but has not included it in the index at present. Review duplicate content, canonical signals, internal links, and whether the page offers enough unique value before requesting another crawl.
Conclusion
When a WordPress page is missing from Google, start with evidence from URL Inspection rather than sending repeated indexing requests. Check for noindex directives, confirm the canonical URL, test crawlability, review robots.txt and server responses, verify internal links and sitemap coverage, and strengthen the page where its value is unclear. Once those signals agree, Google has a clearer basis for evaluating the URL.