Your pricing page is probably your highest-intent page and your most neglected one. Most teams set it up once and forget about it. This skill reads a pricing page (URL or local file) and audits it against conversion best practices, returning a prioritized list of fixes.
What Makes This a Claude Code Skill
Claude Code uses Firecrawl or WebFetch to scrape the pricing page, then analyzes the full page structure — plan naming, feature grids, CTA placement, social proof, FAQ coverage, and anchoring tactics. It can also scrape competitor pricing pages for comparison. The audit output goes directly into your project.
The command file lives at .claude/commands/pricing-audit.md.
What Gets Audited
- Plan Naming — are plan names clear and self-selecting? Do they signal who each plan is for?
- Price Anchoring — is there a visual anchor that makes the target plan look like the obvious choice?
- Feature Comparison — is the feature grid scannable? Are the differences between plans clear?
- CTA Strength — button copy, placement, contrast, urgency signals
- Social Proof — customer logos, testimonials, user counts near the pricing decision point
- Objection Handling — does the page address common purchase objections (refund policy, contract terms, migration)?
- FAQ Section — are the right questions answered? Are common pricing objections addressed?
- Free Tier / Trial — is the free option positioned to drive upgrades, not just usage?
- Enterprise Gating — if there’s a “Contact Sales” tier, is it clear why someone would need it?
Setup
Create .claude/commands/pricing-audit.md:
Audit the pricing page at: $ARGUMENTS
## Step 1: Scrape the Page
Use Firecrawl or WebFetch to retrieve the full pricing page content. Capture:
- Plan names and price points
- Feature comparison grid
- CTA buttons and their copy
- Social proof elements (logos, testimonials, stats)
- FAQ section
- Any trust signals (guarantees, certifications, security badges)
## Step 2: Conversion Audit
Analyze against these criteria:
- **Plan Naming**: Do names self-select? (e.g., "Starter" vs "Team" vs "Enterprise" is clear; "Basic" vs "Plus" vs "Pro" is not)
- **Price Anchoring**: Is there a highlighted/recommended plan? Does the layout guide the eye?
- **Feature Grid**: Can you tell the difference between plans in under 10 seconds?
- **CTA Copy**: Is it specific ("Start free trial") or generic ("Get started")?
- **Social Proof**: Are customer logos, counts, or testimonials visible near the pricing?
- **Objection Handling**: Is there a money-back guarantee? Free trial? No-contract language?
- **FAQ**: Does it cover billing, cancellation, refunds, migration, and discounts?
- **Mobile**: Would this page work on a phone?
## Step 3: Competitor Comparison (Optional)
If relevant competitor URLs are known, scrape 2-3 competitor pricing pages and note:
- How their pricing compares
- What objections they handle that you don't
- Structural choices worth stealing
## Step 4: Prioritized Recommendations
Rank fixes by estimated conversion impact:
- **High Impact**: Changes to CTA, pricing display, or missing social proof
- **Medium Impact**: FAQ gaps, plan naming, feature grid clarity
- **Low Impact**: Copy tweaks, visual polish, minor layout adjustments
## Output
Write to `./audits/pricing-audit-[domain].md`
Print top 5 highest-impact recommendations to terminal.Usage
/project:pricing-audit https://myapp.com/pricingClaude scrapes the page, runs a full conversion audit, and returns prioritized recommendations with specific fixes.
Tips
- Run this on your own pricing page and 2-3 competitors in the same session for comparison
- The FAQ section audit often catches the biggest gaps — most pricing pages skip refund policy and migration questions
- Re-run after any pricing change to catch new issues