SkillAtlasSkill 详情

topical-authority-mapper

Put your AI agent on the growth team.

审核状态:已审核Quality 72Security 70

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年8月21日
CleanShot 2026-07-13 at 20 15 47@2x CleanShot 2026-07-13 at 20 16 54@2x

AI Skills for Brand Growth

Put your AI agent on the growth team.

Research customers and competitors, analyze what is working, create the next campaign, and learn from the result. Goose Skills gives Claude Code, Cursor, Codex, and other coding agents ready-to-use workflows for ads, social media, content, competitive intelligence, SEO, lead generation, and GTM.

Browse all skills at https://skills.gooseworks.ai

Works with Claude Code · Cursor · Codex

npm version License: MIT Skills


Contents


Quick Start

AI Coding Agents (Claude Code, Cursor, Codex, etc)

Paste this into your coding agent (Claude Code, Cursor, or Codex) and it'll set everything up:

Install the Gooseworks skills:

In the terminal, run `npx gooseworks install --all`.

Then run `npx gooseworks login` and it'll open a browser to sign in and set up the tools, then confirm it worked.

The skills can be used with /gooseworks <prompt>

Claude Cowork

Run this command in a terminal first:

npx gooseworks install --all

Then authenticate:

npx gooseworks login

Then make sure you're working inside a local folder on your machine, and then you can use the skills in Cowork like this:

Use /gooseworks skill to generate some ad creatives

Install manually

Prefer to run it yourself? Use the command directly:

npx gooseworks install --all       # All detected agents

This gives your coding agent access to the full catalog of 200+ skills. After installing, just ask your agent to use any skill by name.

If you want a cloud-based AI coworker that already knows all these skills and more, sign up to Gooseworks


Brand Growth collection

The Brand Growth collection is a curated path through the normal Goose Skills catalog for consumer and ecommerce brand work. It is not a separate package or command: install GooseWorks once, then ask /gooseworks for the outcome you need.

StageWhat your agent can doExample skills
ResearchUnderstand the brand, customers, competitors, audiences, creators, trends, comments, and product demandbrand-research, audience-research, comment-mining, competitor-social-research, influencer-prospecting, trend-discovery, product-demand-research
AnalyzeDiagnose ads, creator profiles, transcripts, policy risk, landing-page message match, and unusual social performancecompetitor-ad-intelligence, creator-profile-teardown, transcript-intelligence, meta-ads-analyzer, meta-ad-policy-checker, ad-to-landing-page-auditor, outlier-post-finder
CreateRepurpose research, remix graphic ads, make product photography and social graphics, and animate static imagescontent-repurposing, remix-graphic-ad-from-reference, product-photoshoot, goose-graphics, animate-image
Learn and iterateBring results back into research and analysis, then decide the next testRe-run the relevant analysis skill with current performance and audience evidence

ScrapeCreators powers structured public social and ad-library research behind several workflows. Signed-in GooseWorks users access it through the managed first-party proxy and do not need a separate ScrapeCreators key. The user-facing skills turn that source data into a brief, shortlist, analysis, or recommendation instead of returning raw API output.

Browse the Brand Growth collection

After installation, start with:

/gooseworks onboard me

The agent will collect the useful company context for future growth work and finish by asking what you want to do first. Existing users can skip onboarding and keep using /gooseworks exactly as they do today.


Commands

npx gooseworks search "reddit scraping"   # Search the skill catalog
npx gooseworks credits                     # Check your credit balance
npx gooseworks update                      # Update to latest skill version

Skills Catalog

200+ skills across the growth stack, grouped by focus area:

CategoryWhat's inside
AdsResearch, build, and analyze paid campaigns across Meta and Google
SEOKeyword research, content gaps, SERP analysis, technical audits
Lead generationFind, enrich, and qualify prospects for your pipeline
OutreachDraft, personalize, and run outbound across email and social
ContentBlog posts, social content, carousels, video scripts, newsletters
ResearchCompany, market, and prospect deep-dives
Competitive intelTrack competitor pricing, launches, positioning, and ads
MonitoringWatch for mentions, signals, and changes across the web
SocialScrape and analyze social platforms and audiences
BrandVoice, positioning, and visual brand assets

Browse and search every skill at skills.gooseworks.ai.


Usage Examples

After installing, just ask your coding agent naturally:

"/gooseworks Generate static ad creatives for my brand"
"/gooseworks Use the reddit-post-finder skill to search r/startups"
"/gooseworks Use the apollo-lead-finder skill to find CTOs at AI companies"
"/gooseworks Use the competitor-intel skill to research Acme Corp"
"/gooseworks Use the goose-graphics skill to create a LinkedIn carousel about our launch"

