Exterior Renovations' website has a critical content misalignment: organic traffic is driven almost entirely by blog posts (Tyvek, LVL beams, copper gutters) while core service pages — Roofing, Siding, Decks, Windows — generate almost no traffic. The service pages exist but carry thin content with no local keyword targeting. This article documents the diagnosis, the rewrite strategy, and the AI-assisted workflow used to generate optimized page briefs.
See also: [1] | [2] | [3]
| Element | Current State | Target State |
|---|---|---|
| Word count | ~200 words | 800–1,000+ words |
| H1 | Generic (no location) | Includes "Madison" or "Madison, Wisconsin" |
| H2/H3 hierarchy | Minimal | Full hierarchy with keyword-rich headings |
| Local relevance | None | Wisconsin, Dane County, Madison throughout |
| FAQ section | Absent | Present (targets question-based queries) |
| Schema markup | None | Local Business + Service schema |
| Trust signals | Basic | Expanded (certifications, local tenure, reviews) |
Every service page should target the pattern [Service] + Madison, Wisconsin as its primary keyword. The H1, meta title, and opening paragraph should all include the city. Secondary mentions of "Wisconsin," "Dane County," and neighborhood-level references reinforce local relevance throughout the body.
Target keywords by page:
- Roofing → Roofing Contractor in Madison, Wisconsin
- Siding → Expert Siding in Madison
- Windows → Window Replacement in Madison
- Decks → Deck Installation Madison, Wisconsin
Each rewritten service page should follow this structure:
FAQs are high-value for local SEO because they directly match question-based queries. Each service page should include 4–6 FAQs. Example questions for Roofing:
This workflow was demonstrated live during the call using Claude and Google Search Console exports.
Why PDF? Claude handles PDF uploads more reliably than raw CSV or Google Sheets files. Convert all exports before uploading.
The project persists across sessions. You don't need to re-upload data or re-explain context each time you start a new chat within the project.
Within the project, prompt Claude to generate a full service page. Example prompt:
"Using the GSC and Ahrefs data provided, write a fully optimized service page for [Roofing] targeting the keyword 'Roofing Contractor in Madison, Wisconsin.' Include a proper H1/H2/H3 hierarchy, local keyword density, a FAQ section, and a CTA. The page should be 800–1,000 words."
Claude will reference the uploaded keyword data to inform heading choices, FAQ topics, and keyword placement.
The AI-generated brief will include:
- Full heading hierarchy with Madison/Wisconsin keywords embedded
- Body copy with local references (Dane County, Wisconsin climate, etc.)
- FAQ section targeting question-based queries
- Meta title and description suggestions
- A comparison of current vs. proposed page (word count, structure, local relevance)
Review for accuracy and brand voice. The content is a starting point — not final copy.
Once reviewed and approved by the client:
1. Have the developer create a draft page (e.g., /new-roofing) — not live yet
2. Share the draft link with the client for approval
3. On approval, make the draft the live page
Use a ClickUp task to track each page through this workflow.
| Page | Target Keyword | Status |
|---|---|---|
| Roofing | Roofing Contractor in Madison, Wisconsin | Brief generated (call demo) |
| Siding | Expert Siding in Madison | Pending |
| Windows | Window Replacement in Madison | Pending |
| Decks | Deck Installation Madison, Wisconsin | Pending |