| title | Creating Custom Feeds | ||
|---|---|---|---|
| description | Learn to write custom YAML configurations for RSS feeds when auto-sourcing isn't enough. | ||
| sidebar |
|
When auto-sourcing isn't enough, you can write your own configuration files to create custom RSS feeds for any website. This guide shows you how to take full control with YAML configs.
Prerequisites: You should be familiar with the Getting Started guide before diving into custom configurations.
Use custom configs when:
- Auto-sourcing doesn't work for the website you want to follow
- Existing feeds are incomplete or missing important content
- You need specific formatting or data extraction
- The website has complex structure that requires custom selectors
- You want to combine data from multiple sources
Don't need custom configs? Check the Feed Directory first - there might already be a working feed for your website.
A config file is a simple "recipe" that tells html2rss:
- Which website to look at
- What content to find
- How to organize it into an RSS feed
This tells html2rss basic information about your feed - like giving it a name and telling it which website to look at.
Example:
channel:
url: https://example.com/blog
title: My Awesome BlogThis says: "Look at this website and call the feed 'My Awesome Blog'"
This is where you tell the html2rss engine exactly what to find on the page. You use CSS selectors (like you might use in web design) to point to specific parts of the webpage.
Example:
selectors:
items:
selector: "article.post"
title:
selector: "h2 a"
link:
selector: "h2 a"
attribute: hrefThis says: "Find each article, get the title from the h2 anchor, and get the link from the same h2 anchor's href attribute"
Need more details? Check our complete guide to selectors for all the options.
Step 1: Look at the website you want to create a feed for. Right-click → "View Page Source" to see the HTML structure.
Step 2: Create a file called example.com.yml with this basic structure:
channel:
url: https://example.com/blog
title: My Blog
selectors:
items:
selector: "article.post"
title:
selector: "h2 a"
link:
selector: "h2 a"
attribute: hrefStep 3: Test it with your html2rss-web instance or the Ruby gem.
Need help? See our troubleshooting guide for common issues.
html2rss supports many configuration options:
- Basic selectors for title, description, and links
- Advanced features like custom headers and dynamic parameters
- Multiple strategies for different types of websites
- Post-processing to clean up extracted content
See our Ruby Gem Reference for complete documentation.
Before sharing your config, test it:
-
Test with Ruby gem:
html2rss feed your-config.yml
-
Test with web app: Add your config to the
feeds.ymlfile and restart your instance -
Check the output: Make sure all items have titles, links, and descriptions
Help the community by sharing your config:
- Go to html2rss-configs on GitHub
- Click "Fork" → "Add file" → Create
domain.com.yml - Paste your config → "Commit new file" → "Open pull request"
Need help? See our contribution guide for detailed instructions.
Common issues when writing configs:
- No items found? Check your selectors with browser tools (F12) - the
items.selectormight not match the page structure - Invalid YAML? Use spaces, not tabs, and ensure proper indentation
- Website not loading? Check the URL and try accessing it in your browser
- Missing content? Some websites load content with JavaScript - you may need to use the
browserlessstrategy - Wrong data extracted? Verify your selectors are pointing to the right elements
Need more help? See our comprehensive troubleshooting guide or ask in GitHub Discussions.
🎉 Congratulations! You've learned the basics of creating html2rss configuration files.
For Beginners:
- Browse the Feed Directory - See real-world examples
- Learn more about selectors - Master CSS selectors
- Submit your config via GitHub Web - No Git knowledge required!
For Contributors:
- Browse existing configs - See real examples
- Join discussions - Connect with other users
- Learn advanced features - Take your configs to the next level