Your agent will search the GooseWorks catalog, download the skill, and run it automatically.


Building from Source

git clone https://github.com/gooseworks-ai/goose-skills.git
cd goose-skills
node scripts/validate-skills.js  # Validate SKILL.md + skill.meta.json contract
node scripts/build-index.js      # Generate skills-index.json
node bin/goose-skills.js list    # Test locally

Skill Metadata Contract

Each skill directory must include:

  • SKILL.md — Skill documentation and usage guide
  • skill.meta.json — Machine-readable metadata

skill.meta.json fields:

FieldRequiredDescription
slugYesUnique kebab-case identifier
categoryYescapabilities, composites, or playbooks
tagsYesString array of category tags
installation.base_commandYesInstall command
installation.supportsYesArray: claude, codex, cursor
featuresNoFeature flags
github_urlNoSource repository URL
authorNoSkill author
example_promptNoCopyable prompt shown in the catalog and docs for trying the skill

Security & Trust

These skills run inside your coding agent, so it's worth knowing exactly what they do:

  • Open source & inspectable. Every skill — its SKILL.md instructions and all scripts — lives in this repo under the MIT license. The gooseworks CLI fetches skills at runtime so recipes stay current, but the source you'd run is right here to read, diff, or pin before you run it.
  • Scripts run locally. Skill scripts execute on your machine and write to /tmp/gooseworks-scripts/, never into your project directory. Only API requests go through GooseWorks servers; review any script before letting your agent run it.
  • Your agent stays in control. The skills are a tool your agent reaches for when it fits the task (data at scale, sources behind auth, a specific provider) — not a replacement for its built-in web search or fetch on quick lookups. You can read or edit any installed SKILL.md to tune that behavior.
  • Credentials stay local. Auth is a Bearer token stored at ~/.gooseworks/credentials.json (file mode 0600). Third-party provider keys (Apify, Apollo, etc.) are held server-side — your token never touches them. All network calls are HTTPS.
  • The MCP server is opt-in. Registering the GooseWorks MCP server is off by default; it only happens if you explicitly run gooseworks install --mcp.

Found something that looks off? Open an issue — we'd rather fix it in public.


License

MIT — see LICENSE for details.

The skill files and CLI in this repository are MIT-licensed. The GooseWorks API they connect to is a separate paid service governed by its own terms.

其他

中风险

  • 来源需自行核对维护者身份。
  • 包含脚本或命令调用,安装前请复核。
  • 可能需要外部 token、网络权限或第三方服务。
  • 未检测到高风险命令。
  • 扫描发现:1 条。

Codex — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/gooseworks-ai/goose-skills.git
  3. 将 "skills/seo/composites/topical-authority-mapper" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/gooseworks-ai/goose-skills.git
  3. 将 "skills/seo/composites/topical-authority-mapper" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/gooseworks-ai/goose-skills.git
  3. 将 "skills/seo/composites/topical-authority-mapper" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/gooseworks-ai/goose-skills.git
  3. 将 "skills/seo/composites/topical-authority-mapper" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/gooseworks-ai/goose-skills.git
  3. 将 "skills/seo/composites/topical-authority-mapper" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
name: topical-authority-mapper
description: >
  Map complete topic clusters for any subject area — hub pages, spoke articles,
  supporting content, internal linking architecture. Identifies content gaps,
  priority order, and builds a structured content calendar. Produces topic maps
  that build genuine topical authority, not random blog posts.
tags: [seo]

Topical Authority Mapper

Most content strategies are just keyword lists turned into blog posts. Real topical authority requires a structured map: pillar pages that own broad topics, cluster pages that go deep on subtopics, and an internal linking architecture that tells Google "we comprehensively cover this subject." This skill builds that map.

Core principle: Google rewards topical depth, not random keyword coverage. A site with 15 interlinked articles that thoroughly cover "sales automation" will outrank a site with 50 unrelated blog posts that happen to mention the phrase. This skill builds the cluster architecture that creates genuine authority.

When to Use

  • "What content should we create to dominate [topic]?"
  • "Build a topic cluster strategy for our blog"
  • "Map out our topical authority for [category]"
  • "Create a content calendar based on topic clusters"
  • "What content gaps do we have?"

Tool Enhancement (Optional)

Topic cluster mapping is significantly better with keyword data that shows search volume, difficulty, and semantic relationships across hundreds of subtopic variations.

Agent Prompt to User

"I can build a comprehensive topical authority map using competitive analysis and content gap identification. For the most precise results — especially accurate volume data and keyword clustering at scale — I'd recommend connecting a keyword data API."

