Claude Topic Clusters with Constitutional Alignment

Build Claude topic clusters where every page answers a distinct reader need, checked against search data and free of near-duplicate pages.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

A topic cluster links one broad pillar page to a set of narrower pages on related subtopics. HubSpot's explanation of topic clusters describes the model: the pillar covers the subject at a high level, each cluster page goes deep on one subtopic or question, and internal links connect the cluster pages back to the pillar. Claude topic clusters use Claude to do the heavy thinking in planning one: breaking a subject into the questions real readers have, spotting overlap, and proposing a linking structure.

The "constitutional alignment" part of this skill is about using Claude's intended behavior to keep the plan honest. Anthropic's constitution asks Claude to attend to a person's final goals, the deeper purpose behind a request, and to be forthright about information they would want. When your prompt says the goal is a set of pages that each help a distinct reader, Claude can point out subtopics that are the same question in different words, or pages that would exist only to catch a keyword variant. Those are exactly the pages that weaken a cluster.

The risk being avoided is well defined. Google's spam policies describe doorway abuse, which includes "Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy," and scaled content abuse, which covers generating many pages without adding value for users. A cluster plan that spins every keyword variant into its own page drifts toward both. A plan in which each page answers a different question is what the cluster model is meant to be.

Claude cannot see search demand or current rankings on its own, so this skill pairs its reasoning with your data from Search Console or a keyword tool. Claude proposes and critiques the structure; the data confirms that people actually search for each piece. For background on the constitution, see the parent method.

How It Works

The workflow has four passes. In the first, Claude breaks the pillar topic into the questions and tasks readers bring to it, framed by audience and situation. In the second, it merges candidates that share an intent and flags any that could not support a useful page on their own. In the third, you check the survivors against search data. In the fourth, Claude proposes the internal linking and a short brief for each page.

The prompt for the first pass should describe the reader and your expertise in detail. Google's SEO Starter Guide notes that people who know a topic well search with different words than newcomers do, so name who you are writing for. Tell Claude what your site can speak to with authority, since Google's helpful content guidance warns against entering topic areas without real expertise just to attract search traffic.

The second pass is where Claude's forthright behavior pays off. Ask it directly: which of these candidates would a reader consider the same question? Which could not fill a useful page without padding? Which belong on the pillar page as a section instead of on a page of their own? The constitution's list of good helpfulness habits includes considering what could be added or removed from a response to make it better, and the same habit applied to a site plan removes weak pages before they are written.

In the third pass you replace Claude's judgment about demand with evidence. Look up each surviving subtopic in Search Console or a keyword tool, and check the current results to see what kind of page ranks. Ahrefs' guide to long-tail keywords recommends analyzing the top-ranking pages to decide whether a query is a distinct topic or part of a broader one, which is the same decision you are making for each cluster page.

The fourth pass produces the links and briefs. Each cluster page links to the pillar, the pillar links to each cluster page, and cluster pages link to each other where a reader would naturally want to go next. Google's starter guide asks for descriptive link text that tells users what the linked page contains, so have Claude propose anchor text that reads naturally in a sentence.

Step-by-Step Guide

Step 1: Define the pillar, the reader and your expertise

Write down the pillar topic, the primary reader, what they already know and what they are trying to achieve. Add a short statement of what your team knows first-hand about the topic. This gives Claude the context to generate subtopics your site can actually support. Leave out subtopics you have no standing to write about, however tempting their search demand.

Step 2: Generate candidate subtopics as reader questions

Ask Claude for the questions, tasks and decisions this reader brings to the pillar topic, grouped by stage or situation. Ask it to phrase each in the reader's own words. Request more candidates than you need, since the next step removes many. Ask Claude to mark any candidate it thinks is speculative or depends on facts it cannot confirm.

Step 3: Merge by intent and cut padding

Ask Claude to merge candidates that a reader would consider the same question and to explain each merge. Then ask which remaining candidates could not support a useful standalone page and should become sections of the pillar or of another page. Review its reasoning and overrule it where you know the audience better. The result should be a list where every page has a distinct job.

Step 4: Check demand and competition with real data

For each surviving subtopic, look up queries in Search Console's Performance report or a keyword tool, and look at the current results. Drop subtopics nobody searches for unless they serve readers already on your site. Where the results show a different kind of page than you planned, such as tools instead of articles, adjust the plan. Record the data next to each page so later reviewers can see why it exists.

Step 5: Design the internal links

Give Claude the final page list and ask for a linking plan: pillar to every cluster page, every cluster page to the pillar, and cross-links only where a reader would naturally continue. Ask for anchor text that describes the destination and fits in a sentence. Check the plan for pages with no inbound links from within the cluster. Keep the structure browseable for a human reader.

Step 6: Write a brief for each page

Ask Claude to draft a brief for each page: the reader question, what a complete answer includes, what sources or first-hand material it needs, and what it should leave to other pages in the cluster. The last item prevents overlap during writing. Have the writer or subject expert review the brief before drafting. Briefs that list evidence the team does not have signal a page that is not ready.

Step 7: Review the whole cluster before publishing

Once drafts exist, ask Claude to compare the pages side by side and report any that answer the same question or repeat large sections of each other. Check the result against Google's warning signs of search engine-first content, such as producing lots of content in hopes some of it performs. Merge or cut what fails. Then publish and watch the cluster's queries in Search Console.

Best Practices

• Frame every candidate as a reader question. Questions make overlap obvious in a way keyword lists do not, and they translate directly into page briefs.
• Ask Claude to argue against pages as well as for them. A direct question such as "which of these would you merge and why" draws out the forthright behavior the constitution describes.
• Let data decide demand. Claude's judgment about what people search for is a hypothesis until Search Console or a keyword tool confirms it.
• Keep the cluster within your expertise. Google's helpful content guidance treats entering topics without expertise, mainly for traffic, as a warning sign.
• Write anchor text for readers. Descriptive link text helps users and search engines understand the destination, as Google's SEO Starter Guide explains.
• Record why each page exists. A line of evidence per page makes later pruning decisions faster and less political.

Common Mistakes

• One page per keyword variant: Splitting close variants into separate pages produces near-duplicates that compete with each other and resemble what Google's spam policies call doorway abuse. Merge variants into one page that answers the shared question well.
• Trusting Claude's guesses about demand: Claude can reason about what readers need but cannot see search volumes. Check every page against real data before committing writing time.
• Building the cluster around topics you cannot speak to: Pages outside your expertise tend to summarize others and add little. Keep them out, or bring in someone with real experience.
• Linking everything to everything: Dense cross-linking makes the structure harder for readers to follow. Link where a reader would naturally go next and keep the pillar as the hub.
• Skipping the side-by-side review: Overlap often appears only once pages are written. Compare drafts before publishing and merge where two pages converge.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Claude's Constitution

Related Skills

• Claude AI Long Tail Keywords by User Need
• Automate SEO with Claude: Reasoning Principles
• Claude Content Optimizer: Evaluate Against the Constitution

Sources

• HubSpot: Topic clusters, the next evolution of SEO
• Anthropic: Claude's Constitution
• Google Search Central: Spam policies
• Google Search Central: SEO Starter Guide
• Google Search Central: Creating helpful, reliable, people-first content
• Ahrefs: Long-tail keywords
• Search Console Help: Performance report

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.