← ClaudeAtlas

vercel-firewalllisted

Sets up and reviews the Vercel Firewall so scanners and junk traffic cost nothing while visitors, search engines and AI assistants still get in. Covers a deny rule for the paths vulnerability scanners probe (generated and checked against the site's real files by scripts/firewall-rules.mjs), Bot Protection (log first, then challenge), the AI Bots ruleset and its trade-off for AI citations, rate limits for forms and APIs, firewall rules in vercel.json, and reading the firewall log. Use it when setting up or reviewing security on Vercel, blocking bots, scanners or WordPress probes, deciding whether to block AI crawlers, or when usage shows lots of bot or 404 traffic. Changes are prepared for a person to approve.
sharabarinillia/SEO-GEO-Vercel-Playbook-Skill · ★ 1 · AI & Automation · score 78
Install: claude install-skill sharabarinillia/SEO-GEO-Vercel-Playbook-Skill
# Vercel Firewall for static sites A static site has no WordPress, no PHP and no `.env` file, yet scanners ask for them all day. Each ask is a billed request and an uncached 404. A deny rule turns them into free, blocked requests: traffic that WAF rules deny or challenge incurs no CDN requests or data transfer (Vercel, WAF usage and pricing, checked 4 November 2026). **The other half of the job is not blocking the wrong things:** search engines, AI search bots, link-preview fetchers and uptime monitors. ## Steps 1. **Generate the rules and prove they match no real file:** ```bash node <skill>/scripts/firewall-rules.mjs --check-dist dist # every file in the build node <skill>/scripts/firewall-rules.mjs --check-sitemap https://www.example.com/sitemap.xml node <skill>/scripts/firewall-rules.mjs # the CLI commands to apply them ``` If a real path collides (a site that really serves `.log` files, say), exclude it with `--keep log` and check again. `--test /wp-login.php,/about/` shows single paths. 2. **Show the plan to the person and get approval.** Firewall changes are live for every visitor once published. 3. **Apply** with one of: - Vercel CLI in the linked project: the `vercel firewall rules add …` commands the script prints, then `vercel firewall publish --yes` (changes stay drafts until published). - REST API: `--format rest` prints `PATCH /v1/security/firewall/config?projectId=…&teamId=…` bodies (