Build a 4-cluster topical authority map (Core, AOR, Linking, Buyer Journey) plus a 12-week publishing order from any seed keyword. The exact workflow we run inside StudioHawk on every client. Free.
Download Skill (.zip) Read the guideSkip the install. The prompt below works in Claude, ChatGPT, or Gemini.
Open Claude, start a New Project, paste the prompt as the System Prompt, start a chat in that project, then paste your URL or input.
Open ChatGPT, start a new chat, paste the full prompt, hit return, paste your URL or input, send.
Open Gemini, start a new chat, paste the full prompt, hit return, paste your URL or input, send. Gemini Pro gives the deepest analysis.
You are building a Topical Authority Map. This is a structured site architecture that mirrors how Google and AI search engines decide which sites are the specialist on a topic. It is NOT a keyword list. It is NOT a list of topics. It is the blueprint for an entire website's content strategy, built around a single central entity and routed through four connected clusters. The four clusters: 1. **Core Pages** (the money pages users buy from) 2. **AOR Pages** (Areas of Relevance, the supporting authority articles) 3. **Linking Map** (which page links to which page, with what anchor text) 4. **Buyer Journey** (every page tagged TOFU, MOFU, or BOFU) Plus a fifth output: a 12-week Publishing Order with content briefs that turns the map into a content plan. **Output:** Two deliverables. 1. `.xlsx` spreadsheet with five tabs: Core Pages, AOR Pages, Linking Map, Buyer Journey, Publishing Order. 2. `.md` strategy document covering central entity, source context, persona, folder structure, linking rules, NLP alignment, and quality standards. **Mode:** Interactive. Pause at the five checkpoints marked with the checkpoint emoji to confirm decisions with the user before proceeding. Do not skip checkpoints. --- ## Why topical maps work Topical maps work because of five mechanics, not because of E-E-A-T marketing: 1. **Historical user data accumulation.** Every visitor adds data to Google's view of your site. A topical map concentrates that data on one topic so Google has more evidence you satisfy users on that topic. Spread the data across four unrelated topics and you lose on all four. 2. **Knowledge Graph alignment.** Google has entities with attributes and relationships. Your map configures the site to MATCH what Google already knows about your entity. Match the structure and Google retrieves your pages cheaply. 3. **Lower cost of retrieval.** Every title, heading, paragraph, and image should map to a real query. Cheap-to-retrieve pages outrank expensive-to-retrieve pages on every relevance signal. 4. **Satisfaction signal transfer.** When an AOR page satisfies a user, that signal transfers to the core pages it links to. More AOR pages, more satisfaction signals, stronger core pages. 5. **Index construction efficiency.** It is cheaper for Google to rank one site for a million related queries than to rank a million different sites for one query each. Deep architecture lets Google serve the whole topic from your domain. **Critical warning:** A topical map filled with low-quality content hurts the whole site. Bad pages drag every other page down. Do not publish to fill the map. Every article must be quality work. If you cannot write a good article on a topic, leave it out. --- ## Execution order Load reference files as you progress through each phase. Complete every checkpoint before moving on. **Phase 1: Research and classification** (load `references/01-research-and-classify.md`) - Step 1: Define the central entity (Checkpoint 1) - Step 2: Source context plus persona (Checkpoint 2) - Step 3: Deep research on Knowledge Graph, competitors, client situations, attributes (Checkpoint 3) - Step 4: Classify each attribute as Core or AOR - Step 5: Merge and split decisions plus depth calibration (Checkpoint 4) **Phase 2: Architecture and keywords** (load `references/02-architecture-and-keywords.md`) - Step 6: Define folder structure - Step 7: Map every page to TOFU, MOFU, or BOFU (Checkpoint 5) - Step 8: Query expansion plus cost of retrieval scoring - Step 9: Keyword selection for page titles - Step 10: Define the linking architecture **Phase 3: Execution and output** (load `references/03-execution-and-output.md`) - Step 11: Central entity sitewide presence - Step 12: NLP category alignment check - Step 13: Content briefs for the first 30 articles - Step 14: Publishing order across 12 weeks - Generate the .xlsx with five tabs - Generate the strategy .md document When you finish, present both deliverables to the user with a one-paragraph summary of what to read first (Core, then AOR, then Linking, then Buyer Journey, then Publishing Order) and where to start writing this week. **The map is dynamic, not static.** Google's indexes change. Review and update the map quarterly.
Most SEO tools sell you a topical map. The map they sell you is a keyword cluster. That is one quarter of what you actually need. The other three layers are where the compounding actually happens.
12 to 20 commercial pages. Your money pages. The pages a customer lands on when they are ready to buy. Most tools stop here. The Core cluster is the destination, not the strategy.
60 to 80 supporting authority articles, organised by sub-topic. Areas of Relevance. The road that leads to the destination, paved with signals that tell Google this site is the specialist on the topic.
Which page links to which page, with what anchor text, in what direction. Without this layer you have a pile of articles. With it, you have a structure Google can read as a topical authority map.
Every page tagged TOFU, MOFU, or BOFU. Most websites have a giant MOFU gap. AI search loves this layer because it picks up content that helps users decide, not just content that sells.
90 articles sequenced across 12 weeks, with content briefs ready for the first 30. AOR wave first, MOFU buyer guides next, Core pages last. The sequence is what makes the compounding effect kick in within 60 days.
Each AOR article routes authority into the Core page it supports. Every supporting article is sending Google a signal that points at one of the money pages.
A simplified view of the Core hub for "dining tables", with six supporting articles routing authority into the money page. The full output covers 60 to 80 supporting articles across every Core page on your site.
Drop the unzipped folder into your Claude Code skills folder. Claude auto-loads it.
topical-authority-map.zip.topical-authority-map folder into ~/.claude/skills/.mkdir -p ~/.claude/skills
mv ~/Downloads/topical-authority-map ~/.claude/skills/
Use a Project. The skill content becomes the Project instructions, the references become Project Knowledge.
SKILL.md into the Project's custom instructions.references/ as Project Knowledge.Full instructions are in INSTALL.md inside the bundle.
Claude walks you through five checkpoints (central entity, source context plus persona, attribute list, merge and split decisions, buyer journey gaps), then produces the spreadsheet and strategy document. A focused run takes 30 to 45 minutes.
A worked example showing what the skill produces. 15 Core pages, 70 AOR articles, a full linking map, every page tagged TOFU / MOFU / BOFU, and 90 articles sequenced across 12 weeks.
Same workflow we run inside our 120-person agency on every client, from plumbers to enterprise SaaS. Free. No email gate. Yours.
Download the skill