Why Is My WordPress Site Not Indexed on Google?

Why is my WordPress site not indexed on Google? Almost always because a setting is sending Google the wrong signal, not because Google rejected the content. The usual suspects are the WordPress Reading option that discourages search engines, a noindex tag from an SEO plugin, a robots.txt disallow, a canonical pointing at another URL, or thin tag and date archives that waste crawl budget. Find the blocker, clear it, then submit the real URLs through official channels and let Google recrawl. No tool can force a WordPress page into the index; Google still decides, but clearing the blocker is what gets it there.

WordPress powers a huge share of the web precisely because it hides complexity. That same convenience is why indexing breaks in ways that are easy to miss. One checkbox, one plugin default, or the pile of archive URLs WordPress generates on its own can keep your best posts out of Google while everything looks finished on the surface. Here is how to find the real cause and fix it the white-hat way.

First, confirm the site actually is not indexed

Before diagnosing, verify the problem. The reliable check is the URL Inspection tool in Google Search Console, which reads status straight from Google's index and tells you whether a page is indexed, when it was last crawled, and what any issue is. Do not judge by the site: operator alone. Typing site:yourdomain.com returns a rough number, but Google has said repeatedly that it is an estimate, not a real count of indexed pages, and it misses pages that are genuinely indexed. If you want to check many WordPress URLs at once, use a bulk index checker that reads the same official signal rather than scraping the site: number.

The WordPress Reading setting that silently blocks everything

Start here, because it is the single most common cause and the easiest to overlook. In your dashboard, go to Settings, then Reading, and look for a box labeled "Discourage search engines from indexing this site." Developers tick it while a site is under construction so a half-built site does not show up in Google, and then they forget to untick it at launch.

While that box is checked, WordPress adds a noindex directive across the entire site. Every page can be perfectly built, linked and submitted, and none of it will stay in the index. If your whole WordPress site vanished from Google after a redesign or a new launch, check this box first. Unticking it removes the site-wide noindex, and the pages become eligible again once Google recrawls them.

Plugin noindex tags and wrong canonicals

SEO plugins like Yoast, Rank Math and All in One SEO control indexing per post and per post type, and their defaults do not always match what you want. A post type set to "no index" in the plugin, a single post switched off in its Advanced settings, or a canonical field pointing at a different URL will all keep a page out of the index even when the Reading setting is fine.

Open the affected page in your SEO plugin and check two things: that it is set to index, not noindex, and that its canonical URL points at the page itself rather than another one. A canonical pointing elsewhere tells Google "the real version lives over there," so Google indexes that other URL instead of the one you are looking at. This is a frequent cause of a page that seems fine but never appears.

robots.txt disallow rules

WordPress serves a virtual robots.txt by default, and plugins or manual edits can add disallow rules that block the exact paths you want indexed. A disallow does not add a noindex, but it stops Googlebot from crawling the page, which usually keeps it out of the index and can leave a bare URL with no description if Google indexes it from links alone.

Fetch yourdomain.com/robots.txt in a browser and read it. Make sure nothing disallows the URLs or directories you want crawled, and that your sitemap line is present and correct. Remember that a page carrying both a disallow and a noindex is self-defeating: Google cannot crawl the page to see the noindex, so blocking and noindexing the same URL is a mistake. Pick one method for what you want, and allow crawling of everything you want indexed.

Thin and duplicate archive URLs eating your crawl budget

WordPress creates far more URLs than you publish. Every tag, category, author and date archive becomes its own page, and attachment pages can spin up for each uploaded image. Most of those are thin or near-duplicate, and on a larger site Google can burn its crawl budget fetching them instead of your actual posts. The result shows up in Search Console as "Discovered, currently not indexed": Google knows the URLs but has not prioritized crawling them.

The fix is to stop wasting the budget. Noindex the low-value archives you do not need in search (empty tag pages, date archives, author pages on a single-author blog) in your SEO plugin, keep your sitemap limited to the URLs that should rank, and strengthen internal links to the posts you care about. Cutting the clutter often clears the backlog on its own, because Google finally spends its crawls where they matter. If you are starting fresh rather than untangling an old install, some teams skip the archive maze entirely by building on an AI website builder that ships clean markup and a single sitemap by default.

Brand new WordPress site or post, not yet crawled

If the site is genuinely new, patience plus a nudge is the answer. A fresh domain with no inbound links gives Google little reason to crawl often, so discovery is slow. Verify the site in Search Console, submit your XML sitemap (Yoast, Rank Math and AIOSEO generate one automatically at a path like /sitemap_index.xml), link new posts from pages that are already indexed, and submit priority URLs through the official Google Indexing API and Bing IndexNow. This is the honest way to index a WordPress site on Google faster, and it is exactly what a white-hat indexing tool automates: it clears the check, submits through approved channels, and monitors coverage afterward.

How long should indexing take?

A healthy new WordPress page is usually indexed within a few days to a couple of weeks once Google has discovered and crawled it. A brand new domain can take longer. If a page has been live for weeks, is not blocked, and still is not indexed, that is a signal to look harder at quality and duplication rather than to keep resubmitting. Submitting the same thin page ten times does nothing; making it worth indexing does.

The bottom line

A WordPress site that is not indexed is a diagnosis problem, not a mystery. Work down the list: Reading setting, plugin noindex and canonicals, robots.txt, archive clutter, then age. Clear the blocker, confirm with URL Inspection, and submit through official channels. Once you know which pages Google is missing and why, getting them indexed is mechanical. For an ongoing view of which of your URLs are in the index and which fell out, a tool that both checks whether a page is indexed and resubmits through approved APIs turns this from a recurring scramble into a routine check.