Content-Length: 298369 | pFad | http://github.com/vercel/next.js/issues/81644

7A Sitemap XML generated with incorrect https namespace instead of http (Metadata) - Google Search Console error · Issue #81644 · vercel/next.js · GitHub
Skip to content

Sitemap XML generated with incorrect https namespace instead of http (Metadata) - Google Search Console error #81644

@christiancenti

Description

@christiancenti

Link to the code that reproduces this issue

https://github.com/christiancenti/reproduction-sitemap-bug

To Reproduce

  1. Use MetadataRoute.Sitemap to generate a sitemap with language alternates in Next.js.
  2. Inspect the resulting sitemap XML.
  3. Submit the sitemap to Google Search Console.
  4. Observe the "incorrect namespace" error.

Current vs. Expected behavior

Current:
The sitemap XML generated by the Next.js Metadata system uses https in the namespace declarations:

This causes Google Search Console to report an "incorrect namespace" error.

Expected:
The generated sitemap XML should use the official http namespaces as per spec:

Google Search Console should accept the sitemap without namespace errors.

Provide environment information

Relevant Packages:
next: 15.4.0-canary.129

Additional context

Thank you for your help!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: http://github.com/vercel/next.js/issues/81644

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy