Generate a Referrer-Policy for public content pages
Use a privacy-balanced strict-origin-when-cross-origin policy for SEO and topic pages.
Open exampleGenerate a Referrer-Policy header with Nginx, Apache, Next.js, and HTML meta snippets for privacy and analytics tradeoffs.
适合站点上线前快速生成安全响应头;正式上线前建议按真实跳转、统计和第三方嵌入场景回归测试。
The result will appear here as structured cards.
Short, high-intent examples that are easy to open, share, and understand for search engines and AI systems.
Use a privacy-balanced strict-origin-when-cross-origin policy for SEO and topic pages.
Open exampleCreate a more conservative same-origin or no-referrer starting point for auth, forms, or payments.
Open exampleThese notes help users understand the results and help search engines and AI systems understand the tool.
It helps you inspect or process this value and get a readable result quickly.
Local tools run in the browser when possible. Server-side checks only use the input needed to complete the lookup.
For most public sites, start with strict-origin-when-cross-origin. It keeps full referrers on same-origin requests, sends only the origin cross-site, and avoids leaking paths from HTTPS to HTTP.
Treat it as a compatibility fallback. The site-wide default belongs in the HTTP response header, with meta tags used only when page-level support is needed.
Based on this query: Referrer-Policy generator free network troubleshooting