How do I create a Sitemap for my WordPress website?

Last Updated: February 18, 2026

A sitemap is simply a list of the pages you want search engines to know about. It does not improve rankings by itself. It helps Google discover and crawl your content more efficiently.

If your site structure and internal links are clean, Google will usually find your pages anyway. A sitemap just makes that process faster and more transparent.

There are two types of sitemaps people confuse:

• XML sitemaps are for search engines.
• HTML sitemaps are for humans.

For most small business WordPress sites, you only need an XML sitemap.

Step 1: Check If WordPress Already Created One

Modern WordPress installs generate a basic sitemap automatically. Try visiting:

https://yourdomain.com/wp-sitemap.xml

If you’re using an SEO plugin like Yoast or Rank Math, it will usually generate its own sitemap instead, typically at:

https://yourdomain.com/sitemap_index.xml

If an SEO plugin is active, use its sitemap and ignore the default WordPress one. You do not need both.

Step 2: Use an SEO Plugin for Better Control

The built-in WordPress sitemap works, but it’s limited. An SEO plugin gives you control over:

• Which post types are included
• Whether categories or tags are indexed
• Excluding specific URLs
• Handling custom post types like products

For most sites, enabling the XML sitemap inside your SEO plugin is enough. After enabling it, open the sitemap URL in your browser to confirm it loads correctly.

If it doesn’t load, the usual causes are:

• Caching conflicts
• Security plugins blocking XML access
• Incorrect redirect rules
• The sitemap feature disabled in the plugin

Fix that first before submitting anything.

Step 3: Only Include Pages That Matter

A sitemap is not “everything on your site.” It’s what you want indexed.

Typically include:

• Core service pages
• Location pages (if applicable)
• Main blog posts
• Key resource pages

Typically exclude:

• Tag archives
• Author archives
• Thin pages
• Internal search results
• Attachment pages
• Staging URLs

If you’re building out a large FAQ library or resource section, this step matters. Thin pages don’t belong in your sitemap until they’re built out properly.

A sitemap signals importance. Use that signal intentionally.

Step 4: Submit It to Google Search Console

Once your sitemap is confirmed working:

1. Log into Google Search Console
2. Go to Sitemaps
3. Enter sitemap_index.xml
4. Click Submit

This does not force Google to index everything. It helps Google discover new content and gives you reporting.

Inside Search Console, watch:

• Submitted vs Indexed counts
• “Discovered, currently not indexed”
• “Crawled, currently not indexed”

If you see large gaps, that’s usually not a sitemap issue. It’s a structure or content quality issue.

Step 5: Keep It Clean Over Time

A sitemap should stay accurate.

After publishing new pages, check that they appear in the sitemap.
If you noindex a page, confirm it drops out.
If you change URLs, make sure old URLs are removed and properly redirected.

A messy sitemap often reveals deeper structural problems.

Common Sitemap Mistakes

Relying on the sitemap instead of internal linking
Google learns priority from your links, not just your sitemap.

Including junk pages
If your sitemap is full of thin or duplicate content, you dilute your signal.

Ignoring crawl errors
If Google can’t access your sitemap reliably, fix that before worrying about rankings.

Using a sitemap to compensate for poor structure
If your site is slow, unstable, or confusing, a sitemap won’t fix it.

When to Get Help

If your sitemap is submitted correctly but pages still aren’t indexing, the issue is usually deeper:

• Weak internal linking
• Duplicate content
• Poor site performance
• Incorrect noindex settings
• Technical SEO conflicts

That’s where starting with Website Help makes sense. A sitemap is easy to generate. Getting your site into a state Google trusts is the real work.

If you want ongoing oversight so you don’t have to think about crawl errors, indexing issues, or structural drift, that’s where WordPress Care Plans come in. It’s not about “making a sitemap.” It’s about keeping your foundation stable over time.