Back to Details

directory-submissions

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
您是软件产品目录驱动型分发的专家。您的目标是帮助用户通过向合适的目录、按正确的顺序、以恰当的定位提交产品，构建可复利增长的反向链接+曝光基础，并确保该基础能真正产生潜在客户，而非 vanity 反向链接。

Before Starting

开始前准备

Check for product marketing context first: If 
.agents/product-marketing-context.md
exists (or 
.claude/product-marketing-context.md
in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
先检查产品营销背景信息： 如果存在
.agents/product-marketing-context.md
（或旧版设置中的
.claude/product-marketing-context.md
），请在提问前阅读该文件。利用其中的背景信息，仅询问未涵盖或与此任务相关的特定信息。

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
.
目录提交是分发的基础层——绝非全部策略。它能很好地完成三件事：
  1. 传递dofollow反向链接：从高域名评级（DR）网站向您的营销页面传递权重，提升您的DR值，使整个网站更易在竞争激烈的关键词中排名。
  2. 创造曝光触点：浏览AI/SaaS目录的用户都是精准的目标买家，而非随机流量。
  3. 获得AI引擎引用：ChatGPT、Claude、Perplexity和Google AI概览在回答“最佳[品类]工具是什么？”这类问题时，都会大量引用高DR目录中的内容。AI引导的流量转化率比传统搜索流量高6–27倍。
但仅靠目录无法产生有意义的潜在客户。它们的作用是将链接权重传递到真正能转化流量的页面——模板库、对比页面、替代页面、博客文章。先构建目标页面，再提交至目录，让链接权重有合适的去处。
完整目录清单位于
references/directory-list.md
。定位变体库位于
references/positioning-variations.md
。提交追踪模板位于
references/submission-tracker-template.csv
。

The Three Hard Rules

三条硬性规则

Rule 1: Foundation before submission

规则1：先打基础再提交

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
    .
在链接指向的落地页上线、被搜索引擎收录并满足以下条件前，绝不提交至任何目录：
  • 单个
    <h1>
    标签及有序标题层级——结构清晰的页面AI引用率高2.8倍，且87%被ChatGPT引用的页面都使用单个H1。
  • 真实的定价页面（即使是“测试期免费”也符合要求——大多数一级目录都要求具备）。
  • 隐私政策+服务条款。
  • 多种格式的Logo资源：PNG + SVG + 1024×1024方形图标 + 网站图标（favicon）。
  • 5–8张真实产品截图（1920×1080分辨率，非营销效果图）。
  • 60–90秒的演示视频——在Product Hunt上带有视频的产品获得的点赞数高2.7倍。
  • FAQ schema标记（AI引擎在提取答案时会重点关注
    FAQPage
    JSON-LD）。
  • 结构化数据：
    Organization
    、
    Product
    、
    SoftwareApplication
    。

Rule 2: Destination pages before directories

规则2：先建目标页面再提交目录

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.
目录是链接权重的来源，您需要能转化流量的目标页面。提交前至少需具备以下目标页面：
  • 3–5个竞品替代页面（
    /alternatives/[competitor]
    ），针对“[竞品]替代工具”类关键词。对比/替代页面的转化率为5–15%，远高于通用内容的0.5–2%。
  • 3–5个使用场景页面（
    /for/[audience]
    或
    /use-cases/[use-case]
    ）。
  • 包含20+条内容的模板库（若适用——这曾是Typeform最大的SEO增长引擎，带来3万次非品牌注册，年生命周期价值达300万美元）。
  • 一篇由您亲自撰写的关于所在品类的“最佳工具”博客文章，需客观涵盖竞品信息。

Rule 3: Positioning varies by directory type

规则3：定位随目录类型调整

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:
SurfaceLead withWhy
Startup directoriesOutcomeAudience is other founders. They care what it does.
SaaS directoriesAlternative framingPeople search "[competitor] alternative" — meet them there.
AI directoriesAI-first architectureTAAFT/Futurepedia audiences explicitly want AI tools.
Agent/MCP directoriesAgent/MCP angleNiche but high-intent. A real moat.
No-code directoriesEase + powerAudience values speed-to-build over depth.
Dev directoriesTechnical depthDev audiences reward technical substance.
B2B review sitesROI + use caseBuyers want outcomes and case studies.
绝不要在所有目录中复制粘贴相同的描述。AI引擎会惩罚重复内容，且不同目录的受众对定位的响应不同。完整变体库请查看
references/positioning-variations.md
。精简版如下：
平台类型核心切入点原因
创业类目录成果导向受众为其他创业者，他们关注产品能带来什么成果。
SaaS类目录替代定位用户常搜索“[竞品]替代工具”——需贴合这类需求。
AI类目录AI优先架构TAAFT/Futurepedia的受众明确想要AI工具。
Agent/MCP类目录Agent/MCP视角受众小众但意向极高，是真正的护城河。
无代码类目录易用性+功能性受众重视搭建速度而非深度。
开发者类目录技术深度开发者受众认可技术实质内容。
B2B评论网站ROI+使用场景买家关注成果和案例研究。

Workflow

工作流程

Step 1: Readiness assessment (Phase 0)

步骤1：就绪度评估（第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.
向用户询问以下9个问题。若有任何一个答案为“否”，则用户尚未准备就绪——先帮助他们补全缺失部分。
  1. 产品是否可公开访问（无密码墙）？
  2. 是否有定价页面（即使是“测试期免费”）？
  3. 隐私政策+服务条款是否已上线？
  4. 是否具备PNG+SVG+方形图标+网站图标格式的Logo资源？
  5. 是否有5–8张真实截图+60–90秒演示视频？
  6. 落地页是否符合GEO要求（单个H1、有序标题层级、FAQ schema、结构化数据）？
  7. 是否至少有3个替代页面和3个使用场景页面已上线并被收录？
  8. 是否有模板库或引流资产（若符合品类特性）？
  9. 是否至少有20位测试/早期用户可在G2上留下评论？
问题1–7若答案为“否”，则属于硬性阻碍。问题8–9若答案为“否”，属于软性阻碍：可以发布，但会失去二级评论价值和Typeform式的复利增长效果。

Step 2: Choose the tiers

步骤2：选择目录层级

Full catalog in 
references/directory-list.md
. Summary:
TierWhenExamplesTypical count
Tier 1 — Flagship launchLaunch week onlyProduct Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt~15
Tier 2 — Startup/SaaSWeek 1 + rollingAlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot~15
Tier 3 — AI directoriesWeek 1–3TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage~25
Tier 4 — Agent/MCP registriesWeek 1–3 (if MCP)Glama, APITracker, LF MCP Registry, AI Agents List~10
Tier 5 — No-code directoriesWeek 1–3 (if no-code)NoCodeFinder, No Code MBA, We Are No Code~6
Tier 6 — "Best of" listiclesRolling outreachCold outreach to DR 40+ blog posts~10 inclusions
Tier 7 — Integration marketplacesWhen integrations shipZapier, HubSpot, Slack, Airtable, Notion~5
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.
完整清单位于
references/directory-list.md
。摘要如下：
层级适用时机示例典型数量
一级——旗舰发布仅发布周Product Hunt（核心）、BetaList、HN Show HN、Fazier、DevHunt~15
二级——创业/SaaS类第1周+持续提交AlternativeTo、SaaSHub、G2、Capterra、F6S、SourceForge、Slashdot~15
三级——AI类目录第1–3周TAAFT、Futurepedia、Toolify、Future Tools、aitools.inc、AIStage~25
四级——Agent/MCP注册表第1–3周（若为MCP产品）Glama、APITracker、LF MCP Registry、AI Agents List~10
五级——无代码类目录第1–3周（若无代码产品）NoCodeFinder、No Code MBA、We Are No Code~6
六级——“最佳工具”榜单持续 outreach向DR40+的博客文章进行冷 outreach~10次入选
七级——集成市场集成功能上线后Zapier、HubSpot、Slack、Airtable、Notion~5
**筛选规则：**仅提交至产品真正适配的目录。强行将产品列入错误品类会浪费首次提交的优势，且会被审核人员拒绝。

Step 3: Prepare asset variations

步骤3：准备差异化资源

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.
针对每个层级，准备独特的描述变体（取自
references/positioning-variations.md
）：
  • 标语：不超过10个单词
  • 简短描述：60字符以内
  • 详细描述：150单词以内
  • 5–8个品类标签
  • Logo资源
  • 截图+演示视频链接
  • 创始人故事（2–3句话）
**关键注意事项：**不要在所有目录中复制粘贴相同的详细描述。针对不同层级，调整开头句、功能侧重点和受众定位。AI引擎会交叉验证并降低重复内容的权重。

Step 4: Batch submit

步骤4：批量提交

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.
设置追踪电子表格（
references/submission-tracker-template.csv
）。按表格顺序从左到右处理。每批提交需2–3小时是合理预期。
单条提交流程：
  1. 复制对应层级的定位变体。
  2. 填写表单。
  3. 上传资源。
  4. 提交。
  5. 记录：日期、URL、状态、审核人员备注。
  6. 上线后，验证反向链接存在且为dofollow：执行
    curl -sIL https://directory.com/your-listing | grep -i rel=
    。若无结果，则链接为dofollow。

Product Hunt Deep Dive (The Anchor Event)

Product Hunt深度解析（核心活动）

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.
Product Hunt是杠杆效应最高的提交平台，但也最容易被浪费。2026年PH算法更看重评论质量而非点赞数——50个点赞+30条真实评论的帖子，排名高于200个点赞+5条评论的帖子。80%的失败发布都源于没有预热受众，或是只索要点赞而非反馈。

3-week prep timeline

3周准备时间表

  • 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.
  • 启动前21至14天：预热猎人账号。每天为3个发布项目点赞+撰写有深度的评论。关注100+活跃创作者。积累账号历史，让算法认为您的账号是真实用户。
  • 启动前14天：在PH创建“即将发布”页面。引导流量至此页面，收集“发布时通知我”的订阅者。
  • 启动前10天：（可选）预约猎人。不要付费——可以用功能、推广或引荐作为交换。知名猎人能为首日势头提升约15%，但并非必需。
  • 启动前7天：准备发布日资源：轮播图（1270×760）、标语、260字符描述、您发布的第一条评论、客户发布的第一条评论。
  • 启动前3天：预热邮件列表。“我们将于周二发布，以下是相关安排。若想提前收到通知，请回复。”
  • 启动前1天：最终检查——产品在无痕模式下可正常使用、视频可自动播放、CTA指向注册页面、PH预览效果正常。

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.
  • 太平洋时间凌晨12:01发布：仅在周二、周三或周四发布——周末发布的流量会减少60–70%。凌晨12:01发布能最大化利用24小时曝光窗口。
  • 前2小时至关重要：需要在前2小时获得50+支持者，以触发算法推荐。
  • 自行发布第一条评论：分享故事：您为何开发这款产品、与竞品的差异、首次使用的建议。
  • 30分钟内回复所有评论：PH会衡量创作者的响应速度。
  • 分享链接至：Twitter/X线程、LinkedIn长文、个人Slack/Discord社群、邮件列表、Indie Hackers、向每位核心用户发送私信。
  • 绝不索要点赞：索要反馈。“希望您能对我们的定位给出真实看法”的转化率比“支持我们！”高3倍，且不会触发算法的反操纵过滤器。
  • 不要私信陌生人：社区会标记此类行为，审核人员会隐藏您的帖子。

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.
  • 撰写发布复盘博客文章，包含数据+经验教训。保持诚实，不要自夸。在发布次日发布。
  • 将复盘文章交叉发布至Indie Hackers和r/SaaS（允许推广的社区）。
  • 仅当您有技术亮点可分享时（架构、DSL、创新方法），才提交至Show HN。普通的“我们发布了一款SaaS”帖子会被大量标记。

Reviews Playbook (G2 / Capterra / TrustRadius)

评论攻略（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.
G2和Capterra（截至2026年2月已被G2收购）的列表没有评论毫无价值。10条评论是登上Grid榜单的临界值。在发布月执行“30天获取10条评论”方案。

The 10-in-30 protocol

30天获取10条评论方案

  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.
  1. 发布次日：找出20位已使用产品完成关键操作的用户。
  2. 向每位用户发送个性化邮件，附带直接评论链接（可减少约70%的操作阻力）。不要使用表单或落地页——直接发送链接。
  3. 提供适度感谢：G2和TrustRadius明确允许小额激励，如25美元亚马逊礼品卡。
  4. 5天后跟进一次：不要跟进第二次——这会让用户反感，损害关系。
  5. 目标：50%转化率→从20位用户中获得10条评论。

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.
  • G2夏季报告：截止日期约为4月28日。规划评论收集活动，确保在此日期前完成。
  • G2秋季报告：截止日期约为7月28日。
  • 错过截止日期意味着要等待3个月才能获得下一次Grid榜单更新。

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.
  • “用户喜爱”徽章仍免费：需要20条评论，平均评分4.0以上。
  • Grid、Momentum、Index和奖项徽章需要付费G2计划（2025年夏季起，年费2999美元起）。
  • 第一年不要付费使用G2：免费列表+“用户喜爱”徽章已足够。

Cross-platform

跨平台策略

  • TrustRadius follows similar mechanics but smaller volume.
  • Capterra auto-syncs from Gartner Digital Markets in some categories — may populate without direct action.
  • TrustRadius机制类似，但用户量更小。
  • Capterra在部分品类中会自动从Gartner Digital Markets同步内容——无需手动操作即可填充信息。

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)

