VibeMKT Hub

SEO 与 GEO · directory-submissions

导航站收录 Skill

把产品基础信息转为分层的导航站收录档案，按梯队分发到 Product Hunt 与 AI 工具集，获取外链与曝光。

产品首发或日常引流阶段使用。核对落地页合规性与素材清单，生成 13 个梯队的导航站分发名单与文案变体，提供 Product Hunt 首发倒计时三周动作清单，并产出来源链接跟踪表单。

WHAT IT SOLVES

解决的营销问题

把产品基础信息转为分层的导航站收录档案，按梯队分发到 Product Hunt 与 AI 工具集，获取外链与曝光

把产品基础信息转为分层的导航站收录档案，按梯队分发到 Product Hunt 与 AI 工具集，获取外链与曝光。跑完你拿到的是包含网址、收录状态和 rel 属性验证结果的 CSV 跟踪表单，中间一共 7 步。

最适合的真实场景

  • 01

    海外增长负责人在 Product Hunt 首发新产品，需要安排 3 周预热和发射日互动

  • 02

    SEO 经理需要核查目录页面的链接属性、收录状态和后续引荐流量

  • 03

    出海运营准备向 TAAFT 和 Futurepedia 等 AI 工具集提交产品，获取早期曝光

  • 04

    产品营销人员想给竞品替代页倒流，利用不同导航站的变体文案提高页面转化

  • 05

    市场团队想通过 G2 和 Capterra 积累早期用户评价，进入软件评价榜单网格

你要先准备的资料

  • 落地页必须配置 FAQPage JSON-LD 结构化数据，以及 Organization 和 Product 标记
  • 至少 3 个竞品替代页和 3 个应用场景页上线，页面已被搜索引擎索引
  • 准备格式为 PNG 和 SVG 的 Logo 文件，以及 1024×1024 尺寸的方形图标
  • 至少准备 3 种不同场景的产品定位文案，用于不同分发梯队的描述变体
  • 准备完成核心操作且同意接收评价邀请的真实用户清单

跑完你会拿到什么

  • 包含网址、收录状态和 rel 属性验证结果的 CSV 跟踪表单
  • 涵盖 13 个梯队的导航站分发清单，标注具体分类和提交时机
  • 针对不同梯队站点特点定制的标题和 150 词产品描述变体文档
  • Product Hunt 首发操作清单，包含发射前 3 周的预热动作和当日时间表
  • 针对 G2 和 Capterra 的评价邀请模板，附带直达链接、平台规则和审核状态字段

METHOD

Skill 工作流程

落地页收录标准检查 → 分发梯队与站点匹配 → 分梯队生成文案变体 等 7 个环节

一共 7 步。其中 8 项能力决定了换个 AI 会不会更麻烦。

  1. 落地页收录标准检查检查页面是否具备单一 H1 标签、定价页、隐私政策。需要提供 5 到 8 张 1920×1080 的真实截图和 60 到 90 秒的演示视频链接。
  2. 分发梯队与站点匹配把目标站点按 13 个梯队分类。首发周提交 Product Hunt，第 1 到 3 周滚动提交 AI 工具集，后续提交无代码平台和本地目录。
  3. 分梯队生成文案变体针对不同站点的受众特点生成专属文案。向 AI 工具集强调 AI 原生架构，向 SaaS 站点强调竞品替代框架。每条长描述控制在 150 词。
  4. 表格化批次提交记录向各个导航站填写表单并上传物料。记录每次提交的日期、网址、收录状态和后台备注。单批次集中处理 2 到 3 小时。
  5. 外链属性验证收录页面上线后，检查链接元素与响应信息，分别记录 nofollow、sponsored、ugc 或未标注状态；无法确认时保留页面证据并交给人工复核。
  6. Product Hunt 首发执行按时间线准备账号互动、Upcoming 页面、首发素材和首条评论。正式发布前核对 Product Hunt 当期规则、时区与页面状态，发布后及时处理真实反馈。
  7. 评测站评价获取筛选完成核心操作且愿意反馈的真实用户，发送 G2 或 Capterra 评价直达链接。邀请内容遵守平台激励与披露规则，只记录自愿评价和审核状态。

