How to Get Google to Index Your WordPress Website

WordPress is the easiest major platform to get indexed and, at the same time, the easiest to hide from Google by accident. It ships with a working sitemap and clean HTML. It also ships with one checkbox that blocks the entire site, tucked into a settings page most people visit exactly once.

This guide shows you how to get Google to index your WordPress website in seven steps, in the order that matters. You will see where each setting lives, what a sensible robots.txt looks like, how long indexing usually takes, and how to diagnose a page that still refuses to appear.

Key Takeaways

• Check Settings, then Reading first. While "Discourage search engines from indexing this site" is ticked, nothing else you do has any effect.
• You already have a sitemap. Core WordPress serves /wp-sitemap.xml; Yoast and Rank Math replace it with /sitemap_index.xml.
• Archives are the silent problem. One post can create six crawlable URLs, and most of them should carry noindex.
• Settle permalinks before launch, because changing them later breaks every URL you have.
• IndexNow does not reach Google. It notifies Bing and other participating engines, so Google still relies on your sitemap, links and Search Console.
• After a month, stop changing settings. A page still missing by then usually has a content or links problem, not a configuration one.

How to get Google to index your WordPress website

Work through these seven steps in order, because each one assumes the one before it is done. The animation below walks the sequence, and every step has its own section further down with the exact setting and a diagram.

1. Untick Discourage search engines under Settings, then Reading.
2. Confirm your sitemap loads at the right URL.
3. Submit that sitemap in Google Search Console.
4. Noindex the thin archive pages WordPress generates.
5. Settle your permalink structure before you publish.
6. Block internal search results and password-protect staging.
7. Purge every cache layer, then verify the live HTML.

Step 1: Untick the checkbox that hides your site

Go to Settings, then Reading, and find Search engine visibility. If the box labelled "Discourage search engines from indexing this site" is ticked, WordPress tells crawlers to stay away from every page you publish.

The setting exists for a good reason, since you do not want a half-built site in search results. The problem is the handoff. Developers tick it on day one, launch day arrives without anyone unticking it, and the site goes live while staying invisible for weeks. Check this first on every WordPress site you diagnose, because it is the highest-yield thirty seconds in this guide.

Step 2: Confirm which sitemap you have

WordPress has generated a sitemap at /wp-sitemap.xml since version 5.5, so a site with no SEO plugin already has one that works. Install Yoast or Rank Math, however, and the plugin switches the core sitemap off and serves its own at /sitemap_index.xml instead.

Whichever applies, open the URL in your browser and read it rather than trusting it. You are checking two things: that your posts and pages appear, and that nothing you want kept out of Google has slipped in. Most sites fail the second check.

Step 3: Submit the sitemap in Search Console

Add your site as a property in Google Search Console and verify it. A Domain property is the safer choice, because it covers both the www and bare versions of your domain along with every subdomain.

Next, open the Sitemaps report and submit the sitemap URL from step 2 exactly once. You do not need to resubmit it after each post, because Google rechecks the file on its own schedule, and resubmitting an unchanged file does not speed anything up.

Step 4: Noindex the archives nobody searches for

This is where most WordPress sites leak quality without anyone noticing. WordPress builds an archive page for every category, tag, author and month, plus a results page for every internal search. A site with 300 tags therefore has 300 tag archives, and most of them list one or two posts.

Google crawls all of it, and most of it is thin, near-duplicate content. Use your SEO plugin to set sensible defaults instead:

• Noindex tag archives unless you curate tags deliberately as topic hubs.
• Noindex date archives, because nobody searches your site by month.
• Noindex author archives on a single-author site, since they duplicate your blog index.
• Keep category archives indexable when your categories match real topics people search for.

Step 5: Settle permalinks before you publish

Under Settings, then Permalinks, choose the Post name structure rather than the default with dates and numbers. Do this before launch, or as early as you possibly can afterwards.

Changing permalinks on an established site changes every URL at once. Without redirects in place, every ranking and backlink those URLs earned disappears. If you must change the structure later, add 301 redirects from the old pattern to the new one before you switch.

Step 6: Block internal search and protect staging

Every search a visitor runs on your site creates a crawlable URL with a thin list of results, so an active site produces a steady stream of junk URLs. Block them in robots.txt, which WordPress lets you edit through Yoast, Rank Math or a physical file in your site root.

Copy these lines into your own robots.txt, replacing example.com with your domain:

• User-agent: * applies the rules below to every crawler.
• Disallow: /wp-admin/ keeps crawlers out of your dashboard.
• Allow: /wp-admin/admin-ajax.php keeps themes and plugins working.
• Disallow: /?s= blocks internal search result pages.
• Disallow: /search/ blocks the tidier search URLs some themes use.
• Sitemap: https://example.com/sitemap_index.xml points crawlers at your sitemap.

Staging copies need a different fix. WordPress sites are often cloned to a staging subdomain and left crawlable, which puts a full duplicate of your site in competition with itself. Put staging behind HTTP authentication rather than relying on noindex, because a password stops crawling outright and survives every content sync from production.

