WordPress indexing: get your site into Google and Bing

A page has to be indexed (in the search engine's index, the library it answers from) before it can show in search results or in AI answers built on them, such as Google's AI Overviews. This hub covers where WordPress puts its sitemap, Search Console and Bing setup, IndexNow options, the settings that quietly block indexing, WordPress-specific gotchas, and a checklist to verify it all. Each section links to a detailed guide.

What does it take to get a WordPress site indexed?

Getting a WordPress site indexed means removing every reason a search engine would skip it, then telling the engines where your pages are. Self-hosted WordPress already does part of this: core publishes an XML sitemap and a robots.txt file that points to it. Google notes that content platforms often submit new content automatically and says to "Check your platform's support articles" (Google Search Central). On self-hosted WordPress, what's automatic is that sitemap; connecting Search Console and Bing is up to you.

Google's guidance also sets expectations: crawling (a search engine's bot visiting a page to read it) "can take anywhere from a few days to a few weeks," and requesting a crawl doesn't guarantee inclusion. As of October 17, 2026, the current WordPress release is 7.1.3, according to the wordpress.org API.

The five jobs, in order:

Running a different site builder as well? Our indexing guides for other platforms follow the same five jobs.

Where does WordPress put your sitemap?

WordPress puts its sitemap index at https://example.com/wp-sitemap.xml, and has since version 5.5. The 5.5 announcement says a single sitemap file "can hold a (filterable) maximum of 2000 entries" (Make WordPress Core, July 22, 2020), so large sites get several numbered files under one index.

An SEO plugin usually replaces the core sitemap with its own:

When we requested /wp-sitemap.xml on the Yoast, Rank Math, AIOSEO and SEOPress websites on October 17, 2026, each one redirected to the plugin's own sitemap. Since WordPress 6.5, core sitemaps also carry lastmod dates for posts and pages. Our guide to finding and submitting the WordPress sitemap has the file structure, the live test results and the errors to expect.

How do you connect WordPress to Google Search Console?

You connect WordPress to Google Search Console by adding your site as a property, verifying that you own it, then submitting your sitemap. Search Console offers two property types. A Domain property covers "all subdomains and protocols (http/https)" but "requires you to verify ownership using DNS record verification"; a URL-prefix property covers one address, such as https://www.example.com/ (Search Console Help).

For WordPress, Google's verification help suggests a plugin first: "Site Kit for WordPress can handle verification for you, and also provide simplified views of your Search Console data." It adds that Site Kit "is the only plugin that is officially sponsored by Google" (Search Console Help). As of October 17, 2026, Site Kit by Google on wordpress.org lists 5,000,000+ active installs and is tested up to WordPress 7.1.3. Its setup runs from the Site Kit menu in WordPress.

The other verification methods work on WordPress too, as of October 2026:

Google suggests adding more than one method, because one can break, for example "if you verified using a Google Analytics tracking code, and someone changes a template on your website that omits the tag." Theme changes are exactly that risk on WordPress.

Once verified:

1. Submit your sitemap in the Sitemaps report. Owner permission is needed; see the sitemap guide for the steps.
2. Inspect your home page. For a new site, Google says "the best first step is to request indexing of your homepage" (Page indexing report help). Our URL Inspection tool guide shows how.
3. Watch the Page indexing report over the next weeks. Our Page indexing report guide explains each status.

For more on telling Google about individual pages, see how to submit a URL to Google.

How do you connect WordPress to Bing Webmaster Tools?

The quickest way to connect a WordPress site to Bing Webmaster Tools is to import it from Search Console. Bing says that after an import "the selected sites will be added and get automatically verified in Bing Webmaster Tools," and that "any new sitemap found on your Search Console account will also be imported automatically" (Bing Webmaster Tools help).

To add the site manually instead, Bing offers four methods: DNS auto verification, an XML file (BingSiteAuth.xml) uploaded to the site root, a meta tag pasted "at the end of the <head> section," or a CNAME record. Bing adds that "it usually takes 48 hours for our system to generate analytics and data." Our Bing Webmaster Tools guide covers the reports you'll use after that.

How do you send IndexNow from WordPress?

You send IndexNow from WordPress with one plugin or with Cloudflare. IndexNow is an open "this page changed" notice that Bing and other participating engines accept; Google doesn't use it. Bing's help lists "IndexNow (Strongly Recommended)" first among its submission options (Bing Webmaster Tools help).

Your options as of October 2026:

Use one. Two senders send every URL twice, and the IndexNow FAQ says to "Avoid submitting the same URL many times a day unless there are meaningful content changes" (IndexNow FAQ). Our WordPress IndexNow guide compares the options feature by feature and shows how to test them; our comparison of WordPress indexing plugins adds wordpress.org installs, ratings and update dates. For how the protocol works, see what IndexNow is.

Which WordPress settings stop pages being indexed?

Two kinds of WordPress settings stop pages being indexed: a noindex instruction, which tells search engines not to keep a page, and robots.txt rules, which stop them crawling it. The most common is a single checkbox.