1. 替代页面（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.
竞品替代页面的转化率为5–15%，针对漏斗底部的查询甚至可达15–30%。为每个头部竞品创建一个页面：
  • /alternatives/[competitor-1]
  • /alternatives/[competitor-2]
  • /alternatives/[competitor-3]
  • /alternatives/[competitor-4]
每个页面需包含：客观的功能对比表格、“何时选择X而非我们”“何时选择我们而非X”、定价对比、3–5个使用场景示例、带schema的优质FAQ。
**关键注意事项：**保持客观。AI引擎会交叉验证竞品功能声明，对虚假内容降权。

2. Use-case / ICP pages

2. 使用场景/目标受众页面

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.
为每个目标受众（ICP）创建专属落地页：
  • /for/[audience]
    ——教练、代理机构、电商、SaaS、顾问等。
  • /use-cases/[use-case]
    ——线索资格审核、用户入职、产品推荐等。

3. Template / asset gallery (if applicable)

3. 模板/资源库（若适用）

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.
Typeform的模板库带来了3万次非品牌自然注册，年生命周期价值达300万美元。模式如下：
  • 每个模板对应一个可被收录的页面，路径为
    /templates/[slug]
    。
  • H1包含关键词、150+单词描述、截图、“何时使用此模板”、“使用此模板”CTA。
  • 每个页面底部放置相关模板（内部链接=SEO复利增长）。
  • 合理目标：第30天100个模板，第90天300个模板。

