# First-Link Weight: What the Evidence Actually Says

This unpacks the common claim that "the first link from a spoke to the hub is what Google weights most heavily," where it comes from, and what's still load-bearing in 2026.

## The claim, stated precisely

"First-link priority" is the rule that when a single page contains multiple links pointing to the same destination URL, Google historically counted only the anchor text of the *first* link it encountered in the HTML. All subsequent anchors to that URL were ignored for ranking the destination page. PageRank still flowed through every link (that part was never in dispute), but the anchor signal collapsed to the first one.

Note what this is *not*: it's not a claim that only the first link passes link equity. It's a narrower claim about *which anchor text Google uses* when the same destination is linked twice from the same source page.

## Primary sources

**Rand Fishkin, 2008.** The test that popularized the rule. Fishkin ran a controlled experiment with two links on the same page pointing to the same URL with different anchors, and observed that the destination page ranked for the first anchor's keyword but not the second. The test was clean enough that the rule entered SEO gospel ([Search Engine Journal summary](https://www.searchenginejournal.com/ranking-factors/first-link-priority/)).

**Matt Cutts, 2014.** Google's then-head of webspam confirmed the mechanism on video but added a time stamp. Cutts said that *as of 2009*, Google "only counted the anchor text from the first link," but cautioned "it may not work that way now." On PageRank he was clearer: "PageRank flows to each link individually as it would any other link on the page, at least according to the original PageRank document" ([Search Engine Land, May 2014](https://searchengineland.com/googles-matt-cutts-one-page-two-links-page-counted-first-link-192718)).

**John Mueller, 2018 and later.** Mueller walked the rule back. He said Google hasn't formally defined first-link priority, and behavior "can change and it's not something they have defined," which means "even if you figure out how Google currently does it, that's not necessarily how they'll do it tomorrow or how it always is across all websites" ([Search Engine Journal](https://www.searchenginejournal.com/ranking-factors/first-link-priority/)).

**Cyrus Shepard / Zyppy, 2023.** The most recent primary source. Shepard set up a Search Console property containing pages with no external links anywhere on the internet, then linked to those pages from a single source with specific anchor texts, and used the Top Linking Text report to see which anchors Google had indexed. His finding: Google doesn't always pick the first link, but it does pick *selectively*, hence "selective link priority" rather than strict "first link priority." Hash-fragment links (`#section`) can sometimes slip past the de-duplication and get counted independently ([Niche Pursuits write-up](https://www.nichepursuits.com/cyrus-shepard-internal-links-study/)).

## What "contextual" means and why it matters

The first-link rule is about *which anchor counts*. A separate and more durable finding is about *where on the page the link sits*. In-body contextual links carry more weight than links in navigation, footers, or sidebars. Not because Google has published a rule, but because split tests keep showing it.

SearchPilot's published internal-linking split tests consistently land in the 5-25% organic-uplift range for contextual additions. Their flagship e-commerce test added button links between category levels and produced a 25% uplift in organic sessions on the affected pages ([SearchPilot case study](https://www.searchpilot.com/resources/case-studies/seo-split-test-lessons-increasing-internal-linking)). A separate SearchPilot footer test produced a much weaker 5% uplift ([SearchPilot footer test](https://www.searchpilot.com/resources/case-studies/adding-internal-links-to-home-page-footer)). Same company, same methodology. The placement was the variable.

The intuition: template links (nav, footer, sidebar) appear identically on every page of a site, so Google discounts them as boilerplate. Contextual links inside the body of a specific article are relevance signals about *this page's topic*, not *this site's structure*.

## The practical rule for cluster planning

When a spoke points to its hub, make sure **the first mention of the hub URL is a contextual in-body link with a descriptive anchor.** Not "learn more," not "click here," not a button in a sitewide footer, not a hub tile at the bottom of a template. An actual sentence in the body text like "the broader picture is covered in our [complete guide to email deliverability](/email-deliverability)."

