How to Connect Yoast SEO Sitemaps With Google Search Console

Published On -

Olivia Brown Blog

Submit your Yoast SEO sitemap index URL to Google Search Console, then monitor indexing reports to confirm Google can read your pages. For most WordPress sites using Yoast SEO, the sitemap lives at https://yourdomain.com/sitemap_index.xml. Once added to Search Console, Google gets a clean list of your posts, pages, categories, and other public content.

TLDR: Turn on Yoast SEO sitemaps, copy your sitemap index URL, verify your site in Google Search Console, and submit the sitemap under Sitemaps. For example, a small store with 180 product and blog URLs might see 165 discovered URLs within 48 hours, while the rest may be skipped due to noindex tags, redirects, or duplicate pages. Check the response status, fix blocked URLs, and resubmit if needed. This does not force instant ranking, but it helps Google find your content faster and with fewer missed pages.

Why connect Yoast SEO sitemaps to Google Search Console?

Yoast SEO creates XML sitemaps for WordPress automatically. Google Search Console lets you send those sitemap files straight to Google. Together, they make crawling cleaner.

A sitemap is not a ranking button. It will not move a weak page to page one by itself. Still, it tells Google, “Here are the URLs I want you to know about.” That is useful for new sites, large blogs, ecommerce stores, and sites with deep content that may not be linked well from the homepage.

Honestly, it feels like Google should find every good page on its own. But it often does not. Internal links get messy. Old redirects hang around. Category archives get indexed when you wish they would not. A sitemap gives you a cleaner starting point.

Step 1: Make sure Yoast SEO sitemaps are enabled

Log in to your WordPress admin area. Then follow these steps:

  1. Go to Yoast SEO in the left menu.
  2. Open Settings.
  3. Find the section for XML sitemaps.
  4. Make sure the feature is turned on.
  5. Click the link to view your XML sitemap.

Your main sitemap URL usually looks like this:

https://example.com/sitemap_index.xml

This is the sitemap index. It links to smaller sitemaps, such as posts, pages, categories, authors, or products. Submit the index file, not each smaller file, unless you have a special reason.

Step 2: Check that the sitemap opens correctly

Open the sitemap URL in a browser. You should see a plain XML page or a styled Yoast sitemap page with links to child sitemaps.

If you get a 404 error, try saving your WordPress permalink settings:

  • Go to Settings.
  • Click Permalinks.
  • Do not change anything.
  • Click Save Changes.

This refreshes WordPress rewrite rules. It fixes the sitemap URL more often than it should. The annoying part is that this tiny click can save 20 minutes of pointless plugin troubleshooting.

Step 3: Verify your site in Google Search Console

Now open Google Search Console. If your site is not added yet, create a property.

You will usually see two property types:

  • Domain property: Covers all versions, including http, https, www, and non-www.
  • URL prefix property: Covers only the exact version you enter.

For most site owners, a Domain property is cleaner. It normally requires DNS verification. Your domain registrar or hosting provider will give you a place to add the TXT record.

If DNS sounds painful, use the URL prefix option. You can verify with an HTML file, Google Analytics, Google Tag Manager, or an HTML tag. Just make sure you enter the same version Google and visitors use, such as https://www.example.com or https://example.com.

Step 4: Submit the Yoast sitemap

Once your property is verified, submit the sitemap:

  1. Open your property in Google Search Console.
  2. Click Sitemaps in the left menu.
  3. Find the field labeled Add a new sitemap.
  4. Enter only the ending part: sitemap_index.xml.
  5. Click Submit.

If your full sitemap URL is https://example.com/sitemap_index.xml, Search Console usually preloads the domain for you. Do not paste the full URL if the domain is already shown. That can create a broken path such as https://example.com/https://example.com/sitemap_index.xml.

Step 5: Read the sitemap status

After submission, Google may show one of these statuses:

  • Success: Google read the sitemap. Good. Now watch indexing data.
  • Couldn’t fetch: Google could not access it yet. Wait a few minutes, then test again.
  • Has errors: Open the report and review the listed URLs.

Do not panic if the submitted count and indexed count differ. That is normal. A sitemap can list 500 URLs while Google indexes 430. The missing 70 may include duplicate pages, thin content, redirected URLs, noindex pages, or pages Google has not processed yet.

Common problems and quick fixes

1. The sitemap contains noindex pages.
Yoast usually excludes noindex URLs, but settings can get messy. Check the post, page, taxonomy, or content type settings in Yoast. If you do not want Google to index author archives or tag pages, keep them out of the sitemap.

2. Search Console says the sitemap is HTML.
This often means a security plugin, cache plugin, or server rule is showing the wrong page to Google. Open the sitemap in an incognito browser. Then test it with the URL Inspection tool.

3. The wrong domain version is submitted.
If WordPress uses https://example.com, do not submit a sitemap under http://www.example.com. Pick the live canonical version. Mixed versions create confusing reports.

4. A cache plugin serves an old sitemap.
Exclude XML sitemaps from caching. Yoast sitemaps should update when you publish or remove content. Cached XML can delay changes and make reports look stale.

5. Product sitemaps are missing.
If you use WooCommerce, confirm that products are set to appear in search results in Yoast. If products are noindex, Yoast will not include them.

How often should you resubmit?

You do not need to submit the sitemap every time you publish a post. Yoast updates the sitemap automatically. Google revisits it on its own.

Resubmit only when you make major changes, such as:

  • Moving from HTTP to HTTPS.
  • Changing domain names.
  • Removing hundreds of old pages.
  • Launching a large new content section.
  • Fixing a sitemap error in Search Console.

For a normal blog post, publish it, link to it internally, and let the sitemap do its job. If the page matters a lot, use URL Inspection and click Request indexing. Expect to waste time on this if you do it for every tiny update. Use it for key pages only.

What to check after a week

Give Google a few days. Then review these areas in Search Console:

  • Sitemaps: Confirm the sitemap status still says Success.
  • Pages: Review indexed and not indexed URLs.
  • URL Inspection: Test important pages manually.
  • Performance: Watch impressions, clicks, and average position.

A healthy setup does not mean every URL gets indexed. It means Google can access your sitemap, understand your preferred URLs, and report problems you can fix. Pair your sitemap with strong internal links, clear titles, useful content, and clean technical settings. That is how Yoast SEO and Google Search Console become more than two dashboards you check when something breaks.