How to generate your sitemap.xml for Next.js and Netlify CMS

There are many steps to improve the SEO ranking of your website. Having a sitemap cannot hurt. Here is a method to generate a proper and up-to-date sitemap for a Next.js website powered by Netlify CMS.

3 min read

May 20, 2020

flat ray photography of book, pencil, camera, and with lens

Why did you build a custom solution ?

When I started to look for nextjs generate sitemap.xml, I was slightly disapointed. Maybe because I remember how easy it was to setup while using Nuxt.js. But mostly because most solution seemed either overkill (with a lot of configuration) or on the other hand a bit too bare metal and naive.

Odly enough, I decided to build a fully custom solution. Martin Beierling-Mutz posted an article that is very close to what I need so I edited his solution to meet my needs.

List the content

My website being very simple I only have a handfull of pages (the home, /about and /blog). The most important part was to be able to automatically add new blog posts to the sitemap.

I use Netlify CMS to write control the content of my website. It works very for simple static site generator. The logic of this git-based CMS is that all post/page/etc. are commited in the repo. Whenever there's a new commit the website is built and deployed again.

This mean there is no API to query to know the current articles available on the website. Martin's solution tried to solve this issue by listing the files found in the /pages/ directory.

Since my articles are already in the repo I figured I could use that instead. I use custom slug in configuration so I have to read everyfile to define it's route. I can't rely on the file name. This is a bit of a drawback of my solution compared to Martin's. But, it's already online as I write this 🙈.

  ...fs.readdirSync('site/blog/').map((file) => {
    const rawfile = fs.readFileSync(`site/blog/${file}`);
    const post = JSON.parse(rawfile);
    return `/blog/${post.slug}`;

Writting the file on disk

My version only relies on newer fs features that weren't available (I think) when the original post was written. The files have to be at the root of the website. In my case, the output folder id /out;

This way, I can write the robots.txt like this

const robotsTxt = `User-agent: *

fs.writeFile('out/robots.txt', robotsTxt, () => { 
  console.log('robots.txt saved!');

Then, I write the sitemap.xml like this

let xmlPaths = '';

    (path) => `
  .forEach((xmlPath) => {
    xmlPaths += xmlPath;

const sitemapXml = `<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="">${xmlPaths}

fs.writeFile('out/sitemap.xml', sitemapXml, () => {
  console.log('sitemap.xml saved!');


I think writting this helped me a bit figure out the orginal post solution. You simply have to add the full script as a postexport script in your package.json.

Whenever your website will be deployed again this will be ran again. If your website is built using a flat-file cms this should provide an alway up-to-date sitemap.xml for Google to crawl 🙃.

I will probably write another version of this script very soon to apply my newly acquired knowledge. Don't copy paste it without asking yourself if it's good enough for your use case!

Hey there 👋

I hoped you like this little sample of my brain 🧠. If you have any questions, please reach out 🙏

Marc-Antoine Ferland


Hello, I'm Marc-Antoine. I absolutely love crafting elegant solutions to a wide array of problems. I'm fascinated by theory-crafting and I will love challenging the status quo. I love efficient and people-driven cultures. Work should adapt to your lifestyle, not the other way around. I'm currently a Senior Frontend Engineer at Capdesk 💻✌️