A sitemap is a file listing website addresses and, depending on the format, additional information about those resources. It helps search engines discover pages, particularly on large, new websites or where navigation makes content hard to find. It does not guarantee that every URL will be crawled, indexed or shown at a particular ranking.
Validation should answer two different questions: can the file be read correctly, and do its addresses match the pages intended for public access? Error-free XML can still list redirects, excluded pages or incorrect domain versions. The work does not end when the file is generated.
XML sitemaps, sitemap indexes and HTML navigation
XML is a common URL-listing format and supports extensions for content such as images or videos. A sitemap index can identify several files from a central address. An HTML page with links can help people navigate, but serves a different purpose and does not replace validation of files submitted to search engines.
The protocol allows up to 50,000 URLs and 50 MB per uncompressed file. Split the set if either limit is exceeded. Separating products, categories or languages may also help monitor groups before reaching those limits. There is no general rule that splitting every thousand URLs improves rankings or crawling speed.
Which pages should the file include?
Choose the canonical URLs intended for search results. In a store, these may include categories, products and useful guides. Exclude private pages, internal results without search value, errors, redirects and noindex URLs from the intended set. Do not include every filter combination simply because the system can generate those addresses.
For example, if an article’s HTTPS version is the primary one, use that full address in the sitemap and internal links. An HTTP version that redirects should not be presented as another independent page. This illustration uses a reserved domain; it does not propose changing an existing website’s addresses without inventory and testing.
An XML record contains the address in a loc element. An example fragment within the sitemap structure is <url><loc>https://example.com/categoria</loc></url>. The complete file needs the protocol’s root element and namespace.
How to find or generate a sitemap
Check the generated address in the CMS, module or SEO extension. Do not assume it is always /sitemap.xml or that there is only one file. robots.txt may identify the location with a Sitemap directive. In custom installations, generation should follow content publication and update rules rather than relying on a forgotten manual list.
Test after publishing a page, changing an address or removing a product: the URL set should reflect the decision. For multilingual websites or subdomains, confirm each file’s domain and scope. Where caching exists, check the version actually returned by the server and how frequently it updates.
Checks before submission
- Open the sitemap address and confirm an HTTP 200 response with the expected content, without authentication or a disguised error page.
- Validate XML, UTF-8 encoding, namespace and escaped characters, including & in parameters.
- Confirm each file’s size and URL-count limits.
- Test a URL sample: final response, public content, canonical and indexing directives.
- Compare the sitemap with navigation and the page inventory, looking for omissions and old addresses.
Use lastmod only when it reflects a significant, genuine page update. Changing every page’s date daily does not demonstrate updated content. Google ignores priority and changefreq values. These fields should not be used to claim a module automatically makes a page more important or increases crawling frequency.
Submit and interpret results in Search Console
In the correct Search Console property, submit the file or index address and check whether it was fetched and processed. Successful reading confirms sitemap processing, rather than indexing of every page. If an error occurs, investigate the file and server response before repeatedly resubmitting it.
Compare intended URLs with examples in the indexing report and URL Inspection. Record the reason shown and observation date. A discovered but unindexed page needs assessment of content, technical signals and context; adding it to the sitemap again is not a diagnosis. Live tests and indexed-version information may reflect different times.
Sitemaps, robots.txt and noindex solve different problems
Removing a URL from a sitemap does not prevent discovery through a link. robots.txt guides crawling; noindex says that an accessible resource should not be indexed. If robots.txt prevents the crawler from accessing a page, it cannot read that page’s noindex. None of these files replaces authentication for protecting private data.
Sitemap review forms part of a technical SEO audit when compared with real pages, navigation and indexing. RedeShop can identify inconsistencies and prepare changes with validation before and after publication.