This matters twice over:
1. If first-link priority still applies in some form, the in-body anchor is the one Google uses for the hub's relevance.
2. Even if it doesn't apply anymore, the in-body placement carries more weight by itself (SearchPilot evidence).

A sitewide footer link to the hub is fine as a secondary signal (it doesn't hurt), but it should never be the *only* link from a spoke to the hub, and it should never appear in the HTML before the body link on the page.

## What if first-link priority is outdated?

Assume it is. The contextual-placement rule still holds. You're not losing anything by putting your best anchor in the body; you *are* losing something by burying the hub link in a template block.

The planning rules stand regardless:
- Descriptive anchor text (not "read more")
- One primary body-text anchor per spoke pointing to the hub
- Placement in the first half of the article
- Don't link the hub URL ten times from a single spoke. Two or three is plenty.

## Cross-reference

The page-audit skill cites SearchPilot's 5-25% uplift range when scoring a page's internal linking dimension. This file uses the same evidence base but applies it one layer up, at the cluster-architecture level rather than the page level.

# Technique 20: Ultimate Guide / Pillar Pages

## What It Is
Comprehensive, long-form content that covers an entire topic in depth and serves as the central hub of a topic cluster. Captures broad head terms and establishes topical authority.

## When to Use
Informational/navigational intent -- user wants a complete overview of a broad topic. Use when building topic clusters. The pillar page links to and from all supporting content (how-tos, definitions, comparisons, FAQs).

## Structure Template

```
H1: "The Complete Guide to [Topic] [Year]"
    (e.g., "Alles over zonnepanelen in 2026: de complete gids")

H2: Table of contents
    Clickable anchor links to all major sections
    Acts as a mini-sitemap for the topic

H2: What is [topic]? (Quick overview)
    2-3 paragraphs establishing context
    Link to dedicated definition article

H2: [Core subtopic 1]
    H3: Key aspect A
    H3: Key aspect B
    Link to dedicated cluster article for deeper detail

H2: [Core subtopic 2]
    H3: Key aspect A
    H3: Key aspect B
    Link to dedicated cluster article

H2: [Core subtopic 3-6]
    Same pattern: overview + link out to cluster content

H2: How to get started / Practical steps
    Actionable summary of the process
    Links to relevant how-to articles

H2: Costs and pricing
    Overview of costs, budget ranges
    Link to dedicated pricing/comparison content

H2: Common mistakes
    Top 5-7 mistakes with brief explanations

H2: FAQ
    5-10 questions covering breadth of the topic
    Each answer 2-4 sentences with link to deeper content

H2: Resources and next steps
    Curated internal links organized by user intent
```

## Word Count
3,000-5,000+ words (comprehensive but not padded -- every section earns its place)

## Schema Markup
- **Primary:** Article (with headline, author, datePublished, dateModified)
- **Secondary:** FAQ (for the FAQ section)

## Featured Snippet Strategy
- **Format:** Paragraph snippet for the overview, list snippets for subtopic sections
- **Target:** The "What is" section for definition snippets, ToC for list snippets
- **Tip:** Each H2 section should have a self-contained opening paragraph that can stand alone as a snippet

## CTA Placement
- After table of contents: free resource, checklist, or tool
- Mid-article (every 800-1,000 words): contextual CTAs matching section topic
- End of article: primary conversion CTA (consultation, trial, comparison tool)
- Sticky sidebar CTA on desktop

## Internal Linking Strategy
- **Hub model:** Link OUT to every cluster article (how-tos, definitions, comparisons, FAQs)
- **Receive links:** Every cluster article links back to this pillar page
- **Cross-pillar:** Link to related pillar pages for adjacent topic clusters
- **Breadcrumb:** Pillar page sits one level below the category/topic page
- **Anchor text variety:** Use descriptive anchor text, not "click here" or "read more"

## Key Success Factors
1. **Table of contents is essential:** Users and Google both need to navigate 3,000+ word pages
2. **Overview, not exhaustive:** Cover each subtopic enough to be useful, then link to the deep-dive
3. **Regular updates:** Pillar pages must be updated at least quarterly to maintain rankings
4. **Strong internal linking:** Every section links to at least one cluster article
5. **Visual breaks:** Use images, tables, callout boxes, and diagrams every 300-500 words
6. **Scannable structure:** Users jump between sections -- each H2 must work independently
7. **E-E-A-T signals:** Author byline, publication date, update date, methodology notes

## Common Mistakes
- Writing 5,000 words of shallow content instead of 3,000 words of substantive content
- Not linking to cluster articles (defeats the purpose of a pillar page)
- No table of contents (readers bounce from long pages without navigation)
- Treating it as a one-time publish (pillar pages need regular updates)
- Duplicating cluster content instead of summarizing and linking
- Missing the FAQ section (loses long-tail keyword coverage)
- No visual elements (wall-of-text pillar pages have high bounce rates)

## Anti-AI Focus
Pillar pages are less commonly AI-generated wholesale due to their length and complexity, but individual sections can still read as generic. To ensure authenticity:

- **Inject editorial perspective throughout.** Each section overview should reflect a point of view or prioritization that comes from real expertise, not just neutral summarization.
- **Reference your own cluster content by name.** Linking to your specific articles (with context about what readers will find there) creates a web of evidence that a single AI prompt cannot produce.
- **Include market-specific data and timelines.** Reference current Dutch pricing, regulation changes, or market conditions with specific dates and figures.
- **Add "what we have seen" observations.** Brief editorial notes about trends, common misconceptions, or shifts you have noticed in your industry ground the content in lived experience.
- **Update visibly.** Show a changelog or "last updated" note with specific details about what changed and why. AI-generated content is typically published once and never revisited.

## Example Topics by Niche
- Energy: "Alles over zonnepanelen: kosten, subsidie, terugverdientijd en installatie"
- Telecom: "Internet in Nederland: alles over providers, snelheden en abonnementen"
- SaaS: "The complete guide to marketing automation in 2026"
- E-commerce: "Webshop starten: de complete gids van idee tot eerste verkoop"
- Local services: "Verbouwen in Nederland: vergunningen, kosten, aannemers en subsidies"

# Publishing Sequence: When to Break the Spokes-First Rule

The SKILL.md default: publish 3-4 spokes first, then the hub, then the rest. This file covers the edge cases where that default is wrong.

## Why the default exists

If you publish an empty hub, it launches as a link-less orphan. It has nothing to link out to, and nothing linking back to it, so it accumulates no internal link equity. Publishing a handful of spokes first gives the hub something to reference on day one and gives you internal anchors pointing at it the moment it goes live.

That's the theory. In practice there are five situations where it doesn't hold.

## When to deviate

### 1. Brand-new domain with zero content

A site with no pages doesn't have the crawl budget to get 3-4 spokes indexed before the hub lands. You'll spend a month publishing spokes that aren't even in the index yet.

**Do this instead:** publish 1-2 spokes to establish the domain, then the hub, then scale. The point isn't to have mature spokes before the hub; it's to have *any* indexed content the hub can link to.

### 2. Site with existing content in the space

If the site already has 5-10 articles loosely in the topic area, don't treat this as a blank-slate cluster. Audit first. One of those articles may already function as a hub (broad intent, high traffic, ranks for the seed keyword), in which case you're *upgrading* the existing page and producing net-new spokes around it. Or an existing article may already function as a high-quality spoke, becoming row 1 of your spoke list so you skip writing that one.

**Do this instead:** audit existing URLs against the planned cluster before producing any new content. Publishing a fresh hub that competes with your own existing page is cannibalization.

### 3. Authoritative site with high crawl budget

On a site where Google crawls new URLs within hours (large publishers, established e-commerce, SaaS sites with strong domain signals), the multi-month drip doesn't serve a technical purpose. The whole point of sequencing is to give Google time to see the links form. If Googlebot is pulling new URLs within the same day, that's not a constraint.

**Do this instead:** publish the hub and the first batch of spokes in rapid succession, ideally within a single week, with the hub going live last or simultaneously. You still want the hub to launch with links pointing at it, but you don't need a month of delay to get there.

### 4. Time-sensitive topic

If the topic has a shelf life (a new product launch, a regulation change, a news cycle, a seasonal spike), publication speed beats architectural purity. A suboptimal cluster shipped in time to catch the search surge beats a perfect cluster shipped three weeks after the wave passed.

**Do this instead:** publish whatever you have ready first, hub or spoke, and fill in the rest as fast as you can. The cluster can be assembled retroactively. The search opportunity can't be.

### 5. Resource-constrained team

A solo operator or two-person team can't write 3-4 spokes in a month and still ship the hub in month 2. If you try to enforce the sequence on a team that doesn't have the throughput, you'll publish nothing for a quarter.

**Do this instead:** figure out which single piece has the biggest expected traffic (hub or spoke, doesn't matter) and ship that first. Ship the next one when it's ready. The cluster forms over time. Shipping nothing is worse than shipping out of order.

## Decision tree

Work through these in order. Stop at the first "yes."

1. **Does the topic have a hard deadline in the next 6 weeks?** → Ship fastest-ready piece first, ignore sequencing.
2. **Does the site already have a page ranking top-20 for the seed keyword?** → That's your hub. Don't publish a new one. Audit and upgrade, then publish net-new spokes around it.
3. **Can the team realistically ship 2+ pieces per month?** → No: ship highest-expected-traffic piece first, one per month. Yes: continue.
4. **Is the domain brand new (under ~50 indexed pages)?** → Ship 1-2 spokes, then the hub, then scale.
5. **Is the site well-indexed and crawled within hours of publication?** → Ship hub and first-batch spokes together in one week.
6. **None of the above?** → Default: 3-4 spokes in month 1, hub in month 2, remaining spokes months 3-4.

## Timeline expectations

For the default sequence on a mid-authority site:

- **Month 1-2:** First 3-4 spokes published. Indexation within days. Early rankings (positions 40-80) on long-tail queries.
- **Month 2-3:** Hub published, linked to the spokes. Hub shows up in the index within a week, ranks around 50-100 initially.
- **Month 3-6:** Remaining spokes published, each linking back to the hub. Hub climbs as it accumulates internal anchors. First spokes may reach top-20.
- **Month 6-12:** Cluster matures. Hub lands in top-20 on the seed keyword if competition allows. Topical authority shows up as the whole cluster lifting together, not just the hub.

These numbers assume a normal-authority domain. New domains are slower, established domains faster.

## Cross-reference

The general theory of hub-and-spoke clustering lives in [topic-cluster-strategy.md](./topic-cluster-strategy.md). That file explains *why* clusters work. This file is the operational decision layer: given that you've chosen to build a cluster, which order do you ship the pieces?

# Spoke Selection: A Worked Example

Going from a raw SERP scrape to a finished spoke list. SKILL.md tells you *what* to do. This shows *how* it looks when you do it.

## Seed topic

**Email marketing for SaaS.** Moderate difficulty, rich PAA, strong commercial intent. The seed SERP is dominated by long-form guides from Customer.io, Encharge, HubSpot, and a couple of marketing blogs.

## Step 1: Raw SERP scrape

Pull everything Google offers: PAA, Related Searches, "People also search for," and the H2s of the top 5 ranking guides. Don't filter yet, just capture.

Raw question list:

1. What is email marketing for SaaS?
2. How is SaaS email marketing different from e-commerce email?
3. Best email marketing tools for SaaS companies?
4. What email sequences should a SaaS company send?
5. What is a SaaS onboarding email sequence?
6. How do you write a welcome email for SaaS?
7. What is a trial conversion email?
8. How do you reduce churn with email?
9. What is a win-back email campaign?
10. What KPIs should SaaS email marketers track?
11. How often should a SaaS company email its users?
12. What is product-led email marketing?
13. Should SaaS companies use newsletters?
14. What is a lifecycle email campaign?
15. How do you segment a SaaS email list?
16. What are transactional emails in SaaS?
17. How do you avoid the spam folder for SaaS emails?
18. What is the average open rate for SaaS emails?

That's 18 raw queries. The goal is 8-10 non-overlapping spokes. Overlap is the enemy: two spokes that both answer "how do I write good onboarding emails" will cannibalize each other.

## Step 2: Cluster by semantic overlap

Group questions that belong to the same answer. If two questions share the same underlying intent and would be answered by the same article, fold them.

**Cluster A: Foundational / definition**
- 1 (What is email marketing for SaaS?)
- 2 (SaaS vs e-commerce email)
- 12 (Product-led email marketing)

These answer "what is this and how is it different?" They belong in the hub's intro, not in a spoke.

**Cluster B: Lifecycle and sequences**
- 4 (What sequences should SaaS send?)
- 5 (Onboarding sequence)
- 6 (Welcome email)
- 14 (Lifecycle email campaign)

4 and 14 both map the lifecycle. 5 and 6 are the first touches. Fold into two spokes: the full lifecycle map, and onboarding specifically.

**Cluster C: Conversion / revenue**
- 7 (Trial conversion email)
- 8 (Reduce churn with email)
- 9 (Win-back campaign)

Three distinct lifecycle moments, each large enough for its own spoke. If resource-constrained, 8 and 9 could fold into one "retention and win-back" piece.

**Cluster D: Operations and deliverability**
- 10 (KPIs to track)
- 11 (Send frequency)
- 17 (Avoiding spam folder)
- 18 (Average open rate)

10 and 18 overlap (both metrics). 17 is deliverability. 11 is cadence. Three spokes at most.

**Cluster E: Tools and stack**
- 3 (Best tools)
- 16 (Transactional email in SaaS)

3 is a commercial-intent comparison and becomes a spoke. 16 is technical and mostly answered on product docs, so it becomes an FAQ on the deliverability spoke.

**Cluster F: Segmentation and list management**
- 13 (Newsletters for SaaS?)
- 15 (How to segment a SaaS list)

15 is a standalone spoke. 13 is an opinion piece; fold it into the lifecycle spoke as a section.

## Step 3: Prioritize by difficulty and traffic potential

For each candidate spoke:

- **Difficulty:** who ranks top 10? All DR 80+ domains means 6-12 months to crack the top 20. A DR 40-60 spread is more achievable.
- **Traffic potential:** primary keyword volume plus the related long-tail terms riding along.

Rank highest-value first:

1. SaaS onboarding email sequence (high intent, mid difficulty)
2. SaaS email marketing tools comparison (high intent, high difficulty)
3. Trial-to-paid conversion email sequence (high intent, mid difficulty)
4. Reducing SaaS churn with email (high intent, mid difficulty)
5. SaaS email KPIs and benchmarks (moderate intent, low difficulty, evergreen)
6. SaaS customer lifecycle email map (moderate intent, high topical value)
7. Email list segmentation for SaaS (moderate intent, low-mid difficulty)
8. SaaS email deliverability guide (technical, mid difficulty, long shelf life)
9. Win-back email campaigns for SaaS (lower volume, low difficulty)
10. SaaS email send frequency and cadence (low volume, easy ranks)

That's 10 spokes. Good number.

## Step 4: Hub vs spoke classification

Not all of the 18 raw questions become articles. Some are too broad (those belong in the hub). Some are too narrow (those become FAQs inside an existing spoke).

**Hub-level** (broad, foundational, lives inside the hub):
- 1, 2, 12: the "what is SaaS email marketing and how is it different" questions

**Spoke-level** (specific, standalone article):
- The 10 listed above

**FAQ-level** (too narrow for its own article, folds into a parent):
- 13 (newsletters) → into the lifecycle spoke
- 16 (transactional email) → FAQ inside deliverability spoke
- 18 (average open rates) → subsection of the KPIs spoke

## Step 5: Final spoke map

| # | Spoke Topic | Target Keyword | Content Type | Words | Answers Question |
|---|---|---|---|---|---|
| 1 | SaaS Onboarding Email Sequence | saas onboarding email sequence | How-to + template | 2,500 | #5, #6 |
| 2 | Best Email Marketing Tools for SaaS | email marketing tools for saas | Comparison | 3,500 | #3 |
| 3 | Trial-to-Paid Conversion Emails | trial conversion email | How-to + examples | 2,000 | #7 |
| 4 | Reducing SaaS Churn With Email | reduce saas churn with email | Strategy guide | 2,500 | #8 |
| 5 | SaaS Email KPIs and Benchmarks | saas email marketing kpis | Listicle + data | 2,000 | #10, #18 |
| 6 | SaaS Customer Lifecycle Email Map | saas lifecycle emails | Framework article | 3,000 | #4, #14, #13 |
| 7 | Segmenting a SaaS Email List | saas email segmentation | How-to | 1,800 | #15 |
| 8 | SaaS Email Deliverability Guide | saas email deliverability | Technical guide | 2,800 | #17, #16 |
| 9 | Win-Back Email Campaigns for SaaS | saas win-back email | How-to + examples | 1,800 | #9 |
| 10 | How Often Should SaaS Companies Email Users | saas email frequency | Short opinion + data | 1,200 | #11 |

Total cluster: 1 hub + 10 spokes, roughly 23,000 words of new content.

## Step 6: Internal link graph

Every spoke links back to the hub. Beyond that, only link between spokes when the connection is *natural*. Don't force cross-links.

```
HUB: Complete Guide to SaaS Email Marketing
  |
  +-- 1. Onboarding Sequence --> 2, 6
  +-- 2. Tools Comparison --> 1, 8
  +-- 3. Trial Conversion --> 1, 6
  +-- 4. Reducing Churn --> 6, 9
  +-- 5. KPIs and Benchmarks --> 8
  +-- 6. Lifecycle Map --> 1, 3, 4, 9
  +-- 7. List Segmentation --> 6
  +-- 8. Deliverability --> 5, 2
  +-- 9. Win-Back --> 4, 6
  +-- 10. Email Frequency --> 5
```

Spoke 6 (the lifecycle map) is the center of the graph: most spokes link to it naturally. That's a sign 6 is doing real work as a connective piece. If no spoke naturally links to another, the cluster is probably too fragmented: you're building ten unrelated articles, not a cluster.

## Rejected questions: what to do with them

Some of the 18 didn't make the spoke list. They still have value:

- **Fold as FAQ sections:** "Do I need a newsletter?" works well as an H2 Q-and-A inside spoke 6. Captures long-tail impressions without diluting the main content.
- **Hold for future expansion:** some questions are worth a spoke later, once the cluster has proven it can rank. "Email marketing for PLG vs sales-led SaaS" is a legitimate spoke 11 once the core 10 are live.
- **Drop entirely:** questions too narrow to sustain an article, or already well-covered by an obvious primary source. Don't force a spoke for the sake of the number.

## Cross-reference

Once you've got a spoke list like this, feed any single row into the `content-brief` skill with the target keyword. That produces a writer-ready brief for that specific spoke. Spoke selection happens once per cluster; content-brief happens once per article.

# Technique 11: Topic Cluster & Topical Authority Strategy

## What It Is
Organizing content into interconnected clusters (pillar + spoke pages) to build topical authority -- demonstrating to Google that your site comprehensively covers a subject area, not just individual keywords.

## Why It Works
Google's December 2025 Core Update and the API leak both confirm: Google evaluates topical coverage at the SITE level, not just the PAGE level. A site with 30 interconnected articles on "email marketing" outranks a site with one excellent email marketing article, even if that single article is individually superior.

The mechanism is entity-based: Google builds a topical graph of your site. Deep, interconnected coverage strengthens the entity signals, making each individual page more authoritative.

**Evidence from the field:** Sites that built topic clusters around their core service area saw 50-200% organic traffic increases within 6 months (First Page Sage, 2025 study). Sites that published random unrelated blog posts saw minimal impact regardless of individual article quality.

## Step-by-Step Process

### Step 1: Cluster Identification
1. Use keyword cluster data from to identify natural topic groupings
2. Select 3-5 core clusters aligned with the business's expertise
3. Each cluster should have a clear pillar topic and 8-15 spoke topics
4. Map the cluster hierarchy:
   ```
   PILLAR: "Email Marketing Strategy"
   |-- SPOKE: "Email Subject Line Best Practices"
   |-- SPOKE: "Email Automation Workflows"
   |-- SPOKE: "Email List Building Techniques"
   |-- SPOKE: "Email Analytics and KPIs"
   |-- SPOKE: "Email Deliverability Guide"
   |-- SPOKE: "Transactional Email Best Practices"
   |-- SPOKE: "Email Personalization Strategies"
   |-- SPOKE: "B2B vs B2C Email Marketing"
   +-- SPOKE: "Email Marketing Tools Comparison"
   ```

### Step 2: Content Gap Analysis
5. For each spoke topic, check if existing content already covers it
6. Use opportunity detection to find keywords you rank 4-20 for (existing pages that need strengthening)
7. Identify missing spokes -- topics where you have NO content
8. Prioritize: highest search volume + strongest business relevance first

### Step 3: Internal Linking Architecture
9. Every spoke links TO the pillar page (authority flows up)
10. The pillar page links TO every spoke (distributes authority down)
11. Related spokes link to each other (lateral authority flow)
12. Use descriptive anchor text that includes the target keyword of the destination page
13. Avoid orphan pages (content with zero internal links)

### Step 4: Content Creation Order
14. Write the pillar page FIRST -- comprehensive overview (3,000-7,000 words)
15. Then write spokes in order of priority (search volume x business value)
16. Update the pillar page each time a new spoke is published
17. This order ensures the pillar page exists for internal linking from day 1

### Step 5: Cluster Maintenance
18. Monthly: Review spoke performance, update underperforming content
19. Quarterly: Add new spokes based on emerging subtopics and search trends
20. Annually: Evaluate whether the cluster is comprehensive vs competitors
21. Never let content go stale -- update dates and data regularly

## Tips

- **The "semantic gap" technique**: Use your SEO data source's keyword cluster data to find keywords in your cluster that you DON'T rank for at all. These are gaps in your topical coverage -- filling them strengthens the entire cluster.
- **Competitor cluster analysis**: Check what topics your top competitor covers that you don't. Use competitor data + SERP analysis to map their cluster structure.
- **Don't spread thin**: 3 deep clusters beat 10 shallow ones. Google rewards depth within a topic over breadth across topics.
- **Cross-cluster linking is weaker**: Internal links within a cluster transfer more topical relevance than links between unrelated clusters.

## Common Mistakes

1. **Publishing spokes without a pillar**: Individual articles without a hub page don't form a cluster in Google's eyes
2. **Pillar pages too thin**: A pillar page that's just a list of links isn't a pillar -- it's an index. Pillar pages need substantial content covering the entire topic at overview level
3. **Ignoring internal linking**: The cluster only works if the pages are interconnected. Publishing 15 articles without linking them is 15 individual pages, not a cluster
4. **Off-topic content**: Publishing content outside your core clusters dilutes topical authority. A B2B SaaS blog posting recipes "for engagement" hurts topical signals

## Tools Used
- keyword cluster data -- identify natural topic groupings
- opportunity detection -- find existing pages to strengthen
- internal link data -- audit current linking structure
- keyword search -- prioritize spokes by search volume
- competitor data -- map competitor cluster coverage