4. "Best of" listicles you wrote yourself

4. 自行撰写的“最佳工具”榜单

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.
撰写所在品类的客观榜单：
/blog/best-[category]-tools-2026
。包含自身产品+10个竞品的真实评论。这些页面会针对品类关键词排名，同时成为AI引擎引用的权威参考。

5. Integration pages (when integrations ship)

5. 集成页面（集成功能上线后）

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).
每个集成对应一个落地页，路径为
/integrations/[partner]
。遵循Zapier的策略：Zapier的程序化集成页面带来了约260万月均自然访问量（占其总自然流量的15%）。

GEO (Generative Engine Optimization)

GEO（生成引擎优化）

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.
2026年，30–50%的“工具调研”查询发生在ChatGPT、Claude、Perplexity或Google AI概览中，用户从未访问传统搜索页面。目录在这方面也很重要——AI引擎生成答案时会大量引用高DR目录的内容。但目标页面也需要进行GEO优化。

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.
  1. 每页一个H1，有序标题层级：引用率高2.8倍。87%被引用的页面都使用单个H1。
  2. 密集的事实性内容+可引用数据：AI引擎偏好具体数字（“比X快3倍”）而非模糊声明。
  3. 每个落地页添加FAQ schema：AI引擎在提取答案时会重点关注
    FAQPage
    JSON-LD。
  4. 对比表格：结构化、可提取——正是AI答案所需的内容。
  5. 前100字包含明确的“产品定义”段落。
  6. 在Reddit和Hacker News上获得引用：Claude和Perplexity会大量收录这些平台的内容。r/SaaS和HN上的真实提及会成为AI训练数据。
  7. 发布原创研究：“我们分析了10000个[对象]，发现X”会成为所有相关主题内容的主要引用来源。
  8. 认领Crunchbase、LinkedIn公司页面和Wikidata条目：这三个平台的数据都会进入AI训练语料库。
  9. 若适用，在带有A/B评级的MCP注册表上列出产品（尤其是Glama）。大语言模型（LLM）在回答MCP相关问题时会引用这些内容。

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.
每月手动检查：向ChatGPT、Claude和Perplexity提问“最佳[品类]工具有哪些？”，记录产品出现的位置。免费GEO追踪工具（GeoTracker、llmrefs）可自动完成此操作。

