RSS and Atom feed
An RSS or Atom feed declared in the markup — how readers and aggregators subscribe to new material. Optional.
An RSS or Atom feed is a machine-readable list of your latest posts. Feed readers, aggregators, podcast apps, newsletter tools and automation services (Zapier, IFTTT) subscribe to it to pick up new material without visiting the site. Feeds are optional: a corporate site or a shop without regular publications loses nothing without one.
How SiteScan checks it
The scanner looks in the <head> of the start page for a <link rel="alternate"> whose type is application/rss+xml or application/atom+xml. If it finds one, the row shows RSS or Atom; if not, it shows "None" as a neutral fact, not a fault. A feed that exists but is not declared in the markup is not detected, and readers will not find it automatically either.
How to add or declare one
- Most CMSs generate a feed already: WordPress at
/feed/, Ghost at/rss/, and static site generators through a plugin. - Declare it on every page:
<link rel="alternate" type="application/rss+xml" title="Blog" href="/feed/">. - Include full titles, publication dates and absolute links in the items, and keep the feed on the same domain.
More in our guide to RSS and Atom feeds.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Indexing”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data