The Local Content Strategy Skill: From Keyword List to Content Architecture
You have the keyword list. It’s sitting in a spreadsheet with 80 rows. You know that “emergency plumber Charlotte” and “24 hour plumber Charlotte” and “burst pipe repair Charlotte” probably shouldn’t each have their own page — but you’re not sure which ones should be grouped together, which should become GBP services, and which you’re going to track on geogrids.
You also know that the informational keywords belong in blog posts, but you’re not sure which ones need full articles vs. which need a FAQ section on the location page.
The keyword research is done. The planning work is still entirely manual.
Open a spreadsheet. Copy keywords. Sort by volume. Try to identify patterns. Debate with yourself about whether “roof leak repair” and “emergency roof repair” are the same concept. Decide what content vehicle each cluster needs. Figure out which keywords to track on geogrids. Remember to check what GBP services you should add.
Three hours later, you have a content plan. Maybe.
Or you paste the keyword list into Claude and get back a complete content architecture in one response.
The Shift
The local-content-strategy skill transforms a keyword list into a complete content plan — organized concept clusters, content vehicle assignments for every cluster, geogrid tracking keyword selection with reasoning, GBP service and category confirmations, internal linking architecture, and a phased production priority order.
The organizing work that used to take a half-day in a spreadsheet takes one prompt.
Not a summary. Not suggestions. A complete architecture you can execute against immediately.
What This Looks Like
Prompt: "Take this keyword research output [paste keyword list from
local-keyword-research] and build the complete content strategy
for Peak Roofing in Charlotte NC. Concept clusters, content
vehicle assignments, geogrid tracking keywords, GBP actions."
Skills fired: dispatch → local-content-strategy
CONTENT STRATEGY: Peak Roofing — Charlotte NC
7 concept clusters identified
═══════════════════════════════════════════════════════════════
CLUSTER 1: Roofing Services — Charlotte (Primary)
Primary keyword: "roofing company charlotte nc" | 480/mo | HIGH
Supporting: "roofing contractor charlotte", "charlotte roofing company",
"roofer charlotte nc"
Intent: Transactional — ready to hire
Competition: High
Content vehicle: PRIMARY LOCATION PAGE
URL: /roofing-company-charlotte-nc/
Reasoning: Highest volume transactional concept in the market.
Deserves comprehensive location page treatment — this is the hub
all other pages link to. Must cover: services offered, service area,
credentials, process, differentiators. Target 1,800-2,400 words.
═══════════════════════════════════════════════════════════════
CLUSTER 2: Storm Damage Roofing
Primary keyword: "storm damage roof repair charlotte" | 140/mo | MEDIUM
Supporting: "hail damage roof repair", "wind damage roof charlotte",
"roof damage insurance claim"
Intent: Transactional — urgent, event-driven
Competition: Medium
Content vehicle: LOCATION PAGE + GBP SERVICE
URL: /storm-damage-roof-repair-charlotte/
Reasoning: Distinct concept from general roofing. Significant local
relevance — Charlotte severe weather season runs April through
September. High commercial intent at a specific decision moment.
Requires content covering damage assessment, insurance claims,
emergency tarping, and repair timeline.
Add "Storm Damage Repair" as GBP service immediately.
═══════════════════════════════════════════════════════════════
CLUSTER 3: Roof Cost and Process (Informational)
Primary keyword: "how much does a new roof cost in nc" | 590/mo
Supporting: "roof replacement cost nc", "average roof cost charlotte",
"roofing estimate charlotte"
Intent: Informational — research phase
Competition: Low-Medium
Content vehicle: BLOG POST / FAQ PAGE
URL: /blog/roof-cost-north-carolina/
Reasoning: Informational intent — user is in research phase before
making a service decision. Highest volume keyword in the entire
research output. AI Overview candidate because direct answer format
works well. No location page needed — this is awareness/consideration
content that feeds transactional pages via internal links.
═══════════════════════════════════════════════════════════════
CLUSTER 4: Near-Me Searches
Primary keyword: "roofer near me" | [varies by location]
Supporting: "roofing company near me", "roof repair near me"
Intent: Transactional — proximity-driven
Content vehicle: GBP SIGNAL ONLY — NO PAGE NEEDED
Reasoning: Near-me queries are won through GBP prominence, proximity,
and completeness — not through page content. You cannot rank a page
for "near me" from a user in a different location. These keywords
are served by strong GBP, good reviews, correct business location,
complete service area settings. No content action required.
[continues for all 7 clusters]
═══════════════════════════════════════════════════════════════
GEOGRID TRACKING KEYWORDS (4 selected)
1. "roofing company charlotte nc"
Reasoning: Primary revenue concept. Highest volume transactional
keyword. Ranking improvement here directly increases leads.
2. "storm damage roof repair charlotte"
Reasoning: Seasonal high-value intent. Charlotte storm season
drives urgent searches April-September. SoLV here during
storm season represents significant revenue capture.
3. "roof replacement charlotte nc"
Reasoning: Different job type from repair. Higher ticket,
different customer journey. Tracking separately shows whether
you're capturing major project searches vs. repair searches.
4. "emergency roof repair charlotte"
Reasoning: Urgent intent, high conversion rate. If you offer
24/7 service, this tracks emergency search capture. Geographic
spread matters — emergencies happen across the service area.
═══════════════════════════════════════════════════════════════
GBP ACTIONS (do these today)
Categories:
✓ Roofing Contractor (primary) — already claimed
+ Add: Siding Contractor (if you offer siding)
+ Add: Gutter Cleaning Service (if you offer gutters)
Services to add:
→ Storm Damage Repair
→ Emergency Roof Repair
→ Roof Inspection
→ Roof Replacement
→ Shingle Repair
→ Metal Roofing Installation
→ Gutter Installation
Attributes to confirm:
→ Free estimates (if offered)
→ Identifies as veteran-owned (if applicable)
═══════════════════════════════════════════════════════════════
INTERNAL LINKING ARCHITECTURE
Hub: /roofing-company-charlotte-nc/
← All location pages link here
← All blog posts link here
Spokes:
/storm-damage-roof-repair-charlotte/ → links to hub, emergency page
/emergency-roof-repair-charlotte/ → links to hub, storm damage page
/roof-replacement-charlotte-nc/ → links to hub
Blog → Location Page Links:
/blog/roof-cost-north-carolina/ → links to replacement page
/blog/roof-damage-insurance-claims/ → links to storm damage page
═══════════════════════════════════════════════════════════════
PRODUCTION PRIORITY ORDER
Phase 1 — Today (GBP actions, no content needed):
Add 7 services, confirm attributes. [30 minutes]
Immediate visibility expansion, zero content work.
Phase 2 — First 2 weeks (high-impact content):
Build primary location page (/roofing-company-charlotte-nc/)
Build storm damage page (/storm-damage-roof-repair-charlotte/)
These capture highest-value searches first.
Phase 3 — Weeks 3-6 (supporting content):
Build emergency page, roof replacement page
Build cost blog post (highest informational volume)
Phase 4 — Ongoing:
Insurance blog post, secondary location pages, coverage expansionThat’s the output. Not a keyword list with suggestions. A complete content architecture with every decision made and every action specified.
What This Skill Covers
Concept clustering from any keyword list. Related keywords grouped by shared user intent and topic. Cluster names are concepts, not keyword strings. Each cluster has a primary keyword, supporting keywords, intent classification, and competitive assessment.
Content vehicle assignment with reasoning. Every cluster gets assigned to the right content vehicle — location page, GBP service, blog post, FAQ section, or no action needed. The reasoning explains why, so you understand the logic and can adjust if your situation differs.
Geogrid tracking keyword selection. 3-5 keywords selected from the full concept map, with explicit criteria for each selection. Not the highest-volume keywords — the keywords that best represent your concept coverage and for which geographic ranking variation matters most.
GBP action confirmation. Services to add, categories to claim, attributes to confirm. These actions fall out of the concept map naturally — if a concept exists, the corresponding GBP signal should exist.
Internal linking architecture. Hub and spoke structure connecting all content vehicles. Which pages link to which, with what anchor text, creating a topic cluster that signals authority.
Phased production priority. What to do today (GBP actions). What to build first (highest-impact pages). What to build next. What’s ongoing. A sequenced plan, not a pile of tasks.
Who Uses This and When
After every keyword research session. The local-keyword-research skill produces the raw material. This skill organizes it into a plan. They chain together — run keyword research, paste the output into content strategy, get the architecture.
New client onboarding. When content architecture needs to be established from scratch, this skill produces the complete plan in one session. No spreadsheet organizing, no debating content vehicles, no forgetting to specify GBP actions.
Content audits. When existing pages need to be reorganized against a concept map, paste the current page list along with the keyword research. The skill identifies gaps, duplicates, and misassignments.
Any time you have a keyword list and need to know what to do with it. That’s the trigger. Keywords exist; plan doesn’t. This skill creates the plan.
The Decisions It Makes
The skill makes the organizing decisions that practitioners usually make manually:
Which keywords belong together? Geographic variants of the same term cluster together. Service variants cluster together. A keyword that could belong to two clusters gets assigned to the one where it represents core intent.
What content vehicle serves each cluster? Location pages for transactional local intent with sufficient volume. GBP services for lower-volume service variants. Blog posts for informational intent. No action for near-me queries that GBP handles. The decision logic is explicit.
Which keywords deserve geogrid tracking? One keyword per distinct concept cluster. Transactional intent only. Competitive enough that position matters. Representative of primary revenue services. The selection criteria are stated.
What’s the production sequence? GBP actions first because they’re fast and expand visibility immediately. High-volume transactional pages next. Supporting content after. The sequence optimizes for impact.
These decisions take hours to make manually. The skill makes them in seconds, with reasoning attached to each one.
Cost of Absence
Without this skill, the keyword list becomes a content to-do list where every keyword gets a page.
The result is predictable:
Cannibalization. Multiple thin pages targeting the same concept compete against each other. “Emergency plumber Charlotte” and “24 hour plumber Charlotte” each get a page, and neither ranks because Google doesn’t know which one to show.
Thin content. Pages built for individual keywords rather than complete concepts don’t have enough substance to demonstrate expertise. They rank weakly in traditional search and don’t get retrieved in AI search.
Missing GBP signals. The content plan doesn’t include GBP actions, so services don’t get added, categories don’t get claimed, and query eligibility stays narrow.
No measurement strategy. Without geogrid keyword selection, there’s no plan for what to measure. Rankings get checked ad hoc, or not at all.
No internal linking. Pages get built but not connected. The topic cluster that signals authority doesn’t form.
With this skill, the keyword list becomes a coherent concept map that builds authority systematically. Every keyword has a home. Every cluster has a vehicle. Every piece connects to the whole.
How It Chains
The skill sits in the middle of the content workflow:
local-keyword-research → local-content-strategy → local-content-briefsInput: Keyword list from local-keyword-research, or any keyword list pasted directly. Business context (type, location, services, competitors) improves cluster assignments.
Output: Complete content strategy document. Concept clusters, vehicle assignments, geogrid keywords, GBP actions, linking architecture, production priority.
What comes next: The local-content-briefs skill takes each content vehicle from this output and produces a complete semantic content brief. Run content strategy once; run content briefs for each piece identified.
The skills were designed to chain. The output format of one is the input format of the next.
The First Prompt
After local-keyword-research produces your keyword list:
"Take this keyword research output [paste output] and build the
complete content strategy for [Business Name] in [City].
Concept clusters, content vehicle assignments, geogrid tracking
keywords, GBP actions, and production priority."The organizing work is done. The architecture exists. Now you can brief and build.