这个 Skill 用到的能力： 页面预览中文办公文档运行脚本写本地文件操作前确认读本地资料联网检索打开网页取正文 。不同 AI 对这些能力的支持程度不一样，所以同一个 Skill 换个 AI，有几步做法会变。

WORKED EXAMPLE

业务示例

B2B SaaS 团队首发周外链建设

B2B SaaS 团队首发周外链建设

营销团队准备上线一款针对独立开发者的项目管理工具。团队需要在 1 个月内把产品推到主流导航站，为已建好的 3 个竞品替代页倒流。我们计划拿 Product Hunt 作为首发锚点，同时覆盖 AI 工具集和 SaaS 目录，目标是在 G2 拿到基础评价数量。

  1. 检查落地页的 H1 结构和截图尺寸，确认演示视频时长在 60 秒以上
  2. 把 TAAFT 和 Futurepedia 等站点划入第一周的 AI 工具集提交梯队
  3. 生成针对 AI 工具集和 SaaS 目录的两套不同的 150 词描述变体
  4. 执行 Product Hunt 首发操作清单，并在太平洋时间凌晨回复所有评论
  5. 向符合条件的早期用户发送 G2 评价直达邮件，注明自愿评价与平台规则

预期结果：交付导航站分层清单、两套描述变体、Product Hunt 首发操作清单和 CSV 跟踪表单。表单预留实际收录、rel 属性、引荐访问与评价审核状态字段；链接上线、评价通过和推荐位结果仍由人工持续核验。

PITFALLS · VERIFICATION

能力边界与常见问题

向所有导航站复制同一段描述，造成分类、受众与产品定位不匹配

最常踩的坑

  • 向所有导航站复制同一段描述，造成分类、受众与产品定位不匹配
  • 在没有跑通定价页和隐私政策的情况下强行提交，被 Tier 1 导航站官方拒收
  • 把所有产品链接指向首页，无法判断不同目录带来的访问与转化
  • 在 Product Hunt 私信陌生人拉票，触发社区反作弊机制导致产品贴被隐藏
  • G2 评价集中在月底才去拉票，错过了夏季和秋季报告的固定数据截止日

怎么确认这次跑对了

  • 已经形成可检查的包含网址、收录状态和 rel 属性验证结果的 CSV 跟踪表单，关键判断能回到输入资料或过程证据。
  • 已经形成可检查的涵盖 13 个梯队的导航站分发清单，标注具体分类和提交时机，关键判断能回到输入资料或过程证据。
  • 已经形成可检查的针对不同梯队站点特点定制的标题和 150 词产品描述变体文档，关键判断能回到输入资料或过程证据。
  • 已逐项检查「向所有导航站复制同一段描述，造成分类、受众与产品定位不匹配」等高频问题，并记录需要人工确认的下一步。
导航站收录 Skill适合哪些岗位使用？

海外增长负责人、SEO 经理、产品营销、出海运营。典型场景包括海外增长负责人在 Product Hunt 首发新产品，需要安排 3 周预热和发射日互动；SEO 经理需要核查目录页面的链接属性、收录状态和后续引荐流量；出海运营准备向 TAAFT 和 Futurepedia 等 AI 工具集提交产品，获取早期曝光。

开始前需要准备什么资料？

至少需要落地页必须配置 FAQPage JSON-LD 结构化数据，以及 Organization 和 Product 标记、至少 3 个竞品替代页和 3 个应用场景页上线，页面已被搜索引擎索引、准备格式为 PNG 和 SVG 的 Logo 文件，以及 1024×1024 尺寸的方形图标。资料越具体，结果越能直接用于决策。

最后能得到什么可检查的结果？

包含网址、收录状态和 rel 属性验证结果的 CSV 跟踪表单、涵盖 13 个梯队的导航站分发清单，标注具体分类和提交时机、针对不同梯队站点特点定制的标题和 150 词产品描述变体文档。每项都可以逐条核对来源和数字。

哪些情况下结果会不可靠？

向所有导航站复制同一段描述，造成分类、受众与产品定位不匹配；在没有跑通定价页和隐私政策的情况下强行提交，被 Tier 1 导航站官方拒收。出现这些情况时需要人工复核。

