To get Google to index your WordPress blog, make sure the “Discourage search engines” box is unchecked, verify your site in Google Search Console, submit your XML sitemap, and request indexing for your most important URLs with the URL Inspection tool. After that, indexing depends on quality: pages that are useful, internally linked and technically clean get indexed and stay indexed, while thin or duplicate pages are often crawled and then left out.
This guide walks through each step in the order you should do it, explains what the Search Console status messages actually mean, and covers the reasons a WordPress post can sit unindexed for weeks. If you want the background on why Google must index your WordPress website before it can rank for anything, WPBeginner’s beginner guide covers the basics well; here we focus on the practical checklist and troubleshooting.
Crawling, indexing and ranking are three different things
People often use these words interchangeably, but separating them makes problems much easier to diagnose.
- Crawling is when Googlebot fetches a URL. It finds URLs through links, sitemaps and manual requests.
- Indexing is when Google processes the page and decides to store it in its index. A crawled page is not guaranteed to be indexed.
- Ranking is where an indexed page appears for a given search. A page can be indexed and still show up on page nine.
Most “Google won’t index my blog” complaints are really one of two issues: Google cannot reach the page at all (a technical block), or Google reached it and chose not to keep it (a quality or duplication signal). The fixes are different, so it pays to know which one you have.
Step 1: Check the WordPress search engine visibility setting
In your dashboard, go to Settings > Reading and look at “Search engine visibility.” If the box labeled “Discourage search engines from indexing this site” is checked, WordPress adds a noindex signal to every page. Developers often tick it on staging sites and forget to untick it at launch, so this is always the first thing to check. Uncheck it and save.
While you are there, confirm that your permalinks (Settings > Permalinks) use a readable structure such as “Post name.” Changing permalinks on an established blog creates redirects and temporary churn, so settle this early.
Step 2: Verify your site in Google Search Console
Google Search Console is the free tool that tells you what Google has crawled and indexed, and lets you ask for crawls. You can add your site in two ways:
- Domain property: covers every subdomain and both http and https versions. It requires adding a TXT record at your domain registrar or DNS host. This is the better option if you can edit DNS.
- URL-prefix property: covers one exact version, such as https://www.example.com. You can verify with an HTML meta tag, which SEO plugins like Yoast, Rank Math and All in One SEO let you paste into a settings field without touching theme files.
Once verified, data starts to fill in over the following days. If you use Site Kit by Google, it can handle verification and show Search Console data inside WordPress, but the full Search Console interface is still where you will do most troubleshooting.
Step 3: Generate and submit an XML sitemap
Since version 5.5, WordPress core generates a basic sitemap at /wp-sitemap.xml. SEO plugins usually replace it with their own, often at /sitemap_index.xml, with more control over what is included. Only use one sitemap system to avoid confusion.
Open your sitemap in a browser to make sure it loads, then in Search Console go to Sitemaps, enter the sitemap path and submit. A healthy sitemap should list only pages you actually want in search: published posts, key pages and perhaps categories. Exclude tag archives, attachment pages, author archives on single-author blogs and thank-you pages. Sending Google hundreds of low-value URLs dilutes the signal about which pages matter.
Step 4: Request indexing for important URLs
For a new or updated post you care about, paste its URL into the URL Inspection bar at the top of Search Console. You will see whether the URL is on Google. Click “Test live URL” to confirm Google can fetch it, then “Request indexing.” There is a daily quota on manual requests, so save it for genuinely important pages rather than resubmitting your whole archive. Requesting indexing puts the page in a queue; it does not guarantee inclusion.
Step 5: Link new posts from pages Google already knows
Internal links are how Googlebot discovers most pages, and they signal importance. When you publish a post, add a link to it from two or three older, related articles that are already indexed. A new post that is only reachable through the sitemap and a paginated archive looks like a low-priority page. Category pages, a “start here” page and related-post sections all help, but a contextual link inside a relevant paragraph carries the most meaning.
What Search Console status messages mean
The Pages report groups URLs by status. These are the ones WordPress bloggers see most often:
| Status | What it usually means | What to do |
|---|---|---|
| Excluded by “noindex” tag | A plugin setting or the visibility box is telling Google not to index | Check Settings > Reading and the SEO plugin’s per-post and archive settings |
| Blocked by robots.txt | Your robots.txt disallows the path | Edit robots.txt (often via the SEO plugin) to allow it |
| Discovered, currently not indexed | Google knows the URL but has not crawled it yet | Improve internal links; check server speed; be patient |
| Crawled, currently not indexed | Google fetched it and decided not to index it for now | Improve depth and originality; merge thin posts |
| Duplicate without user-selected canonical | Google sees it as a copy of another URL | Set a clear canonical; remove near-duplicate pages |
| Page with redirect / Not found (404) | The URL no longer resolves to content | Normal for old URLs; fix any internal links pointing there |
Common reasons a WordPress post is not getting indexed
Thin or unoriginal content
Since Google’s helpful content changes were folded into its core ranking systems, sites with a lot of short, generic or rewritten material have found that new posts stay in “Crawled, currently not indexed” for long stretches. The fix is not technical. Write fewer, deeper posts that answer the question fully, add real examples or first-hand experience, and consider merging or removing old posts that add nothing.
Plugin settings that noindex more than you intended
SEO plugins let you noindex post types, taxonomies and individual posts. It is easy to set a category or a whole post type to noindex by accident. Check the “Advanced” tab on a problem post and the plugin’s global search appearance settings.
Slow hosting or server errors
If your server responds slowly or returns 5xx errors, Google crawls less. Look at Settings > Crawl stats in Search Console for average response time and host problems. Caching plugins, a CDN and a decent host usually solve this. Security plugins or firewalls that block unfamiliar bots can also stop Googlebot, so check their logs.
Duplicate URLs from WordPress itself
WordPress can produce many URLs for similar content: tag pages, date archives, attachment pages and paginated comment pages. When those outnumber real posts, they waste crawl attention. Noindex or disable the ones you do not need, and make sure each post outputs a self-referencing canonical tag (all major SEO plugins do this by default).
How long indexing takes
There is no fixed timeline. On an established blog with a good track record, new posts are often indexed within a day or a few days. On a brand-new site, it can take anywhere from several days to several weeks before Google crawls much at all. If a page is still unindexed after a few weeks, run it through URL Inspection, review the status, and look honestly at whether it offers something the pages already ranking do not.
After indexing: building toward rankings
Getting indexed is the entry ticket. Google keeps recrawling your pages to reassess them, and rankings depend on relevance, depth, page experience and authority. Keep posts updated, fix broken links, make pages fast on mobile and earn links from sites in your field. Our look at the benefits of digital marketing for small businesses explains where search fits alongside other channels, and if you decide to bring in outside help, read how to choose an SEO consultant before signing a contract. For a broader view of why search investment matters for online businesses, see our guide on why professional SEO matters.
Quick indexing checklist
- “Discourage search engines” is unchecked.
- Site verified in Search Console, ideally as a Domain property.
- One XML sitemap, submitted, containing only index-worthy URLs.
- robots.txt does not block posts, CSS or JavaScript.
- Each new post is linked from at least two related indexed posts.
- Important URLs submitted through URL Inspection.
- Thin, duplicate and archive pages noindexed, merged or removed.
Frequently asked questions
How do I check if my WordPress blog is indexed by Google?
Paste a post URL into the URL Inspection tool in Google Search Console, which tells you whether that URL is on Google. The Pages report shows totals for indexed and non-indexed URLs. A site: search in Google gives only a rough picture.
Do I need an SEO plugin to get indexed?
No. WordPress core outputs a sitemap and is crawlable by default. An SEO plugin makes it easier to control sitemaps, canonicals, noindex settings and Search Console verification.
Why does Search Console say “Crawled, currently not indexed”?
Google fetched the page but decided not to add it for now. This is usually about perceived value or duplication rather than a technical block. Make the page more complete and original, and link to it from related posts.
Should I request indexing every time I update a post?
Only for significant updates to important pages. Google recrawls updated content on its own, and manual requests are limited by a daily quota.
Can a slow host stop my blog from being indexed?
It can slow things down. If your server is slow or returns errors, Google reduces how much it crawls. Check Crawl stats in Search Console and fix hosting or caching problems.
