A feed

Can a reader subscribe to the site’s posts?

Coverage · 10 of 100 in Coverage · yours to do · feed

What we look for

We look for the feed a reader would subscribe to for your own posts. When nothing links one, we try up to five of the usual addresses, /rss.xml, /feed, /feed/, /atom.xml, and /index.xml, in that order and as far as the scan’s request limit allows, for a site with a blog-like section or posts in its sitemap, and the sentence names the ones we read; a working feed found only there earns half, since nothing links it. A feed whose only item is your home page or a test page is not a feed of your posts, and we say so. Dates we can’t read are said as that, never as missing. A feed is stopped when it is more than 90 days behind your newest post, dated by the post itself, the date in its address (/blog/2026/…), or your feed, never by a sitemap lastmod, which says when a page changed. We read every RSS or Atom feed linked from the home page’s head; if none of those is a feed of your posts, the feeds linked from the head of the blog-like sections the home page links (two at most: a blog, a journal, news, a changelog, …); and, with none anywhere, the address a platform puts one by default (/feed/, /rss.xml, /atom.xml, or a Shopify blog’s .atom). We pass over a comments feed, a feed whose items are mostly other sites’ pages (bookmarks, a link blog), and a feed whose items are all one page or the home page. A feed on a place you claim as your own counts as yours: a newsletter or a blog on another host that your sameAs or a rel="me" link names (yourname.substack.com, a Medium publication, a sibling domain). What decides is where the items are, not where the feed file lives: an item is on your site when any address it gives itself is (its link, a link beside it such as a link blog’s permalink, a permalink guid, an Atom id), so a link blog whose entries each have their own page on your site is your feed, and a feed of bookmarks, whose items have no page of their own on your site, isn’t. Of the rest, the one with the most items on your site wins, then one whose title or address says blog, posts, journal, or articles, and only then the one with the newest item. We fetch it and check that it’s valid XML with at least one item in it; how it’s served doesn’t matter as long as it reads. A working feed linked from the head of the home page or any other page passes, and we say where we found it; a working feed we found only at a default address, that nothing links, gets half, and the fix is to link the feed you have; a feed the home page links that is broken or empty gets half; no feed anywhere scores nothing, and if we passed one over, we say which and why. A feed whose items carry no dates gets half: it can’t tell a reader or an engine what’s new. A feed that has stopped gets half, and we say both dates (we never fetch a page just to date it): one whose newest post is more than 90 days behind your newest post (in your sitemap, in a dated address the home page links, or on a post we read, by the date it was published; never a page that lists dated entries, a page’s “last modified” date, or a feed we passed over), and we say where we found that post. A date that isn’t a post’s (a page’s “last modified” or “last updated”) never makes a feed stopped, however much newer it is. A feed on another site that the home page links counts as yours, held to the same rule. If the request budget ran out before we could read your blog’s page or its feed, we say we couldn’t check.

We only ask sites that publish posts, and we find them in your sitemap first: a sitemap of posts (post-sitemap.xml, news-sitemap.xml), or addresses under a section where writing lives (/blog/, /posts/, /journal/, /articles/, /news/, /notes/, /writing/) or with a date in them (/2026/11/…). Then a feed with items on your site, then articles, posts, or episodes among the pages we read (in structured data, or a piece of writing that shows its date), and, when the pages we read are indexes (an archive, a list of posts), the newest posts an index lists on your site, each judged by its own page. A company, a product, or a person who doesn’t publish posts skips this criterion: there’s nothing to subscribe to. If we couldn’t read what would tell us (your sitemap didn’t answer, or the request budget ran out first), we say we couldn’t check, never that you don’t publish. Any kind of site that publishes posts is asked, a company with a blog or a changelog as much as a magazine; a page is a post only by its own content: it shows a date or a byline of its own (in the article itself, or in the structured data that describes the page as an article), or a feed that your site or the page itself links has an entry for it, or it has a place among your posts: an <article> at an address where writing lives (/blog/a-post, /2026/11/a-post), or a page one of your indexes of posts labels as an article. Such a page is a post even with no date and no byline, which is how we can tell you to put a date on it. A label alone, anywhere else, makes no post: not an <article> your template wraps around every page or around an intro paragraph, not og:type, not an author card every page carries in its footer, and not a date we judged a build’s stamp (such a page leaves the count; it is never an undated article). A page under your about section, or one your navigation lists as a product, tool, or landing page, is never a post, and neither is a page that only carries its own dateModified or a legal page’s “Last updated”: a modified date never dates a post. Never a post, whatever it carries: your about page, a press release, reference docs (/docs/, /help/, /guides/, /api/), a login, signup, cart, thank-you, or test page, a landing page your navigation lists as a section, a page of five or more dated entries, or the home page. A page’s date is its own publication date, in its structured data, its header or byline, a meta tag, your feed, its address, or alone under its title, and never a date in its prose.

Why it matters

A feed is the fastest way for a machine to learn what’s new on a site: one small file, newest first, with titles, dates, and links. Crawlers and aggregators check feeds far more often than they recrawl whole sites, so new posts get noticed sooner.

We also use your feed to find your newest articles, so the criteria for authors, dates, and citations judge your actual writing, not just the pages near the top of the site.

How to pass

  1. Turn on your platform’s feed if it has one (WordPress, Ghost, Substack, and most blog tools do), or have your developer publish one.
  2. Link it from the head of the home page (and ideally every page), so it can be found:
    <link rel="alternate" type="application/rss+xml" title="Example" href="https://example.com/feed.xml">
  3. Make sure the feed loads and lists your posts, newest first, each with a title, link, and date.

Last changed .

The whole rubric