Two Different Things Called a Sitemap

The word sitemap is used for two entirely different assets, and confusing them causes a lot of wasted effort. An XML sitemap is a machine-readable file that lists the URLs on your site along with metadata such as the date each was last modified. Its audience is search engine crawlers, and its purpose is discovery: making sure nothing important is overlooked, especially on large sites or sites with weak internal linking. An HTML sitemap page is a normal page on your website that links to your content in an organised hierarchy. Its audience is people, and its secondary benefit is providing a clean internal linking hub.

Yoast SEO handles the first one for you automatically and does not create the second one at all. A complete setup uses both, so this guide covers configuring the XML sitemap properly and then building the HTML page by hand.

How We Help at AAMAX.CO

At AAMAX.CO, we manage WordPress sites of every size, from small business brochures to large content libraries and WooCommerce catalogues with tens of thousands of URLs. Sitemap misconfiguration is one of the most common issues we find during technical audits: bloated sitemaps full of tag archives and attachment pages, important templates excluded by accident, or sitemaps that were never submitted at all. We audit indexation properly, decide deliberately which URL types belong in the index, and pair that with the internal linking structure that actually distributes authority. If crawling and indexation are limiting your organic growth, our SEO services team can diagnose and fix it.

Step One: Confirm the XML Sitemap Is Active

In your WordPress dashboard, open the Yoast SEO settings and look under the site features or general settings area for the XML sitemaps toggle. It is enabled by default in modern versions. Beside the toggle there is a link that opens the sitemap index directly, and that is the fastest way to verify it works. Your sitemap index normally lives at your domain followed by sitemap_index.xml.

Yoast does not produce one giant file. It produces an index that points to several child sitemaps, typically one for posts, one for pages, one for each public custom post type, and separate ones for categories, tags, and author archives. Each child sitemap holds up to a thousand URLs before Yoast creates another. Open the index and click through the children so you can see exactly what is being submitted.

Step Two: Decide What Belongs in It

This is the step almost everyone skips, and it matters more than the rest. Yoast builds the sitemap from whatever you have set to be indexed. If a content type is set to appear in search results, it goes in the sitemap; if you set it to not show in search results, Yoast removes it. So controlling the sitemap means controlling your indexation settings rather than editing a file.

Work through your content types and taxonomies and ask a simple question about each: would a searcher landing here get real value, and does this page have unique content? Categories that organise substantial content and carry a description usually earn their place. Tag archives, on many sites, are near-duplicate lists that add clutter and dilute crawl attention, so they are frequently better excluded. Author archives make sense on a multi-author publication and rarely make sense on a single-author business blog. Media attachment pages almost never deserve indexation, and Yoast offers a setting to redirect them to the file itself, which is normally the right choice. Custom post types created purely for internal structure, such as sliders or layout blocks, should be excluded.

You can also exclude individual URLs. Open any post or page, scroll to the Yoast panel, open the advanced section, and set the option that controls whether search engines should show this page in results. Set it to no and the URL leaves the sitemap while remaining live for visitors.

Step Three: Submit and Monitor

Once the sitemap reflects what you actually want indexed, submit the sitemap index URL in Google Search Console under the sitemaps report and in Bing Webmaster Tools. Also make sure your robots.txt file references the sitemap location, which gives any crawler a reliable pointer.

After submission, treat the sitemap report as an ongoing diagnostic rather than a one-time task. Compare the number of URLs discovered against the number indexed. A large gap is a signal, not a mystery: it usually means thin content, duplication, canonical conflicts, or crawl budget being consumed by low-value archives. Fixing the underlying cause raises indexation far more reliably than resubmitting the file.

Step Four: Build the HTML Sitemap Page

Now create the page your visitors can use. Add a new WordPress page, title it clearly, and give it a memorable slug. Then populate it with an organised set of links. There are three practical approaches.

The manual approach is best for small sites: simply list your main sections as headings and your pages as links beneath them. It gives you total control over hierarchy, anchor text, and which pages get prominence, which is exactly what makes an HTML sitemap useful for internal linking. The block approach uses WordPress core blocks such as the latest posts block or a page list block to output content groups automatically, which keeps the page current with minimal maintenance. The plugin approach uses a dedicated HTML sitemap plugin when your archive is too large to maintain by hand.

Whichever route you take, organise by topic rather than by date, use descriptive link text instead of generic phrases, and keep the page genuinely readable. Then link to it from your footer so both visitors and crawlers can reach it from anywhere on the site. Do not exclude this page from indexation; it is a legitimate page with a legitimate purpose.

Common Problems and Fixes

If the sitemap returns a not-found error, first re-save your permalinks, which regenerates the rewrite rules that serve the file. If the file loads but appears as unstyled raw markup, that is normally a caching or security plugin interfering with the stylesheet and the sitemap itself is still valid. If a page is missing from the sitemap, check that its indexation setting has not been switched off and that it is genuinely published rather than private or scheduled. If your sitemap is enormous and full of archives, revisit the indexation decisions in step two rather than trying to trim the file.

Finally, remember that a sitemap is a discovery aid, not a ranking mechanism. Including a URL does not guarantee indexation, and excluding a URL from the sitemap does not remove it from the index. Use a noindex directive for genuine removal and rely on the sitemap to help crawlers find what you want found.

Wrapping Up

A properly configured Yoast sitemap plus a thoughtfully built HTML sitemap page gives you clean discovery for crawlers and clear navigation for people. The real work is not toggling the setting; it is deciding deliberately which URLs deserve to be in the index and then keeping that decision current as the site grows.

If you would like an expert review of your WordPress indexation, internal linking, and crawl efficiency, hire AAMAX.CO for SEO services. We combine technical digital marketing execution with hands-on WordPress development for clients worldwide.