Most small business WordPress sites have an xml sitemap running in the background. It was probably set up by a plugin, possibly years ago, and nobody has looked at it since. The site looks fine to human visitors. Pages load, forms work, the phone rings occasionally. But underneath, sitemap problems can quietly prevent important pages from appearing in search results, slow down the discovery of new content, and waste the attention search engines give your site. This article walks through the common xml sitemap issues that affect indexation and explains how to fix them on WordPress without needing a computer science degree.
Key Takeaways
- XML sitemap problems can silently stop your most valuable pages from being indexed, even when your site looks perfectly normal to visitors.
- Common xml sitemap issues include missing key pages, noindex pages listed in the sitemap, redirected or broken URLs, and conflicts with canonical tags.
- WordPress sites with automatically generated sitemaps from cms plugins or the core often need manual cleanup and ongoing monitoring in google search console.
- A clean, curated sitemap tells search engines which website urls matter most, improving crawl efficiency and helping search engines find new or updated content faster.
- If you feel stuck, you can work through the checklist below or speak with Gareth at Redshaw Consulting via the contact page for hands-on help with technical seo issues.
What An XML Sitemap Really Does For A Small Business Site
An xml sitemap is a machine-readable file in xml format that lists the website’s pages you want search engine crawlers to know about. Google, Bing, and other search engines use it to discover pages, evaluate what content exists, and decide what to crawl next. It is not a page your customers will ever see. It exists purely so that search engines crawl your site more intelligently.
For a typical small business WordPress site with 30 to 500 URLs, the sitemap acts as a curated declaration of which individual urls the owner considers worth indexing. XML sitemaps guide search engines to a site’s most valuable pages. They also enable the discovery of orphan pages with few internal links, which is particularly useful for deeper service pages or blog posts that are not prominently linked from your main navigation.
Submitting a sitemap in google search console does not guarantee that pages get indexed. Google uses content quality, internal linking, canonical tags, and many other signals to decide what enters the index. But a clean sitemap strongly influences crawl discovery. Sitemaps help search engines find new or updated content faster, and xml sitemaps help Google discover new pages faster. For a small, low-authority domain, this matters because Googlebot may not visit frequently. Sitemaps improve crawl efficiency by listing all urls, which means your crawl budget goes further. You must explicitly point search engines to your sitemap, typically via your robots.txt file or direct submission in search console.
It is worth noting the difference between xml sitemaps and html sitemaps. An html sitemap is a visible page designed for human visitors to navigate your site. It helps with internal linking and usability. The xml file is strictly for search engines, not for people. They serve different purposes and one does not replace the other.
How WordPress Generates Sitemaps (And Where Things Go Wrong)
Since WordPress 5.5, released in August 2020, WordPress core ships with an automatically generated sitemap at /wp-sitemap.xml. This was a useful addition, but it created a problem that many site owners still do not realise they have.
Common SEO plugins like Yoast, rank math, All in One SEO, and SEOPress each create sitemaps of their own, typically at paths like /sitemap_index.xml. These plugin-generated sitemaps usually override or exist alongside the core version. The result is that many small sites inadvertently end up with multiple sitemaps and overlapping individual sitemaps, sending mixed signals about which website urls are canonical and which should be indexed.
Dynamic sitemaps from these plugins update automatically with site changes, which is generally helpful. But if both the core and a plugin are generating sitemaps simultaneously, you get duplicate entries, inconsistent noindex rules, and confusion in google search console about which sitemap url Google should follow.
The fix is straightforward: pick one system. Either use the native WordPress sitemap or the one from your SEO plugin, and disable the other. Include your sitemap url in your robots txt file so search engines know where to look. Gareth at Redshaw Consulting often begins audits by checking robots.txt, the root sitemap.xml, and any gz extension versions to see exactly which sitemap Google is actually being pointed to. That single check frequently reveals the first layer of problems.
Core Sitemap Structure: Index Files, Individual Sitemaps, And Limits
A sitemap index file, such as /sitemap_index.xml, acts as a master list that references multiple individual sitemaps. These might be organised by content type: one for posts, one for pages, one for categories, one for product pages. This structure makes diagnostics far easier when you are reviewing the indexing report in google search console, because you can see exactly which content type is struggling.
Search engines impose strict limits on xml sitemaps. A sitemap can include up to 50,000 URLs per file, and sitemaps should not exceed 50,000 URLs per file. Sitemap files must be under 50MB when uncompressed. Keep sitemap files under 50MB and 50,000 URLs. For most websites running a small business WordPress site, you will never approach these limits, but the principle of hygiene matters more than scale.
A few technical details catch people out. The xml standard requires correct syntax: a single missing closing tag can render a sitemap useless. Empty sitemaps will result in an error in google search console. Dates in <lastmod> fields must follow ISO 8601 format, and all the urls must use fully qualified urls with consistent protocol (HTTPS, not a mix of HTTP and HTTPS).
For a typical small site, aim for one sitemap index referencing three to eight individual sitemaps. That structure simplifies maintenance and makes it manageable for non-technical owners to understand what is included.
Problem 1: Important Pages Missing From The Sitemap
Small business owners often assume that all the pages on their site are in the sitemap. They rarely are. Plugin settings, custom post types, and manual toggles can quietly exclude the very pages that drive enquiries.
Common missing-page scenarios include:
- Flagship service pages built as a custom post type that the SEO plugin does not include by default
- City or service-area landing pages excluded because their post type is not set to “public”
- Seasonal offers or campaign pages that were published but accidentally marked as noindex
- Cornerstone blog content that generates leads but sits outside the default sitemap configuration
To spot gaps, compare the sitemap url list against a manual checklist of your key pages or pull a google analytics report showing top landing pages over the last 90 days. Any page bringing meaningful traffic or enquiries that is not in the sitemap needs to be added.
In Yoast or rank math, check that the correct post types and taxonomies are enabled for sitemap inclusion. Verify that individual posts are not accidentally toggled to noindex. Sitemaps should only include high-value, indexable pages, but you need to make sure those high-value pages are actually there. Include only high-value pages in your sitemap, and confirm that nothing important has fallen through the cracks.
If a page is intentionally hidden from menus but still meant to rank, such as a PPC landing page also targeting organic queries, it must still be indexable and present in an appropriate individual sitemap.
Problem 2: Noindex URLs Sneaking Into Your Sitemap
Having noindex pages listed in your xml sitemap sends contradictory signals. The sitemap says “please index this,” while the meta robots tag on the page says “do not index this.” This confusion wastes crawl budget and can drag down perceived site quality in search engines’ eyes.
Common culprits include:
- Thank-you pages after form submissions
- Internal search results pages
- Filtered ecommerce views
- Staging content accidentally left with noindex directives
Sitemaps should exclude noindex pages to avoid confusion. Avoid including noindex pages in your sitemap. Google may also ignore URLs blocked in robots.txt files, adding another layer of potential conflict.
To find these, open google search console’s Page Indexing report and filter for “Submitted URL marked ‘noindex’.” This shows individual urls that are both in a submitted sitemap and blocked from indexation. The Yoast help documentation on this error walks through the specifics clearly.
The fix is binary: either remove the noindex tag if the page should rank, or exclude the page from the sitemap if it genuinely should not be indexed. Gareth and Redshaw Consulting usually align sitemap inclusion rules with meta robots logic so they remain in sync automatically as the site evolves, preventing this from recurring every time new content is published.
Problem 3: Redirected And Broken URLs Listed In The Sitemap
Listing 301, 302, 404, or 410 URLs in your sitemap wastes crawl budget and dilutes search engines’ trust in your index files. Sitemaps should not include 404 or 410 error pages. Every time a crawler follows a sitemap url only to hit a redirect chain or a dead page, that is attention diverted from your genuinely valuable content.
This happens most often after:
- Site redesigns where URL slugs changed but sitemap entries stayed
- Discontinued product pages in a small ecommerce catalogue
- Location pages removed after an office move or service area change
Regularly scan your sitemap and remove URLs that do not return a 200 OK status code. Tools like Screaming Frog or Sitebulb can crawl all the urls in your sitemap in bulk and report every status code. Google search console also flags these as “Submitted URL not found (404)” or “Submitted URL seems to be a Soft 404.”
The resolution is to remove redirected or broken URLs from the sitemap and ensure the final destination URLs are included instead. In audits of small ecommerce sites, it is common to find that 15 to 25 percent of URLs in product sitemaps are redirects or 404s. Cleaning those up has been shown to improve submission-versus-indexed ratios noticeably within four to six weeks.
Problem 4: Canonical Tag Conflicts And Duplicate Variants
Each indexable page should have a single, self-referencing canonical tag, and the sitemap should list only those canonical urls. When the sitemap includes non-canonical variants, you create a conflict that search engines have to resolve on their own, often not in your favour.
Typical mistakes include:
- Listing both HTTP and HTTPS versions of the same page
- Including www and non-www variations as separate entries
- Adding query-parameter versions (e.g. ?utm_source=email) to individual sitemaps
- Listing paginated archive pages that canonicalise back to page one
Sitemaps should not contain duplicate URLs. Google search console will show “Duplicate, Google chose different canonical than user” for URLs where your declared canonical does not match what Google’s canonicalization process selects.
To fix this, crawl the entire website, export all canonical tags, and cross-reference against the sitemap. Ensure only canonical pages appear. Update WordPress settings and plugin configuration so future URLs are generated consistently. For multilingual or multi-location setups, hreflang and canonical logic must align so each language or region has its own clean sitemap segment listing only the preferred versions.
Problem 5: Stale Pages And Outdated Content In The Sitemap
Old, thin content lingering in the sitemap weakens the overall quality signals you send to search engines. Including low-quality content in a sitemap can dilute site authority. Think 2017 blog posts with 100 words, expired seasonal offers, or empty category archives with no useful content behind them.
Use google analytics or another analytics suite to identify URLs in the sitemap that receive almost no organic traffic over the last six to twelve months. Then decide:
- Improve and expand the page substantially with unique, valuable content
- Merge it into a stronger piece and redirect the old URL
- Apply noindex and remove it from the sitemap if it serves no clear purpose
Including <lastmod> helps prioritize recrawling of updated content. Use <lastmod> to indicate when a page was last updated, but make sure those dates reflect genuine updates: new copy, richer media, updated FAQs. Not just a footer year change or a minor CSS tweak. Misleading lastmod values erode the trust search engines place in your sitemap data.
Treat the sitemap as a curated library of your best work, not a dumping ground for every URL WordPress happens to generate.
Problem 6: Overly Noisy Sitemaps From Plugins And Archives
WordPress can generate dozens of low value urls from archives: author archives, tag archives, date archives. Many cms plugins add these to individual sitemaps by default, and for most local service businesses, they add zero search value.
These utility pages consume crawl budget, clutter search console reports, and make it harder to see where real problems are. For a plumber or accountant, nobody is searching for your author archive or your June 2023 date archive.
In your SEO plugin settings, switch off sitemap inclusion for:
- Author archives
- Date-based archives
- Tag archives (unless genuinely useful and well-populated)
- On-site search result pages
Ecommerce shops using WooCommerce need a more careful approach: include product pages and main category URLs while excluding faceted filters, sort orders, and on-site search results that can explode the number of indexed pages with thin content.
A focused sitemap structure makes it much easier for Gareth or any seo specialist to diagnose issues like thin category pages or poorly performing collections.
Google Search Console: Your Primary Sitemap Health Dashboard
Google search console is the central tool for monitoring sitemap performance and indexing status. Submit your xml sitemap via google search console using the sitemaps report. You can submit or resubmit a sitemap index url and verify that Google can fetch it successfully without access or syntax errors.
The Page Indexing report, filterable by sitemap, shows which individual urls are pages indexed, which are excluded, and why. Common exclusion reasons include “Crawled, currently not indexed,” “Alternate page with proper canonical tag,” and the various error states discussed above.
Use the URL Inspection tool to diagnose sitemap issues on a per-page basis. It shows the live versus indexed version, the canonical Google selected, any noindex directives, and the last crawl date. Validating a sitemap can also be done using the W3C XML Schema Validator if you suspect syntax problems.
Set a recurring monthly reminder to review sitemap coverage. Watch for spikes in “Submitted URL not indexed” or sudden drops in indexed counts. For complex cases, document what you find in search console and contact Redshaw Consulting through the contact page to review findings together.
How Sitemaps Affect Crawl Budget And Discovery On Smaller Sites
Crawl budget is more commonly discussed in the context of large sites and large websites with millions of pages, but even modest sites feel the effects of a messy sitemap. If Google crawls a batch of redirected, noindexed, or duplicate URLs from your sitemap, your new pages wait longer to be discovered.
A lean, updated sitemap helps search engines prioritise strong pages over low value urls like login pages, cart steps, and duplicate listing views. This directly improves crawl efficiency.
Consider a practical example: a local electrician adding a new “EV charger installation” page in April 2026 wants it discovered and indexed quickly. When that page appears cleanly in a dedicated services sitemap with an accurate lastmod date, Google crawls and indexes it far faster than if it is buried among hundreds of irrelevant archive URLs.
For sites occasionally surfacing in google discover, fresh and clearly signalled updates can help new content get picked up more reliably. Giving google accurate freshness signals through lastmod matters here, although Discover is never guaranteed.
Internal linking and site structure still matter. A sitemap cannot compensate for orphaned pages with no internal links from other pages. But it can speed up discovery significantly once those links exist.
Special Cases: Ecommerce Catalogues And Service-Area Businesses
Ecommerce and multi-location service sites have specific sitemap edge cases that often surface in audits Gareth runs at Redshaw Consulting.
For ecommerce, separate individual sitemaps for product pages, primary categories, and informational content. Exclude filtered URLs, sort parameters, and site search results that can create thousands of low-value entries. Discontinued products should be redirected to successors or return a 410 status and be removed from product sitemaps. You might also consider an image sitemap for product photography and video sitemaps if you produce product demonstrations, though these are separate from your main xml sitemap and follow their own conventions.
For service-area businesses covering multiple towns, resist the temptation to auto-generate hundreds of near-duplicate landing pages. One audit found a business with 50 thin town pages, most excluded by Google for duplicate content. Pruning to five well-written, unique pages and canonicalising the rest improved SERP visibility for the main service pages. A dedicated sitemap segment for location pages allows precise tracking in google search console to see whether locations, products, or news articles are suffering more indexation issues.
Prioritising Cleanup: What To Fix First When Time Is Tight
Small business owners rarely have days to spend on technical seo. You need a clear order of operations that targets the highest-impact problems first.
A practical priority sequence:
- Remove obvious errors: 404s, 301s, test pages, and blocked url entries from all sitemaps
- Align canonical tags and protocols so the sitemap contains only canonical urls
- Remove noindex pages and thin content from the sitemap
- Fill in any missing pages, especially revenue-generating service or product pages
- Prune noisy archives and low-value taxonomies
Start with the sitemap index that contains core service pages or product pages, since improving their indexation has the biggest commercial impact on website performance.
Keep a written change log, even a simple spreadsheet, noting which individual sitemaps were edited, when they were resubmitted in search console, and what metrics to recheck after four to six weeks. That discipline turns sitemap maintenance from guesswork into a measurable process.
If you would rather stay focused on running your company while someone else handles this sequence, Gareth at Redshaw Consulting can review and prioritise technical fixes after a quick enquiry via the contact page.
Monitoring After Fixes: How To Know If Your Changes Worked
Sitemap improvements rarely produce instant ranking jumps. What they should produce is better index coverage and faster reflection of content changes over several weeks.
In google search console, compare “Submitted vs Indexed” counts for each individual sitemap over 30 to 90 day periods. A rising ratio of indexed pages to submitted URLs is the clearest sign of progress.
Track impressions and clicks for key landing pages in the Performance report. Cross-reference with organic sessions and conversions in google analytics to confirm that more indexed pages actually translates to useful traffic. Spot-check previously excluded URLs using the URL Inspection tool to confirm Google is now treating them as indexable and correctly canonicalised.
Schedule a quarterly review cycle: validate sitemaps, tidy new redirects, remove obsolete URLs, and re-evaluate any templates that continue to struggle. Structured data issues, affect rankings signals, and site structure changes all accumulate over time, and periodic reviews catch problems before they snowball.
When To Bring In Help (And What To Expect)
It is entirely normal for non-technical business owners to feel overwhelmed by xml sitemap errors, index files, and error codes in google search console. The terminology alone can be off-putting.
An seo specialist like Gareth at Redshaw Consulting typically audits the current sitemaps, cross-checks with live URLs and analytics, fixes structural problems, and aligns plugin settings so future content behaves properly. An experienced consultant can usually identify and prioritise the 20 percent of sitemap and indexation issues that deliver 80 percent of the practical benefit for a small WordPress site.
If you suspect sitemap issues but are not sure where to start, gather your search console screenshots and reach out via the contact page for a straightforward initial conversation. Sitemap work is rarely “one and done,” and having someone periodically review crawl and index patterns prevents subtle problems from becoming serious visibility losses. The goal is not perfection for its own sake. It is making sure that when someone searches for what you do, search engines find the right pages and those pages are eligible to appear in search results.
FAQ
This section addresses common follow-up questions that small WordPress site owners tend to ask once they start looking at their sitemaps more closely.
Do I need both a sitemap.xml and a sitemap_index.xml file?
Many WordPress setups end up with a simple sitemap.xml that redirects to or references a more complex sitemap_index.xml created by an SEO plugin. In most cases, you only need one master entry point listed in google search console, usually the sitemap index file that organises all the individual sitemaps. Keep whichever implementation is more complete and controllable, then adjust your robots txt file and search console so search engines consistently follow that one. Running multiple sitemaps from different sources creates confusion and makes it harder to discover pages reliably.
How often should I update or resubmit my sitemap in Google Search Console?
For a stable small business site, manual resubmission is only necessary after significant structural changes such as a redesign, new content sections, or large-scale URL redirects. Dynamic sitemaps update automatically with site changes, and Google will recrawl them periodically without manual prompts. Check the sitemaps report in search console every month or two and resubmit only if you have fixed errors or added substantial new groups of new pages.
Can a bad sitemap alone stop my pages from ranking?
A flawed sitemap can make it harder or slower for search engines to find and trust your pages, but rankings also depend on content quality, link equity, and user signals. Sitemap fixes are about removing friction: getting key pages crawled and indexed reliably so that other pages and other seo work can actually have an effect. Do not expect sitemap tweaks alone to rescue thin content or poor on-page optimisation. Google indexes pages based on many factors, and the sitemap is one signal among several.
Should I include my blog category and tag pages in the sitemap?
High-quality, well-written category pages that serve as useful content hubs can be good candidates for inclusion. However, automatically generated tag archives often create thin, overlapping pages that dilute relevance. These are usually better excluded from sitemaps and sometimes from indexing altogether. Evaluate each archive type based on whether it genuinely helps visitors discover content and whether it contains enough unique value to stand on its own as a single page worth indexing.
What if my sitemap shows URLs that no longer exist on the live site?
This situation commonly arises after a migration or redesign where plugins were not reconfigured or old sitemap caches were not cleared. The result is missing pages from the live site still being submitted to Google as if they exist. Fetch a fresh sitemap from the plugin, clear any caches, and crawl it with a tool that checks for 404 and 301 responses. Remove any non-existent URLs and ensure that legacy URLs either redirect properly to create sitemaps for the current site structure, or return a correct 410 status if they are gone permanently.
