Sitemap

What a sitemap actually is

A sitemap is a structured file that lists the URLs a website wants search engines to know about. Think of it as a table of contents handed directly to a crawler: instead of relying only on links to discover pages, the crawler can read one document that names every important address on the domain. The most common format is the XML sitemap, a machine readable file that search engines fetch automatically. There is also the HTML sitemap, a human readable page that helps visitors browse a large site. Both share the same goal, which is making content easy to find, but they serve very different audiences.

A sitemap does not change how your pages rank. It is a discovery and crawling aid, not a ranking signal. Its job is to reduce the effort a search engine spends finding your URLs, which matters most when a site is large, new, poorly linked, or frequently updated.

XML sitemaps versus HTML sitemaps

An XML sitemap follows a strict schema defined by the sitemaps protocol. Each entry sits inside a url block and can carry a location, a last modification date, and sometimes a change frequency or priority value. Google today mostly reads the location and the last modification date and ignores the rest, so obsessing over priority values is wasted effort. A single XML file can hold up to fifty thousand URLs or fifty megabytes uncompressed. Beyond that, you split the list into several files and reference them from a sitemap index, which is a sitemap of sitemaps.

An HTML sitemap is a normal web page with links organized by category. It is useful for human navigation on sprawling sites and can pass internal link equity, but it is not what you submit to a search engine. When people say sitemap in an SEO context, they almost always mean the XML version.

How search engines use a sitemap

When a crawler like Googlebot finds your sitemap, it treats the listed URLs as candidates for crawling. It does not visit them all instantly, and it does not promise to index any of them. The sitemap simply enters those addresses into the crawl queue and provides hints, especially the last modification date, about which pages changed recently and deserve a fresh visit. Search engines discover a sitemap in two ways: you submit it inside Google Search Console or Bing Webmaster Tools, or you declare its address in the robots.txt file with a Sitemap line. Doing both is good practice.

The last modification date is the most valuable field. When it is accurate, crawlers can prioritize genuinely updated pages and skip the ones that have not moved. When it lies, for example when every URL claims to have changed today, search engines learn to distrust the signal and eventually ignore it.

When a sitemap matters (and when it does not)

Sitemaps deliver the most value in specific situations. Large sites with thousands of URLs benefit because internal linking alone rarely surfaces every page. New sites with few external links benefit because crawlers have little else to follow. Sites with rich media, or with pages that are only reachable through search forms or complex navigation, benefit because those URLs are hard to discover organically. Sites that publish or update content often benefit because the last modification date guides recrawling.

Conversely, a small, well linked site of twenty tidy pages gains almost nothing from a sitemap. Every page is one or two clicks from the homepage, so the crawler finds everything anyway. Submitting a sitemap still does no harm, and it gives you useful coverage reporting inside Search Console, so we recommend it regardless. Just do not expect it to fix indexing problems that come from thin content, duplication, or technical blocks.

Common sitemap mistakes

The most damaging mistake is listing URLs you do not actually want indexed: redirects, pages that return errors, canonicalized duplicates, or addresses blocked by robots.txt. A clean sitemap should contain only final, indexable, canonical URLs that return a success status. Mixing in noindex pages sends search engines contradictory instructions.

Other frequent problems include forgetting to update the sitemap when the site structure changes, leaving stale URLs that now redirect or return a 404, using inconsistent protocols such as mixing http and https, and exceeding the size limits without splitting into an index. Fake last modification dates are another classic error, because they erode the trust that makes the field useful in the first place. Finally, many teams generate a sitemap once and never submit it, which wastes half of its value.

Sitemaps at BeBranded

Most of the sites we build run on Webflow, which generates and maintains an XML sitemap automatically at the /sitemap.xml address. Webflow keeps it in sync as you add pages and CMS items, and it lets you exclude specific pages from the sitemap through the page settings. For projects that need finer control, we can disable the automatic file and publish a custom one instead, which is sometimes necessary when a site mixes Webflow pages with externally hosted sections.

Our standard launch checklist includes submitting the sitemap in Google Search Console, declaring it in robots.txt, and confirming that it lists only canonical, indexable URLs. On larger multilingual builds we pay particular attention to how localized URLs appear, so that each language version is discoverable without creating duplicate or conflicting entries. The sitemap is never a magic lever, but treated as part of a wider technical SEO foundation, it helps ensure that the content we produce is found quickly and crawled efficiently.