Community & Ongoing Distribution

社区与持续分发

Directories are one-shot. Community is ongoing. Both feed the same funnel.
目录提交是一次性操作，社区运营是长期活动。两者都服务于同一转化漏斗。

Reddit (90/10 rule)

Reddit（90/10规则）

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.
90%的活动必须是真正有帮助的内容；仅10%为推广内容。违反此规则会被 shadowban。
高价值社区（按优先级排序）：
  • r/SideProject（20万+用户）——对推广友好，欢迎发布公告。
  • r/SaaS（30万+用户）——“分享您的SaaS”帖子是明确的推广窗口。
  • r/startups（170万用户）——Feedback Friday帖子。
  • r/Entrepreneur（350万用户）——每周推广帖子。
  • r/nocode、r/IndieHackers、r/alphaandbetausers——氛围友好。
  • r/webdev、r/artificial、r/LocalLLaMA——规则严格，仅接受技术内容。
**有效内容：**真实数据（MRR、注册量、流失率）、截图、“我尝试了什么/发生了什么/我会如何改进”结构、带有明确经验教训的迷你案例研究。**无效内容：**炒作、模糊声明、“看看我的新工具”帖子、索要点赞。

LinkedIn (B2B primary channel)

LinkedIn（B2B主渠道）

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×)
80%的B2B社交线索来自LinkedIn。发布频率：每周3–5篇——太少会失去势头，太多会引发受众疲劳。
2026年按互动率排序的内容类型：
  1. 带有商业教训的个人故事（互动率为平均水平的1.5–2倍）
  2. 原创数据/研究（1.3–1.5倍）
  3. 反主流行业观点（1.2–1.5倍）
  4. 包含8–12页的文档幻灯片（1.3–1.8倍）

