GDPR Privacy Audit n8n Workflow: HTTP Scrape & HTML Report

Audit GDPR privacy signals in minutes—scrape a homepage, verify the privacy policy, and generate an HTML compliance report

This GDPR Privacy Audit n8n Workflow performs an HTTP-based review of a target website’s GDPR signals. By scraping the homepage HTML and locating a likely privacy-policy page, it outputs a branded HTML audit report with a site compliance score, detected trackers, cookie-consent findings, and a policy-quality grade.

What this workflow does

• Manual start: Run the workflow manually when you want to evaluate a specific site.
• Scrape the homepage via HTTP: Fetches the homepage HTML using your provided website_url and scans it for common tracking and consent signals.
• Detect tracking and cookie-consent signals: Looks for typical patterns associated with trackers (e.g., Google Tag Manager, Meta Pixel, Hotjar) and checks for cookie-consent banner signals.
• Find and verify the privacy policy: Identifies a privacy-policy link—or generates fallback policy URL candidates—then fetches each candidate via HTTP and selects the first page that appears to be a real privacy policy (not a soft 404 and with sufficient policy-related text).
• Compute a GDPR site score: Scores based on privacy-policy presence, cookie-consent signals, and whether trackers appear to load without consent.
• Grade policy content: If a readable policy is found, grades it against GDPR-related criteria such as controller/contact details, purposes, lawful basis/consent, data-subject rights, international transfers, security/retention, and transparency.
• Generate the final report: Renders the results into a final HTML audit report showing scores, detected gaps, and the policy-quality section.

Use cases

• Evaluate whether marketing pages contain expected GDPR compliance signals before a campaign launch.
• Quickly assess third-party websites (or vendors) for privacy policy availability and cookie-consent behavior.
• Internal SaaS checks for privacy-policy and consent consistency during releases.

Technical details

• Nodes/steps include: manual trigger, set, code, html, sticky note, and HTTP Request.
• Input: website_url (must include https://).
• Output: a rendered HTML report with GDPR score, tracker/cookie-consent findings, and policy-quality grading.