Recommended: DataForSEO (pay-per-use, ~$0.01/keyword, no monthly minimum)

  • Sign up at dataforseo.com → get API login + password
  • Set DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD env vars

Alternatives that also work:

  • Keywords Everywhere API ($1 per 10 credits = 100K keywords, very cheap) → set KEYWORDS_EVERYWHERE_API_KEY
  • SEMrush API (if you have a subscription) → set SEMRUSH_API_KEY
  • Ahrefs API (if you have a subscription) → set AHREFS_API_TOKEN

"Want to use one of these, or should I proceed with baseline mode? Baseline uses our existing SEO tools and web research — still produces a strong topic map, but with less granular volume data per subtopic."

Mode Selection

  • Enhanced mode — Bulk keyword data via DataForSEO / Keywords Everywhere / SEMrush / Ahrefs. Gets search volume, difficulty, and semantic grouping for every subtopic. Enables data-driven prioritization and precise gap identification. Also supports keyword clustering APIs that automatically group related terms.
  • Baseline mode — Uses seo-domain-analyzer for domain metrics, web_search for topic research, reddit-post-finder for question mining, competitor analysis via site-content-catalog. Topic mapping and cluster architecture are equally strong. Volume estimates are directional rather than exact.

Phase 0: Intake

  1. Your site URL — For existing content audit
  2. Target topics — 1-5 broad topic areas you want authority in (e.g., "sales automation", "content marketing", "data privacy")
  3. Competitors — 2-5 competitor URLs who rank well for these topics
  4. ICP — Who reads your content? (role, pain, goal)
  5. Content capacity — How many articles can your team produce per month?
  6. Existing content — Do you have a blog? How many articles? (we'll audit it)
  7. Time horizon — 3-month plan? 6-month? 12-month?
  8. Tool preference — Enhanced mode with keyword API, or baseline? (see Tool Enhancement above)

Phase 1: Current State Audit

1A: Your Existing Content

Run site-content-catalog on your site:

python3 skills/site-content-catalog/scripts/catalog_content.py \
  --url "<your_site_url>" \
  --output json

Map all existing content:

  • Blog posts by topic
  • Resource pages, guides, glossary
  • Landing pages with content
  • Identify which topics you already have content for
  • Note: thin pages, outdated content, orphan pages (no internal links)

1B: Competitor Content Mapping

For each competitor, run site-content-catalog:

python3 skills/site-content-catalog/scripts/catalog_content.py \
  --url "<competitor_url>" \
  --output json

Map their content architecture:

  • How do they structure topic clusters?
  • Which topics have pillar pages?
  • How deep do their clusters go?
  • Internal linking patterns
  • Content freshness (update dates)

1C: Domain Authority Baseline

Run seo-domain-analyzer for your site and competitors:

  • Your domain authority vs. competitors
  • Keyword overlap analysis
  • Where competitors rank that you don't

Phase 2: Topic Universe Expansion

2A: Subtopic Discovery

For each target topic area, generate the full subtopic universe:

Enhanced mode (DataForSEO / Keywords Everywhere):

# DataForSEO keyword suggestions
POST /v3/dataforseo_labs/google/keyword_suggestions/live
{
  "keyword": "<topic>",
  "limit": 500
}

# DataForSEO related keywords
POST /v3/dataforseo_labs/google/related_keywords/live
{
  "keyword": "<topic>",
  "limit": 500
}

Extract:

  • All related keywords and questions
  • Search volumes per keyword
  • Keyword difficulty scores
  • Semantic groups (auto-clustered by meaning)

Baseline mode:

Use multiple sources to build the subtopic list:

  • web_search for "topic + [what/how/why/best/vs/guide/examples]"
  • reddit-post-finder for questions people ask about the topic
  • Google autocomplete patterns (via web search)
  • Competitor content titles (from Phase 1B)
  • PAA questions from search results

2B: Question Mining

Run reddit-post-finder for each topic area:

python3 skills/reddit-post-finder/scripts/search_reddit.py \
  --subreddit "<relevant_subs>" \
  --keywords "<topic>" \
  --days 365 --sort top --time year

Extract:

  • Questions people ask (→ individual article topics)
  • Recurring themes (→ cluster pillars)
  • Misconceptions (→ myth-busting content)
  • Comparisons people make (→ vs/ content)
  • Use cases discussed (→ use-case content)

2C: Keyword Clustering

Group all discovered keywords/subtopics into semantic clusters:

Enhanced mode: Use DataForSEO keyword clustering API or group by SERP overlap (keywords that share 3+ ranking URLs likely belong to the same cluster).

Baseline mode: Manual semantic grouping based on:

  • Shared root concepts
  • User intent alignment (informational / commercial / navigational)
  • Topic hierarchy (broad → specific)

Phase 3: Cluster Architecture

3A: Pillar-Cluster Mapping

For each topic area, design the cluster hierarchy:

PILLAR: [Broad Topic] — "The Complete Guide to [Topic]"
│
├── CLUSTER 1: [Subtopic Group A]
│   ├── Article: [Specific subtopic A1]
│   ├── Article: [Specific subtopic A2]
│   └── Article: [Specific subtopic A3]
│
├── CLUSTER 2: [Subtopic Group B]
│   ├── Article: [Specific subtopic B1]
│   ├── Article: [Specific subtopic B2]
│   └── Article: [Specific subtopic B3]
│
├── CLUSTER 3: [Subtopic Group C]
│   ├── Article: [Specific subtopic C1]
│   └── Article: [Specific subtopic C2]
│
└── SUPPORTING: [Glossary terms, FAQs, tools]
    ├── Glossary: [Term 1]
    ├── Glossary: [Term 2]
    └── FAQ: [Common questions]

3B: Content Type Assignment

For each piece in the cluster:

Content TypeWhen to UseTypical Word Count
Pillar pageBroad topic overview, links to all cluster content3,000-5,000+
Cluster articleDeep dive on subtopic1,500-3,000
Comparison postvs/ or alternatives content2,000-3,500
How-to guideStep-by-step instruction1,500-2,500
Glossary entryDefinition + context500-1,000
Tool/CalculatorInteractive resource500 + tool
Case studyProof point1,000-2,000
ListicleCurated collection1,500-3,000

3C: Internal Linking Architecture

Design the linking structure:

  1. Pillar → All cluster articles (every cluster article gets a link from the pillar)
  2. Cluster articles → Pillar (every article links back to the pillar)
  3. Cluster articles ↔ Related cluster articles (cross-links within the cluster)
  4. Cross-cluster links where topics overlap
  5. Supporting content → Relevant cluster articles (glossary terms link to articles that explain them in depth)

Map specific anchor text for each link.

Phase 4: Gap Analysis & Prioritization

4A: Coverage Gap Matrix

SubtopicYour ContentCompetitor ACompetitor BVolumeDifficultyGap?
[subtopic 1]✗ None✓ Pillar page✓ Blog post[vol][diff]✓ High priority
[subtopic 2]✓ Thin post✓ Deep guide✗ None[vol][diff]✓ Update needed
[subtopic 3]✓ Strong guide✓ Similar✓ Similar[vol][diff]✗ Covered
[subtopic 4]✗ None✗ None✗ None[vol][diff]✓ White space

4B: Priority Scoring

Score each content piece to create:

FactorWeightDescription
Search volume25%Monthly search demand
Competitive gap25%How much better can you be than what exists?
Intent alignment20%Does the searcher match your ICP?
Cluster completeness15%Does this fill a critical gap in a cluster?
Effort15%How much work to create high-quality content?

4C: Content Calendar

Based on content capacity and priority scores:

Month 1: Build [N] pillar foundations

  • [Pillar 1] — [rationale]
  • [3-5 highest-priority cluster articles]

Month 2: Deepen Cluster 1, start Cluster 2

  • [5-8 articles] — [rationale]

Month 3: Complete Cluster 2, begin Cluster 3

  • [5-8 articles] — [rationale]

Months 4-6: Expansion

  • [Continue pattern based on capacity]

Phase 5: Output

# Topical Authority Map — [Site/Client] — [DATE]

## Executive Summary
- Topic areas mapped: [N]
- Total content pieces identified: [N] (pillars: [N], clusters: [N], supporting: [N])
- Existing content: [N] pages ([N] strong, [N] need updates, [N] gaps)
- Net new content needed: [N] pages
- Estimated timeline to full coverage: [N] months at [N] articles/month

---

## Topic Map: [Topic Area 1]

### Cluster Architecture
[Visual tree structure per Phase 3A]

### Pillar Page
- **Target keyword:** [keyword] ([volume]/mo, [difficulty])
- **Title:** [recommended title]
- **Content type:** Comprehensive guide
- **Word count target:** [X]-[Y]
- **Links to:** [all cluster articles listed]
- **Status:** [Exists — needs update / New — priority [P0/P1/P2]]

### Cluster: [Subtopic Group A]

#### Article: [Subtopic A1]
- **Target keyword:** [keyword] ([volume]/mo, [difficulty])
- **Content type:** [how-to / comparison / listicle / etc.]
- **Word count target:** [X]-[Y]
- **Links to:** Pillar + [related articles]
- **Links from:** Pillar + [related articles]
- **Priority:** [P0/P1/P2]
- **Anchor text:** "[anchor]" from pillar, "[anchor]" from [related article]

#### Article: [Subtopic A2]
...

### Cluster: [Subtopic Group B]
...

---

## Topic Map: [Topic Area 2]
...

---

## Internal Linking Matrix

| From ↓ / To → | Pillar | Article A1 | Article A2 | Article B1 | ... |
|----------------|--------|-----------|-----------|-----------|-----|
| **Pillar** | — | ✓ "[anchor]" | ✓ "[anchor]" | ✓ "[anchor]" | |
| **Article A1** | ✓ "[anchor]" | — | ✓ "[anchor]" | | |
| **Article A2** | ✓ "[anchor]" | ✓ "[anchor]" | — | | |
| **Article B1** | ✓ "[anchor]" | | | — | |

---

## Content Calendar

### Month 1: Foundation
| Week | Content Piece | Type | Cluster | Keywords | Priority |
|------|--------------|------|---------|----------|----------|
| W1 | [Pillar: Topic 1] | Pillar page | — | [kw] ([vol]) | P0 |
| W1 | [Article A1] | Cluster article | A | [kw] ([vol]) | P0 |
| W2 | [Article A2] | Cluster article | A | [kw] ([vol]) | P0 |
| W2 | [Article B1] | Cluster article | B | [kw] ([vol]) | P0 |

### Month 2: Depth
...

### Month 3: Expansion
...

---

## Coverage Gap Report

### High Priority (Competitors rank, you don't)
| Topic | Competitor Coverage | Your Status | Volume | Recommended Action |
|-------|-------------------|-------------|--------|--------------------|
| [topic] | A: Pillar, B: Blog post | None | [vol] | Create [content type] |

### Medium Priority (Weak coverage)
| Topic | Your Current Page | Issue | Volume | Recommended Action |
|-------|------------------|-------|--------|--------------------|
| [topic] | [URL] | Thin (400 words) | [vol] | Expand to [X] words, add [sections] |

### Existing Content Updates Needed
| URL | Issue | Action Required | Effort |
|-----|-------|----------------|--------|
| [url] | Outdated (2023 data) | Update stats, refresh examples | 2 hours |
| [url] | No internal links | Add [N] links to cluster articles | 30 min |
| [url] | Missing from pillar | Add link from pillar with "[anchor]" | 15 min |

---

## Metrics to Track
- **Topical coverage %** — Articles created vs. total identified
- **Internal link density** — Avg links per article within cluster
- **Cluster ranking velocity** — Time from publish to page 1 per cluster
- **Pillar page rankings** — Position for head terms
- **Organic traffic by cluster** — Traffic attributed to each topic cluster

Save to the current working directory or wherever the user prefers.

For large topic maps (3+ topic areas), also export a summary CSV: content-calendar-[YYYY-MM-DD].csv

Cost

ComponentCost
Site catalog (your site, once)~$0.05-0.10
Site catalog per competitor~$0.05-0.10
SEO domain analyzer~$0.10-0.20
Reddit scraper (per topic area)~$0.05-0.10
DataForSEO keyword data (enhanced)~$0.50-3.00 (depending on keyword count)
Keywords Everywhere (enhanced alt)~$0.01-0.10
Page fetches (competitor content analysis)~$0.01-0.05
AnalysisFree (LLM reasoning)
Total per topic area (baseline)~$0.25-0.50
Total per topic area (enhanced)~$0.75-3.50
3 topic areas (baseline)~$0.75-1.50
3 topic areas (enhanced)~$2.25-10.50

Tools Required

  • Apify API token — APIFY_API_TOKEN env var
  • Upstream skills: site-content-catalog, seo-domain-analyzer, reddit-post-finder, fetch_webpage
  • Optional (enhanced): DataForSEO (DATAFORSEO_LOGIN + DATAFORSEO_PASSWORD), Keywords Everywhere (KEYWORDS_EVERYWHERE_API_KEY), SEMrush (SEMRUSH_API_KEY), or Ahrefs (AHREFS_API_TOKEN)

Scheduling

For ongoing topical authority tracking:

  • Run quarterly to reassess coverage gaps
  • Monthly: check for new subtopics emerging in the space
  • After each content batch: update the map with published URLs and internal links

Trigger Phrases

  • "Map our topical authority for [topic]"
  • "Build a topic cluster strategy"
  • "What content gaps do we have?"
  • "Create a content calendar for SEO"
  • "How do we build authority in [topic area]?"
  • "Plan our content architecture"

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!