You hit publish, wait a few days, and search your own headline on Google. Nothing comes up. If a WordPress page is not indexed, the frustrating part is that WordPress itself is rarely the real reason: something in a settings screen, a plugin, or the content itself is quietly telling Google to skip the page.
This isn’t a rare glitch. It’s one of the most common WordPress SEO problems, and it almost always traces back to one of a handful of causes. Below is the order to check them in, from the two-minute settings fix to the deeper content problem that takes longer to solve.
Why Isn’t Google Indexing Your WordPress Pages?
A WordPress page usually fails to get indexed for one of four reasons: search engine visibility is blocked in WordPress settings, a noindex tag is set on the page itself, robots.txt is blocking the URL, or Google crawled the page and decided it wasn’t worth adding to the index yet. The first three are settings problems that take minutes to fix. The fourth, usually shown in Search Console as “Crawled, currently not indexed,” means the content itself needs work before Google will index it.
The order matters. Checking Search Console before ruling out the simple settings issues wastes time chasing a content problem that doesn’t exist. Start with the site-wide toggle, then the page-level tags, then the sitemap and robots.txt rules, and only then start rewriting content.
Check This First: Is WordPress Set to Discourage Search Engines?
Every WordPress install has a setting called “Discourage search engines from indexing this site” under Settings, then Reading, and if it’s checked, no page on the site gets indexed no matter what else is right. This setting exists for staging and development sites, and it’s meant to be temporary.
It gets left on by accident constantly, especially right after a site migrates from staging to a live domain, or after a developer hands off a finished build without a final settings review. This single checkbox has quietly kept entire WordPress sites out of Google for months.
- Go to Settings, then Reading, in the WordPress dashboard
- Find “Search engine visibility” near the bottom of the page
- Make sure “Discourage search engines from indexing this site” is unchecked
- Click Save Changes
This setting controls a site-wide signal, not a per-page one. Even with it unchecked, individual pages can still carry their own noindex tag from an SEO plugin, which is covered further down.
How Do You Check a WordPress Page’s Indexing Status?
The only reliable way to check a WordPress page’s indexing status is Google Search Console’s URL Inspection tool: paste the exact page URL into the search bar at the top of Search Console and it will report whether the page is indexed, and if not, exactly why. Guessing based on a Google search for the page title is not reliable, since indexed pages can still take time to show up for specific queries.
- Open Google Search Console for the site (see the setup guide linked below if it isn’t connected yet)
- Paste the full page URL into the inspection bar at the top
- Read the status: “URL is on Google” means it’s indexed, anything else names the specific block
- Click “Test Live URL” to check the current version of the page, not Google’s last crawl
- If the live test passes and the page just needs to be recrawled, click “Request Indexing”
Search Console needs to be verified for the domain before any of this works. If it isn’t set up yet, that’s step one before any of this troubleshooting: setting up Google Search Console for WordPress takes about 15 minutes and unlocks the URL Inspection tool along with the rest of this process.
“Crawled” vs “Discovered, Currently Not Indexed”: What’s the Difference?
“Discovered, currently not indexed” means Google knows the URL exists but hasn’t crawled it yet, usually a crawl budget or priority issue. “Crawled, currently not indexed” means Google visited the page and chose not to add it to the index, which almost always points to a content quality problem rather than a technical one. Both statuses show up in the Page Indexing report inside Search Console, and they need different fixes.
An analysis of 213 Google Search Console profiles by SEOTesting found that 89% of the sites had at least one “Crawled, currently not indexed” entry, making it one of the most common indexing statuses site owners run into. Having a few pages in this status is normal. Having most of a site stuck there is a sign of a bigger content or structure problem.
| Status | What It Means | Typical Fix |
|---|---|---|
| Crawled, currently not indexed | Google visited the page but decided against indexing it | Expand thin content, remove duplication, add internal links |
| Discovered, currently not indexed | Google found the URL but hasn’t crawled it yet | Add it to the sitemap, link to it internally, be patient |
| Excluded by noindex tag | The page tells Google directly not to index it | Remove the noindex tag if the page should rank |
| Blocked by robots.txt | robots.txt disallows crawling of that path | Update the robots.txt rule for that URL pattern |
Noindex Tags Are the Silent Killer of WordPress Indexing
A noindex tag is a direct instruction telling Google not to add a specific page to its index, and it overrides everything else on the page, including a perfect sitemap entry and strong content. SEO plugins like The SEO Framework, Yoast, and Rank Math all include a per-page “Indexing” or “Visibility” toggle, and it’s easy to leave it set to “noindex” after testing a page on staging or copying settings from a template.
To check for a noindex tag manually, right-click the page and choose “View Page Source,” then search the page for the word “noindex.” If <meta name="robots" content="noindex"> shows up anywhere in the head section, that page will never appear in Google results until the tag is removed, no matter how good the sitemap or the content is.
Pages that legitimately should carry a noindex tag include internal search results, tag archives with thin content, and duplicate print or PDF versions of a page. A homepage, service page, or blog post showing this tag is almost always a mistake, not a deliberate choice.
Thin or Duplicate Content Is Behind Most “Crawled, Not Indexed” Pages
Thin or duplicate content is the most common real reason Google crawls a WordPress page and still leaves it out of the index. Industry data on Search Console behavior suggests that roughly 20% to 30% of a typical site’s crawled pages can end up in this unindexed state, usually because the page doesn’t offer enough unique value compared to other pages already in the index.
Common culprits on WordPress sites include near-identical service pages built from the same template with only the city or product name swapped, tag and category archive pages with little unique content of their own, and short blog posts that restate what a dozen other sites already say. The fix is rarely more pages. It’s fewer, stronger ones: merge near-duplicate pages into one comprehensive page, and expand thin posts with specific detail, examples, or data that competing pages don’t have.
How Sitemaps, Robots.txt, and Internal Links Work Together
An XML sitemap, robots.txt, and internal linking each solve a different part of the indexing problem, and a WordPress site needs all three working correctly, not just one. The sitemap tells Google which pages exist and should be considered for crawling. Robots.txt tells Google which paths to leave alone entirely. Internal links tell Google, and users, which pages on the site actually matter.
A page that’s missing from the XML sitemap and has no internal links pointing to it is effectively invisible to Google, even if nothing is technically blocking it. Adding a page to the WordPress XML sitemap and linking to it from at least one other indexed page on the site both send a clear signal that the page is worth crawling. On the flip side, an overly aggressive robots.txt file can block Google from important pages by accident, which is worth double-checking any time indexing problems show up after a robots.txt edit.
How Long Does It Take for a WordPress Page to Get Indexed?
A new WordPress page typically gets indexed anywhere from a few days to a few weeks, depending on how often Google already crawls the site and how strong the internal linking to that page is. Established sites that publish consistently tend to get new pages indexed faster, since Google is already crawling them on a regular schedule.
Clicking “Request Indexing” in Search Console can speed this up, but it’s a nudge, not a guarantee: Google still applies the same quality checks, and a thin or duplicate page requested for indexing a dozen times will still sit unindexed until the content itself improves.
The fastest way to fix a WordPress page that isn’t indexed is to work through this list in order: confirm search engine visibility isn’t discouraged in Settings, check the page for a noindex tag, confirm robots.txt isn’t blocking the URL, then look at the content itself if none of those turn up a problem. Most indexing issues get solved in the first three steps.
Frequently Asked Questions
The most common causes are the “Discourage search engines” setting being enabled, a noindex tag on the page, a robots.txt rule blocking the URL, or Google crawling the page and deciding the content isn’t strong enough to index yet.
It means Google visited the page but chose not to add it to the search index, usually because the content is too thin, too similar to other indexed pages, or doesn’t offer enough unique value yet.
Go to Settings, then Reading, in the WordPress dashboard and make sure “Discourage search engines from indexing this site” is unchecked, then check individual pages for a noindex tag set through the SEO plugin.
New pages on an established, regularly crawled WordPress site typically get indexed within a few days to a few weeks. Newer sites or sites that publish rarely can take longer since Google crawls them less often.
No. A sitemap only tells Google a page exists and should be considered for crawling. It does not guarantee indexing, since Google still evaluates content quality and uniqueness before adding any page to the index.
Leave a Reply