See which WordPress pages
Google may be missing.

Why WordPress Pages Don't Index Despite Yoast or RankMath

Installing Yoast SEO or RankMath doesn't guarantee your pages get indexed — it gives you tools to control indexing. The distinction matters because both plugins can block content just as easily as they can promote it.

Plugin defaults on secondary content types. Out of the box, Yoast and RankMath set noindex on tag archives, author pages, and date archives. This is usually the right call — those pages rarely offer unique value and Google won't index what it doesn't consider useful. The problem is when that logic bleeds over to legitimate content. Check under Yoast > Search Appearance > Taxonomies (or RankMath > Titles & Meta > Taxonomies) to confirm which content types are set to noindex.

Individual post/page overrides. Every post and page has its own SEO panel where the "Allow search engines to show this post in search results" toggle can be switched off. If a post was drafted or imported with noindex applied, that setting sticks when it's published.

The crawling-vs-indexing gap. WordPress makes it easy to get Googlebot to visit your pages. Actually getting them stored is the harder part. GSC's Coverage report is the right place to distinguish between a blocked page, a crawled-but-not-indexed page, and a page Google simply hasn't visited yet. Those three situations need different fixes.

Thin content on auto-generated pages. WordPress generates a lot of URLs automatically: tag archives with two posts, empty author archives, paginated versions of short category pages. Google crawls many of these and quietly decides not to index them. The "Crawled – currently not indexed" status in GSC almost always means thin, duplicate, or low-signal content — not a technical block.

The "Discourage Search Engines" Setting and noindex on Archives

This is the most common self-inflicted wound in WordPress indexing, and it often goes unnoticed for weeks.

Settings > Reading > "Discourage search engines from indexing this site." This checkbox adds Disallow: / to your robots.txt file, which tells Googlebot not to crawl anything on the domain. It's designed for staging environments. Developers check it, launch the site, and forget to uncheck it. Google Search Console will show widespread "Blocked by robots.txt" errors across Coverage — that's the tell.

Fix: uncheck the box, save, then verify your robots.txt at yourdomain.com/robots.txt no longer contains the Disallow: / directive.

noindex on tag and category archives. Even with the global setting clear, tag and category pages are frequently set to noindex in SEO plugins. In Yoast: SEO > Search Appearance > Taxonomies. In RankMath: Titles & Meta > Taxonomies. Check "Tags," "Categories," and any custom taxonomies. If these pages carry genuine content, switch them to indexable. If they're thin, keep them noindex and redirect your energy to the content pages themselves.

Canonical conflicts on paginated archives. WordPress pagination (/page/2/, /page/3/) can trigger canonicalization issues depending on how your SEO plugin handles them. If page 1 canonicals back to itself but paginated versions don't, you may see GSC flag those URLs as duplicates. Verify canonical tags in GSC's URL Inspection before assuming these pages need direct submission.

Submitting the WordPress Sitemap via GSC and robots.txt

WordPress generates XML sitemaps automatically when Yoast or RankMath is active — but generating a sitemap and submitting it are two different steps.

Where to find your sitemap URL.

• Yoast SEO: yourdomain.com/sitemap_index.xml
• RankMath: yourdomain.com/sitemap_index.xml (same path by default)
• WordPress core (since 5.5): yourdomain.com/wp-sitemap.xml

Submit via Google Search Console. Navigate to GSC > Sitemaps, paste your sitemap URL into the "Add a new sitemap" field, and click Submit. GSC will periodically re-fetch the sitemap and discover new URLs from it. This doesn't trigger immediate crawling — it queues your URLs for Google's regular crawl schedule.

Reference the sitemap in robots.txt. Add a Sitemap: directive to your robots.txt file:

Sitemap: https://yourdomain.com/sitemap_index.xml

This lets any crawler — not just Google — find your sitemap without needing a separate submission step. Both methods should be in place simultaneously; they complement rather than replace each other.

Note on sitemap pinging. Google retired its sitemap ping endpoint (google.com/ping?sitemap=) in late 2023 — sending a ping there accomplishes nothing. Bing's ping endpoint (bing.com/ping?sitemap=) still works and remains valid for Bing indexing. Do not expect a Bing ping to affect Google's crawl behavior directly.

Plugin sitemap settings to verify. Both Yoast and RankMath let you exclude specific content types from the sitemap. If new pages aren't appearing in your sitemap, check whether their post type or taxonomy is excluded: Yoast > Search Appearance > Content Types > toggle "Show in sitemap." A page that's indexable but excluded from the sitemap takes longer to be discovered because there's no signal pointing Google to it.

Getting New WordPress Posts Indexed Faster

Slow wordpress google indexing is mostly a discovery problem. Google crawls established pages on a regular schedule, but a new post that's not in the sitemap, not linked internally, and on a domain with modest crawl frequency can wait weeks before Googlebot notices it.

Build internal links right away. After publishing, link to the new post from at least one already-indexed, regularly crawled page on the site. A link from your homepage, a top category page, or a related post that already ranks gives Googlebot a path to follow. This is the highest-ROI step most WordPress site owners skip.

Confirm the sitemap updated. Visit your sitemap URL directly after publishing and verify the new post appears. If it doesn't show up, the post may be excluded from the sitemap — check the individual post's SEO settings in Yoast or RankMath.

Use GSC URL Inspection for individual priority pages. For high-value content — a new service page, a campaign landing page, a major article — use Google Search Console's URL Inspection tool and click "Request indexing." This queues the specific URL for a crawl. It's manual and limited (roughly 10–12 requests per day per property), so reserve it for pages that matter most.

FastIndexing checks readiness, selects only the signals applicable to the URL and search engine from its up-to-eight-channel layer, and monitors status from D0 through D14. The search engine decides the outcome and timing; no aggregate indexing rate is promised.

Address thin content before submitting. Submitting a 200-word post with no original insight won't produce different results than waiting — Google will crawl it and not store it. The "Crawled – currently not indexed" status in GSC is Google's way of saying the content didn't clear its quality threshold. Fix the page first, then submit.

For a current read on which of your WordPress URLs are indexed and which aren't, the index checker gives you a fast answer without needing GSC access for every URL.

From the Field

Dmytro Puhach · Founder, FastIndexing · 15+ years in SEO

The WordPress indexing issues I see most often aren't mysterious. They're almost always one of two things: a setting that was wrong since before the site launched, or content that Google crawled and decided wasn't distinct enough to store.

The "Discourage search engines" checkbox is almost a rite of passage — I've audited sites that had it checked for six months after launch. The pages were getting traffic from direct links, so nobody noticed there was a problem. That one's easy to find and easy to fix.

The harder situation is when everything looks clean — sitemap submitted, no noindex tags, robots.txt correct — but pages are sitting in "Crawled – currently not indexed." That status almost always points to content: thin category pages, boilerplate product descriptions, auto-generated archives with minimal original content. No submission channel resolves a content quality problem. You fix the page, give Google a clear signal it's changed, and then submit.

Multi-channel submission is genuinely useful for the discovery gap — new posts on sites that aren't crawled daily, freshly migrated URLs, content that's solid but buried. It's not a substitute for fixing what's actually broken.

FAQ