Feeds and oEmbed stopped being blog plumbing

Polling HTML is a cost nobody pays

Feeds and oEmbed look like old blog plumbing, and agents use them to find and summarise what you publish. AI assistants now answer the question before anyone clicks a result, so a missing feed is a missed update in the answer.

An integrator deciding whether to follow a source compares two paths: parse a feed, or write and maintain a scraper against markup that changes without notice. The second path is chosen roughly never. Publishing RSS, Atom or JSON Feed and declaring it in the head, so it is discoverable rather than guessable, moves a site from the second category into the first.

Embedding is citation

oEmbed is the mechanism by which another site, a chat surface or an agent renders your content inline together with your name and link. Without it, the same content is reproduced as unattributed text. The citation you lose is the one that would have compounded.

The read API is the last mile

Feeds cover change; an OpenAPI description covers structure. Together they let an integration be written from the documentation rather than reverse-engineered from HTML. Qomvia publishes both (an openapi.json and a declared feed) because a rubric its own author would not pass is not a rubric.

How Qomvia checks your feeds

Qomvia's score checks for feeds and oEmbed discovery and tells you what to add.

The free scan runs all 26 checks of the agent-readiness score in about a minute and lists every failing check with a copy-paste fix; the free Site monitor re-scans weekly, no signup for the score. The AI monitor then asks your buyers' questions to ChatGPT, Gemini and Grok every day and shows whether you are named, which rival is named instead and which sources the models used. Qomvia Market and the MCP server take it one step further, letting agents act on the recommendation. Sign up free or see plans and pricing.