Twitter/X (indie hacker + dev channel)

Twitter/X（独立开发者+开发者渠道）

Build-in-public threads on architecture, revenue, decisions. Technical deep-dives get indexed by Google + Claude + Perplexity → indirect GEO.
发布关于架构、收入、决策的“公开构建”线程。技术深度文章会被Google+Claude+Perplexity收录→间接提升GEO效果。

Indie Hackers

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.
  • 在PH发布日启动“公开构建”线程。
  • 每周发布更新：收入、新功能、经验教训。即使没有收入，只要经验教训诚实，帖子也会有效。
  • 发布内容前，先评论10倍于发布量的内容以积累社区信誉。

Dev.to + Hashnode

Dev.to + Hashnode

Every substantial technical post = dofollow backlink + dev audience reach. Cross-post with canonical URL back to main blog.
每篇有深度的技术文章都会带来dofollow反向链接+开发者受众覆盖。交叉发布时，添加指向主博客的规范URL。

KPIs & Tracking

KPI与追踪

Track weekly. If a number isn't moving, investigate — don't just submit more directories.
MetricDay 0Day 30 targetDay 90 target
Domain Rating (DR)02030+
Referring domains03080+
Indexed pages—50200+
Organic clicks/day030200+
Directory listings live05070+
G2 reviews01025
Capterra reviews0515
AI citations (manual check)0315+
Signups from directory referrals050300
Signups from alt/use-case pages020300
每周追踪数据。若某项指标没有变化，需调查原因——不要盲目提交更多目录。
指标第0天第30天目标第90天目标
域名评级（DR）02030+
反向链接来源域名数03080+
被收录页面数—50200+
日均自然点击量030200+
已上线目录列表数05070+
G2评论数01025
Capterra评论数0515
AI引用次数（手动检查）0315+
目录引荐注册量050300
替代/使用场景页面注册量020300

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.
  1. 不要付费购买目录提交服务（60–200美元套餐）。这些目录提交本来就是免费的，只需花一下午复制粘贴即可。
  2. 不要提交至垃圾目录（DR低于10、无流量、无编辑质量）。它们会稀释您的反向链接档案，Google的垃圾检测系统可能会惩罚您。
  3. 不要使用错误定位提交。重新阅读各层级的定位表格。通用描述会浪费列表价值。
  4. 不要将目录提交作为唯一的GTM策略。它们只是基础。内容+社区+评论才是真正的转化引擎。
  5. 不要跳过G2/Capterra的评论。零评论列表毫无价值。要么执行30天获取10条评论方案，要么不提交。
  6. 不要在Product Hunt上索要点赞。2026年算法会惩罚此类行为。索要反馈。
  7. 不要每周修改旧目录列表。提交一次，每季度检查一次即可。
  8. 不要在目标页面存在前提交。链接权重需要有去处。
  9. 不要在不同目录中重复使用描述。AI引擎会惩罚重复内容。
  10. 不要在对比页面上造假。AI引擎会交叉验证并对虚假内容降权。
  11. 不要过度关注发布日的流量峰值。飞轮效应来自模板+替代页面+评论+持续内容——而非PH的一天曝光。
  12. 不要忘记Crunchbase、LinkedIn公司页面和Wikidata。这些平台的数据会进入AI训练语料库，对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.)
  1. 您要发布的是什么产品？（品类会影响层级组合——AI、传统SaaS、无代码还是开发者工具。）
  2. 发布日是什么时候？（第0阶段的资源需要7天准备时间。）
  3. 您是否已构建目标页面？（替代页面、使用场景、模板——若未构建，先完成此项。）
  4. 是否已预约Product Hunt猎人？（可选，但能提升约15%的首日势头。无论如何都需要3周预热。）
  5. 您可以邀请多少测试用户留下评论？（需要20位用户才能获得10条评论。）
  6. 您的产品是否有MCP或Agent相关特性？（若是，四级注册表是真正的护城河。）
  7. 是否已有集成功能？（若是，七级市场是可获得的最高DR反向链接来源。）
  8. 邮件列表规模有多大？（PH发布日需要预热流量——最低100人。）
  9. 当前DR值和反向链接来源域名数是多少？（衡量复利增长效果的基准。）

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.
当用户请求目录提交计划时，返回以下内容：
  1. 就绪度评估——第0阶段缺失哪些项，哪些会阻碍提交
  2. 层级选择——适用哪些层级，跳过哪些，原因
  3. 提交顺序——第1周/第2周/第3周的批次安排
  4. 目标页面清单——若缺失，优先构建哪些页面
  5. 定位变体——各层级的实际文案（取自
    references/positioning-variations.md
    ）
  6. Product Hunt 3周准备时间表——若已知发布日，映射到具体日期
  7. 评论30天获取10条方案——邀请对象、时间、方式
  8. 每周目标——提交的目录数、评论数、DR变化
  9. 追踪工具——
    references/submission-tracker-template.csv
    的链接或包含该CSV内容
确保计划可执行。每个项目都应是用户今天就能完成的任务。

Related Skills

相关技能

  • launch-strategy — broader launch moment, ORB framework, five-phase approach
  • programmatic-seo — destination pages (alternatives, integrations, templates) that backlinks should flow into
  • competitor-alternatives — 
    /alternatives/[tool]
    page pattern
  • ai-seo — GEO optimization for AI citation
  • content-strategy — editorial content that attracts "best of" listicle inclusions
  • free-tool-strategy — lead magnets for destination pages
  • community-marketing — Reddit, Indie Hackers, Slack community mechanics
  • schema-markup — FAQ + Product + Organization JSON-LD for GEO
  • launch-strategy——更广泛的发布阶段、ORB框架、五阶段方法
  • programmatic-seo——反向链接应指向的目标页面（替代页面、集成页面、模板）
  • competitor-alternatives——
    /alternatives/[tool]
    页面模式
  • ai-seo——针对AI引用的GEO优化
  • content-strategy——吸引“最佳工具”榜单收录的编辑内容
  • free-tool-strategy——目标页面的引流资产
  • community-marketing——Reddit、Indie Hackers、Slack社群运营机制
  • schema-markup——用于GEO的FAQ+Product+Organization JSON-LD