GDPR Audit and Markdown Generator. Two tools, one URL.

By John Carlsson, Founder of AIWebPageSEO · Published 9 August 2026

GDPR compliance is not a one-time checkbox — it is an ongoing obligation that touches every third-party script, every form and every cookie your site sets. The most common failure is not a missing privacy policy but a correctly worded one that is contradicted by the site's own technical implementation: scripts loading before consent is given, data processors named in the policy that are not actually in use, and consent banners that offer no genuine reject option. The GDPR Audit checks the technical reality, not just the documents.

What GDPR actually requires from a website

Under GDPR and the UK PECR, any website processing personal data must: obtain freely given, specific, informed and unambiguous consent before setting non-essential cookies or firing tracking scripts; maintain a privacy policy that discloses what data is collected, for what purpose, how long it is retained and who it is shared with; and ensure that consent can be withdrawn as easily as it was given. Pre-ticked boxes, dark patterns that make rejection harder than acceptance, and banners that load after the tracking scripts have already fired are all non-compliant regardless of how the banner is worded.

Why script loading order matters

The most common technical failure is loading analytics and advertising scripts in the page head, before the consent banner has loaded and before any user interaction. The sequence matters: the script executes, data is sent to a third party, and only then the banner appears asking for consent that has already been bypassed. The GDPR Audit detects every third-party script on the page, identifies the provider, and checks whether it fires before or after a consent signal is present.

The indirect SEO impact

GDPR compliance is not a direct Google ranking signal. It has indirect effects that matter. A consent implementation that blocks analytics before acceptance means your data is incomplete and you are making decisions on a distorted picture of your traffic. A missing privacy policy or absent contact information weakens E-E-A-T trust signals, which do affect rankings. And a data breach or ICO enforcement action is a reputational event that affects far more than your search visibility.

A practical GDPR compliance checklist

• Check that your consent banner loads before any non-essential scripts fire — not after.
• Ensure a genuine reject option is available without burying it in settings.
• Verify your privacy policy covers every third-party processor your site actually uses.
• Link your privacy policy from every page, including the footer.
• Run a GDPR audit after every tech stack change — a new plugin can introduce a gap.

Compliance is not expensive to achieve — most of the common failures are configuration errors, not fundamental architecture problems. The GDPR Audit finds them, explains them in plain English, and tells you exactly what to fix.

By John Carlsson, Founder of AIWebPageSEO · Published 9 August 2026

A compliant page and an AI-readable page solve two unrelated problems, and increasingly you need both. GDPR compliance protects you from enforcement action. Markdown readiness determines whether ChatGPT, Perplexity and Google AI can actually parse your page cleanly enough to cite it. Neither one substitutes for the other, and a page can pass one while quietly failing the other.

Why AI agents struggle with normal HTML

A web page is built for a browser, not a language model. Navigation menus, cookie banners, ad scripts and styling all sit in the same HTML as your actual content, and an AI system has to work to separate the signal from the noise. The Markdown Generator does that separation for you — stripping scripts and layout chrome, keeping headings, paragraphs, lists and structured data, in the order they actually appear on the page.

What the llms.txt specification actually asks for

The llms.txt v2 proposal calls for a clean, plain-text Markdown companion to a page — typically saved alongside it as page.md — so an AI agent gets a small, precise version of the content instead of parsing the full rendered HTML. It is explicitly not about dumping everything on the page; it is about giving an agent exactly the real content, nothing else. That is the standard the Markdown Generator's output is built against.

Where compliance and Markdown readiness overlap

They meet in one place: your privacy policy and cookie disclosures are themselves content an AI agent might try to read and summarise on a user's behalf. A privacy policy trapped inside a script-heavy cookie consent widget, or split across tabs that only render after a click, is invisible to both a compliance auditor skimming quickly and an AI agent parsing the static page. Clean Markdown output makes your compliance documentation legible to both audiences at once.

What a good Markdown export actually preserves

A correct conversion keeps every heading at its real level, every list as a real list, and pulls in content that only exists in a page's schema.org JSON-LD or in dynamically-loaded lists — not just the static text a simple scraper would catch. It should work regardless of the platform the page is built on, from a hand-coded site to WordPress, Shopify or Webflow, without needing a plugin or integration.

A practical AI-readability checklist

• Generate a Markdown export of your key pages and check every real heading survived the conversion.
• Confirm your privacy policy and cookie disclosures are static, readable text — not locked behind a script-only widget.
• Check whether any content only exists in JSON-LD schema, and whether that's the version you want an AI agent to read.
• Re-generate after any significant content change, the same way you'd re-run a compliance check.

Being compliant and being AI-readable are separate jobs, and doing one well says nothing about the other. The GDPR Audit checks whether your page is legally sound. The Markdown Generator checks whether it's actually usable by the systems increasingly standing between you and your next visitor.