Most WordPress sites running Yoast, Rank Math or All in One SEO generate an XML sitemap automatically, and that automation is exactly why so many sitemaps are wrong. The plugin lists every published URL by default, including pages that are noindexed, redirected, or sitting behind a canonical tag pointing somewhere else. Getting xml sitemap best practices right means deciding what stays and what gets stripped out, not accepting whatever the plugin produces.
What actually belongs in an XML sitemap
A sitemap should list only the URLs worth indexing and ranking: canonical pages that return a 200 status, are not blocked by robots.txt, and are not marked noindex. That is the entire brief. Google’s own sitemap documentation describes it as a hint for discovery, not a request for ranking, and treats every other URL as noise that slows down how a crawler spends its time on the site.
For a typical UAE service business, this usually means the homepage, service pages, location pages, published blog posts and a handful of core pages like the about and contact page. Thin tag archives, paginated search results and internal utility pages such as a cart or account dashboard do not qualify, even though WordPress happily includes them by default.
Sitemap SEO mistakes that quietly waste crawl budget
The most common sitemap seo mistakes share one root cause: nobody checks the sitemap after the plugin builds it. Four show up repeatedly on sites Dominate Online audits in Dubai.
Noindexed pages still appear in the sitemap because the noindex tag and the sitemap generator run independently of each other inside most SEO plugins. Redirected URLs linger after a site migration or a URL structure change, sending Googlebot to a 301 instead of the live page. Pages with a canonical tag pointing elsewhere get listed under their own URL rather than the canonical target, which sends a mixed signal about which version should rank. Parameter URLs from filtered category pages or tracking parameters multiply the sitemap with near-duplicate entries that add nothing.
What to exclude from a sitemap
Treat the sitemap as a curated list, not an export. Pull out anything with a noindex directive, anything returning a 3xx or 4xx status, anything canonicalised to a different URL, and anything generated by a filter or search parameter. Staging URLs, PDF downloads that duplicate on-page content, and tag or author archives with little unique content belong on that exclusion list too.
Checking this by hand across a few hundred URLs is slow and error-prone. Screaming Frog’s list mode, pointed at the sitemap XML directly, cross-references every listed URL against its status code, indexability and canonical tag in one pass. That is the fastest way to catch the mismatches before Google does.
Segmenting sitemaps for larger sites
A single sitemap file works fine under a few thousand URLs. Past that, split it by content type: one sitemap for pages, one for posts, one for products if the site runs an ecommerce catalogue, each referenced from a sitemap index file. This makes it far easier to spot a problem. If the post sitemap suddenly jumps from 400 URLs to 4,000 overnight, that is a visible signal rather than a number buried inside one enormous file.
Segmentation helps with diagnosis inside Google Search Console too, where the coverage report can be checked per sitemap rather than across the whole site at once. A sitemap index submitted at the site root, with each child sitemap under 50,000 URLs and 50MB uncompressed, matches Google Search Central’s sitemap guidelines and keeps each file fast to process.
Auditing your current sitemap
Start by pulling the sitemap URL directly, usually /sitemap_index.xml or /sitemap.xml on a WordPress site, and checking it resolves with a 200 status. Then crawl every URL it lists and flag anything that is not a 200, indexable, canonical page. Compare the count against what Search Console reports as submitted versus indexed. A large gap between the two numbers usually points to exactly the exclusion problems covered above.
This kind of hygiene issue sits alongside the duplicate content problems covered in our guide to fixing duplicate content with canonical tags, since a bloated sitemap and unresolved canonical conflicts tend to appear on the same sites. A clean technical foundation affects more than crawling, as covered in our guide on how technical SEO affects conversion rates once pages get indexed and found.
Frequently asked questions
Why does Search Console show URLs in my sitemap as “Discovered, currently not indexed”?
This usually means Google crawled the URL but decided it was not worth indexing, often because the page is thin, duplicates another page, or the sitemap listed a URL that should have been excluded under the rules above. Removing the URL from the sitemap will not fix the underlying content or canonicalisation issue, only the signal around it.
Should I include paginated pages like /blog/page/2/ in the sitemap?
No. Paginated archive pages are a navigation aid, not content worth ranking on their own, and including them adds low-value URLs that compete for crawl attention against the individual posts and pages that should rank.
My developer regenerated the sitemap after a site migration and rankings dropped, could the sitemap be the cause?
The sitemap itself cannot cause a ranking drop since it is only a discovery hint, but a migration that left redirects, canonical tags and the sitemap out of sync often explains the timing. Check that the new sitemap lists only live, canonical URLs and that old URLs now return the correct redirect rather than a 404.
Do I need a separate sitemap for images or videos?
Only if image or video discovery matters to the business and the default XML sitemap does not already include image tags, which most modern WordPress SEO plugins do. For most UAE service sites, a single well-maintained page and post sitemap covers the need without a dedicated image sitemap.
Sitemap hygiene is a small, mechanical task that gets ignored because it rarely breaks anything visibly. On a larger site, crawl budget eventually gets spent on noindexed pages and expired redirects instead of the content that should rank. See how Dominate Online’s technical SEO audits catch sitemap and indexation problems like these before they cost a site its crawl budget.