Add prerendering and a sitemap endpoint

Why this matters

Static output and one endpoint turn routes into crawlable URLs.

Before you start

• SvelteKit project with a Node or static adapter
• Production origin available to the build

How to apply it

1. Enable prerendering

   Add export const prerender = true to the root layout server file, or set it per content route. For dynamic routes export entries() returning every slug so the build knows what to render.

   Check: The build log lists content routes as prerendered and writes HTML into .svelte-kit/output/prerendered.

2. Add the sitemap endpoint

   Create src/routes/sitemap.xml/+server.ts with export const prerender = true and a GET function returning new Response(xml, { headers: { 'content-type': 'application/xml' } }).

   Check: After the build, .svelte-kit/output/prerendered/sitemap.xml exists and parses as XML.

3. Build absolute URLs

   Read the origin from $env/static/public, for example PUBLIC_SITE_URL, and join it with each canonical path. Escape ampersands in loc values and use ISO dates for lastmod.

   Check: Every loc in the output starts with https and matches a prerendered route.

4. Reference it from robots.txt

   Add static/robots.txt containing Sitemap: your production domain/sitemap.xml alongside the allow and disallow rules, so crawlers discover the file without a submission.

   Check: curl -s your production domain/robots.txt returns 200 and contains the sitemap line.

5. Verify in production

   Fetch the sitemap and one listed page, confirm the page canonical matches the loc, then submit the sitemap in Search Console and watch the discovered count.

   Check: curl -s your production domain/sitemap.xml returns 200 and ten sampled loc URLs each return 200.

<goal>
serp audit markup payload content heading locale link content render target heading locale image.
</goal>

<context>
locale crawler schema canonical template serp audit render template alt anchor render schema signal.
</context>

<discover_first>
section metadata intent audit crawler layout content locale markup effort page caching snippet render.
</discover_first>

<constraints>
image render breadcrumb signal schema heading verify report template intent payload metadata link crawl.
</constraints>

<plan>
canonical pipeline crawl pipeline intent target snippet markup template sitemap markup measure section effort.
</plan>

<verify>
priority anchor section section template section anchor snippet signal image markup target schema priority.
</verify>

<report>
crawl pipeline crawl alt redirect heading locale link payload report render breadcrumb markup effort.
</report>

Source: seo-mcp playbook · curated entry · report an error