Step 7: Purge caches, then verify

If a fix appears not to work, check your caching layer before you doubt the fix. A page cache, an object cache and a CDN can each keep serving an older version of a page, including its old meta tags, long after you changed them. Purge every layer, then view the page source in a private window to confirm the live HTML says what you expect.

How long does it take Google to index a WordPress site?

Expect anything from a few hours to a few weeks. The biggest variable is not WordPress at all but how established your domain already is, because Google crawls sites it already trusts far more often.

A new post on an established site, linked from pages Google already crawls, is often picked up within days. A brand new domain with no inbound links can take weeks, since Google has no history telling it to visit often. If a page is still missing after a month with every setting correct, stop adjusting settings. At that point the cause has almost always moved to thin content or a lack of links.

How to speed up WordPress indexing

You cannot force Google to index a page, but you can remove every reason for delay. These are the levers that actually move the timeline.

Request indexing for your most important URLs. In Search Console, inspect the URL and use Request indexing. The button is rate limited, so save it for pages that matter rather than every post.

Link to new posts from pages Google already crawls. A link from your homepage or a popular post gives Googlebot a direct route in, which is usually faster than waiting for it to reread your sitemap.

Understand what IndexNow does and does not do. Rank Math and several other plugins can ping IndexNow automatically when you publish. That notifies Bing, Yandex and the other participating engines, but Google does not use IndexNow, so it will not change your Google timeline.

Submit in bulk when you have a backlog. When you are pushing dozens or hundreds of URLs at once, such as a site migration, a content refresh or a batch of guest posts, one-at-a-time requests stop scaling. SEO Indexing lets you submit up to 10,000 URLs per project with no Search Console connection required, choosing a Standard mode or a Fast mode, then confirm the results with its index checker, which scans up to 2,000 URLs per run.

Why is my WordPress site not indexed?

Match the symptom you see in Search Console to the most likely cause, and apply the fix beside it. The diagram covers the five cases that account for most WordPress indexing problems.

• Whole site missing: the discourage checkbox is ticked, or an SEO plugin applied a sitewide noindex.
• "Crawled, currently not indexed": Google read the page and judged it thin or duplicated, so add depth or merge it into a stronger page.
• "Discovered, currently not indexed": crawl budget went on archives and search URLs, so noindex the archives and block ?s=.
• Traffic fell after a redesign: permalinks changed and old URLs now return 404, so add 301 redirects.
• Fix applied but nothing changed: a cache still serves old HTML, so purge it and check the source in a private window.

How to check if your WordPress site is indexed

The quickest check is the site: operator: search for site:yourdomain.com/your-post and see whether the page appears. For a definitive answer, use URL Inspection in Search Console, which reports Google's own verdict for the exact URL and the canonical it selected.

Checking one URL at a time stops being practical once you publish regularly. The SEO Indexing index checker verifies up to 2,000 URLs per run, which suits a full post archive or a batch of guest posts. For the trade-offs between every method, see our guide on how to check if a page is indexed on Google, and if you need the date rather than the status, read how to check when a page was indexed by Google.

Common questions

How long does it take Google to index a new WordPress site?

Usually a few days to a few weeks. An established domain with internal links to the new page often sees it indexed within days, while a brand new domain with no inbound links can wait several weeks because Google has no reason yet to crawl it often.

Does IndexNow work with Google?

No. IndexNow notifies Bing, Yandex and the other participating engines, and Google does not take part. Plugins such as Rank Math make it easy to enable, which helps your Bing visibility, but your Google timeline still depends on sitemaps, links and Search Console.

Do I need an SEO plugin to get indexed?

No. WordPress generates a working sitemap at /wp-sitemap.xml and produces crawlable HTML without any plugin. A plugin becomes worth having as the site grows, because it gives you control over archives, canonicals and per-post settings.

Should I noindex tags and categories?

Noindex tag archives unless you curate them as topic hubs, since tag archives on most sites are thin and near-duplicate. Keep category archives indexable when they map to real topics people search for, and noindex date archives on every site.

Why did my WordPress site get deindexed?

The common causes are the discourage checkbox being ticked during maintenance, a plugin or theme update adding a sitewide noindex, a robots.txt change blocking crawlers, or a manual action for spam. Check Settings and Reading first, then the page source for a noindex tag, then the Manual Actions report in Search Console.

How do I stop my staging site being indexed?

Put it behind HTTP authentication. A noindex tag can be wiped out by a sync from production and still requires the page to be crawled before Google reads it, whereas a password prevents crawling entirely.

The short version

To get Google to index your WordPress website, untick the discourage checkbox, confirm and submit your sitemap, noindex thin archives, settle permalinks before launch, block internal search and protect staging, then purge your caches and verify. WordPress gets you most of the way by default. The real work is stopping it from generating pages you never wanted Google to see.