Build your own feed

What you can filter on

Parameters combine freely. Each feed carries its own title in your reader — “SEO-Serps Info — Crawling & Indexing” rather than six identical subscriptions — and tags every item with its technical areas, so you can filter again inside the reader.

Ready-made recipes

Copy any of these straight into a reader.

Ideas worth stealing

• One feed per client. Build a feed for each client's vertical and technical priorities, and put each in its own reader folder. Their monthly report writes half of itself.
• Pipe high-impact into Slack. Most Slack workspaces can subscribe to an RSS URL directly. ?impact=high gives your team the handful of stories a week that warrant a conversation — and /feed/updates alongside it tells you the moment Google confirms a rollout.
• Split reading from monitoring. Subscribe to ?impact=high for alerts and browse the site itself when you have time. Two very different jobs, badly served by one feed.
• Narrow before you widen. A feed you actually read beats a feed that makes you feel informed. Start with one topic; add another only when the first stops filling your week.
• Combine with the OPML. Import the OPML for the raw publishers, then add one or two filtered feeds from here for the cross-cutting views no single publisher can give you.
• Check it before you commit. Hit Preview above. A feed returning nothing usually means the filters are narrower than intended — the feed will say so rather than looking broken.