What does CorrectFeed do?

CorrectFeed validates and fixes RSS and Atom feeds, helping you prevent 404s, XML errors, and feed health issues that break readers, aggregators, and search indexing.

Which feed formats does CorrectFeed support?

CorrectFeed focuses on RSS 2.0 and Atom 1.0 feeds, including blog feeds, news feeds, podcast feeds, and OPML-powered reading workflows that depend on healthy feeds.

Is CorrectFeed safe to use with private feeds?

CorrectFeed is designed to process feeds safely; feeds are validated and fixed, and you should avoid embedding secrets or authentication tokens directly in feed URLs where possible.

Do I need an account to validate a feed?

You will be able to run basic feed validation without an account; advanced monitoring, automation, and API usage will require a CorrectFeed account once the product launches.

Help Center

Practical guides for keeping RSS, Atom, podcast, and OPML workflows reliable — and making sure feeds stay crawlable, indexable, importable, and easy to migrate.

Validate a feed View pricing Developer API docs

Common problems

Start here if a feed is broken right now

RSS feed validator Validate broken feeds and diagnose the first problem

Atom feed validator Validate Atom feeds and diagnose stale update problems

RSS feed returns 404 Not Found Missing or moved feed URL

Feed is stuck in a redirect loop Too many redirects / broken canonical URL

Feed has invalid XML Parsing failures and malformed markup

How to fix a broken RSS feed Endpoint, XML, redirect, and update problems

Atom feed is not updating Caching, timestamps, and polling issues

OPML import errors when moving feed lists Broken outlines / reader compatibility

Podcast feed validator Validate podcast feeds and diagnose ingestion problems

Podcast feed validation errors Apple Podcasts / Spotify / enclosure issues

In-depth guides

Longer walkthroughs and reference material

RSS Feed Validator Validator landing page

Atom Feed Validator Validator landing page

Podcast Feed Validator Validator landing page

Best Practices for Reliable Feed Publishing Publishing + reliability

RSS SEO: Faster Indexing, Better Crawl Frequency, More Discoverability SEO overview

The Ultimate Guide to RSS for Content Sites Long-form SEO and crawl guide

Export OPML from Feedly Backup or migrate subscriptions

Export OPML from Inoreader Backup or migrate subscriptions

Import OPML into Inoreader Reader-specific import guide

Import OPML Hub for moving subscription lists between readers

OPML vs RSS: What’s the Difference? Format comparison

What Is an OPML File? Definition and use cases

OPML Workflow Guide: Export, Import, and Move Feed Subscriptions Reader workflow reference

Getting started

Tip If you just need to know what’s wrong with a feed, start with the validator or the most relevant problem card above.

The basics

What is CorrectFeed? It validates and fixes RSS and Atom feeds so readers, aggregators, and crawlers can parse them reliably.
What formats matter most? RSS 2.0 and Atom 1.0 are the main targets, with podcast and OPML workflows covered where they intersect with feed reliability.
Is it safe? Avoid embedding credentials directly in URLs. See “Privacy” below for the general handling model.

Popular how-tos

Check the feed URL directly: Open it in a browser and confirm it returns XML instead of HTML, a login page, or an error.
Watch redirects carefully: Multiple redirects, redirect loops, or redirecting to the homepage commonly break feed readers.
Validate after changes: Small template or CMS edits can introduce malformed XML, bad dates, or duplicate IDs.
Use OPML for migrations: Export OPML from one reader, import into another, and verify folders/outlines survived the move.
Podcast feeds need extra care: Enclosures, MIME types, and episode metadata need to be consistent for Apple Podcasts and Spotify.

Troubleshooting

Common failure modes explained

404s and missing feeds

If the old feed URL moved or vanished, many readers will keep polling the stale URL until you update it or provide a clean redirect.

Invalid XML

Unescaped characters, malformed tags, broken CDATA, or template fragments leaking into the feed can make readers reject it entirely.

Readers not seeing new posts

Incorrect pubDate/updated handling, caching, or duplicate GUID/ID values can make a feed look unchanged even when content was added.

Podcast-specific issues

Broken enclosure URLs, wrong MIME types, missing episode metadata, or platform-specific namespace issues commonly trigger Apple or Spotify validation errors.

Limits & Privacy

Handle feed URLs carefully Private feed URLs can act like credentials. Avoid sharing them publicly and strip tokens before posting examples.

Private feeds

If a feed URL contains a token, treat it like a password. Rotate it if it leaks.

Validation workflow

Use test URLs and staging feeds when possible so production subscribers are not affected while debugging.

Operational safety

Feed issues often come from deploys, CMS plugins, or caching layers, so validate after publishing changes.

Using CorrectFeed

What to expect from the product right now

Current state: The CorrectFeed validator and dashboard are still in active development.
What’s coming: This page will expand with step-by-step instructions for the web UI, API, monitoring, and autofix workflows as the product ships.
Need something now?: Use the guides above for feed debugging and reach out via contact if you need help planning an integration.

Contact support API docs