RepoPicks Radar

Updated every day around 23:30 UTC

Guides

next-sitemap

iamvishnusankar/next-sitemapReviewed by AI

Checked by RepoPicks Radar on

What is next-sitemap?

next-sitemap is for people who build websites with Next.js. After each build it walks through the pages the site produced and writes sitemap.xml and, if you ask, robots.txt into the public folder, splitting very large sitemaps into numbered files and supporting Google news, image and video entries plus other-language versions of a page. You add it to the project with one command, create a small next-sitemap.config.js with your site address, and run it as a postbuild step. It has no screen of its own and only works inside a Next.js project.

next-sitemap is free and open source (MIT) and can replace Screaming Frog SEO Spider.

How easy is it to install next-sitemap?

C · install 1 or 2 tools · Windows

  • Windows C
  • macOS C
  • Linux C

The same on all three systems, grade C: with Node.js already installed you run "yarn add next-sitemap", write a next-sitemap.config.js file with "siteUrl" and add "postbuild": "next-sitemap" to package.json. There is nothing to open or click, and it is only useful inside an existing Next.js project; with pnpm you must also add "enable-pre-post-scripts=true" to an .npmrc file.

next-sitemap on GitHub

Stars
3,751on Nov 10, 2026
Downloads
—all releases
Growth
+1stars in 6 days

Stars over time

3,7503,7513,752 Nov 7Nov 8Nov 9Nov 10 3,7503,7513,752 Nov 7Nov 9

Facts

Runs on
Windows, macOS, Linux
You need to install
Node.js
To build from source
Node.js
Disk space
100 MB–500 MB · estimate
Accounts or keys
None
Cost
Free · MIT licensed with no paid tier mentioned anywhere in the repository.
License
MIT (Permissive)
Can replace
SEO Spider
Last change on GitHub
Mar 10, 2026

next-sitemap risk signals (6)

  • Attentionstale releases

    Last release on 2023-09-06 (1157 days ago)

    automatic check

  • Attentioncode is newer than the last published version

    The checks record the last release on 2023-09-06 (v4.2.3) while the last commit is 2026-03-10, with 236 releases in total. Anyone installing it with "yarn add next-sitemap" gets the 2023 version, not the code in this repository, and the README does not say what changed since.

    AI review

  • Inforobots txt entries are public and only a request

    The full example writes a robots.txt with "User-agent: black-listed-bot / Disallow: /sub-path-1" and excludes "'/protected-page', '/awesome/secret-page'" from the sitemap. A robots.txt file is readable by anyone and well-behaved crawlers choose to follow it; listing a private path there does not block access to it, and leaving it out of the sitemap does not hide it either.

    AI review

  • Infosettings file runs your own code at build time

    The configuration file is JavaScript with "transform: async (config, path) => ..." and "additionalPaths: async (config) => ..." functions, and the README notes "next-sitemap will load environment variables from .env files by default". Whatever you write there runs during the build with access to those variables.

    AI review

  • Infoonly works with nextjs

    The tool reads the Next.js build folder ("sourceDir (optional) | next.js build directory. Default .next") and the server-side helpers are Next.js route handlers (getServerSideSitemap, getServerSideSitemapIndex). It does nothing for a site built with anything else.

    AI review

  • Infositemap values are guesses by default

    Defaults in the options table are "changefreq ... Default daily", "priority ... Default 0.7" and "autoLastmod ... Default true", and the sample transform sets lastmod to "new Date().toISOString()". Every page is then announced as changing daily and as modified at build time, whether or not it really changed.

    AI review

Evidence is shown in its original language.

What Radar could not check about next-sitemap

  • Whether it works with the newest Next.js versions, since the published package dates from 2023
  • Whether search engines actually index the pages it lists, which only they decide
  • What the code committed after the last release changes compared with the published package
  • Real disk use, which the checks could only estimate at 100 to 500 MB for the repository and its dependencies

Similar projects

The RepoPicks app

Coming soon: install in 1 click with the RepoPicks app.

Before you download

See the release page on GitHub