/website-audit

# Page Audit

Use this skill to audit the current page as a working web page, not as abstract copy. The goal is to give the user fixes they can apply immediately.

## When to Use

Use this skill when the user wants feedback on a landing page, article, pricing page, product page, signup flow, or any live page.

## Inputs

Use the current browser page by default. If the user mentions another page, navigate there first. If the page requires login or contains private data, summarize only what is necessary and avoid quoting sensitive content.

## Process

1. Inspect the page visually and read the page text.
2. Identify the page goal, likely audience, primary call to action, and conversion path.
3. Check SEO fundamentals: title, meta description if available, H1, heading structure, internal links, search intent match, indexable content, image alt text, and schema clues if visible.
4. Check accessibility fundamentals: semantic headings, keyboard path risks, form labels, link text, contrast risks, alt text, focus and motion concerns, and error states if visible.
5. Check conversion quality: clarity of promise, above the fold message, proof, objections, trust signals, CTA placement, pricing clarity, friction, and mobile layout risks.
6. Check credibility: claims that need proof, vague language, missing specifics, outdated content, and security or privacy reassurance.
7. Prioritize issues by likely user impact. Do not list generic best practices unless they apply to evidence on the page.

## Output Format

Start with this exact structure:

## Verdict
A 2 to 4 sentence summary of what the page does well, what is holding it back, and the highest leverage fix.

## Critical Fixes
List only issues that can materially hurt search, accessibility, trust, or conversion. For each issue include: Evidence, Why it matters, Fix.

## Important Improvements
List medium impact improvements. For each issue include: Evidence, Why it matters, Fix.

## Copy and UX Rewrites
Provide replacement copy for the hero, primary CTA, confusing sections, or weak trust copy when relevant.

## 30 Minute Fix List
Give 3 to 7 quick actions the user can complete today.

## Deeper Backlog
Give larger fixes that may require design, engineering, or content work.

## Rules

- Be specific to the page. Avoid generic audit filler.
- Include concrete replacement text when copy is weak.
- If you cannot verify something from the page, say that it was not visible.
- Do not use em dashes.