icp-website-audit
End-to-end website audit through ICP eyes. Builds synthetic personas (if they don't already exist), runs a structured scorecard review of the client's site, then runs a head-to-head competitive comparison against top competitors. Produces a single consolidated report with persona feedback, competitive positioning, and prioritized recommendations. The complete "how do our buyers actually experience our site vs the competition?" workflow.
Best use case
icp-website-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
End-to-end website audit through ICP eyes. Builds synthetic personas (if they don't already exist), runs a structured scorecard review of the client's site, then runs a head-to-head competitive comparison against top competitors. Produces a single consolidated report with persona feedback, competitive positioning, and prioritized recommendations. The complete "how do our buyers actually experience our site vs the competition?" workflow.
Teams using icp-website-audit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/icp-website-audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How icp-website-audit Compares
| Feature / Agent | icp-website-audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
End-to-end website audit through ICP eyes. Builds synthetic personas (if they don't already exist), runs a structured scorecard review of the client's site, then runs a head-to-head competitive comparison against top competitors. Produces a single consolidated report with persona feedback, competitive positioning, and prioritized recommendations. The complete "how do our buyers actually experience our site vs the competition?" workflow.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ICP Website Audit
The complete "how do buyers experience our site vs the competition?" workflow. Chains persona building, website evaluation, and competitive comparison into a single end-to-end audit.
## Quick Start
```
Run an ICP website audit for [company]. Site: [url]. Compare against [competitor 1] and [competitor 2].
```
With existing personas:
```
Run an ICP website audit for [client]. Personas already exist. Compare against [competitor urls].
```
## Inputs
| Input | Required | Source |
|-------|----------|--------|
| **Company name** | Yes | User provides |
| **Company URL** | Yes | User provides |
| **Competitor URLs** | Yes (1-3) | User provides, or discovered in Phase 1 |
| **Client context file** | Optional | `clients/<client>/context.md` |
| **Existing personas** | Optional | `clients/<client>/personas/personas.json` |
## Step-by-Step Process
### Phase 1: Persona Setup
**Check if personas already exist:**
```
clients/<client>/personas/personas.json
```
**If personas exist:** Load them, confirm they look current, and list them for the user. Skip to Phase 2.
**If no personas exist:** Run `icp-persona-builder`:
1. Research the company — what they sell, who they serve, pricing model, stage
2. Identify 4-6 ICP segments from website, case studies, reviews, job postings
3. Build detailed synthetic personas with full profiles
4. Save to `clients/<client>/personas/`
**Output from this phase:**
- `clients/<client>/personas/personas.json` (machine-readable)
- `clients/<client>/personas/personas.md` (human-readable)
- `clients/<client>/personas/segments.md` (summary table)
### Phase 2: Website Scorecard Review
Run `icp-website-review` in **scorecard mode** against the client's own site.
1. **Crawl the client's site** — homepage, pricing, product, solutions, about, case studies, blog, docs
2. **Check external presence** — search results, review sites, social proof
3. **Run each persona through the site**, scoring on:
- First Impression (1-10)
- Messaging Relevance (1-10)
- Trust & Credibility (1-10)
- Clarity & Navigation (1-10)
- Objection Handling (1-10)
- Overall (1-10)
4. **Cross-persona synthesis** — consensus issues, segment-specific gaps, messaging disconnects
**Output from this phase:**
- Per-persona scored reviews
- Cross-persona analysis
- Initial recommendations
### Phase 3: Competitive Head-to-Head
Run `icp-website-review` in **head-to-head mode** against each competitor.
For each competitor (1-3):
1. **Crawl the competitor's site** — same pages as the client site
2. **Run each persona through BOTH sites**
3. **Per-persona comparison:**
- Quick takes on each site
- Dimension-by-dimension scoring for both
- "If I had to choose today..." verdict
- What the client should steal from the competitor
- What the client does better
4. **Cross-persona competitive summary:**
- Where the client wins across personas
- Where the competitor wins across personas
- At-risk segments (personas who lean toward competitor)
- Priority competitive moves
**Output from this phase:**
- Per-competitor, per-persona head-to-head reviews
- Competitive positioning map
- At-risk segments identified
### Phase 4: Consolidated Report
Merge all findings into a single audit report. This is the deliverable.
**Synthesis work:**
1. **Combine scorecard + competitive findings** — scorecard shows absolute quality, head-to-head shows relative positioning. Both perspectives matter.
2. **Identify the "so what"** — what are the 3-5 moves that would make the biggest difference?
3. **Rank recommendations by:**
- How many personas it affects (breadth)
- How much it would change conversion likelihood (depth)
- Whether competitors already do it better (urgency)
- Estimated effort (feasibility)
4. **Flag at-risk segments** — ICPs where competitors are winning. These need immediate attention.
---
## Output
Save to `clients/<client-name>/icp-website-audit.md`
Also save the sub-reports:
- `clients/<client>/personas/` (persona assets, reusable)
- `clients/<client>/icp-reviews/<date>-scorecard.md` (site review)
- `clients/<client>/icp-reviews/<date>-head-to-head-<competitor>.md` (per competitor)
### Consolidated Report Template
```markdown
# ICP Website Audit: [Company Name]
**Date:** [Date]
**Website:** [url]
**Competitors:** [competitor 1], [competitor 2], [competitor 3]
**Personas used:** [N] (from `clients/<client>/personas/`)
---
## Executive Summary
[5-7 sentences. How do buyers actually experience this site? What's working, what's
broken, where are competitors winning? Top 3 things to fix and why.]
### Scorecard Overview
**Average score across personas: [X/10]**
| Persona | Segment | Own Site Score | Would Convert? |
|---------|---------|:-:|:-:|
| [Name] | [Segment] | [X/10] | [Yes/Maybe/No] |
| ... | ... | ... | ... |
### Competitive Overview
| Persona | Own Site | [Comp 1] | [Comp 2] | Pick |
|---------|:-------:|:--------:|:--------:|:----:|
| [Name] | [X/10] | [X/10] | [X/10] | [Winner] |
| ... | ... | ... | ... | ... |
**Personas at risk:** [Names of personas who preferred a competitor — these represent ICP segments you may be losing]
---
## Part 1: ICP Segments & Personas
### Segments Identified
| # | Segment | Description | Priority |
|---|---------|-------------|----------|
| 1 | [Name] | [One line] | Primary |
| 2 | [Name] | [One line] | Primary |
| 3 | [Name] | [One line] | Secondary |
| ... | | | |
### Persona Summaries
[2-3 sentence summary of each persona — who they are, what they care about, how they evaluate. Link to full profiles in `personas/personas.md`.]
---
## Part 2: Website Scorecard
### Score Matrix
| Dimension | [P1] | [P2] | [P3] | [P4] | [P5] | Avg |
|-----------|:----:|:----:|:----:|:----:|:----:|:---:|
| First Impression | | | | | | |
| Messaging Relevance | | | | | | |
| Trust & Credibility | | | | | | |
| Clarity & Navigation | | | | | | |
| Objection Handling | | | | | | |
| **Overall** | | | | | | |
### Persona-by-Persona Highlights
For each persona, include:
- **[Persona Name]** ([Score]/10) — [One sentence summary]. Liked: [key positive]. Frustrated by: [key negative]. Blocker: [#1 thing stopping conversion].
### Cross-Persona Findings
#### Consensus Issues (All Personas)
1. [Issue] — [Why it matters]
2. ...
#### Segment-Specific Gaps
| Gap | Personas Affected | Impact |
|-----|------------------|--------|
| [Gap] | [Names] | [H/M/L] |
#### Messaging Disconnects
| Site says | Buyers say | Personas |
|-----------|-----------|----------|
| "[quote]" | "[quote]" | [Names] |
---
## Part 3: Competitive Analysis
### vs [Competitor 1]
**Overall: [Company wins / Competitor wins / Split]**
| Dimension | [Company] | [Competitor] | Winner |
|-----------|:---------:|:------------:|:------:|
| First Impression | [avg] | [avg] | |
| Messaging | [avg] | [avg] | |
| Trust | [avg] | [avg] | |
| Clarity | [avg] | [avg] | |
| Objections | [avg] | [avg] | |
| **Overall** | **[avg]** | **[avg]** | |
**Where competitor wins:**
- [Specific advantage, which personas care]
**Where we win:**
- [Specific advantage, which personas care]
**Personas who'd choose competitor:** [Names — these are at-risk segments]
---
### vs [Competitor 2]
[Same structure]
---
### Competitive Position Map
| Persona | Best Experience | Worst Experience | Notes |
|---------|:-:|:-:|---|
| [P1] | [Company/Comp] | [Company/Comp] | [Why] |
| [P2] | ... | ... | ... |
### At-Risk Segments
[Personas who preferred competitors. For each: which competitor, why, and what it would take to win them back.]
### Competitive Advantages to Amplify
[Things the company does better than ALL competitors — lean into these.]
### Gaps to Close
[Things competitors do better across most personas — neutralize these.]
---
## Part 4: Prioritized Recommendations
### Tier 1: High Impact, Do Now
These affect the most personas and/or address competitive gaps.
1. **[Recommendation]**
- **Why:** [Evidence from scorecard + competitive analysis]
- **Personas affected:** [Names]
- **Competitive context:** [Do competitors already do this better?]
- **Expected impact:** [What changes — conversion, trust, clarity]
- **Effort:** [Low/Med/High]
2. **[Recommendation]**
...
### Tier 2: Medium Impact, Plan For
3. **[Recommendation]**
...
### Tier 3: Segment-Specific Optimizations
These improve experience for specific ICP segments.
5. **[Recommendation]** — For [persona/segment]
...
### Quick Wins
- [Small change] → Benefits [persona]
- [Small change] → Benefits [persona]
---
## Appendix
### A. Full Persona Profiles
→ `clients/<client>/personas/personas.md`
### B. Detailed Scorecard Review
→ `clients/<client>/icp-reviews/<date>-scorecard.md`
### C. Detailed Competitive Reviews
→ `clients/<client>/icp-reviews/<date>-head-to-head-<competitor>.md`
### D. Persona Data (JSON)
→ `clients/<client>/personas/personas.json`
```
---
## Parallelization
Some phases can run in parallel to save time:
```
Phase 1: Build personas (if needed)
↓
Phase 2 + Phase 3 can partially overlap:
- Crawl all sites (client + competitors) at once
- Run scorecard first (client site only)
- Then run head-to-heads (reuse client crawl data)
↓
Phase 4: Consolidate (needs all prior phases)
```
If personas already exist, the whole workflow is just:
```
Crawl all sites → Scorecard → Head-to-heads → Consolidate
```
## Tips
- **Start with 1-2 competitors, not 5.** Each competitor adds a full head-to-head evaluation pass. Start focused, add more if needed.
- **The at-risk segments are the most actionable finding.** If a persona consistently prefers a competitor, that's an ICP segment you're actively losing deals in. That should drive urgency.
- **Reuse this quarterly.** Run personas once, then re-run the audit after site changes or quarterly to track improvement. Compare scores across dates.
- **Combine with SEO content audit for the full picture.** ICP audit tells you "does the messaging work for buyers?" SEO audit tells you "are buyers finding you in the first place?" Together they cover the full funnel.
- **This makes a great client deliverable.** The consolidated report is structured for sharing. Use `content-asset-creator` to make it into a polished HTML report.
- **Don't skip the competitive analysis.** The scorecard alone is useful, but the head-to-head is where the real insights are. Buyers always compare — your audit should too.
## Dependencies
- Skills: `icp-persona-builder`, `icp-website-review`
- Web search capability (for research, external presence checks)
- Web fetch capability (for reading website pages)
- No API keys or paid tools required
## Cost
Free — no paid APIs. All research and evaluation is done via web search and web fetch.Related Skills
seo-content-audit
Comprehensive SEO footprint analysis that orchestrates site-content-catalog, seo-domain-analyzer, and brand-voice-extractor into a single deep-dive report. Catalogs all content, pulls real SEO metrics, runs competitor analysis, builds topic/keyword and content-type gap matrices, extracts brand voice, and produces a prioritized recommendations report. The complete SEO audit for any company.
ad-to-landing-page-auditor
Analyze the message match between your ads and landing pages. Checks if the promise in the ad copy carries through to the landing page headline, body, and CTA. Flags disconnects that kill conversion rates. Works with Google, Meta, and LinkedIn ads.
icp-website-review
Evaluate a website, landing page, content, or any online asset through the eyes of pre-built synthetic ICP personas. Loads personas from icp-persona-builder output, then runs them against target URLs. Supports three modes: structured scorecard, freeform focus group, and head-to-head competitive comparison. Reusable — run against the same site after changes, or against new content anytime.
signal-detection-pipeline
Detect buying signals from multiple sources, qualify leads, and generate outreach context
seo-content-engine
Build and run an SEO content engine: audit current state, identify gaps, build keyword architecture, generate content calendar, draft content.
outbound-prospecting-engine
End-to-end outbound prospecting: detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign.
event-prospecting-pipeline
Find attendees at conferences/events, research their companies, qualify against ICP, and launch outreach
competitor-monitoring-system
Set up and run ongoing competitive intelligence monitoring for a client. Tracks competitor content, ads, reviews, social, and product moves.
client-packet-engine
Batch client packet generator. Takes company names/URLs, runs intelligence + strategy generation, presents strategies for human selection, executes selected strategies in pitch-packet mode (no live campaigns or paid enrichment), and packages into local delivery packets.
client-package-notion
Package all work done for a client into a shareable Notion page with subpages and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured Notion workspace the client can browse. Lead list CSVs are uploaded to Google Sheets and linked from the Notion pages. Use when you want to deliver work to a client in a polished, navigable format.
client-package-local
Package all work done for a client into a local filesystem delivery package with .md files and Google Sheets. Reads the client's folder (strategies, campaigns, content, leads, notes) and builds a structured directory with dated deliverables. Lead lists are uploaded to Google Sheets and linked from the markdown files. Use when you want to deliver work to a client in a polished, navigable format without requiring Notion.
client-onboarding
Full client onboarding: intelligence gathering, synthesis into Client Intelligence Package, and growth strategy generation. Phases 1-3 of the Client Launch Playbook.