Autodiscovery is the reason you can paste a website’s homepage URL into a podcast app or feed reader and have it find the actual feed on its own, without you ever locating or pasting the real feed link. It’s a single line in a page’s HTML — and when it’s missing or broken, tools quietly fall back to guessing, or fail to find your feed at all.
Autodiscovery runs on one <link> tag placed in a page’s <head>:
<link rel="alternate" type="application/rss+xml" title="Site Name" href="https://example.com/feed/">
Any tool that supports autodiscovery — browsers, feed readers, podcast apps, automation platforms — reads a page’s HTML head, looks for this tag, and follows the href straight to the feed. No manual searching, no guessing common paths like /feed or /rss.xml.
View your homepage’s page source (or use a “view page source” browser extension) and search for rel="alternate". If it’s there with a type of application/rss+xml or application/atom+xml and a valid href, autodiscovery is working. Most major CMS platforms — WordPress, Ghost, Squarespace — add this tag automatically on every page without any configuration, so its absence is usually a sign of a heavily customized theme or a static site built by hand.
Autodiscovery tends to fail quietly rather than loudly. A theme rebuild can drop the tag from the head template entirely. A migration to a new domain or subdirectory can leave the href pointing at the old, now-dead feed URL. A page builder plugin can strip head tags it doesn’t recognize as “content.” None of these show up as a visible error on the site itself — the page looks completely normal, only the invisible discovery path is broken, which means new subscribers relying on autodiscovery quietly can’t find the feed anymore.
Larger sites often generate several feeds — one for all posts, separate ones per category, and sometimes one for comments. Autodiscovery supports declaring more than one <link> tag, each with its own title so tools can show a human-readable choice. The practical guidance is to make sure the main, all-posts feed is always declared on every page (not just the homepage), since that’s the one automation tools and readers default to when only one is expected.
When autodiscovery is missing or points to the wrong place, knowing the default feed address of your platform is the fastest way around it. These are the usual locations:
English
Lietuviškai
Deutsch
Français
Русский
Español
Polski
Italiano
Українська
Čeština
Português
日本語
Latviešu valoda
Eesti
Magyar
Bahasa Indonesia
Türkçe
हिन्दी
Ελληνικά
العربية
ไทย
Tiếng Việt
Română
Bahasa Melayu
বাংলা
/feed/ after the site address, and /category/name/feed/ for a single category./feeds/posts/default?alt=rss./rss/, with /tag/slug/rss/ and /author/slug/rss/ for tags and authors./blog-feed.xml.?format=rss to a blog page address./blogs/news.atom for the blog and /collections/all.atom for products./rss.xml for the front page.?format=feed&type=rss to a category blog or list view.The full list, including Magento, Webflow, Medium, Etsy and YouTube channel feeds, is on the PostRSS integrations page.
Autodiscovery is convenient for readers, but for automation the most reliable approach is to give the tool the exact feed address. In PostRSS you paste the feed URL as a source, and PostRSS reads any valid RSS 2.0 or Atom feed from it. If your site declares several feeds, choose deliberately: the main feed for your general accounts, and a category feed for a target that should only receive one topic.
The href in your autodiscovery tag is also a quick way to confirm which address your CMS considers the main feed. If it differs from the address you added to PostRSS, check which one is current before a migration or redesign makes one of them stop updating.
It is also worth checking one ordinary article page, not only the homepage. Some themes print the autodiscovery tag on the homepage template alone, so a reader who pastes the address of a single article into a feed reader finds nothing. Declaring the main feed in the shared head template of every page removes that gap, and it costs nothing in page weight or speed. It is a one-time fix that keeps working through later content changes.
rel="alternate" tag is still there.href address in a browser and check that it shows your newest post.PostRSS checks each feed as often as every minute, so a working feed shows up on your accounts quickly, and a silent break becomes visible as soon as a new post fails to appear. If your site is moving to a new domain, read what happens to your auto-posting setup when you migrate.
Not directly as a ranking factor, but it affects how reliably crawlers, aggregators, and automation tools that respect it can find and use your content, which matters for distribution rather than rankings.
Yes — the visible RSS icon some older browsers showed was just a UI convenience for finding the same tag. Its absence in modern browsers doesn’t mean autodiscovery is missing; check the actual HTML tag, not for a browser icon.
Check the autodiscovery tag in your homepage’s source first; if it’s present and correct, that href value is your feed URL, and it’s also the one to hand to any automation or podcast tool directly.
Autodiscovery is a one-line HTML tag doing an outsized job: letting every feed-aware tool find your content without manual setup. It’s worth a direct check after any theme change, migration, or redesign, since it fails silently and the only sign is subscribers or automation tools quietly no longer finding new posts.
What changed in the networks, what broke, and how to fix it before it costs you reach.
Built by Internet Solutions, the team behind PostRSS. Each product saves you time in its own way.