[Bug/Security] Fresh self-hosted n8n instance flagged as Phishing/Social Engineering by Google Safe Browsing

Describe the bug Immediately upon deploying a clean, self-hosted n8n instance using Docker on a dedicated subdomain (n8n.example.com), Google Safe Browsing and Google Search Console flagged the domain for Social Engineering / Phishing. Google Search Console specifically highlights the /signin redirect endpoint as deceptive: • This appears to be an automated false-positive triggered when Googlebot scans new subdomains (via Certificate Transparency logs) and encounters an unindexed authentication screen (/signin) without existing domain authority. To Reproduce 1. Spin up a fresh n8n Docker container on a new subdomain behind a reverse proxy (Nginx / Cloudflare) over HTTPS. 2. Access for the first time. 3. Observe Google Safe Browsing flagging the site as "Deceptive site ahead" within hours or days of deployment. Expected behavior The n8n web interface should include standard anti-indexing directives (e.g., <meta name="robots" content="noindex, n…