An XML sitemap is a file that lists the URLs on your site and helps search engines and AI crawlers discover, understand, and prioritise your content. It's a map that tells machines where everything lives, when it was last updated, and which pages are worth paying attention to.

Why sitemaps matter for AEO

AI engines discover content through crawling, internal links, and sitemaps. If your site has strong internal linking, a sitemap is less critical. But most sites have gaps: new pages that haven't been linked to yet, deep content that's hard to reach through navigation, or updated articles that need to be re-crawled quickly.

A sitemap fills those gaps. It gives crawlers a direct list of your most important URLs so they don't have to find everything by following links. For AEO, that matters because the faster AI engines discover and process your content, the sooner it becomes eligible to be cited.

What a bad sitemap looks like

A sitemap that causes more harm than good usually has one or more of these problems:

  • Pages that redirect to somewhere else rather than the final URL
  • Broken pages that return 404 or 500 errors
  • noindex pages you've already told crawlers to ignore
  • Duplicate URLs from HTTP and HTTPS or www and non-www versions
  • Thousands of thin, low-quality pages you'd rather crawlers didn't find
  • A lastmod date that's never updated, making it look like nothing changes

How to make your sitemap work for AEO

Only include pages you want discovered

Your sitemap should contain the pages you genuinely want AI engines to find and potentially cite. Admin pages, thank-you pages, and internal search result pages don't belong there.

Keep the lastmod date accurate

If you update an important guide, make sure the lastmod date reflects that. AI engines use this to prioritise re-crawling recently updated content, which matters for freshness signals and citation potential.

Reference it in robots.txt

Add a line to your robots.txt file: Sitemap: https://yourdomain.com/sitemap.xml. This makes it immediately findable by any crawler that reads robots.txt first.

Keep it clean and current

Review your sitemap after any major site restructure, URL change, or content migration. Stale sitemaps pointing to redirected or deleted pages are one of the most common and easily avoidable technical AEO problems.

A real example

Synapse, a forex broker, has a well-written guide section covering market analysis and trading fundamentals. But their sitemap was generated during the initial site build and never updated. It still lists old product pages that redirect, several articles that have since been consolidated, and the lastmod dates haven't changed in eight months.

An AI crawler reading that sitemap gets a misleading picture of the site's currency and structure. A fresh, accurate sitemap pointing to the right pages with current lastmod dates changes that immediately.

Don't obsess over priority values. The priority field in XML sitemaps (0.0 to 1.0) is largely ignored by most crawlers. Spending time tuning priority values is far less useful than making sure your URLs, lastmod dates, and page selection are accurate.