Here's your prompt library

Point this at the client's current site. It reads every page and hands you a written record of what's actually there — which is the thing you're going to build every later decision on.

# Audit an existing small business website

## Context
I'm rebuilding the website for a local business. Before I design anything I need an
honest picture of what they already have — what's on the site, what's ranking, and
what's actively working against them.

- Site to audit: [URL]
- Business: [NAME] — [what they do]
- Where they work: [CITY, STATE / service area]
- Their money service (the one that pays best): [SERVICE]

## What to do
Crawl the site and work through it page by page. Fan out parallel agents — one per
batch of pages — so this doesn't take all day. For every page, record:

1. URL, page title, meta description, H1.
2. A plain-language transcription of the actual content on the page.
3. Word count, and whether the content is genuinely unique or a template with the
   city/service swapped out.
4. Structured data / schema markup present (or missing).
5. Internal links in and out.

Then find the problems. I care about these specifically:

- **Duplicate and templated pages.** How many pages are near-copies of each other with
  a city or service name swapped? Give me a count and a percentage of the site.
- **Keyword cannibalization.** Which pages are competing against each other for the
  same search term? List the offenders and name the single page that should own each
  term. This is usually the most expensive problem on the site.
- **Thin content.** Pages under ~300 words with nothing unique to say.
- **Proof gaps.** Are the photos stock or real work? Are there testimonials or reviews
  anywhere? Is there a blog that was started and abandoned?
- **Structure.** Is the URL scheme consistent? Are services and locations organised in
  a way a human would predict?
- **Local SEO.** Does the site's location targeting line up with a Google Business
  Profile and their real service area, or is it a spray of city pages they've never
  worked in?

## Output
Write these files:
- `audit/sitemap.md` — every URL with its title, word count, and a one-line verdict.
- `audit/pages/.md` — the transcription of each page.
- `audit/README.md` — the findings. Lead with the three problems costing them the most
  money, each with the evidence (page counts, the specific URLs, the exact keywords).

## Rules
Only report what's actually on the site. Don't estimate traffic, rankings, or revenue
you can't see — if you don't have the data, say so and tell me where I'd get it. I'd
rather have five findings I can prove than twenty I can't.

Feed the audit back in. This turns "here's what's broken" into a new sitemap and a content brief for every page — so by the time you build, the copy and the SEO are already decided.

# Turn the audit into a redesign plan

## Context
You audited [BUSINESS NAME]'s existing site — the findings are in `audit/README.md`
and `audit/sitemap.md`. Now plan the rebuild. I'm not designing anything yet; I want
the structure and the content decided before I open an editor.

- Business: [NAME] — [what they do]
- Service area: [CITIES they genuinely work in — not a wish list]
- Money service: [SERVICE]
- Goal: keep every bit of SEO value they've earned, drop everything that's diluting it.

## What to do

### 1. Propose the new sitemap
Consolidate. A focused site beats a big one. Specifically:
- Merge the cannibalizing pages into ONE page per search term. Name which URL wins.
- Cut spun location pages down to the cities they can actually prove work in — a
  handful of real ones beats fifty templates, and it lines up with their Google
  Business Profile.
- Fold overlapping services together where a searcher wouldn't tell them apart.
- Give me a consistent URL scheme and explain the rule in one line.

Every consolidation decision has to cite the audit finding it came from. If you can't
point at the evidence, don't make the cut.

### 2. Map every old URL to a new one
Produce `redesign/redirect-map.md` — every existing URL with an explicit 301 target.
Nothing 404s. This is where people lose their rankings, so be exhaustive.

### 3. Write a brief for every new page
One file per page in `redesign/briefs/.md` containing:
- Target keyword (one primary, and it must not be the primary of any other page)
- Page title and meta description
- Every heading, in order (H1 → H2s → H3s)
- The actual body copy — written, not described. Their voice, not marketing mush.
- The structured data / schema for the page
- Internal links: which pages this one links to, and why
- Images needed, with the alt text written out
- What the page is asking the visitor to do

### 4. Flag the gaps
List what you could NOT write because it needs a human: real testimonials, real
project photos, licence numbers, pricing, guarantees. Be specific — that list is what
I take to the client.

## Output
`redesign/new-sitemap.md` (the plan + consolidation decisions with their evidence),
`redesign/redirect-map.md`, and `redesign/briefs/*.md`.

## Rules
Do not invent proof. No made-up reviews, no fake project counts, no "trusted by 500+
homeowners" unless the audit found it. Placeholder text is fine — invented credibility
is not, and it's the fastest way to get a client in trouble.

Now it builds. Start from a template repo you already own and trust — a past client site works perfectly — and let it apply the briefs. This is the part you can walk away from.

# Build the site from the briefs

## Context
I've cloned a site I built for a previous client as the starting template. The
structure, CSS architecture, and JS all work — I want to keep them. Build [NAME]'s
site by applying the redesign plan to this template.

- Plan: `redesign/new-sitemap.md`
- Briefs: `redesign/briefs/*.md` — one per page
- Redirects: `redesign/redirect-map.md`
- Business: [NAME] — [what they do] in [CITY, STATE]
- Brand vibe: [e.g. rugged & straightforward / warm & local / clean & modern]
- Brand colours: [HEX, or "pick to suit the logo"]
- Photos: [attached / in ./uploads — or "use placeholders, real photos coming"]

## What to do
1. Build every page in the sitemap using the template's existing components. This is a
   content and branding swap, not a rebuild — keep the CSS architecture, the variables,
   the JS, and the responsive behaviour.
2. Use each brief verbatim: the headings, the body copy, the title and meta, the schema.
   The briefs are the source of truth — don't rewrite them as you go.
3. Wire up the internal links and implement the redirect map.
4. Set the brand colours and swap the logo and business name everywhere.
5. Images: use the real photos if I gave you any. If not, pull placeholders via the
   [Freepik / stock API] key in my `.env` and name every file so I can find and replace
   it later. Write real alt text from the brief either way.
6. Scrub for leftovers — the previous client's name, phone number, alt text, or demo
   content anywhere in the build. Search the whole repo, not just the pages you touched.

## What NOT to touch
Don't restructure the CSS, rename classes, or change the component system unless I ask.
If a page genuinely doesn't fit the template, stop and flag it rather than improvising
a new layout.

## Output
Build it, then give me a review list, because I'm checking all of it:
- Every page you created, and which brief it came from
- Every placeholder image that needs a real photo swapped in
- Anything in the briefs you couldn't implement, and why
- Anything you had to make a judgement call on