01
Paste the copy
Use rendered copy, markdown, or HTML from any landing page or AI-generated draft.
Free tool
Paste any page copy and get a browser-only score for SaaS filler density, unsupported superlatives, and missing product mechanics. Use the fix list to make the copy more specific.
How to use
This scorecard checks copy against common generic SaaS phrases, unsupported superlatives, and missing concrete mechanics. It works on any page — not just Pagewell-generated ones.
01
Use rendered copy, markdown, or HTML from any landing page or AI-generated draft.
02
See generic phrase count, superlative risk, mechanic density, and a benchmark comparison.
03
Replace filler with concrete mechanics, add proof, remove unsupported claims, then paste again.
Example output
The scorecard lists filler phrases, superlatives, and missing mechanics so you can replace vague claims with concrete product proof.
Genericness score: 34/100 (needs work)
Generic phrases found: 4
- streamline your workflow
- all-in-one platform
- boost productivity
- unlock your potential
Unsupported superlatives: 2
- industry-leading
- best-in-class
Missing: concrete product mechanics, examples, commands
Target: keep generic filler low and add mechanics only your product can claim. Related tools
Generate better copy
Pagewell gives your coding agent product facts, claim rules, and anti-generic QA gates — so every page uses real mechanics, examples, commands, and constraints.
bunx skills add ReScienceLab/pagewell --skill pagewell Then ask: Use Pagewell to generate a page with concrete product mechanics and no generic filler.
FAQ
It counts generic SaaS filler phrases, unsupported superlatives, and missing concrete mechanics. It also benchmarks your score against typical ranges.
No. The scorecard runs entirely in your browser with client-side logic. No text is sent to a server.
Yes. The tool includes a default list of common SaaS filler, and you can add your own banned phrases in the custom input field.
Not necessarily. A high genericness score means the copy could describe many products. The fix is to add specific mechanics, examples, commands, and proof that only your product can claim.