What response headers tell you
Before a browser renders anything, the server sends headers: instructions about caching, security, content type and whether the page may be indexed. They are invisible on the page, which is why problems here go unnoticed for months.
Headers that affect SEO
- X-Robots-Tag. The header version of a robots meta tag. A stray
noindexhere keeps a page out of Google even when the HTML looks fine. Common on PDFs and on staging configs that leak into production. - Cache-Control, ETag, Last-Modified. Good caching makes repeat visits fast and lets crawlers revalidate pages cheaply instead of downloading them again.
- Content-Encoding. Brotli or gzip compression cuts HTML and CSS transfer size by 70% or more. It is one of the cheapest speed wins there is.
- Content-Type. A page served as
text/plainwill not render as HTML. A sitemap served astext/htmlmay be ignored.
Security headers worth sending
- Strict-Transport-Security (HSTS) forces HTTPS on every future visit.
- Content-Security-Policy limits which scripts can run, the main defence against cross-site scripting.
- X-Content-Type-Options: nosniff stops browsers guessing file types.
- X-Frame-Options or CSP frame-ancestors stops other sites framing your pages for clickjacking.
- Referrer-Policy and Permissions-Policy control what you leak to other sites and which browser features pages can use.
None of these are direct ranking factors, but they protect visitors and the trust signals that do matter. Most can be added in one place: your CDN, host or framework config.
Check where a URL lands first with the redirect checker, and confirm your certificate with the SSL checker.