Part of the SiteMap Series
You have just finished the audit from Lesson 2: What’s Actually In Your Sitemap. You know what you have, what is wrong, what is missing, and whether the lastmod dates are honest. You have a list of findings sitting in front of you. Now comes the decision that shapes everything that follows: how should you actually build or rebuild your sitemap?
This is not the kind of decision that gets made once and never revisited, but it is the kind worth making thoughtfully. Choose well now, and you avoid months of fighting with the wrong tool. Choose poorly, and you end up rebuilding a year from now anyway, having learned what you should have asked at the start.
There are four real ways to get a sitemap, and the right one for you depends on your CMS, how often your content changes, and what your audit just told you. This lesson walks through each option honestly, names the trade-offs, and gives you a framework for making the call.
Start with what your audit told you
Before you compare methods, look back at your findings from the previous lesson. The shape of the problems points to specific kinds of solutions, and a few minutes of matching findings to methods saves you from picking the wrong tool entirely.
If your audit found junk URLs that should not be in the sitemap, you need a method with strong exclusion controls. Most SEO plugins handle this well. CMS-native sitemaps usually do not.
If your audit found missing content types (custom post types, certain page templates, particular taxonomies), you need a method that lets you include them explicitly. Plugins handle this. Generators that crawl your site can pick them up automatically. CMS-native generators tend to ignore anything outside their default content types.
If your audit found a same-date-everywhere lastmod problem, you need a method that pulls lastmod from actual page modification dates. Yoast and Rank Math both do this correctly by default. Some cheaper plugins and most one-off generators do not, and you end up back where you started.
If your audit turned up nothing because no sitemap exists at all, you have the cleanest situation. You get to choose freely without inheriting baggage from a previous setup.
And if your audit found a mostly working sitemap with only minor issues, the right call may be to keep the method you have and fix the configuration. Switching methods for the sake of switching makes things worse, not better. It introduces new problems in exchange for solving old ones that could have been fixed in place.
The four ways to get a sitemap
The four practical methods, in rough order of how often each is the right choice for a real site.
1. Using a Wordpress Plugin
The first is plugin-based generation. On WordPress, this means Yoast SEO, Rank Math, All in One SEO, or one of the smaller alternatives. The plugin watches your content as you publish, edit, and delete pages and updates the sitemap automatically. You configure what to include and exclude through a settings page, and the plugin handles the XML generation in the background. This is the dominant approach for a reason: it is the closest thing to set-and-forget that actually works well, and the lastmod values it produces are usually honest.
2. CMS- native generation
The second is CMS-native generation. Modern platforms generate a sitemap automatically without any plugin: WordPress since version 5.5, Shopify, Wix, Squarespace, Webflow, and Ghost. The platform builds the sitemap from the content database and updates it whenever content changes. There is nothing to install and nothing to configure. The trade-off is that you get very little control over what is included or excluded, so if your audit found content type problems, this method is not going to fix them.
3. Using Generator tools
The third is generator tools. Screaming Frog can crawl a site and export a sitemap. Online tools like xml-sitemaps.com take a URL and return a downloadable XML file. These produce a snapshot of the site as it exists at the moment you run them. If the site changes the next day, the sitemap does not, and you have to re-run the tool. This is useful for static sites that change infrequently, for one-off audits, and for sites where the CMS cannot produce a sitemap natively at all.
4. Manual XML creation by hand
The fourth is manual XML. You write the file by hand, list the URLs yourself, set the lastmod dates yourself, and upload the file to your server. Total control, total maintenance burden. The only time this is genuinely the right answer is when the site is tiny (a dozen pages or fewer), the content rarely changes, and you want full control over every detail without any plugin or platform getting in the way. This is rarer than the discourse around manual sitemaps would suggest.
How to choose your Sitemap Creation Method
The choice usually comes down to three questions, asked in this order.
What CMS are you on?
If you are on WordPress, the answer is almost always a plugin, because the configuration controls and ongoing maintenance are too important to give up. If you are on Shopify, Wix, Squarespace, Webflow, or any other hosted platform with a built-in sitemap, the native sitemap is usually fine, and trying to replace it creates more problems than it solves. If you are on a static site, a headless CMS, or a custom-coded site, the answer is a generator tool, custom code, or manual XML, depending on the size.
How often does your content change?
If you publish weekly or more often, automatic updating matters and you want a method that handles it without your involvement. That rules out manual XML and one-off generator tools as the primary approach. If you publish a few times a year, almost any method works, because staleness is less of an issue when nothing has changed.
How much technical control do you need?
If your site has unusual content types, complex exclusion rules, or specific lastmod requirements, you need a method with strong configuration. Plugins are your best bet here. If your site is simple and standard, the native sitemap is probably enough, and the extra control a plugin provides is overkill; you will not use it.
For most WordPress sites with regular content updates, the answer is a plugin. For most hosted-platform sites, the answer is the native sitemap. For most static or custom sites, the answer is a generator. The exceptions exist, but they are rarer than the noise around sitemap tools would suggest.
A note on switching later
The choice you make now is not permanent. You can switch methods later, and people do, particularly when their site grows past the limits of a CMS-native sitemap or when they outgrow a plugin’s capabilities.
The reason to choose carefully now is to avoid unnecessary churn. Every time you change sitemap sources, the URL of the sitemap itself usually changes too, which means updating robots.txt, resubmitting in Google Search Console and Bing Webmaster Tools, and dealing with the transition period while search engines (and the AI crawlers that have started visiting alongside them) re-learn where the sitemap lives.
It is not a disaster to switch. It is friction worth avoiding. So choose the method that fits your site as it is now and as it will likely be a year from now, not just the easiest option to set up this afternoon.
Where this leaves us
You now have a clear choice in front of you. The shape of your audit findings points to the method that fits your situation. Your CMS and your content cadence narrow it further. The three questions above should make the call obvious in most cases, and the cases where they do not are usually the cases where two methods would both work and the choice does not really matter.
What comes next in this module depends on the method you picked. If you chose a plugin, which is the most common path, the next lesson walks through configuring Yoast, Rank Math, and All in One SEO to produce a clean sitemap. If you chose to build manually, the lesson after that covers the XML-by-hand approach for sites that need it. If you chose CMS-native or a generator tool, the building lessons are still worth reading for context, but the configuration work will be lighter.
Up next: Building a Sitemap with WordPress Plugins →
This is Module 2: Lesson 3 of The Sitemap Series, a Technical SEO series on sitemaps from first principles, built for the AI Search era.