content-protection-auditlisted
Install: claude install-skill zaraonrecord/claude-marketing-skills
# Content protection audit
Protect a site's content without hurting its search traffic. Warnings and guard rails, nothing hostile: no blocking real visitors, no traps, no attacks on bots.
## Inputs to ask for
- The site URL, and where it's hosted (Cloudflare, Netlify, Vercel, WordPress host, other). Header and robots changes are made differently on each.
- What is public, what is paid or members-only, and where the paid content is served from.
- Every outside service the site loads or calls: fonts, analytics, payments, forms, embeds, APIs. If you can fetch the site, list them yourself and ask the owner to confirm.
- Whether the owner wants to appear in AI answer tools (most do: they send visitors).
## Step 1: check what's there
Fetch and report, as a table (item | found | risk | fix):
- Response headers on the homepage: Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options or frame-ancestors, Referrer-Policy, Permissions-Policy.
- /robots.txt, /llms.txt, /.well-known/tdmrep.json, and the terms page.
- Whether any paid content is reachable without signing in: view the page source and the JavaScript and data files it loads. Paid text in a public file is the biggest risk, ahead of everything else here.
Never claim something is present or missing without having fetched it. If you couldn't fetch it, say so.
## Step 2: security headers
Draft headers in the host's format. Build the Content-Security-Policy from the confirmed list of outside s