Noindex, canonical and sitemap conflict checker
Noindex, canonical and sitemap conflict checker: see where one page's three signals contradict Google's own guidance. Free, runs in your browser.
RSS feed validator: paste feed XML to check RSS 2.0 and Atom 1.0 for parse errors, required elements, dates, guids, enclosures and URLs. Runs in-browser.
Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.
Paste the raw XML of a feed and this validator checks it against the RSS 2.0 specification or RFC 4287, whichever the root element says it is. It parses the text in your browser and never fetches a URL.
The validator runs a syntax pass, then a structure pass for the format it detects.
Syntax. The text is parsed with the browser’s DOMParser as text/xml. Malformed markup, such
as an unclosed tag or a bare &, produces a parse error, which the tool shows before anything else.
RSS 2.0, on well-formed XML only:
rss with version="2.0", holding one channel.title, link and description.item needs a title or a description. The spec requires at least one.pubDate and lastBuildDate must be RFC 822 dates. The spec allows a two or four digit year.guid must be unique per item. When isPermaLink is true, which is the default, the spec says
the guid can be assumed to be a permalink, so the tool expects an absolute URL.enclosure needs url, length and type.link or guid missing from an item, a relative URL, and a duplicate link are warnings: the
spec does not require them, but a crawler cannot use an item without an address.Atom 1.0:
feed in the Atom 1.0 namespace.entry need exactly one id, title and updated.updated must be an RFC 3339 date-time with an uppercase T and Z.content needs a link with rel="alternate".author unless every entry has one, and should have a rel="self" link.The syntax line reads “Well-formed XML.” or shows the parse error. Below it, three counts: the detected format, the number of items or entries, and the file size.
The pre-filled feed has three items. The first is clean. The second and third carry these problems:
<item>
<title>Second post</title>
<link>/second</link>
<guid>https://example.com/first</guid>
<pubDate>2026-09-29</pubDate>
</item>
<item>
<link>https://example.com/third</link>
<enclosure url="https://example.com/third.mp3" type="audio/mpeg"/>
</item>
The syntax line reads “Well-formed XML.” and the root and channel checks pass. The summary shows RSS 2.0 and 3 items. Then, in order:
item #2: <link> "/second" is not an absolute URL.item #2: <guid> repeats item #1.item #2: <pubDate> "2026-09-29" is not an RFC 822 date.item #3 needs a title or a description.item #3 has no guid.item #3: <enclosure> is missing length.Write the link as https://example.com/second, give the item its own guid, use
Tue, 29 Sep 2026 09:00:00 GMT, add a title to item 3 and a length to the enclosure, and the
feed passes.
2026-09-29 is not RFC 822; RSS needs a date such as
Tue, 29 Sep 2026 09:00:00 GMT. Atom is the reverse: it needs a full RFC 3339 date-time.link, guid or an enclosure url.feed root.updated value.Google’s sitemap documentation says it accepts RSS 2.0 and Atom 1.0 feeds, and also says such a feed only provides information on recent URLs. A feed is a good supplement to an XML sitemap, not a full replacement for one. Search Engine Journal reported that John Mueller suggested RSS feeds as a way for AI crawlers to find content: see Mueller on sitemaps and AI crawlers.
It never fetches the URLs it finds, so it cannot confirm that a link resolves or can be indexed. It does not check encoding, media RSS extensions or other namespaces, and it cannot tell you which live pages are missing from the feed.
No. It only parses XML you paste into the textarea, entirely in your browser. That avoids a CORS-dependent network fetch and means nothing you paste is sent anywhere, but you have to copy the feed's contents yourself.
Yes. Google's documentation says it accepts RSS 2.0 and Atom 1.0 feeds. It also says such a feed only provides information on recent URLs, so it does not replace a full XML sitemap for a large site.
No. It checks RSS 2.0 and Atom 1.0 only. A file whose root is rdf:RDF, which is RSS 1.0, is reported as unsupported, and any other root element is reported as not a feed.
The RSS 2.0 specification makes guid optional. It is still worth having, because it is how a reader tells a changed item from a new one, so the tool warns instead of failing.
It means the file is well formed and meets the spec rules this tool checks. It does not confirm the listed URLs exist, return a 200 status or are eligible for indexing.
Noindex, canonical and sitemap conflict checker: see where one page's three signals contradict Google's own guidance. Free, runs in your browser.
Hreflang sitemap generator: turn language codes and URLs into sitemap XML with xhtml:link alternates, and check codes and URLs. Free, runs in your browser.
HTTP status code lookup: see how Google's crawlers handle each code you paste, plus a redirect hop count against the 10-hop limit. Free, runs in browser.
Robots meta tag validator: check meta robots and X-Robots-Tag rules against Google's list, and catch bad values and conflicts. Free, runs in your browser.