When planning sitemaps, first distinguish between two purposes: an HTML sitemap helps users find content, while an XML sitemap helps search engines discover pages. Neither can replace the other. Start by organizing the site’s hierarchy, then choose how to generate the sitemap based on how often the site is updated. Continue checking URLs, file accessibility, and page indexing status. The goal is not to list as many links as possible, but to provide clear navigation paths and keep the sitemap up to date as the site changes.
Plan navigation first, rather than just listing links
In 2026, Search Engine Journal reported that Google staff explained how HTML sitemaps still serve a navigation purpose. Search engines can crawl their links like any other links, but HTML sitemaps do not have the same structural characteristics as XML sitemaps.
For example, an e-commerce site could list its main product categories, allowing visitors to browse a category to find products rather than cramming every product URL onto a single page. This approach also works for content sites organized by topic. Keep these points in mind:
- Keep the main categories and navigation menus consistent within a logical hierarchy.
- Prioritize category links that guide visitors deeper into the content.
- Do not make listing every page the sole objective; avoid creating an enormous list that is difficult to use.
Choose how to generate XML sitemaps based on how often URLs change
Check whether the site already generates a sitemap before deciding to create another one. Semrush’s XML sitemap guide recommends built-in platform features or automated tools as the first choice for most sites. Writing a sitemap manually is more suitable when the site has few URLs that rarely change, or when you need control over each entry.
Automatic generation does not necessarily mean ongoing updates. The same guide distinguishes between one-time exports and tools that update automatically. When choosing a tool, check how it updates the sitemap, not just whether it offers an XML download. Consider:
- Whether the tool can handle enough URLs for the site and exclude duplicate URLs, URLs with parameters, or pages you do not want indexed.
- Whether the tool provides format validation and URL status checks.
- Whether the site needs specialized sitemaps, such as those for images or videos, and whether the tool supports them.
If writing a sitemap manually, follow the protocol for the XML structure and namespace, and list each canonical URL. Validate the syntax before placing the file in a publicly accessible location. Include lastmod, which records the last modification time, only if you can keep it accurate.
Keep checking after submission—the file is only the start
When maintaining a sitemap, check both the file and the site itself: does the file load properly, are the listed URLs suitable for indexing, and does the sitemap include new or changed URLs? If you use a one-time export or a manually written file, do not assume that the sitemap will update automatically as the site changes.
Backlinko’s 2024 guide recommends submitting the XML sitemap to Google Search Console and checking page indexing status and the reasons pages are not indexed. Alongside these checks, maintain clear internal navigation and fix broken links. A sitemap helps search engines discover pages, but it cannot replace maintenance of the site’s own navigation. When planning maintenance, consider ongoing error checks separately from one-time sitemap generation.
Sitemap planning and maintenance: perspectives from across the web
If a website has multiple XML sitemaps, does each one need to be submitted separately?
Consider submitting a sitemap index rather than submitting each individual sitemap separately. Semrush's Shopify guide explains that the index links to the individual sitemaps, allowing search engines to access them by following those links. If sitemaps are split into sections such as products, articles, or categories, first check that the links in the index point to the correct individual sitemaps, then submit the index.
What should you check first if submitting a Shopify sitemap results in a "Couldn't fetch" message?
First check whether the sitemap is publicly accessible. Semrush's Shopify guide recommends opening the sitemap URL in an incognito window when you encounter a "Couldn't fetch" message to check whether the site is password-protected. This is a starting point for troubleshooting a fetch failure, not an indication that all submission errors are caused by access permissions.
References
- Small Business SEO: 10 Tips to Get Your Website Found Onlinebacklinko.com · 2024-06-17T09:13:21-05:00 — Source used in the article above.
- Shopify Sitemap: What It Is & How to Submit Onewww.semrush.com · 2021-06-04T20:10:00Z — Discusses: If a website has multiple XML sitemaps, does each one need to be submitted separately?; What should you check first if submitting a Shopify sitemap results in a "Couldn't fetch" message?
- Google Explains How To Use HTML Sitemaps For SEOwww.searchenginejournal.com · 2026-10-09T21:31:30+00:00 — Source used in the article above.
- XML Sitemap: What It Is And How To Generate Onewww.semrush.com · 2015-08-14T15:16:00Z — Source used in the article above.
- What Is Website Architecture? (& How to Improve it for SEO)www.semrush.com · 2020-12-22T14:44:00Z — Discusses: If a website has multiple XML sitemaps, does each one need to be submitted separately?



