NextJs 14 Dynamic XML Sitemap

[@RaddyDev]

[@alidlt2515]

That's awesome, thank you so much, please make a full course or crash course about next js. 👍

[@shayankhaz]

The revalidate trick was awesome dude

[@davx1992]

Man, thanks for this video, was struggling with revalidation, this worked! Thanks!

[@yfullstackhub]

You showed revalidation part and that's great! Revalidation of sitemaps not shown in documentation.

[@RaddyDev]

That's true. I think that it's because revalidate is a caching feature. Maybe they could mention it

[@krk101]

Thanks, man. Really appreciate your help.

[@antoniobologna]

Great video. Couple of questions: 1. What is the advantage of this as opposed to using nested sitemaps, for example `blog/post/sitemap.ts`, where you have a `blog/post/[id]/page.tsx`? 2. What about thousands of records, (there's a limit of 50K URLs for sitemaps) my concern is that for big pages this will take too long for a sitemap to generate, and also do you just get up to 50,000 records based on time creation? Cheers :D

[@RaddyDev]

A flat sitemap is just easier to create and maintain and it's perfect for smaller sites. In your case a nested sitemap might be the way as it better represents your hierarchical structure. They both have their advantages and disadvantages. I haven't tried compiling thousands of records and I can imagine that it would be painful especially if the data comes from a CMS. Are they all in markdown files? It would be a cool experiment to see how long it takes to do 50,000 records. You could ask on Reddit to see what other people are experiencing

[@polatbey7261]

thank you so much

[@Sitepow]

great thk man.

[@dananjayachathuranga7113]

Thnak you and subscribed !

[@sahilanand30]

thanks really helpful

[@TheKobraIRAQ]

What theme are you using for vscode ?

[@RaddyDev]

Color Theme: Dracula & File Icon: Namo Dark for Visual Studio Code

[@okao08]

So sitemap can be very huge?

[@eshwargetenv1]

@@RaddyDevhow to catche it?

[@RaddyDev]

How big is your sitemap? It's cached as default.

[@milanpoudel7212]

will this work in pages router or not?

[@RaddyDev]

I am not sure about the page router. Have a quick look into the official documentation. I am sure that they will have something there

[@md.fakweruddinmazumder9063]

Next.js (14.2.3) out of date (learn more) Error: Page "/sitemap.xml/[[...__metadata_id__]]/route" is missing exported function "generateStaticParams()", which is required with "output: export" config. I am getting this error. Please help me.

[@RaddyDev]

You can use generateStaticParams() when it comes to pages, but for the sitemap you need to use the "export default function sitemap()" function. Unless you want to do it as a page with a custom route handler? If you need to create multiple dynamic sitemaps you can use generateSitemaps() together with sitemap(). Normally you only need to use generateSitemaps when you have more than 50,000 URLs and you need to split them per sitemap as that is the Google max number.

[@doylace]

Not really working on my end I am using the next js 14

[@RaddyDev]

It should work on 13 and 14 as long as you are using the App router. Do you get any errors?

[@MikaelMeira]

Module parse failed: Unexpected token (13:86) | | if (typeof handler !== 'function') { > throw new Error('Default export is missing in "C:\\Users\\cka\\OneDrive - Organizações\\Área de Trabalho\\projeto\\app\\sitemap.ts"') | }

[@RaddyDev]

It could be the sitemap() function. It should look like this: export default async function sitemap() {

[@MikaelMeira]

@@RaddyDev Resolved: Friend, I managed to solve it after racking my brains a lot, my project was on the Desktop and One Drive, I removed it and put it in the Downloads folder, it worked perfectly!!