Two Different Things Called a Sitemap

Before touching any settings, it is worth separating two ideas that share a name. An XML sitemap is a machine-readable file that lists the URLs you want search engines to crawl, along with metadata such as when each was last modified. Yoast generates this automatically and it is meant for crawlers, not for people. An HTML sitemap is an ordinary page on your website that lists your content in a readable, organised way for human visitors. It also happens to be useful for internal linking and discovery, especially on larger sites. Yoast produces the first automatically and does not create the second, which is the source of most of the confusion around this topic.

Both are worth having. The XML file supports efficient crawling, and the HTML page supports navigation, accessibility, and internal link distribution. This guide covers how to handle each, and how to display the content of one on a page when that is what you actually need.

How AAMAX.CO Can Help You With SEO Services

Sitemap configuration is a small task that sits inside a much larger technical picture, and getting the larger picture right is where results come from. AAMAX.CO provides web development, digital marketing, and SEO services to clients worldwide, and we routinely audit WordPress installations where the sitemap is technically present but full of pages that should never be indexed, or missing the pages that matter most. Because we work in both WordPress development and search strategy, we can align your sitemap with your indexation policy, your internal linking, and your content plan rather than treating it as an isolated setting. If your site has grown organically over several years, that alignment is usually overdue.

Finding Your Yoast XML Sitemap

By default, Yoast publishes an index file at your domain followed by sitemap_index.xml. Visiting that address shows a list of child sitemaps, typically one for posts, one for pages, one for each public taxonomy, one for any custom post types, and one for author archives if those are enabled. Each child sitemap contains up to a set number of URLs and links through to the individual entries. If the index loads and lists child files, your sitemap is working. Submit the index URL in Google Search Console under the sitemaps report, and check back after a day or two to confirm it was read successfully and to see how many URLs were discovered.

Enabling and Controlling What Appears

Yoast's sitemap functionality lives under the plugin's general settings, in the features area, where XML sitemaps can be switched on or off. Once enabled, what appears inside it is governed by your indexation choices rather than by a separate sitemap list. Under the content types and taxonomies settings, anything you mark as not shown in search results is excluded from the sitemap automatically. This is the correct way to control it: decide what should be indexable, and the sitemap follows. Individual posts and pages can also be excluded by setting them to noindex in the Yoast panel on the editing screen. Common candidates for exclusion include tag archives on sites that use tags loosely, author archives on single-author sites, media attachment pages, and thin utility pages.

Creating an HTML Sitemap Page for Visitors

To give humans a readable index, create a normal page titled something like Sitemap and populate it with organised lists of your content. There are three practical approaches. The simplest is to use built-in blocks: WordPress includes list blocks for latest posts and page lists that can be grouped under headings for each section of your site. The second is to use a dedicated HTML sitemap plugin, which generates and updates the listing automatically as you publish. The third, and the most flexible, is a small amount of custom code in your theme that queries your post types and outputs grouped, linked lists. Whichever route you take, organise by topic rather than by date, keep the page linked from your footer, and let it be indexed since it is genuinely useful.

Displaying Sitemap Content Inside a Page

Some site owners specifically want the sitemap listing to appear within an existing page rather than as a standalone document. Because the Yoast file is XML, embedding it directly is not appropriate; it is styled for machines and will look broken to visitors. The correct approach is to generate the same information as HTML. If you are comfortable editing your theme, create a page template that loops through your published pages and posts by type and category and renders them as nested lists, then assign that template to your sitemap page. If you prefer not to write code, an HTML sitemap plugin with a shortcode or block lets you drop the listing into any page, including one with your own introductory copy above it.

Common Problems and How to Fix Them

If your sitemap URL returns a not-found error, first confirm the feature is enabled, then resave your permalinks, which regenerates rewrite rules and resolves the majority of these cases. If it returns a blank page or a raw list without styling, the cause is usually a caching layer or a plugin conflict interfering with the stylesheet, so clear caches and test with other plugins temporarily disabled. If pages are missing from the sitemap, check whether they are set to noindex, whether their post type is excluded, or whether they are password protected. If the sitemap contains pages you do not want indexed, fix the indexation setting rather than trying to filter the file. And if a security plugin or firewall blocks the request, whitelist the sitemap paths.

Keeping the Sitemap Useful Over Time

A sitemap is only as valuable as the URLs inside it. Review it quarterly and confirm that every entry returns a successful status, is canonical, and is genuinely worth indexing. Remove redirects and duplicates by fixing their source. Watch the coverage report in Search Console for a growing gap between submitted and indexed URLs, because that gap usually indicates thin or duplicate content rather than a sitemap fault. On very large sites, splitting sitemaps by section makes diagnosis much easier, since you can see which part of the site is under-indexed. Treating the sitemap as a mirror of a deliberate indexation policy, supported by clean structured data, also strengthens your visibility in AI-driven answer surfaces, which is where GEO services increasingly matter.

Final Thoughts

Getting a Yoast sitemap working is straightforward: enable the feature, visit the index URL, control the contents through your indexation settings, and submit it in Search Console. Getting a human-readable sitemap onto a page takes a little more effort but pays off in navigation and internal linking. If you would like help auditing what should and should not be in your index, or you want a technical review of your WordPress setup, our team is available to take a look.