Sitemap

A sitemap is a structured listing of all relevant pages of a website. It helps search engines capture a domain’s content efficiently and helps users find their way around large websites. There are two fundamentally different forms that are frequently confused: the XML sitemap is a technical document for crawlers – it lists URLs with metadata in a machine-readable format. The HTML sitemap is a visible page for visitors, often laid out as a text-based content overview. Both have their place; both address different audiences. In everyday SEO, the XML sitemap matters most. It’s one of the central signals with which you hand Google and Bing a domain’s important URLs “on a silver platter”.

The XML sitemap in detail

The XML sitemap follows the sitemaps protocol and at its core looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.aceart.de/</loc>
    <lastmod>2026-05-22</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://www.aceart.de/leistungen/seo</loc>
    <lastmod>2026-05-10</lastmod>
  </url>
</urlset>

In practice, <loc> and <lastmod> are the only fields still carrying real value.

Limits and the sitemap index

A single sitemap may contain at most 50,000 URLs or 50 MB uncompressed. For larger websites, the collection is split into several sitemaps combined via a sitemap index:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://www.aceart.de/sitemap-pages.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://www.aceart.de/sitemap-blog.xml</loc>
  </sitemap>
</sitemapindex>

A sensible split follows the content structure: one sitemap per section (pages, blog, glossary, portfolio, images, videos). That also eases debugging when one area suddenly stops being indexed.

Special sitemaps

Alongside the standard XML sitemap, specialised variants exist:

• An image sitemap: references images per page (title, caption, licence)
• A video sitemap: preview thumbnail, duration, player URL, content description
• A news sitemap: for Google News, publication date and title per article
• An hreflang sitemap: multilingualism, alternative language versions per URL

These variants can either be embedded in the main sitemap or referenced as separate sitemaps in the index.

The HTML sitemap

An HTML sitemap is a normal web page with a hierarchically sorted link list of all important subpages. Advantages:

• Help for users: alternative navigation, especially on large sites
• Internal linking: additional link juice for deeper-lying pages
• Accessibility: a screen-reader-friendly overview of the site structure

For small websites (< 50 pages), an HTML sitemap is usually superfluous – the main navigation suffices. For large shops or portals, it can be a sensible complement.

Submission to search engines

Search engines find sitemaps in several ways:

1. Link it in robots.txt

Sitemap: https://www.aceart.de/sitemap.xml

This line tells every crawler immediately where the sitemap sits, regardless of whether a search engine operator has explicitly signed up.

2. Google Search Console

Enter the sitemap’s URL in the “Sitemaps” area. Google reads it immediately and then shows errors, discovered URLs and indexed URLs.

3. Bing Webmaster Tools

Analogous to Search Console: submit the sitemap manually. Bing also feeds other search engines from it (DuckDuckGo, Ecosia).

4. Automatic pings

Some CMS send a “ping” to Google when saving a new article to have the sitemap re-read. Practically without effect today – Google prioritises its own crawl cycles.

Best practices

• List only indexable URLs: no noindex pages, no blocked URLs, no redirects
• Use canonical URLs: without tracking parameters, with the correct protocol (https://) and host (www. vs. not)
• Update lastmod: an honest change date — Google evaluates it
• Have it generated automatically: Hugo, WordPress (Yoast, Rank Math), TYPO3, Shopify – all common CMS produce sitemaps dynamically
• Check the sitemap regularly: Search Console shows 4xx, 5xx and redirect URLs in the sitemap
• Keep the maximum size in view: from ~30,000 URLs, better split before limits are reached
• Include images and videos: if visual content matters, image/video sitemaps belong in too

Common sitemap mistakes

• Outdated URLs: deleted or moved pages stay in the sitemap and produce 404/301
• noindex combined with the sitemap: including a URL in the sitemap and blocking it with noindex at once sends contradictory signals
• A protocol mismatch: sitemap on http://, pages on https:// (or vice versa)
• Restricted content: only 50 URLs in the sitemap even though 5,000 should be indexed
• A stale lastmod: statically frozen on the build date – Google notices

Sitemap and “.htaccess” – clean URLs

If you work with URL rewrites (e.g. the .htaccess stripping .html extensions as on aceart.de), the sitemap must be served accordingly: the <loc> entries point to the canonical form, not the .html variant. Otherwise Google indexes the file variant or follows a 301 redirect instead of learning the right URL directly.

Frequently asked questions about sitemaps

Do I even need a sitemap? For small, well-linked websites, Google finds almost everything even without a sitemap. It’s still recommended – it speeds up crawling, helps with large sites and new content, and delivers valuable feedback in Search Console.

Does a sitemap change my ranking? No, not directly. But it accelerates crawling and ensures new content is indexed faster – which can affect visibility indirectly.

Where do I put the sitemap file? Usually in the web root at /sitemap.xml. If the file lives elsewhere, it must be explicitly referenced via robots.txt or Search Console.

Should I also include URLs with parameters? No – only the canonical URL per piece of content. Tracking parameters, sort and filter permutations don’t belong in the sitemap.

How often should the sitemap be updated? Automatically on every relevant content change. Static sitemaps regenerated only once a month lose their value.

Conclusion

The sitemap is one of the least spectacular yet most effective SEO tools: a simple XML file telling search engines what there is to find and what matters. Have it generated automatically, maintain it cleanly and monitor it in Search Console, and you permanently switch off one of the most common indexing problems. We set up clean sitemap structures in every SEO setup and relaunch project – feel free to reach out for a no-obligation consultation.