A Claude Code plugin that checks whether your work on a Webflow dev site broke anything. Run one command after publishing, and it checks forms, key flows, SEO and images against production, then gives you a PDF report.
/site-guard:check
Use /site-guard:check --full before a production publish. It checks all of the session's work and runs the wider non-submitting checks.
Run these in a normal terminal, such as PowerShell, then start a new Claude Code session:
claude plugin marketplace add psingh-valorx/site-guard
claude plugin install site-guard@valorx-tools
You need Claude Code's claude command on your laptop. Inside a terminal Claude Code session you can use /plugin instead, but the desktop app's Code tab and the VS Code panel don't have that panel.
Desktop app: use a local session on Windows. Once the marketplace is added, you can also manage the plugin from + > Plugins next to the prompt box. It doesn't work in WSL or cloud sessions, and it doesn't appear in Cowork.
Run these in a normal terminal, then restart Claude Code or the desktop app:
claude plugin marketplace update valorx-tools
claude plugin update site-guard@valorx-tools
If you change the plugin, raise version in .claude-plugin/plugin.json too, so the update picks up your change.
After your private settings are in place, run this once on your own laptop:
powershell -ExecutionPolicy Bypass -File scripts\make-team-setup.ps1
It creates %USERPROFILE%\.site-guard\Site-Guard-Setup.cmd. Teammates double-click it, and it saves the settings and installs the plugin. If Claude Code's command line is missing, it offers to install it.
By default the file holds no secrets, so you can share it like any file. Without Marketo, form delivery is reported as not verified. Add -IncludeMarketo to include your Marketo credentials too, and then share that file only privately.
Teammates still turn on Claude in Chrome and connect Webflow themselves. If your settings change, make a new file and have everyone run it again.
For teammates on a Mac, run this on your laptop as well:
powershell -ExecutionPolicy Bypass -File scripts\make-team-setup-mac.ps1 -IncludeMarketo
It creates Site-Guard-Setup-Mac.zip, which holds Site-Guard-Setup-Mac.command with permission to run. Building the zip needs Python. On the Mac, teammates unzip it and double-click the file. It saves the settings, installs PowerShell 7 if Homebrew is available, installs the plugin, and tests Marketo. The plugin's scripts run on a Mac with PowerShell 7 (pwsh), and the check itself works the same way.
The first time, macOS may block a file downloaded from chat. If it does, open System Settings > Privacy & Security, click Open Anyway next to the message about the file, and confirm. On older macOS versions, right-click the file and choose Open.
- Site config (required): copy
config/site-guard.example.ymlto%USERPROFILE%\.site-guard\site-guard.ymland fill it in, or get your team's copy. The plugin stops without it, and it never tests a site that isn't in that file. - Claude in Chrome: install the extension and connect it. It runs the checks in a new tab. In a terminal, start Claude Code with
claude --chrome, or run/chrome. - Webflow connector: connect it in Claude.
- Marketo (optional): copy
.env.exampleto%USERPROFILE%\.site-guard\.envand add your values. Don't put this file in OneDrive or a repo. Without it, form delivery is reported as not verified.
Chrome or Edge creates the PDF, and PowerShell, which comes with Windows, runs the scripts. Nothing else needs installing.
Keep both files private. Share them through a password manager, and never commit them.
| Verdict | Meaning |
|---|---|
PASS |
Every check in scope ran, and this work added no issues |
BREAKING |
At least one breaking issue was found |
INCOMPLETE |
No breaking issue was found, but something couldn't be verified |
Reports are saved in %USERPROFILE%\.site-guard\reports.
- It only clicks, types and submits on the configured dev site. Production is only read for comparison.
- It never publishes, and never changes Webflow, Marketo or a CRM.
- It only makes real form submissions on pages you worked on in the session, using your configured test address.
- It doesn't get around CAPTCHA.
Real submissions are off by default. Turn on real_submissions.enabled only after you've proven cleanup works.
Real submissions have real effects, such as confirmation emails, alerts and CRM records. List each form's effects in your config so people know before they run it. A Marketo trigger campaign, limited to the exact test address, should delete the test lead afterwards.
- Forms, flows and known differences: your local
site-guard.yml. A form that isn't listed is never submitted. - SEO and image rules:
config/seo-rules.yml. - After changing the report script, run
powershell -ExecutionPolicy Bypass -File tests\run-tests.ps1. It checks the verdict rules against 64 cases and prints how many passed.
- It only sees changes Claude made through the Webflow tools in the session's saved history. Tell Claude about any edits you made by hand.
- A new session can't see earlier work. The report then says so and marks the run
INCOMPLETE. - A
PASScovers what was tested, not the whole site. The report's Coverage section shows what wasn't. - The plugin can't see your CRM or helpdesk, so check those by hand.
- Windows only for now.
Set up cleanup and its protections yourself, and never test with a real customer's address. Deleting a person from Marketo with Remove from CRM on can't be undone, so limit the campaign to the exact test address.
No warranty. You're responsible for what you run against your own site.