RSS Capability Matrix Guide

Learn how to read feed field coverage, validity, and deterministic diagnostics in the RSS Inspector capability matrix.

What it does

The capability matrix shows which feed fields are present, valid, and countable across RSS and Atom documents.

Who it is for

Developers, SEO teams, and publishers who need predictable feed quality checks without black box scoring.

Use cases

Use matrix output for feed onboarding reviews, parser migration QA, and publisher quality scorecards.

What you will see

A field-by-field matrix, deterministic validity states, supporting examples, and feed-level metrics.

Common issues it detects

The matrix surfaces structural errors early.

  • Duplicate GUID or ID values
  • Missing item dates
  • Missing self links for feed identity
  • Content type mismatch with XML payload

How to fix

Start with invalid fields first, then resolve missing fields that your parser requires for ranking and deduplication.

  • Normalize dates to parseable formats
  • Keep GUIDs stable and unique
  • Add Atom self links where possible
  • Return XML content types consistently

How to interpret results

Treat Present as coverage, Valid as reliability, and Invalid as breakage risk for downstream consumers.

Safety and correctness

Feed fetches use SSRF-safe validation and deterministic metric calculations so results are repeatable and safer to run in production workflows.

Export options and why they matter

Export JSON for complete audits and CSV for spreadsheet triage and stakeholder sharing.

Diagnostic pattern: high Present, low Valid

If many fields are present but invalid, the feed likely has formatting drift rather than missing data.

  • Typical cause: date format changes, malformed GUID values, or invalid namespace usage
  • Next check: inspect raw payload for one failing item and compare against one passing item

Diagnostic pattern: low Present on core fields

If core fields are missing entirely, this is usually a source-template problem, not a parser bug.

  • Typical cause: upstream feed template no longer outputs required channel/item fields
  • Next check: verify CMS/export template and then rerun inspection before rollout

Related links