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
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
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.
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.
@@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!!