支持哪些 AI Agent？

已适配 WorkBuddy、OpenClaw、Hermes Agent、Codex、Claude Code、TRAE、ZCode 共 7 种，每种都有独立的安装说明和能力对照。

ORIGINAL SOURCE

完整 Skill 内容与版本资料

6 个原始文件，87 个文档章节，固定在 7868cb92

上游原文完整保留在加搜服务器上，可逐节查看，也可以直接下载。 当前镜像共 6 个文件、85.6 KB。

原始 Skill 文档 上游原文完整保留，中文概述已转换为营销任务、输入资料和交付结果。

Directory Submissions

You are an expert in directory-driven distribution for software products. Your goal is to help the user build a compounding backlink + discovery foundation by submitting to the right directories, in the right order, with the right positioning — and to make sure that foundation actually produces leads instead of vanity backlinks.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Core Philosophy

Directory submissions are the foundation layer of distribution — never the whole strategy. They do three things well:

  1. Pass dofollow backlinks from high domain-rating sites into your marketing pages. This raises your DR, which makes your entire site easier to rank for competitive keywords.
  2. Create discovery surface area — people browsing AI/SaaS directories are in-market buyers, not random traffic.
  3. Get cited by AI engines — ChatGPT, Claude, Perplexity, and Google AI Overviews all pull heavily from high-DR directories when answering "what's the best [category]?" queries. AI-referred traffic converts 6–27× higher than traditional search traffic.

But directories alone will not generate meaningful leads. They exist to pass link equity into the pages that DO generate leads — template galleries, comparison pages, alternative pages, blog posts. Build the destination pages first, then submit to directories so the link equity has somewhere useful to land.

The full directory catalog lives in references/directory-list.md. The positioning variant library lives in references/positioning-variations.md. The submission tracker template lives in references/submission-tracker-template.csv.

The Three Hard Rules

Rule 1: Foundation before submission

Never submit to a directory until the landing page it will link to is live, indexed, and has:

  • A single <h1> and sequential heading hierarchy — pages with clean hierarchy have 2.8× higher AI citation rates, and 87% of ChatGPT-cited pages use a single H1.
  • A real pricing page (even "free while in beta" counts — most Tier 1 directories require one).
  • Privacy policy + terms.
  • Logo assets in PNG + SVG + square 1024×1024 + favicon.
  • 5–8 real product screenshots at 1920×1080 (not marketing mockups).
  • A 60–90 second demo video — products with video on Product Hunt get 2.7× more upvotes.
  • FAQ schema markup (AI engines heavily weight FAQPage JSON-LD for answer extraction).
  • Structured data: Organization, Product, SoftwareApplication.
Rule 2: Destination pages before directories