"Discourage search engines from indexing this site" sits under Settings → Reading. WordPress's documentation says that since version 5.3 ticking it causes a noindex,nofollow robots meta tag "to be generated into the <head> </head> section (if wp_head is used) of your site's source," and notes "it is up to search engines to honor your request" (WordPress documentation). The same setting switches off core sitemaps: the 5.5 announcement says that when you discourage search engines, "sitemaps will be disabled." Microsoft's IndexNow plugin also checks this setting and won't submit while it's on.

A public site's home page carries max-image-preview:large in its robots meta tag instead, from core's wp_robots_max_image_preview_large() (robots-template.php source). That gives you a quick test, shown in the checklist below.

Pages hidden this way appear in Search Console's Page indexing report as Excluded by 'noindex' tag. Google's advice is short: "If you do want this page to be indexed, you should remove the 'noindex' directive." Check per-post settings in your SEO plugin too, since each one can set noindex on single posts, post types or archives.

robots.txt controls crawling, not indexing. Our WordPress robots.txt guide covers the default file, how to edit it, and why it's the wrong tool for removing pages; pages it blocks show as Blocked by robots.txt.

Which WordPress-specific gotchas keep pages out of Google?

Most WordPress indexing problems come from how WordPress and its plugins generate URLs and sitemaps, not from the content. The ones to check:

• A sitemap that moved when you changed SEO plugins. Each plugin uses its own URL, so a sitemap submitted under the old plugin stops working. Search Console then reports Sitemap could not be read; submit the new URL and remove the old one.
• A cached sitemap. Rank Math's sitemap guide says "It is possible that your sitemap is cached" and to exclude it from caching (Rank Math). New posts that don't appear in the sitemap usually mean a page cache.
• Thin archive pages in the sitemap. Core lists category, tag and author archives by default. If those pages add little, Google may crawl them and leave them out, which shows as Crawled - currently not indexed. The 5.5 post shows how to drop a taxonomy with the wp_sitemaps_taxonomies filter.
• The same content at more than one URL. Archives, parameters and old protocol or www variants can make Google pick its own canonical (the version it indexes), which shows as Duplicate without user-selected canonical.
• Plugins that call Google's Indexing API. Google says that API "can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject" (Google Search Central). Our Google Indexing API guide explains why it isn't a route for blog posts.
• Subfolder installs. WordPress only serves its virtual robots.txt when installed at the domain root; the robots.txt guide explains what to do instead.

If any of these applied to your site, check which of your WordPress pages Google has indexed now that it's fixed.

What's the verify and push checklist for a WordPress site?

Verify a WordPress site's indexing setup from the outside first, then in each engine's tools. We ran these three commands against make.wordpress.org/core, a public WordPress site, on October 17, 2026:

SITE=https://make.wordpress.org/core
# 1. Is the home page asking search engines to stay away?
curl -s "$SITE/" | grep -io "<meta name=['\"]robots['\"][^>]*>"
# 2. Does the sitemap answer with 200, and where does it end up?
curl -s -o /dev/null -w "%{http_code} %{url_effective}\n" -L "$SITE/wp-sitemap.xml"
# 3. Any X-Robots-Tag header on the home page?
curl -sI "$SITE/" | grep -i "x-robots-tag" || echo "no X-Robots-Tag header"

They returned <meta name='robots' content='max-image-preview:large' />, then 200 https://make.wordpress.org/core/wp-sitemap.xml, then no X-Robots-Tag header: a public site with a working core sitemap. On your own site, replace SITE and the sitemap path with yours. A noindex in step 1 or 3 means something is hiding the site.

Then work through the engines:

1. Settings → Reading: "Discourage search engines" is unticked.
2. Sitemap: one working URL, submitted in Search Console's Sitemaps report, with status Success.
3. Home page: inspected in URL Inspection and, if not indexed, requested.
4. Bing: site imported or verified in Bing Webmaster Tools.
5. IndexNow: exactly one sender on, with URLs arriving in Bing's IndexNow report.
6. Page indexing report: filtered to "All submitted pages" to see which sitemap URLs are indexed and which aren't.
7. Re-check after changes: fix the page first, then ask Google to look again.

What nobody can promise, and what you can control

Nobody can promise that Google or Bing will index a WordPress page, or how soon. Google decides what to crawl and keep, Bing makes its own call on every IndexNow notice, and AI answers choose their own sources from what's indexed. Being indexed is the first step; being cited still depends on quality, authority and relevance. Our AI search optimization guide covers what comes after indexing.

What you control is everything above: no accidental noindex, one working sitemap that both engines know about, verified accounts, one IndexNow sender, and pages that are worth keeping.

Where FreshlyCited fits

FreshlyCited is the last checklist step done for you: it checks each WordPress URL against Google ("Seen by Google" or "Invisible"), pushes only the invisible ones, and re-checks them on days 1, 3 and 7. Index credits are reserved when you submit and used only if the link is indexed; if it's still not indexed after the day-7 re-check, the credit comes back automatically (exclusions apply, such as pages that return an error or carry noindex). For sites you verify with an IndexNow key, pushes also go through IndexNow ("Sent to Bing"), free, with a per-site off switch if a WordPress plugin already handles it. Agencies running many WordPress client sites can see how that works on FreshlyCited for agencies.

Set up the basics? Check your WordPress pages free: 10 free links to try, then 100 free checks a month, no card needed.