next-sitemap: [Probs a bug] Totally empty sitemap? Lol?

Hello.

I’m using Next.js 13 with the App Router. I know that next-sitemap can generate good sitemaps files with this setup. I’ve already done this in my current (and first Next.js) project.

I’m doing my best with generateStaticParams, and have an exhaustive output of my paths when I build my Next project.

Output of yarn build:

Route (app)
┌ ● /[locale]
├   ├ /fr
├   └ /en
├ ● /[locale]/[categ]
├   ├ /fr/patch-notes
├   └ /en/patch-notes
├ ● /[locale]/[categ]/[subcateg]
├   ├ /fr/patch-notes/dashboard
├   ├ /fr/patch-notes/discord-bot
├   ├ /en/patch-notes/dashboard
├   └ /en/patch-notes/discord-bot
├ ● /[locale]/[categ]/[subcateg]/[slug]
├   ├ /fr/patch-notes/dashboard/post-01
├   ├ /en/patch-notes/dashboard/post-01
├   ├ /fr/patch-notes/discord-bot/post-01
├   └ /en/patch-notes/discord-bot/post-01
├ ● /[locale]/dashboard
├   ├ /fr/dashboard
├   └ /en/dashboard
├ ○ /apple-icon.png
├ ○ /favicon.ico
└ ○ /icon.svg

●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)

Here is sitemap.xml:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
</sitemapindex>

(yah, I’m crying)

Moreover, here’s the disaster: As I’m a bit of an idiot (lol), I tend to use the git commit --amend command a lot and I totally lost the original code which was somehow “compatible” (?) with next-sitemap, and which was not generating empty sitemaps.

To be honest, I don’t have the courage, nor the knowledge, to understand what’s happening to take me from a correct sitemap generation to a totally empty one. ( 😢 )

I’ve made a branch to help you to reproduce and investigate. https://github.com/Tirraa/dashboard_rtm/tree/next-sitemap-empty-sitemap-issue

ℹ️ It would be also helpful to know how could I investigate myself? I naively assumed that if my routes were displayed correctly in the build output, it should be fine (lol).

Warm regards. ( I’m so sad to have an empty sitemap. 😢 )

About this issue

Original URL
State: open
Created 10 months ago
Reactions: 6
Comments: 30

Most upvoted comments

Empty sitemap here as well

+10

fgeorgsson on Sep 7, 2023

For me it is just happening with the new app directory, I have 2 other projects with this same library and almost exactly the same configuration but they use the old pages directory and they work perfectly

letops on Sep 14, 2023

Up this, I have the same issue as well

yongyi520 on Sep 7, 2023

in my case it was related to this: https://github.com/iamvishnusankar/next-sitemap/issues/692

AlexanderBich on Dec 25, 2023

I had it working for some time without any issue. And today it decided to not work anymore as mentioned by everyone here. Trying to retrace what happened. My main changes have been to add trpc and clerk.

In case someone really stuck with it, I’ve migrate to the official, took me 20 minutes and its smooth.

agonist on Dec 6, 2023

I’m using Next 14 with the pages folder and I’m getting empty sitemaps too. No errors.

kevinstark86 on Feb 7, 2024

I have one project having issues with sitemap on app router while others works fine, it was driving me crazy, I compared versions and downgraded to 4.1.8 and it seems to be working now. This library seems a little abandoned? The oficial sitemap support from nextjs is very basic, how do you even generate sitemaps for static pages generated at build time @agonist ?

It depends on how you generate your static page, but on my side, I generate page based on data from my db, so I’m simply generating my sitemap based on the same data I use to generate static page. Just an example for the idea :

  const tools = await findAllToolsSlugOnly(); // this is my db call

  const allTools = tools.map((t) => {
    const to: R = {
      url: `${site}/ai-tools/${t.slug}`,
      lastModified: new Date(),
      changeFrequency: "daily",
      priority: 0.7,
    };
    return to;
  });

I’m doing something like that. So I have various array of from my static pages for different routes. once setup you don’t have to touch it anymore and what’s happening is very predictable which make the sitemap less mysterious and give you full control over it. and adding a single regular page just take 10 seconds which is find.

agonist on Jan 24, 2024

I have pages of all kinds in my build (two server side and two static) - still doesn’t work.

Hmm, that’s curious.

Does your next build feedback prints something like this?

λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps)

○ (Static) automatically rendered as static HTML (uses no initial props)

● (SSG) automatically generated as static HTML + JSON (uses getStaticProps)

Yup, with one more:


ℇ  (Streaming)  server-side renders with streaming (uses React 18 SSR streaming or Server Components)
λ  (Server)     server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)     automatically rendered as static HTML (uses no initial props)
●  (SSG)        automatically generated as static HTML + JSON (uses getStaticProps)

rafalzawadzki on Sep 29, 2023

I have pages of all kinds in my build (two server side and two static) - still doesn’t work.

rafalzawadzki on Sep 25, 2023

Having the same issue, I thought it’s my issue (missing some config) until I see this. Will wait for the inputs here.

RaenonX on Sep 3, 2023