POPIA Compliance Scan Workflow for Website & Privacy Policy HTML

Scan your website for POPIA compliance signals—get a privacy policy quality grade in one run

This POPIA Compliance Scan Workflow for Website & Privacy Policy HTML manually audits a target website by fetching its homepage HTML, detecting common tracker and cookie-consent indicators, locating a privacy policy page, and then producing a site compliance score plus a keyword-based privacy policy quality grade.

What this workflow does

• Runs manually from an n8n workflow start trigger.
• Sends an HTTP request to fetch the provided website URL homepage HTML.
• Analyzes the homepage HTML to detect:
  • Common trackers such as Google Tag Manager, Meta Pixel, and Hotjar
  • Cookie-consent banner presence
  • On-site privacy policy link while skipping third-party policy links
• Builds candidate privacy policy URLs (from the detected link and common fallback paths) and fetches them via HTTP.
• Selects the first fetched page that appears to be a real privacy policy (e.g., sufficient length, not a 404, and containing privacy/POPIA language).
• Calculates a site-level compliance score and generates a gap list.
• Grades the privacy policy against seven POPIA-oriented criteria, then outputs the full results (score, detected gaps, and breakdown).

Use cases

• SaaS operators validating POPIA-related readiness for a new or updated website.
• Automation engineers testing privacy and cookie-consent implementation before launch.
• Internal compliance checks to quickly surface tracker presence and privacy policy quality issues.

Technical details (n8n workflow)

• Manual trigger workflow start
• HTTP Request nodes to fetch homepage and privacy policy HTML pages
• Logic built with Set, Code, and supporting sticky note documentation
• Outputs final scoring and POPIA policy grading results

Setup note: update the website_url input step and ensure the site is publicly accessible over HTTP/HTTPS so the workflow can retrieve the pages.