2.2.0 • Public • Published


npm Release workflow Test workflow codecov semantic-release Commitizen friendly License: MIT

Eleventy plugin to generate a sitemap using ekalinin/sitemap generator.


Install the package:

npm install --save @quasibit/eleventy-plugin-sitemap

Add the plugin to your Eleventy configuration (usually .eleventy.js):

const sitemap = require("@quasibit/eleventy-plugin-sitemap");

module.exports = function(eleventyConfig) {
  eleventyConfig.addPlugin(sitemap, {
    sitemap: {
      hostname: "https://example.com",


Create a sitemap file and use the shortcode to generate the sitemap XML:

permalink: /sitemap.xml
layout: null
eleventyExcludeFromCollections: true
{% sitemap collections.all %}

The above snippet does the following:

  • Sets the permalink to /sitemap.xml.
  • Disables any layout.
  • Excludes the sitemap file from Eleventy collections.
  • Calls the sitemap shortcode.

As the first argument to the shortcode, you pass the collection of items that you want to use in the sitemap.

This shortcode is available for Liquid, Nunjucks, and Javascript templates.

You can also copy this sample from the examples and adapt it to your needs:

cp node_modules/@quasibit/eleventy-plugin-sitemap/examples/default/sitemap.njk sitemap.njk

After creating the sitemap, you should add the sitemap to robots.txt:

Sitemap: https://example.com/sitemap.xml


The following options are available:

eleventyConfig.addPlugin(sitemap, {
  // Name of the property for the last modification date.
  // By default it is undefined and the plugin will fallback to `date`.
  // When set, the plugin will try to use this property and it will fallback
  // to the `date` property when needed.
  lastModifiedProperty: "modified",

  sitemap: {
    // Options for SitemapStream. See https://github.com/ekalinin/sitemap.js/blob/master/api.md#sitemapstream
    // Hostname is needed when the URLs of the items don't include it.
    hostname: "https://example.com",


See ./examples folder.

Advanced usage

Customizing sitemap properties

You can customize the values used for the sitemap links by adding front matter to your pages.

  changefreq: weekly
  priority: 0.8

Alternatively, you can apply the properties to a folder of items by creating a directory data file.

Assuming you want to apply this to all the files in posts/*:

// posts/posts.11tydata.js
module.exports = () => {
  return {
    sitemap: {
      changefreq: "weekly",
      priority: 0.8,

For a full list of options, please refer to Sitemap Item Options.

Exclude pages from the sitemap

You have several options to exclude pages from the sitemap.

You can exclude them using the standard eleventyExcludeFromCollections property, which will exclude them from all collections.

eleventyExcludeFromCollections: true

You can use the ignore property on the sitemap data, which will only exclude it from the sitemap.

  ignore: true

Or you can create a custom collection that excludes the items that you don't want in the sitemap and then pass that collection to the shortcode.

eleventyConfig.addCollection("sitemap", function(collectionApi) {
  return collectionApi.getAll().filter(item => {
    // Place your condition here for excluding items from the sitemap.
    return true;

Specify the collection in the shortcode:

{% sitemap collections.sitemap %}

Create a multilingual sitemap

For creating a multilingual sitemap you need to add alternate language child links for each link.

You could do this with front matter and the links property , but in most cases it's easier to do this with a custom collection.

eleventyConfig.addCollection("sitemap", function(collectionApi) {
  return collectionApi
    .map((item, index, all) => {
      return {
        url: item.url,
        date: item.date,
        data: {
          sitemap: {
                // Find all the translations of the current item.
                // This assumes that all translated items that belong together
                // have the same `translationKey` value in the front matter.
                .filter(other => other.data.translationKey === item.data.translationKey)

                // Map each translation into an alternate link. See https://github.com/ekalinin/sitemap.js/blob/master/api.md#ILinkItem
                // Here we assume each item has a `lang` value in the front
                // matter. See https://support.google.com/webmasters/answer/189077#language-codes
                .map(translation => {
                  return {
                    url: translation.url,
                    lang: translation.data.lang,

And then pass that collection to the sitemap shortcode:

{% sitemap collections.sitemap %}

You can see an example with dynamic hostnames in ./examples/multilingual/.

Related plugins




Package Sidebar


npm i @quasibit/eleventy-plugin-sitemap

Weekly Downloads






Unpacked Size

58.8 kB

Total Files


Last publish


  • nunof
  • dercias