X-DNS-Prefetch-Control header missing — the fix
The X-DNS-Prefetch-Control header is not set. DNS prefetching can leak information about which links a user might visit.
Where this fits: security in SEO
Security issues erode both rankings and trust. HTTPS has been a ranking signal since 2014, and browsers actively warn users away from insecure or mixed-content pages — a warning interstitial is a 100% bounce rate. Missing security headers rarely block indexing, but they widen your attack surface, and a hacked site (injected spam, malicious redirects) can be removed from results entirely. Security is the SEO work you do so you never have to do recovery work.
Why x-dns-prefetch-control header missing hurts your rankings
When DNS prefetching is enabled, the browser resolves domain names for links on the page before the user clicks them. While this improves performance, it can leak user browsing intentions to DNS servers and network observers, which may be a privacy concern for sensitive applications.
This is a low-severity issue: a polish item. Fix it in batches during scheduled maintenance; the win is cumulative quality, not a step change.
How to fix it
Add the X-DNS-Prefetch-Control header set to 'off' for sensitive pages, or 'on' if performance is prioritized over privacy. Evaluate your use case to choose the appropriate value.
X-DNS-Prefetch-Control: offSecurity best practices
- Serve everything over HTTPS and redirect HTTP with a single 301.
- Send HSTS, X-Content-Type-Options, and a Content-Security-Policy on every response.
- Eliminate mixed content — one insecure asset breaks the padlock.
- Keep dependencies and CMS plugins patched; most site hacks are known-CVE exploits.
- Monitor Search Console's security section — Google often knows you're hacked before you do.
The full library: SEO best practices, by category.
Frequently asked questions
What does "X-DNS-Prefetch-Control header missing" mean?
The X-DNS-Prefetch-Control header is not set. DNS prefetching can leak information about which links a user might visit.
Why does x-dns-prefetch-control header missing matter for SEO?
When DNS prefetching is enabled, the browser resolves domain names for links on the page before the user clicks them. While this improves performance, it can leak user browsing intentions to DNS servers and network observers, which may be a privacy concern for sensitive applications.
How do I fix x-dns-prefetch-control header missing?
Add the X-DNS-Prefetch-Control header set to 'off' for sensitive pages, or 'on' if performance is prioritized over privacy. Evaluate your use case to choose the appropriate value.
How serious is this issue?
This is a low-severity issue: a polish item. Fix it in batches during scheduled maintenance; the win is cumulative quality, not a step change. It belongs to the security family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects x-dns-prefetch-control header missing on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by x-dns-prefetch-control header missing, and hands you a ready-made fix task.
Check my site free