How do you add RSS and sitemap to a Jekyll site?
WordPress provides a built-in RSS feed and sitemap system that search engines and feed readers rely on. When migrating to Jekyll, you need to manually set these up — but thankfully, it's easy and takes just a few steps. This ensures your content is still indexable and subscribable.
Why RSS and sitemaps matter after migrating
- RSS feeds allow users to subscribe to your blog in feed readers and email digests.
- Sitemaps help Google and other crawlers discover all your content efficiently, especially if you're not linking everything manually.
Setting up RSS feed in Jekyll
1. Install the Jekyll Feed plugin
In your _config.yml, add the following line under the plugins section:
plugins:
- jekyll-feed
On GitHub Pages, jekyll-feed is officially supported, so no extra setup is needed. After build, Jekyll will generate an atom.xml file automatically at the root of your site.
2. Add metadata to your config
Still in _config.yml, provide essential site information used in the feed:
title: My Jekyll Blog
description: A static blog powered by Jekyll
url: https://myjekyllsite.github.io
author:
name: John Doe
3. Link to your RSS feed in your layout
Edit your _includes/head.html and add:
<link rel="alternate" type="application/atom+xml" title="RSS" href="{{ "/feed.xml" | relative_url }}">
4. Optional: Add RSS icon or link to navigation
Use a recognizable icon or simple text to link to /feed.xml so users can find it easily.
Creating a sitemap.xml for search engines
1. Install the Jekyll Sitemap plugin
In your _config.yml, add:
plugins:
- jekyll-sitemap
Just like with the feed plugin, jekyll-sitemap is supported on GitHub Pages builds.
2. Add site URL to config
The sitemap needs your full site domain:
url: https://myjekyllsite.github.io
After the next build, you’ll get a fully functional /sitemap.xml.
Verifying your sitemap and RSS feed
You can verify that both files are generated correctly by visiting:
https://yoursite.com/feed.xmlhttps://yoursite.com/sitemap.xml
Use the Google Search Console to submit your sitemap for faster indexing.
What if you use GitHub Pages with no custom plugin support?
GitHub Pages supports both jekyll-feed and jekyll-sitemap out of the box. However, if you use GitHub Actions to build your Jekyll site (custom domain or CI/CD setup), you can include other advanced plugins too.
How do these features compare to WordPress?
| Feature | WordPress | Jekyll |
|---|---|---|
| RSS Feed | Built-in | Plugin (jekyll-feed) |
| Sitemap | Built-in via Yoast or core | Plugin (jekyll-sitemap) |
| Automatic Discovery | Yes | Yes (if URL configured) |
SEO benefits of having both feed and sitemap
- Feeds help distribute your content to aggregators like Feedly and Substack.
- Sitemaps ensure even non-linked pages are crawled by search engines.
- Combined, they improve visibility without relying on dynamic infrastructure.
Common mistakes to avoid
- Forgetting to add
urlin_config.yml— this breaks both feed and sitemap. - Blocking
/sitemap.xmlor/feed.xmlinrobots.txt. - Missing metadata like
titleordescriptionin the config file.
Next steps: Validate with external tools
- Use Google Search Console to submit your sitemap.
- Check your RSS feed using W3C Feed Validator.
Conclusion
Just because you've migrated to a static platform like Jekyll doesn't mean you have to give up features that help users and search engines. Adding an RSS feed and sitemap is not only possible — it’s easy, automated, and fully supported on GitHub Pages. By doing so, your site becomes as discoverable as any WordPress blog, without the bloat or plugin chaos.
Comments
Post a Comment