HTTP Header SEO & Caching Auditor
Misconfigured headers silently waste crawl budget, break CDN caching, and fail security audits. Paste your raw HTTP response headers from DevTools or cURL and get an instant 22-rule audit covering caching, indexing, security, and performance.
Tool interface
Audit Results
Parsed Headers
Introduction
HTTP response headers control how search engines crawl your site, how CDNs cache
your content, and how browsers secure the connection. A missing
Cache-Control wastes crawl budget. A stray X-Robots-Tag: noindex
deindexes your entire site. This auditor catches all of it from pasted headers.
How It Works
- Lines are tokenized into
Name: Valuepairs (case-insensitive names). - 22 rules run across four categories: Caching, SEO Indexing, Security, Performance.
- Each rule returns pass, warn, or fail with a specific fix suggestion.
- An aggregate score summarizes overall header health.
Privacy
Your headers are parsed entirely in your browser using string manipulation. No content is transmitted anywhere. No API calls, no tracking.
Limitations
- Cannot fetch live headers (CORS); you must paste them from DevTools, cURL, or logs.
- Rules are generic best practices; context-specific requirements (e.g., API vs HTML) aren't distinguished.
- Does not validate header values against external specs beyond common patterns.
FAQ
What's the difference between no-cache and no-store?
no-cache means the browser must revalidate with the server before using a cached copy. no-store means never cache at all. For SEO-critical HTML pages, neither is ideal — use short max-age instead.
Why does Vary: Accept-Encoding matter?
Without it, CDNs may serve gzip-compressed content to clients that only accept identity, or vice versa. It ensures the correct encoding variant is cached and served.
Are my headers uploaded?
No. Everything is parsed locally in your browser. Nothing is transmitted.