
What This RSS Validator Checks
The validator reads your feed the way a strict feed reader would, then checks it against the RSS 2.0 specification, RFC 4287 (Atom), the JSON Feed 1.1 spec and the requirements of Apple Podcasts. It detects the format by itself, so you never have to choose one.
- Well-formed XMLUnescaped ampersands, HTML entities, unclosed tags, wrong encodings and characters before the XML declaration, with the exact line.
- Required elementsTitle, link and description in RSS; id, title and updated in Atom; version, title and items in JSON Feed.
- DatesRFC 822 dates in RSS and RFC 3339 dates in Atom and JSON Feed, including wrong weekdays, missing time zones and future dates.
- GUIDs and IDsMissing, empty or duplicate GUIDs, and guids that are not URLs while isPermaLink defaults to true.
- Links and URLsRelative links, relative images inside content, spaces in URLs and missing self links.
- EnclosuresThe url, length and type attributes, valid MIME types and more than one enclosure per item.
- Podcast tagsitunes:image, itunes:category, itunes:explicit, episode numbers, durations and episode types.
- NamespacesUndeclared prefixes, misspelled namespace URIs, unknown and deprecated tags.
- HTTP deliveryStatus code, Content-Type, compression, ETag and Last-Modified, redirects, HTTPS and response time.
How to Validate a Feed
- Paste the address of the feed (not the website) into the field and press Validate feed. Don't know the feed address? Use the Feed Finder.
- Read the verdict. Errors break the feed in at least some readers. Warnings are allowed by the spec but cause problems in practice. Tips are optional improvements.
- Click a line number to jump to the problem in the source, fix the first error in your CMS or code, and check again. One mistake often causes several messages.
Working on a feed that isn't online yet? Switch to Paste code or Upload file. Nothing you paste leaves your browser: validation runs locally in JavaScript.
The Most Common Feed Errors and How to Fix Them
| Error | Cause | Fix |
|---|---|---|
| EntityRef: expecting ';' | A bare & in a title or URL | Write &, or wrap the text in CDATA |
| Entity 'nbsp' not defined | HTML entities in XML | Use   or the real character, or use CDATA |
| XML declaration allowed only at the start | Whitespace or output before <?xml | Remove blank lines before <?php and after ?> in your theme or plugins |
| Date is not RFC 822 | Dates like 2026-11-10 14:00 | Use Tue, 10 Nov 2026 14:00:00 +0000 (PHP: date(DATE_RSS)) |
| guid is not a URL | <guid>123</guid> without isPermaLink | Add isPermaLink="false" |
| Missing atom:link self | No self-reference | Add <atom:link rel="self" …/> and the Atom namespace |
| Prefix not defined | media: or itunes: used without xmlns | Declare the namespace on the root element |
| Relative URLs in content | Images like /img/a.jpg | Make every link and image source absolute |
The FAQ covers more problems, and the RSS 2.0 reference lists every element with its rules.
Why Validating Your Feed Matters
Feed readers, podcast apps, news aggregators and automation tools such as Zapier or IFTTT all parse feeds differently. Some forgive mistakes; others silently drop items, show the wrong dates or refuse the feed altogether. Apple Podcasts and Spotify reject podcast feeds with missing artwork or invalid enclosures. A valid feed is the only way to be sure everyone sees the same thing.
Search engines and AI crawlers also read feeds to discover new pages quickly. A broken feed means slower discovery of your new content.
Validator Questions
Is this the same as the W3C Feed Validation Service?
No. It checks the same specifications and adds checks for podcast tags, JSON Feed, HTTP caching and content quality. It also explains each problem with a concrete fix. Results can differ in details because the W3C service has its own rule set.
Why does my feed work in my reader but fail here?
Many readers silently repair broken XML. Others don't, and podcast directories are strict. Fixing the errors makes your feed work everywhere instead of only in forgiving apps.
Can I validate a feed behind a login or on localhost?
The URL checker only reaches public addresses. For private feeds, open the feed in your browser, copy the source and use Paste code, which runs entirely on your device.
Can I link to a validation result?
Yes. Every URL check gets a shareable address like rssfeeds.com/rss-validator?url=…. Use Copy link to this result to send it to a developer.
Sources and Further Reading
- RSS 2.0 SpecificationRSS Advisory Board
- RFC 4287: The Atom Syndication FormatIETF
- JSON Feed Version 1.1jsonfeed.org
- Podcast RSS Feed RequirementsApple Podcasts for Creators
- W3C Feed Validation ServiceW3C