XML Sitemap Architecture: What to Include, Exclude, and Build in Next.js

An XML sitemap is a structured document conforming to the sitemaps.org XML schema protocol 0.9. While search engines discover pages primarily through internal hyperlinks, sitemaps act as a reliable discovery fallback for newly created articles, deep category archives, and media assets that have few inbound links.

As outlined in our technical SEO pre-launch checklist, search engines do not guarantee that every URL listed in a sitemap will be indexed. Instead, sitemaps provide discovery hints that allow Googlebot and Bingbot to allocate their crawl budgets efficiently toward valuable, high-quality content.

The golden rule of technical SEO sitemap architecture is: Only include URLs you actively want search engines to rank in organic search results. Mixing erroring, redirected, or utility pages into your sitemap dilutes crawl budget and creates conflicting signals in Google Search Console.

The standard sitemap XML schema defines five core tags. However, how modern search engines interpret these tags differs significantly from theoretical documentation:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/blog/xml-sitemap-guide-nextjs</loc>
    <lastmod>2026-10-22T12:00:00Z</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Next.js App Router simplifies sitemap generation by providing the src/app/sitemap.ts convention. This TypeScript route handler automatically queries your content repository, formats the XML payload, sets the proper Content-Type: application/xml headers, and serves /sitemap.xml without external plugins.

import type { MetadataRoute } from "next";
import { ALL_POSTS } from "@/content/blog";
import { getSiteUrl } from "@/lib/utils/url";

export default function sitemap(): MetadataRoute.Sitemap {
  const baseUrl = getSiteUrl();

  // 1. Static high-value marketing and hub pages
  const staticRoutes: MetadataRoute.Sitemap = [
    {
      url: baseUrl,
      lastModified: new Date(),
      changeFrequency: "daily",
      priority: 1.0,
    },
    {
      url: `${baseUrl}/blog`,
      lastModified: new Date(),
      changeFrequency: "daily",
      priority: 0.9,
    },
    {
      url: `${baseUrl}/glossary`,
      lastModified: new Date(),
      changeFrequency: "weekly",
      priority: 0.8,
    },
  ];

  // 2. Dynamic content routes generated from blog schema
  const blogRoutes: MetadataRoute.Sitemap = ALL_POSTS.map((post) => ({
    url: `${baseUrl}/blog/${post.slug}`,
    lastModified: new Date(post.reviewedAt || post.updatedAt || post.publishedAt),
    changeFrequency: "monthly",
    priority: 0.7,
  }));

  return [...staticRoutes, ...blogRoutes];
}

For very large websites with tens of thousands of items, Next.js also supports generateSitemaps(), which splits URLs across multiple sitemap indices (/sitemap/0.xml, /sitemap/1.xml) automatically, preventing individual file size bottlenecks.

Auditing enterprise web applications reveals recurring sitemap mistakes that trigger crawl budget loss and indexing warnings:

Before releasing major updates or site migrations, review this verification checklist to guarantee sitemap integrity: