Add support for SitemapIndex in metadata route resolver #81001
Conversation
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| @@ -149,9 +149,33 @@ export function resolveManifest(data: MetadataRoute.Manifest): string { | |||
| return JSON.stringify(data) | |||
| } | |||
|
|
|||
| export function resolveSitemapIndex(data: MetadataRoute.SitemapIndex): string { | |||
| let content = '<?xml version="1.0" encoding="UTF-8"?>\n' | |||
| content += '<sitemapindex xmlns="https://www.sitemaps.org/schemas/sitemap/0.9">\n' | |||
There was a problem hiding this comment.
The sitemap index namespace URL should use the standard HTTP protocol rather than HTTPS. According to the official sitemap protocol specification, the correct namespace is http://www.sitemaps.org/schemas/sitemap/0.9.
While modern browsers handle both protocols, some sitemap validators and parsers strictly check for the exact namespace URI as defined in the specification. Using the incorrect protocol may cause validation failures or compatibility issues with certain tools.
Consider updating the namespace URL to ensure maximum compatibility:
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">| content += '<sitemapindex xmlns="https://www.sitemaps.org/schemas/sitemap/0.9">\n' | |
| content += '<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">\n' |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
This PR introduces a new SitemapIndex type and extends the resolveRouteData function to properly generate sitemap index XML files.
With this enhancement, Next.js can natively support sitemap index files, offering improved flexibility and better sitemap management for applications.