Topical Gaps

Topical Gap Analysis — Phase 7

Executive Summary

Topical authority is the #1 long-term competitive moat in local SEO. Google's Helpful Content System (integrated into core algorithm March 2024) rewards businesses that comprehensively cover a topic cluster vs. those that superficially mention many topics. The 25-article threshold signal: sites with 25+ articles in a cluster receive significantly stronger topical authority signals than sites with 10 or fewer (SEMrush 2024). AI Overviews (AIO) cite topically authoritative sources 2–3× more than shallow coverage sites. This phase maps the client's topical universe, identifies coverage gaps vs. top competitors, and produces a prioritized content roadmap.

2025–2026 topical authority benchmarks:

• Pillar pages: minimum 3,000 words; competitive 5,000–10,000 words for high-competition topics
• Cluster pages: minimum 1,500 words; competitive 2,000–2,500 words; Surfer Score ≥70
• Supporting/spoke pages: 800–1,500 words; 3–5 internal links per 1,000 words
• Minimum viable cluster: 1 pillar + 5 cluster pages (starting point); 10–15 = AIO eligibility threshold
• Authority threshold: 25+ articles per cluster = topical authority signal begins accumulating (SEMrush 2024)
• Content decay trigger: >20% YoY click decline → refresh required; >50% → full rewrite or consolidate
• AIO topical citation: 58% AIO surge for businesses with full topic cluster coverage (Amsive early 2026)
• ChatGPT freshness factor: pages updated within 30 days cited at 76.4% rate; AI Overviews prefer content ` internal link from every cluster page to its parent pillar. Also add cluster link from pillar. Effort: 30 min each. Priority: 20 (4×5). Expected: direct PageRank flow improvement.

1. Create/upgrade pillar pages to 3,000+ words — For top 2 service clusters with missing or thin pillars: build comprehensive pillar pages using Surfer SEO (target score ≥80) + Clearscope (target A-). Include: all subtopics, 5+ FAQs, HowTo schema, unique local data/statistics. Effort: 8–12 hrs each.
2. Fill "red" cluster gaps — Clusters where ALL competitors have pages but client doesn't: create 1,500+ word cluster pages, link to pillar immediately after publish. Effort: 3–5 hrs each.
3. Answer top 10 PAA questions — Use AlsoAsked.com for each pillar topic → extract top 10 PAA questions → add as FAQ entries on relevant service pages + FAQPage schema. Effort: 1–2 hrs. Expected: AIO citation + PAA box wins.
4. Add FAQPage schema to ALL cluster pages — AIO cites pages with FAQPage at 3.2× rate. Add 5 FAQ minimum per page. Effort: 30 min/page. Priority: 20.

Numbered Action Steps (Comprehensive)

| Step | Action | Effort | Priority | Expected Impact | |------|--------|--------|---------|----------------| | 1 | Fix orphaned cluster links (pillar ↔ cluster) | 30 min/page | 20 | PageRank distribution | | 2 | Expand thin pillar to 3,000+ words + Surfer ≥80 | 8–12 hrs each | 15 | Rankings lift + AIO | | 3 | Create missing cluster pages (red gaps) | 3–5 hrs each | 16 | New keyword rankings | | 4 | Add PAA-based FAQ content + FAQPage schema | 1–2 hrs | 15 | AIO + PAA boxes | | 5 | Refresh content decay pages (>20% YoY) | 2–4 hrs each | 16 | Traffic recovery | | 6 | Build original data/statistics page per pillar | 8–16 hrs | 12 | AI citation priority | | 7 | Create location × service intersection pages | 2–4 hrs each | 12 | Local long-tail rankings | | 8 | Monitor Google Trends weekly for emerging topics | 30 min/week | 10 | First-mover advantage |

Medium-Term (Days 31–90)

1. Build out secondary clusters topic-by-topic using Ahrefs Content Gap data
2. Create supporting topic content for each established cluster
3. Publish FAQ hub pages for each pillar with schema markup (FAQPage + HowTo)
4. Build original data/statistics pages — survey customers, create localized studies

Long-Term (Months 3–6)

1. Complete coverage of all topic pillars to topical authority status
2. Build seasonal sub-clusters (holiday, weather-related, emergency services)
3. Create emerging topic content before competitors (monitor Google Trends + AlsoAsked weekly)
4. Commission original research/case studies per pillar — primary data = AI citation priority

---

Deliverable: Complete Topical Map

TOPICAL AUTHORITY MAP — [Business Name]
Generated: [Date]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

PILLAR 1: [Main Service/Topic]
├── CLUSTER: [Subtopic]
│   ├── ✅ [Existing page URL] — [title]
│   ├── ❌ MISSING: [page idea] — Priority: High | Est. Traffic: [X/mo]
│   └── ⚠️ THIN: [existing URL] — needs expansion
├── CLUSTER: [Subtopic]
│   └── [...]
Overall Status: [X]% complete
Gap vs. Leader: [X] pages needed to match [competitor]

PILLAR 2: [Main Service/Topic]
[...]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TOPICAL COVERAGE SCORE: [X]%
Pages needed to reach 80% coverage: [X] pages
Estimated time to topical authority: [X months]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

---

Output

Write complete topical map and gap analysis to {AUDIT_DIR}/topical-gaps.md with YAML frontmatter. Write HTML report to {REPORTS_DIR}/phase-7-topical-gaps.html and convert to PDF via python3 scripts/generate_pdf.py.

---
skill: research/topical-gaps
phase: 7
date: [YYYY-MM-DD]
business: [Business Name]
url: [URL]
score: [X/100]
status: complete
topical_coverage_pct: [X%]
pillars_mapped: [X]
gaps_identified: [X]
---

Key consumers:

• strategy/topical-authority — uses map for authority building strategy
• research/keyword-gaps — maps keyword data onto topical gaps
• output/report-generation — topical coverage % in master report section 7

---

Topical Gap Quick Reference

Cluster Completeness Scoring Table

| Cluster Status | Page Count | Pillar? | Cluster Pages? | AIO Eligible? | Action | |---------------|-----------|---------|---------------|--------------|--------| | Not started | 0 | No | No | No | Build pillar + 5 cluster pages first | | Minimal | 1–4 | Maybe | 1–3 | No | Expand to 10+ pages, add FAQPage schema | | Building | 5–14 | Yes | 4–13 | Maybe | Fill cluster gaps, fix orphaned pages | | AIO threshold | 15–24 | Yes | 14–23 | Yes | Add supporting pages, original data | | Authority | 25+ | Yes | 20+ | Yes (priority) | Maintain freshness, earn editorial links |

Content Decay Detection Table (INP + Freshness)

| Signal in GSC | Interpretation | Action | Effort | |--------------|----------------|--------|--------| | Impressions ↓ >20% YoY, position stable | Topical coverage weakening | Add depth, update stats, expand subtopics | 2–4 hrs/page | | Impressions ↓ >50% YoY | Severe authority loss | Full rewrite or consolidate + 301 | 4–8 hrs/page | | CTR ↓, impressions stable | Title/meta mismatch with search intent | Rewrite title + meta; check SERP features | 30 min/page | | Position slipping from P1→P3 | Competitor added stronger content | Expand word count, add original data, add FAQPage | 3–6 hrs/page | | Zero impressions on new page | Indexation or orphan issue | Check GSC URL Inspection; add internal links | 30 min |

E-E-A-T Signals by Content Tier

| Tier | Page Type | Required E-E-A-T Signal | How to Add | |------|-----------|------------------------|-----------| | Tier 1 | Pillar page | Expert author byline + original data/research | Add author schema + local case study/survey | | Tier 2 | Cluster page | Specific expertise signals + cited sources | Link to government/trade association sources | | Tier 3 | Supporting/FAQ | Real-world examples or testimonials | Add quote from client or specific local context | | All tiers | Any content | Updated within 90 days | Update stats, add current-year examples |

GBP + Topical Authority Connection (2025)

GBP Q&A is an underused topical authority signal. Seed GBP Q&A with questions matching your cluster topics — Google pulls GBP Q&A content into AI Overviews for local service queries. Each seeded Q&A pair that appears in AIO = measurable topical authority signal for that cluster.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: mshahiddigital
• Source: mshahiddigital/agentic-local-seo-audit
• License: MIT

Install and usage instructions live in the source repository linked above.