Sitemap generator for Crystal apps
0.9.0 Latest release released


Sitemapper helps you to generate sitemaps for your website. It generates sitemap compliant XML, and gives you the flexibility to handle what is generated, and where you place your sitemaps.


Add this to your application's shard.yml:

    github: jwoertink/sitemapper


require "sitemapper"

# Configure sitemapper
Sitemapper.configure do |c|
  # Generate a sitemap_index file
  c.use_index = true # default false = ""

  c.sitemap_host = "" # default nil

  # The max number of <url> elements to add to each sitemap
  c.max_urls = 20 # default 500

  # use gzip compression?
  c.compress = false # default true

  # which storage class to use = Sitemapper::AwsStorage  # default is SiteMapper::LocalStorage

  # see the aws config docs below
  c.aws_config = # default is nil but should be an AwsStorageConfig when used

# Use sitemapper
sitemaps = do |builder|
  builder.add("/about", changefreq: "yearly", priority: 0.1)
  builder.add("/profiles/somedude", changefreq: "always", priority: 0.9)

# Do whatever you want with these.
# Maybe upload to S3, or write to a file
puts typeof(sitemaps) #=> Array(Hash(String, String))
puts sitemaps.first #=> {"name" => "sitemap1.xml", "data" => "<?xml ..."}

# Just have Sitemapper write them out to your public/sitemaps folder
# This will create ./public/sitemaps/sitemap1.xml, etc..., "./public/sitesmaps")

You can also pass options to build. "your host", max_urls: 20, use_index: true) do |builder|
  builder.add("/whatever", lastmod: Time.utc)

Adding videos to your sitemap

You can add in video information which will generate the necessary XML for videos. Check out the docs for all the different options you can use.

Sitemapper uses a Sitemapper::VideoMap object for building out video sitemap data. Pretty much the attributes all map 1 to 1 except for tag. Use the plural tags as an array.

video = "", title: "Video", description: "This is a video", tags: ["one", "two"])
sitemaps = do |builder|
  builder.add("/videos/123", video: video, changefreq: "yearly")

Same goes for in you want to add an image. Use Sitemapper::ImageMap and pass add("/image/1", image: image). Read up more on image sitemaps here.

Saving your XML

Sitemapper gives you the raw XML in strings. This gives you the option to save that data however you wish. Maybe you're crazy and want to store it in your DB? Maybe you're running on Heroku and can't just write locally, so you need to ship it off to AWS. What ever the case, you have that freedom.

There's a few options you have built in. LocalStorage, and AwsStorage. These are config options through


By default Sitemapper will use local storage which is just writing your XML to some flat files and stored somewhere relative to your application.

Sitemapper.configure do |c|
  # no need to configure anything extra

# `sitemaps` is the Array(Hash(String, String)) from above
# writes to ./public/sitemaps/sitemap.xml, "public/sitemaps")

If you would like to store these sitemaps in gzip files, you'll need to set the compress option.

Sitemapper.configure do |c|
  c.compress = true

# writes to ./public/sitemaps/sitemap.xml.gz, "public/sitemaps")


If you're hosted somewhere like Heroku or Elasticbeanstalk then you may not have the ability to just write your flat files locally. In this case, you can use the AwsStorage option to push the files to S3 (or an S3 compatible location).

You'll probably also want to set the sitemap_host option here. This is so the sitemap_index.xml will know where all the other sitemap files will be located.

Sitemapper.configure do |c| = Sitemapper::AwsStorage

  # This option is important!
  c.aws_config =
    region: ENV["AWS_REGION"],
    key: ENV["AWS_ACCESS_KEY"],
    secret: ENV["AWS_SECRET_KEY"],
    # Set this option only if you need an alternative host from S3, or the S3 host has changed
    endpoint: ""

  c.sitemap_host = ""

# uploads to your bucket my-prod-bucket/sitemaps/sitemap.xml, "my-prod-bucket/sitemaps")

Lastly, so the searchengines know where your sitemaps are located (unless you aliased /sitemap_index.xml), you'll want to update your robots.txt with Sitemap:

Notifying Search Engines

Once you have your sitemaps updated, it's usually a good idea to let the search engines know. Generally, they will crawl your site regularly anyway, but this at least gets things moving a little quicker. To do this, you can use the ping_search_engines method.

sitemap_url = whatever_you_put_in_your_robots_txt

Currently, this only pings Google and Bing. However, if you wanted to ping another engine like a custom one, or maybe Yandex, you can pass that in as well.

# be sure to include %s so we know where to place your `sitemap_url`
Sitemapper.ping_search_engines(sitemap_url, yandex: "")


Nothing fancy. Just pull down the repo, add code and make sure specs are passing.


  1. Fork it ( )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Add some specs and run crystal spec/
  4. Commit your changes (git commit -am 'Add some feature')
  5. Push to the branch (git push origin my-new-feature)
  6. Create a new Pull Request


  github: jwoertink/sitemapper
  version: ~> 0.9.0
License MIT
Crystal >= 1.4.0


Dependencies 2

  • awscr-s3 ~> 0.8.0
    {'github' => 'taylorfinnell/awscr-s3', 'version' => '~> 0.8.0'}
  • habitat ~> 0.4.7
    {'github' => 'luckyframework/habitat', 'version' => '~> 0.4.7'}

Development Dependencies 2

  • ameba ~> 1.5.0
    {'github' => 'crystal-ameba/ameba', 'version' => '~> 1.5.0'}
  • webmock master
    {'branch' => 'master', 'github' => 'manastech/'}

Dependents 2

Last synced .
search fire star recently