Directories are the source of link equity. You need destinations that can convert the resulting traffic. Minimum destinations before submitting to anything:

  • 3–5 competitor alternative pages (/alternatives/[competitor]) targeting "[competitor] alternative" keywords. Comparison/alternative pages convert at 5–15% vs 0.5–2% for generic content.
  • 3–5 use-case pages (/for/[audience] or /use-cases/[use-case]).
  • Template gallery with 20+ entries (if applicable — this was Typeform's largest SEO growth driver, generating 30K non-branded signups and $3M/year LTV).
  • 1 "best of" blog post you wrote yourself about your own category, including honest coverage of competitors.
Rule 3: Positioning varies by directory type

Never copy-paste the same description everywhere. AI engines penalize duplicate content, and each directory audience responds to different framing. See references/positioning-variations.md for the full variant library. Short version:

Surface Lead with Why
Startup directories Outcome Audience is other founders. They care what it does.
SaaS directories Alternative framing People search "[competitor] alternative" — meet them there.
AI directories AI-first architecture TAAFT/Futurepedia audiences explicitly want AI tools.
Agent/MCP directories Agent/MCP angle Niche but high-intent. A real moat.
No-code directories Ease + power Audience values speed-to-build over depth.
Dev directories Technical depth Dev audiences reward technical substance.
B2B review sites ROI + use case Buyers want outcomes and case studies.

Workflow

Step 1: Readiness assessment (Phase 0)

Ask the user these 9 questions. If any are "no", they're not ready — help them build the missing piece first.

  1. Is the product publicly accessible (no password wall)?
  2. Is there a pricing page (even "free while in beta")?
  3. Are privacy policy + terms live?
  4. Logo assets in PNG + SVG + square + favicon?
  5. 5–8 real screenshots + 60–90s demo video?
  6. Landing pages GEO-ready (single H1, sequential hierarchy, FAQ schema, structured data)?
  7. At least 3 alternative pages and 3 use-case pages live and indexed?
  8. Template gallery or lead magnet asset (if applicable to category)?
  9. At least 20 beta/early users who could leave a review on G2?

A "no" on any of 1–7 is a hard block. A "no" on 8–9 is a soft block: you can launch but will lose Tier 2 review value and Typeform-style compounding.

Step 2: Choose the tiers

Full catalog in references/directory-list.md. Summary:

Tier When Examples Typical count
Tier 1 — Flagship launch Launch week only Product Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt ~15
Tier 2 — Startup/SaaS Week 1 + rolling AlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot ~50
Tier 3 — AI directories Week 1–3 TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage ~40
Tier 4 — Agent/MCP registries Week 1–3 (if MCP) Glama, APITracker, LF MCP Registry, AI Agents List ~10
Tier 5 — No-code directories Week 1–3 (if no-code) NoCodeFinder, No Code MBA, We Are No Code, MakerPad ~8
Tier 6 — "Best of" listicles Rolling outreach Cold outreach to DR 40+ blog posts ~10 inclusions
Tier 7 — Integration marketplaces When integrations ship Zapier, HubSpot, Slack, Airtable, Notion ~5
Tier 8 — Profile & content platforms Rolling GitHub, WordPress.com, Substack, Dev.to, SlideShare, Behance ~50
Tier 9 — Local business directories Rolling (if applicable) Manta, Hotfrog, Locanto, MerchantCircle ~20
Tier 10 — Forums & communities Rolling (participate first) SitePoint, GrowthHackers, Warrior Forum, Designer News ~13
Tier 11 — Press release & article sites Launch + milestones PRLog, PR.com, EzineArticles, Feedspot ~25
Tier 12 — Social bookmarking Rolling Scoop.it, Diigo, Pearltrees ~5
Tier 13 — Niche vertical directories When vertical fits Justia (legal), Porch (home), LandBook (design), etc. ~20

Triage rule: Only submit where the product is a genuine fit. Forcing a listing into the wrong category burns the first-submission advantage and gets rejected by moderators.

Step 3: Prepare asset variations

For each tier, prep a distinct description variant (pulled from references/positioning-variations.md):

  • Tagline under 10 words
  • Short description at 60 chars
  • Long description at 150 words
  • 5–8 category tags
  • Logo assets
  • Screenshots + demo video URL
  • Founder story (2–3 sentences)

Critical: Don't copy-paste the same long description into every directory. Vary the opening sentence, the feature emphasis, and the audience framing per tier. AI engines cross-reference and down-weight duplicate content.

Step 4: Batch submit

Set up the tracker spreadsheet (references/submission-tracker-template.csv). Work left-to-right through it. 2–3 hours per batch is realistic.

Per submission:

  1. Copy the tier-appropriate positioning variant.
  2. Fill in the form.
  3. Upload assets.
  4. Submit.
  5. Log: date, URL, status, moderator notes.
  6. Once live, verify the backlink exists and is dofollow: curl -sIL https://directory.com/your-listing | grep -i rel=. If absent, the link is dofollow.

Product Hunt Deep Dive (The Anchor Event)

Product Hunt is the single highest-leverage submission but also the most easily wasted. The 2026 PH algorithm weights comment quality more than upvote count — a post with 50 upvotes + 30 genuine comments ranks above one with 200 upvotes + 5 comments. 80% of failed launches fail because they launched without a warm audience OR asked for upvotes instead of feedback.

3-week prep timeline
  • Day -21 to -14: Warm up hunter account. Upvote + thoughtfully comment on 3 launches/day. Follow 100+ active makers. Build history so your account looks real to the algorithm.
  • Day -14: Create "Upcoming" page on PH. Drive traffic to it to collect "notify on launch" subscribers.
  • Day -10: (Optional) book a hunter. Don't pay cash — trade a feature, shoutout, or intro. A known hunter adds ~15% to day-one momentum but isn't required.
  • Day -7: Draft launch-day assets: gallery images (1270×760), tagline, 260-char description, first comment from you, first comment from a customer.
  • Day -3: Email list warm-up. "We're launching Tuesday. Here's what to expect. Reply if you want a heads up."
  • Day -1: Final check — product works in incognito, video autoplays, CTA goes to signup, PH listing preview looks right.
Launch day execution
  • Launch at 12:01 AM Pacific Time. Tuesday, Wednesday, or Thursday only — weekend launches get 60–70% less traffic. The 12:01 AM PT start maximizes your 24-hour window.
  • First 2 hours are everything. Need 50+ supporters in the first 2 hours to trigger algorithmic distribution.
  • Post the first comment yourself with the story: why you built it, what's different, what to try first.
  • Reply to every comment in under 30 minutes. PH measures maker responsiveness.
  • Share the link to: Twitter/X thread, LinkedIn long-form post, personal Slack/Discord communities, your email list, Indie Hackers, every power user via DM.
  • Never ask for upvotes. Ask for feedback. "Would love your honest take on the positioning" converts 3× better than "support us!" and doesn't trigger the algorithm's anti-manipulation filters.
  • Don't message strangers. The community flags this and moderators will hide your post.
Post-launch
  • Write a launch recap blog post with numbers + lessons. Honest, not bragging. Publish on day 2.
  • Cross-post the recap to Indie Hackers and r/SaaS (where promotion is allowed).
  • Only submit to Show HN if you have a technical angle to share (architecture, DSL, novel approach). A generic "we launched a SaaS" post will get flagged to death.

Reviews Playbook (G2 / Capterra / TrustRadius)

G2 and Capterra (now owned by G2 as of Feb 2026) listings are worthless without reviews. 10 reviews is the magic threshold for Grid appearance. Run the 10-in-30 protocol during launch month.

The 10-in-30 protocol
  1. Day 1 post-launch: Identify 20 users who have completed a meaningful action with the product.
  2. Send each a personal email with a direct review URL (reduces friction by ~70%). No forms, no landing pages — direct link.
  3. Offer a modest thank-you. G2 and TrustRadius explicitly allow small incentives like a $25 Amazon gift card.
  4. Follow up once after 5 days. Don't follow up twice — it becomes annoying and damages the relationship.
  5. Target: 50% conversion → 10 reviews from 20 asks.
Critical deadlines
  • G2 Summer reports: cut off ~April 28. Plan review drives to land before this.
  • G2 Fall reports: cut off ~July 28.
  • Missing a cutoff means waiting 3 months for the next grid update.
Badges and paid plans
  • "Users Love Us" badge is still free: requires 20 reviews at 4.0+ average.
  • Grid, Momentum, Index, and Award badges require a paid G2 plan ($2,999+/year starting Summer 2025).
  • Do not spend on paid G2 in year one. The free listing + Users Love Us badge is sufficient.
Cross-platform
  • TrustRadius follows similar mechanics but smaller volume.
  • Capterra auto-syncs from Gartner Digital Markets in some categories — may populate without direct action.

Destination Pages Strategy (What the Backlinks Point At)

Directories are useless if the backlinks land on a generic homepage. Build these destination pages before submitting:

1. Alternative pages (highest ROI)

Competitor alternative pages convert at 5–15%, often hitting 15–30% for bottom-of-funnel queries. One page per top competitor:

  • /alternatives/[competitor-1]
  • /alternatives/[competitor-2]
  • /alternatives/[competitor-3]
  • /alternatives/[competitor-4]

Each page needs: honest feature comparison table, "when to choose X over us," "when to choose us over X," pricing comparison, 3–5 use-case examples, strong FAQ with schema.

Critical: Be honest. AI engines cross-reference competitor feature claims and de-rank pages that lie.

2. Use-case / ICP pages

Every ICP gets a dedicated landing page:

  • /for/[audience] — coaches, agencies, ecommerce, SaaS, consultants, etc.
  • /use-cases/[use-case] — lead qualification, onboarding, product recommendations, etc.
3. Template / asset gallery (if applicable)

Typeform's template library generated 30,000 non-branded organic signups and $3M/year LTV. The pattern:

  • One indexable page per template at /templates/[slug].
  • H1 with the keyword, 150+ word description, screenshot, "when to use this," "use this template" CTA.
  • Related templates at the bottom of each page (internal linking = SEO compounding).
  • 100 templates by day 30, 300 by day 90 is the realistic target.
4. "Best of" listicles you wrote yourself

Write honest roundups of your own category: /blog/best-[category]-tools-2026. Include yourself + 10 competitors with real reviews. These rank for category queries AND serve as canonical references AI engines cite.

5. Integration pages (when integrations ship)

Every integration = one landing page at /integrations/[partner]. Follows the Zapier playbook: Zapier gets ~2.6M monthly organic visits from programmatic integration pages (~15% of their total organic traffic).

GEO (Generative Engine Optimization)

In 2026, 30–50% of "research a tool" queries happen inside ChatGPT, Claude, Perplexity, or Google AI Overviews without ever touching a traditional search page. Directories matter here too — AI engines pull heavily from high-DR directories when generating answers. But the destination pages also need to be GEO-optimized.

Tactics that get pages cited
  1. One H1 per page, sequential heading hierarchy. 2.8× higher citation rate. 87% of cited pages use a single H1.
  2. Dense, factual content with citable stats. AI engines prefer specific numbers ("3× faster than X") over vague claims.
  3. FAQ schema on every landing page. AI engines heavily weight FAQPage JSON-LD for answer extraction.
  4. Comparison tables. Extractable, structured — exactly what an AI answer needs.
  5. Explicit "what it is" paragraph in the first 100 words.
  6. Get cited on Reddit and Hacker News. Claude and Perplexity index these heavily. Genuine mentions on r/SaaS and HN count as training fuel.
  7. Publish original research. "We analyzed 10,000 [things] and found X" becomes the primary citation for anyone writing about that topic.
  8. Claim Crunchbase, LinkedIn company page, and Wikidata entries. All three feed AI training corpora.
  9. If applicable, list on MCP registries with A/B grades (Glama in particular). LLMs pull from these when answering MCP questions.
Measurement

Manually check monthly: ask ChatGPT, Claude, and Perplexity "what are the best [category] tools?" and log where the product appears. Free GEO tracking tools (GeoTracker, llmrefs) automate this.

Community & Ongoing Distribution

Directories are one-shot. Community is ongoing. Both feed the same funnel.

Reddit (90/10 rule)

90% of activity must be genuinely helpful; only 10% promotional. Violating this gets shadowbanned.

High-value subs (ranked):

  • r/SideProject (200K+) — friendly to promo, launch announcements welcome.
  • r/SaaS (300K+) — "Share Your SaaS" threads are explicit promo windows.
  • r/startups (1.7M) — Feedback Friday thread.
  • r/Entrepreneur (3.5M) — weekly promo thread.
  • r/nocode, r/IndieHackers, r/alphaandbetausers — friendly.
  • r/webdev, r/artificial, r/LocalLLaMA — strict, technical only.

What wins: real numbers (MRR, signups, churn), screenshots, "what I tried / what happened / what I'd do differently" structure, mini case studies with a clear lesson. What fails: hype, vague claims, "check out my new tool" posts, asking for upvotes.

LinkedIn (B2B primary channel)

80% of B2B social leads come from LinkedIn. Cadence: 3–5 posts/week — fewer loses momentum, more causes fatigue.

Content types ranked by 2026 engagement:

  1. Personal stories with business lessons (1.5–2× avg engagement)
  2. Original data / research (1.3–1.5×)
  3. Contrarian industry takes (1.2–1.5×)
  4. Document carousels with 8–12 slides (1.3–1.8×)
Twitter/X (indie hacker + dev channel)

Build-in-public threads on architecture, revenue, decisions. Technical deep-dives get indexed by Google + Claude + Perplexity → indirect GEO.

Indie Hackers
  • Launch a build-in-public thread on PH launch day.
  • Post weekly updates: revenue, ships, lessons. Zero-revenue posts work if the lesson is honest.
  • Comment 10× more than you post to build karma before your own links.
Dev.to + Hashnode

Every substantial technical post = dofollow backlink + dev audience reach. Cross-post with canonical URL back to main blog.

KPIs & Tracking

Track weekly. If a number isn't moving, investigate — don't just submit more directories.

Metric Day 0 Day 30 target Day 90 target
Domain Rating (DR) 0 20 30+
Referring domains 0 30 80+
Indexed pages — 50 200+
Organic clicks/day 0 30 200+
Directory listings live 0 50 70+
G2 reviews 0 10 25
Capterra reviews 0 5 15
AI citations (manual check) 0 3 15+
Signups from directory referrals 0 50 300
Signups from alt/use-case pages 0 20 300

What NOT to Do

  1. Don't pay for directory submission services ($60–$200 packages). The whole point is these are free. It's an afternoon of copy-paste.
  2. Don't submit to spam directories (DR under 10, no traffic, no editorial quality). They dilute your backlink profile and Google's spam detection can penalize you.
  3. Don't submit with the wrong positioning. Re-read the positioning table per tier. Generic descriptions waste the listing.
  4. Don't treat directories as your entire GTM. They're the foundation. Content + community + reviews are what actually convert.
  5. Don't skip reviews on G2/Capterra. Zero-review listings are dead. Run the 10-in-30 protocol or don't submit.
  6. Don't ask for upvotes on Product Hunt. The 2026 algorithm penalizes it. Ask for feedback.
  7. Don't amend old directory listings every week. Submit once, check quarterly.
  8. Don't submit before the destination page exists. Link equity needs a destination.
  9. Don't duplicate descriptions across directories. AI engines penalize duplicate content.
  10. Don't lie on comparison pages. AI engines cross-reference and de-rank lies.
  11. Don't over-index on launch-day spike. The flywheel is templates + alternatives + reviews + ongoing content — not one day of PH.
  12. Don't forget Crunchbase, LinkedIn company page, and Wikidata. These feed AI training corpora and matter for GEO.

Task-Specific Questions

  1. What are you launching? (Category changes tier mix — AI vs traditional SaaS vs no-code vs dev tool.)
  2. When is launch day? (Phase 0 assets need 7 days of prep.)
  3. Do you have destination pages built? (Alternatives, use cases, templates — if not, build first.)
  4. Product Hunt hunter lined up? (Optional but adds ~15% day-one lift. 3-week warm-up required regardless.)
  5. How many beta users can you ask for reviews? (Need 20 to hit 10.)
  6. Do you have an MCP or agent angle? (If yes, Tier 4 registries are a real moat.)
  7. Existing integrations? (If yes, Tier 7 marketplaces are the highest-DR backlinks available.)
  8. Email list size? (Needed for PH launch day warm traffic — 100+ is the minimum.)
  9. Current DR and referring domain count? (Baseline for measuring the compounding effect.)

Output Format

When the user asks for a directory plan, return:

  1. Readiness assessment — which Phase 0 items are missing, which block submission
  2. Tier selection — which tiers apply, which to skip, why
  3. Submission order — week 1 / week 2 / week 3 batches
  4. Destination page list — what to build first if missing
  5. Positioning variants — the actual copy per tier (from references/positioning-variations.md)
  6. PH 3-week prep timeline — mapped to calendar dates if launch day known
  7. Reviews 10-in-30 plan — who to ask, when, how
  8. Weekly targets — directories submitted, reviews, DR movement
  9. Tracker — link to or include the CSV from references/submission-tracker-template.csv

Keep the plan actionable. Every item should be something the user can do today.

Related Skills

  • launch — broader launch moment, ORB framework, five-phase approach
  • programmatic-seo — destination pages (alternatives, integrations, templates) that backlinks should flow into
  • competitors — /alternatives/[tool] page pattern
  • ai-seo — GEO optimization for AI citation
  • content-strategy — editorial content that attracts "best of" listicle inclusions
  • free-tools — lead magnets for destination pages
  • community-marketing — Reddit, Indie Hackers, Slack community mechanics
  • schema — FAQ + Product + Organization JSON-LD for GEO

来源与版本声明

本页面由加搜科技整理业务说明并托管安装文件。原始 Skill 来源渠道：GitHub； 原始项目名称：directory-submissions； 固定版本：7868cb9251fa； 许可证：MIT。技能包内保留完整出处和许可证说明。

各 Agent 能力说明参考对应官方文档。页面不提供外部跳转。

INSTALL

三种安装方式

导航站收录 Skill v1.0.0，ZIP 带 SHA256 校验

默认做法是把提示词复制给 AI Agent，让它自己下载并安装。提示词里已经写清要用完整 ZIP、装完报告目录、并先跑一个小任务验证。

METHOD 01 · 交给 AI 自己装

复制提示词

适合大多数情况。Agent 会下载 ZIP、解压、放到正确目录，并在缺少权限时告诉你需要手工做哪一步。

请帮我把「导航站收录 Skill」安装到我正在使用的 AI Agent。
1. 下载完整 Skill ZIP：https://www.vibemarketing.work/packages/skill-directory-submissions/1.0.0/skill-directory-submissions.zip
   注意：网页 HTML 不能当作 Skill 文件安装，必须使用 ZIP 里的完整文件。
2. 解压后保留 SKILL.md 及全部配套文件，按你所用 Agent 的 Skill 目录规则安装。
3. 安装完成后告诉我实际安装目录。
4. 用一个只读小任务验证 Skill 已被识别。
5. 如果你没有联网、下载或写目录权限，请直接告诉我哪几步需要我手工完成。
参考：原始 SKILL.md https://www.vibemarketing.work/raw/skill-directory-submissions/SKILL.md；安装指南 https://www.vibemarketing.work/agent-install/skill-directory-submissions.md

FURTHER READING

导航站收录 Skill 相关的实操文章

别人做同类任务时踩过的坑和总结，动手前后都值得翻一下。

联盟只看点击数，佣金和归因窗口会在结算时吵起来

联盟和红人一上量，后台最先好看的是点击。结算时吵起来的，通常是另一批东西：这笔单算谁的、窗口过了没有、视频里有没有把你不敢承诺的效果说出去。佣金结构、归因窗口、禁止承诺，要在合作开始前写进协议。只看带

  • 内容分发
  • 出海增长
  • 红人营销

GEO和SEO的区别：从搜索流量到AI答案引擎的范式转移

GEO（生成式引擎优化）不是SEO的升级版，而是针对AI答案引擎的不同优化逻辑。本文从展示形式、排名机制、内容策略和技术实现四个维度对比GEO与SEO的核心差异，帮助营销团队理解两种流量来源的共存策略

  • AI搜索优化
  • 生成式引擎优化
  • 搜索流量
  • SEO

一条长视频拆成短条，每条都要能单独发

一场五十分钟的产品讲解，按时间轴每五分钟切一段，切出来的东西在 TikTok 和 Reels 上站不住。因为那五分钟的开头常常是「刚才我们说了」，结尾是「下面这部分」。短视频平台上，每一条都得自己有钩

  • 短视频脚本
  • 海外社媒
  • 内容分发

搭配使用

按这个 Skill 的产出能不能直接被下一个 Skill 用上来推荐，不是固定名单。多数情况下按顺序跑完一组，比单独用一个效果更好。

内容与创意#02

专家评审 Skill

自动组建 7 到 10 人的虚拟专家团队，对文案、落地页或营销方案进行打分并提出修改建议，直到评分达到 90 分。

来源项目热度 同步中
海外广告投放#04

LinkedIn Ads 投放 Skill

为 B2B 获客设计 LinkedIn 广告目标、受众、素材、表单和预算结构。

来源项目 · kostja94/marketing-skills ★ 742 · Fork 108

VibeMKT COMMUNITY

加入 VibeMKT 社群

微信扫码，交流营销 Skill 的选择、安装、试用与业务化改造。

加入 VibeMKT 社群的微信二维码

二维码会持续显示，关闭弹窗后返回当前页面。