Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lastmod Field Always Set to Current Date #930

Open
doxsch opened this issue Feb 8, 2025 · 0 comments
Open

lastmod Field Always Set to Current Date #930

doxsch opened this issue Feb 8, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@doxsch
Copy link

doxsch commented Feb 8, 2025

Description:

I've encountered a bug in the next-sitemap package when using it with next export. The field is always set to the current date instead of the date when the content actually changed. This could lead to Google ignoring this information in the future.

Steps to Reproduce:

  1. Install and configure next-sitemap with next export.
  2. Generate the sitemap
  3. Check the field in the generated sitemap.

Expected Behavior:

The field should be set to the actual modification date of the content.

Actual Behavior:

The field is always set to the current date.

@doxsch doxsch added the bug Something isn't working label Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants