π Audit website GDPR privacy compliance with HTTP checks and HTML reports
β‘ 8 views Β· π Market Research & Insights
π‘ Pro Tip β HTTP Request scraping tends to break when sites update their markup. If youβre scraping a major platform, check if ScraperNode covers it β it has maintained scrapers for LinkedIn, Instagram, TikTok, YouTube, and 20+ other platforms that return structured data.
Description
Quick overview
This workflow manually audits a websiteβs GDPR signals by scraping the homepage and attempting to locate and analyze its privacy policy, then generates an HTML report with a site compliance score, detected trackers, cookie-consent findings, and policy-quality grading.
How it works
- Starts when you manually run the workflow.
- Uses the provided website URL to fetch the siteβs homepage HTML via HTTP.
- Scans the homepage HTML to detect common tracking scripts (Google Tag Manager, Meta Pixel, Hotjar), looks for cookie-consent banner signals, and identifies a privacy-policy link or builds fallback policy URL candidates.
- Fetches each candidate privacy-policy URL via HTTP and selects the first page that looks like a real privacy policy (not a soft 404 and with sufficient policy-related text).
- Computes a site-level GDPR score based on the presence of a privacy policy, cookie consent signals, and whether trackers appear to load without consent.
- If a readable policy page is found, grades the policy text against GDPR-related criteria (controller/contact details, purposes, lawful basis/consent, data-subject rights, international transfers, security/retention, and overall transparency).
- Renders a branded HTML audit report containing the scores, identified gaps, and policy-quality section as the final output.
Setup
- Enter the target URL (including https://) in the workflowβs input field for
website_url. - Ensure the audited site is publicly accessible so n8n can fetch the homepage and candidate privacy-policy pages over HTTP.
- (Optional) Customize the HTML report branding and wording in the report template before running the workflow.
π Nodes Used
HTTP Request
π₯ Import
Download workflow.json and import into n8n:
Workflow menu β Import from File