[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71E8ZXFD87C5QFTW0NPJQHX":3,"skill-same:01M71E8ZXFD87C5QFTW0NPJQHX":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":14,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M71E8ZXFD87C5QFTW0NPJQHX","directory-submissions",null,"When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions \"directory submissions,\" \"submit to directories,\" \"backlinks from directories,\" \"list my product,\" \"submit to Product Hunt,\" \"BetaList,\" \"TAAFT,\" \"Futurepedia,\" \"G2 listing,\" \"Capterra listing,\" \"AlternativeTo,\" \"SaaSHub,\" \"AI directories,\" \"MCP registry,\" \"agent directory,\" \"dofollow backlinks,\" \"launch directories,\" or \"directory tracker.\" Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.","patinaproject\u002Fskills","patinaproject","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229996889?v=4","01M71E58JKTDNY1138WYZK44TR","Patina Project","01M71E58K5GH4K16MV6A8BQ6NZ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdirectory-submissions\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"directory submissions","directory","product launch","saas","use","discovery","for","seo","domain","No-Code","programmatic seo","live","list","registry","ai-seo","tracker","product hunt","MCP","campaign","directories","2026-11-10 10:12:30",false,"---\nname: directory-submissions\ndescription: When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions \"directory submissions,\" \"submit to directories,\" \"backlinks from directories,\" \"list my product,\" \"submit to Product Hunt,\" \"BetaList,\" \"TAAFT,\" \"Futurepedia,\" \"G2 listing,\" \"Capterra listing,\" \"AlternativeTo,\" \"SaaSHub,\" \"AI directories,\" \"MCP registry,\" \"agent directory,\" \"dofollow backlinks,\" \"launch directories,\" or \"directory tracker.\" Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.\nmetadata:\n  version: 2.0.0\n---\n\n# Directory Submissions\n\nYou 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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\n---\n\n## Core Philosophy\n\nDirectory submissions are the **foundation layer** of distribution — never the whole strategy. They do three things well:\n\n1. **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.\n2. **Create discovery surface area** — people browsing AI\u002FSaaS directories are in-market buyers, not random traffic.\n3. **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.\n\nBut 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.**\n\nThe full directory catalog lives in `references\u002Fdirectory-list.md`. The positioning variant library lives in `references\u002Fpositioning-variations.md`. The submission tracker template lives in `references\u002Fsubmission-tracker-template.csv`.\n\n---\n\n## The Three Hard Rules\n\n### Rule 1: Foundation before submission\nNever submit to a directory until the landing page it will link to is live, indexed, and has:\n- A single `\u003Ch1>` 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.\n- A real pricing page (even \"free while in beta\" counts — most Tier 1 directories require one).\n- Privacy policy + terms.\n- Logo assets in PNG + SVG + square 1024×1024 + favicon.\n- 5–8 real product screenshots at 1920×1080 (not marketing mockups).\n- A 60–90 second demo video — products with video on Product Hunt get **2.7× more upvotes**.\n- FAQ schema markup (AI engines heavily weight `FAQPage` JSON-LD for answer extraction).\n- Structured data: `Organization`, `Product`, `SoftwareApplication`.\n\n### Rule 2: Destination pages before directories\nDirectories are the *source* of link equity. You need *destinations* that can convert the resulting traffic. Minimum destinations before submitting to anything:\n- 3–5 competitor alternative pages (`\u002Falternatives\u002F[competitor]`) targeting \"[competitor] alternative\" keywords. Comparison\u002Falternative pages convert at **5–15%** vs 0.5–2% for generic content.\n- 3–5 use-case pages (`\u002Ffor\u002F[audience]` or `\u002Fuse-cases\u002F[use-case]`).\n- Template gallery with 20+ entries (if applicable — this was Typeform's largest SEO growth driver, generating 30K non-branded signups and $3M\u002Fyear LTV).\n- 1 \"best of\" blog post you wrote yourself about your own category, including honest coverage of competitors.\n\n### Rule 3: Positioning varies by directory type\nNever copy-paste the same description everywhere. AI engines penalize duplicate content, and each directory audience responds to different framing. See `references\u002Fpositioning-variations.md` for the full variant library. Short version:\n\n| Surface | Lead with | Why |\n|---|---|---|\n| Startup directories | **Outcome** | Audience is other founders. They care what it does. |\n| SaaS directories | **Alternative framing** | People search \"[competitor] alternative\" — meet them there. |\n| AI directories | **AI-first architecture** | TAAFT\u002FFuturepedia audiences explicitly want AI tools. |\n| Agent\u002FMCP directories | **Agent\u002FMCP angle** | Niche but high-intent. A real moat. |\n| No-code directories | **Ease + power** | Audience values speed-to-build over depth. |\n| Dev directories | **Technical depth** | Dev audiences reward technical substance. |\n| B2B review sites | **ROI + use case** | Buyers want outcomes and case studies. |\n\n---\n\n## Workflow\n\n### Step 1: Readiness assessment (Phase 0)\n\nAsk the user these 9 questions. If any are \"no\", they're not ready — help them build the missing piece first.\n\n1. Is the product publicly accessible (no password wall)?\n2. Is there a pricing page (even \"free while in beta\")?\n3. Are privacy policy + terms live?\n4. Logo assets in PNG + SVG + square + favicon?\n5. 5–8 real screenshots + 60–90s demo video?\n6. Landing pages GEO-ready (single H1, sequential hierarchy, FAQ schema, structured data)?\n7. At least 3 alternative pages and 3 use-case pages live and indexed?\n8. Template gallery or lead magnet asset (if applicable to category)?\n9. At least 20 beta\u002Fearly users who could leave a review on G2?\n\nA \"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.\n\n### Step 2: Choose the tiers\n\nFull catalog in `references\u002Fdirectory-list.md`. Summary:\n\n| Tier | When | Examples | Typical count |\n|---|---|---|---|\n| **Tier 1 — Flagship launch** | Launch week only | Product Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt | ~15 |\n| **Tier 2 — Startup\u002FSaaS** | Week 1 + rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot | ~50 |\n| **Tier 3 — AI directories** | Week 1–3 | TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage | ~40 |\n| **Tier 4 — Agent\u002FMCP registries** | Week 1–3 (if MCP) | Glama, APITracker, LF MCP Registry, AI Agents List | ~10 |\n| **Tier 5 — No-code directories** | Week 1–3 (if no-code) | NoCodeFinder, No Code MBA, We Are No Code, MakerPad | ~8 |\n| **Tier 6 — \"Best of\" listicles** | Rolling outreach | Cold outreach to DR 40+ blog posts | ~10 inclusions |\n| **Tier 7 — Integration marketplaces** | When integrations ship | Zapier, HubSpot, Slack, Airtable, Notion | ~5 |\n| **Tier 8 — Profile & content platforms** | Rolling | GitHub, WordPress.com, Substack, Dev.to, SlideShare, Behance | ~50 |\n| **Tier 9 — Local business directories** | Rolling (if applicable) | Manta, Hotfrog, Locanto, MerchantCircle | ~20 |\n| **Tier 10 — Forums & communities** | Rolling (participate first) | SitePoint, GrowthHackers, Warrior Forum, Designer News | ~13 |\n| **Tier 11 — Press release & article sites** | Launch + milestones | PRLog, PR.com, EzineArticles, Feedspot | ~25 |\n| **Tier 12 — Social bookmarking** | Rolling | Scoop.it, Diigo, Pearltrees | ~5 |\n| **Tier 13 — Niche vertical directories** | When vertical fits | Justia (legal), Porch (home), LandBook (design), etc. | ~20 |\n\n**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.\n\n### Step 3: Prepare asset variations\n\nFor each tier, prep a distinct description variant (pulled from `references\u002Fpositioning-variations.md`):\n- **Tagline** under 10 words\n- **Short description** at 60 chars\n- **Long description** at 150 words\n- **5–8 category tags**\n- **Logo** assets\n- **Screenshots** + demo video URL\n- **Founder story** (2–3 sentences)\n\n**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.\n\n### Step 4: Batch submit\n\nSet up the tracker spreadsheet (`references\u002Fsubmission-tracker-template.csv`). Work left-to-right through it. 2–3 hours per batch is realistic.\n\nPer submission:\n1. Copy the tier-appropriate positioning variant.\n2. Fill in the form.\n3. Upload assets.\n4. Submit.\n5. Log: date, URL, status, moderator notes.\n6. Once live, verify the backlink exists and is dofollow: `curl -sIL https:\u002F\u002Fdirectory.com\u002Fyour-listing | grep -i rel=`. If absent, the link is dofollow.\n\n---\n\n## Product Hunt Deep Dive (The Anchor Event)\n\nProduct 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.\n\n### 3-week prep timeline\n\n- **Day -21 to -14:** Warm up hunter account. Upvote + thoughtfully comment on 3 launches\u002Fday. Follow 100+ active makers. Build history so your account looks real to the algorithm.\n- **Day -14:** Create \"Upcoming\" page on PH. Drive traffic to it to collect \"notify on launch\" subscribers.\n- **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.\n- **Day -7:** Draft launch-day assets: gallery images (1270×760), tagline, 260-char description, first comment from you, first comment from a customer.\n- **Day -3:** Email list warm-up. \"We're launching Tuesday. Here's what to expect. Reply if you want a heads up.\"\n- **Day -1:** Final check — product works in incognito, video autoplays, CTA goes to signup, PH listing preview looks right.\n\n### Launch day execution\n\n- **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.\n- **First 2 hours are everything.** Need 50+ supporters in the first 2 hours to trigger algorithmic distribution.\n- **Post the first comment yourself** with the story: why you built it, what's different, what to try first.\n- **Reply to every comment** in under 30 minutes. PH measures maker responsiveness.\n- **Share the link to:** Twitter\u002FX thread, LinkedIn long-form post, personal Slack\u002FDiscord communities, your email list, Indie Hackers, every power user via DM.\n- **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.\n- **Don't message strangers.** The community flags this and moderators will hide your post.\n\n### Post-launch\n\n- Write a launch recap blog post with numbers + lessons. Honest, not bragging. Publish on day 2.\n- Cross-post the recap to Indie Hackers and r\u002FSaaS (where promotion is allowed).\n- 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.\n\n---\n\n## Reviews Playbook (G2 \u002F Capterra \u002F TrustRadius)\n\nG2 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.\n\n### The 10-in-30 protocol\n\n1. **Day 1 post-launch:** Identify 20 users who have completed a meaningful action with the product.\n2. **Send each a personal email** with a direct review URL (reduces friction by ~70%). No forms, no landing pages — direct link.\n3. **Offer a modest thank-you.** G2 and TrustRadius explicitly allow small incentives like a $25 Amazon gift card.\n4. **Follow up once** after 5 days. Don't follow up twice — it becomes annoying and damages the relationship.\n5. **Target:** 50% conversion → 10 reviews from 20 asks.\n\n### Critical deadlines\n\n- **G2 Summer reports:** cut off ~April 28. Plan review drives to land before this.\n- **G2 Fall reports:** cut off ~July 28.\n- Missing a cutoff means waiting 3 months for the next grid update.\n\n### Badges and paid plans\n\n- **\"Users Love Us\" badge** is still free: requires 20 reviews at 4.0+ average.\n- **Grid, Momentum, Index, and Award badges** require a paid G2 plan ($2,999+\u002Fyear starting Summer 2025).\n- **Do not spend on paid G2 in year one.** The free listing + Users Love Us badge is sufficient.\n\n### Cross-platform\n\n- TrustRadius follows similar mechanics but smaller volume.\n- Capterra auto-syncs from Gartner Digital Markets in some categories — may populate without direct action.\n\n---\n\n## Destination Pages Strategy (What the Backlinks Point At)\n\nDirectories are useless if the backlinks land on a generic homepage. Build these destination pages *before* submitting:\n\n### 1. Alternative pages (highest ROI)\n\nCompetitor alternative pages convert at **5–15%**, often hitting 15–30% for bottom-of-funnel queries. One page per top competitor:\n\n- `\u002Falternatives\u002F[competitor-1]`\n- `\u002Falternatives\u002F[competitor-2]`\n- `\u002Falternatives\u002F[competitor-3]`\n- `\u002Falternatives\u002F[competitor-4]`\n\nEach 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.\n\n**Critical:** Be honest. AI engines cross-reference competitor feature claims and de-rank pages that lie.\n\n### 2. Use-case \u002F ICP pages\n\nEvery ICP gets a dedicated landing page:\n- `\u002Ffor\u002F[audience]` — coaches, agencies, ecommerce, SaaS, consultants, etc.\n- `\u002Fuse-cases\u002F[use-case]` — lead qualification, onboarding, product recommendations, etc.\n\n### 3. Template \u002F asset gallery (if applicable)\n\nTypeform's template library generated **30,000 non-branded organic signups and $3M\u002Fyear LTV**. The pattern:\n- One indexable page per template at `\u002Ftemplates\u002F[slug]`.\n- H1 with the keyword, 150+ word description, screenshot, \"when to use this,\" \"use this template\" CTA.\n- Related templates at the bottom of each page (internal linking = SEO compounding).\n- 100 templates by day 30, 300 by day 90 is the realistic target.\n\n### 4. \"Best of\" listicles you wrote yourself\n\nWrite honest roundups of your own category: `\u002Fblog\u002Fbest-[category]-tools-2026`. Include yourself + 10 competitors with real reviews. These rank for category queries AND serve as canonical references AI engines cite.\n\n### 5. Integration pages (when integrations ship)\n\nEvery integration = one landing page at `\u002Fintegrations\u002F[partner]`. Follows the Zapier playbook: Zapier gets **~2.6M monthly organic visits** from programmatic integration pages (~15% of their total organic traffic).\n\n---\n\n## GEO (Generative Engine Optimization)\n\nIn 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.\n\n### Tactics that get pages cited\n\n1. **One H1 per page, sequential heading hierarchy.** 2.8× higher citation rate. 87% of cited pages use a single H1.\n2. **Dense, factual content with citable stats.** AI engines prefer specific numbers (\"3× faster than X\") over vague claims.\n3. **FAQ schema on every landing page.** AI engines heavily weight `FAQPage` JSON-LD for answer extraction.\n4. **Comparison tables.** Extractable, structured — exactly what an AI answer needs.\n5. **Explicit \"what it is\" paragraph in the first 100 words.**\n6. **Get cited on Reddit and Hacker News.** Claude and Perplexity index these heavily. Genuine mentions on r\u002FSaaS and HN count as training fuel.\n7. **Publish original research.** \"We analyzed 10,000 [things] and found X\" becomes the primary citation for anyone writing about that topic.\n8. **Claim Crunchbase, LinkedIn company page, and Wikidata entries.** All three feed AI training corpora.\n9. **If applicable, list on MCP registries with A\u002FB grades** (Glama in particular). LLMs pull from these when answering MCP questions.\n\n### Measurement\n\nManually 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.\n\n---\n\n## Community & Ongoing Distribution\n\nDirectories are one-shot. Community is ongoing. Both feed the same funnel.\n\n### Reddit (90\u002F10 rule)\n\n90% of activity must be genuinely helpful; only 10% promotional. Violating this gets shadowbanned.\n\n**High-value subs (ranked):**\n- **r\u002FSideProject** (200K+) — friendly to promo, launch announcements welcome.\n- **r\u002FSaaS** (300K+) — \"Share Your SaaS\" threads are explicit promo windows.\n- **r\u002Fstartups** (1.7M) — Feedback Friday thread.\n- **r\u002FEntrepreneur** (3.5M) — weekly promo thread.\n- **r\u002Fnocode**, **r\u002FIndieHackers**, **r\u002Falphaandbetausers** — friendly.\n- **r\u002Fwebdev**, **r\u002Fartificial**, **r\u002FLocalLLaMA** — strict, technical only.\n\n**What wins:** real numbers (MRR, signups, churn), screenshots, \"what I tried \u002F what happened \u002F 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.\n\n### LinkedIn (B2B primary channel)\n\n80% of B2B social leads come from LinkedIn. Cadence: **3–5 posts\u002Fweek** — fewer loses momentum, more causes fatigue.\n\nContent types ranked by 2026 engagement:\n1. Personal stories with business lessons (1.5–2× avg engagement)\n2. Original data \u002F research (1.3–1.5×)\n3. Contrarian industry takes (1.2–1.5×)\n4. Document carousels with 8–12 slides (1.3–1.8×)\n\n### Twitter\u002FX (indie hacker + dev channel)\n\nBuild-in-public threads on architecture, revenue, decisions. Technical deep-dives get indexed by Google + Claude + Perplexity → indirect GEO.\n\n### Indie Hackers\n\n- Launch a build-in-public thread on PH launch day.\n- Post weekly updates: revenue, ships, lessons. Zero-revenue posts work if the lesson is honest.\n- Comment 10× more than you post to build karma before your own links.\n\n### Dev.to + Hashnode\n\nEvery substantial technical post = dofollow backlink + dev audience reach. Cross-post with canonical URL back to main blog.\n\n---\n\n## KPIs & Tracking\n\nTrack weekly. If a number isn't moving, investigate — don't just submit more directories.\n\n| Metric | Day 0 | Day 30 target | Day 90 target |\n|---|---|---|---|\n| Domain Rating (DR) | 0 | 20 | 30+ |\n| Referring domains | 0 | 30 | 80+ |\n| Indexed pages | — | 50 | 200+ |\n| Organic clicks\u002Fday | 0 | 30 | 200+ |\n| Directory listings live | 0 | 50 | 70+ |\n| G2 reviews | 0 | 10 | 25 |\n| Capterra reviews | 0 | 5 | 15 |\n| AI citations (manual check) | 0 | 3 | 15+ |\n| Signups from directory referrals | 0 | 50 | 300 |\n| Signups from alt\u002Fuse-case pages | 0 | 20 | 300 |\n\n---\n\n## What NOT to Do\n\n1. **Don't pay for directory submission services** ($60–$200 packages). The whole point is these are free. It's an afternoon of copy-paste.\n2. **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.\n3. **Don't submit with the wrong positioning.** Re-read the positioning table per tier. Generic descriptions waste the listing.\n4. **Don't treat directories as your entire GTM.** They're the foundation. Content + community + reviews are what actually convert.\n5. **Don't skip reviews on G2\u002FCapterra.** Zero-review listings are dead. Run the 10-in-30 protocol or don't submit.\n6. **Don't ask for upvotes on Product Hunt.** The 2026 algorithm penalizes it. Ask for **feedback**.\n7. **Don't amend old directory listings every week.** Submit once, check quarterly.\n8. **Don't submit before the destination page exists.** Link equity needs a destination.\n9. **Don't duplicate descriptions across directories.** AI engines penalize duplicate content.\n10. **Don't lie on comparison pages.** AI engines cross-reference and de-rank lies.\n11. **Don't over-index on launch-day spike.** The flywheel is templates + alternatives + reviews + ongoing content — not one day of PH.\n12. **Don't forget Crunchbase, LinkedIn company page, and Wikidata.** These feed AI training corpora and matter for GEO.\n\n---\n\n## Task-Specific Questions\n\n1. **What are you launching?** (Category changes tier mix — AI vs traditional SaaS vs no-code vs dev tool.)\n2. **When is launch day?** (Phase 0 assets need 7 days of prep.)\n3. **Do you have destination pages built?** (Alternatives, use cases, templates — if not, build first.)\n4. **Product Hunt hunter lined up?** (Optional but adds ~15% day-one lift. 3-week warm-up required regardless.)\n5. **How many beta users can you ask for reviews?** (Need 20 to hit 10.)\n6. **Do you have an MCP or agent angle?** (If yes, Tier 4 registries are a real moat.)\n7. **Existing integrations?** (If yes, Tier 7 marketplaces are the highest-DR backlinks available.)\n8. **Email list size?** (Needed for PH launch day warm traffic — 100+ is the minimum.)\n9. **Current DR and referring domain count?** (Baseline for measuring the compounding effect.)\n\n---\n\n## Output Format\n\nWhen the user asks for a directory plan, return:\n\n1. **Readiness assessment** — which Phase 0 items are missing, which block submission\n2. **Tier selection** — which tiers apply, which to skip, why\n3. **Submission order** — week 1 \u002F week 2 \u002F week 3 batches\n4. **Destination page list** — what to build first if missing\n5. **Positioning variants** — the actual copy per tier (from `references\u002Fpositioning-variations.md`)\n6. **PH 3-week prep timeline** — mapped to calendar dates if launch day known\n7. **Reviews 10-in-30 plan** — who to ask, when, how\n8. **Weekly targets** — directories submitted, reviews, DR movement\n9. **Tracker** — link to or include the CSV from `references\u002Fsubmission-tracker-template.csv`\n\nKeep the plan actionable. Every item should be something the user can do today.\n\n---\n\n## Related Skills\n\n- **launch** — broader launch moment, ORB framework, five-phase approach\n- **programmatic-seo** — destination pages (alternatives, integrations, templates) that backlinks should flow into\n- **competitors** — `\u002Falternatives\u002F[tool]` page pattern\n- **ai-seo** — GEO optimization for AI citation\n- **content-strategy** — editorial content that attracts \"best of\" listicle inclusions\n- **free-tools** — lead magnets for destination pages\n- **community-marketing** — Reddit, Indie Hackers, Slack community mechanics\n- **schema** — FAQ + Product + Organization JSON-LD for GEO\n","# Directory Submissions\n\nYou 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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\n---\n\n## Core Philosophy\n\nDirectory submissions are the **foundation layer** of distribution — never the whole strategy. They do three things well:\n\n1. **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.\n2. **Create discovery surface area** — people browsing AI\u002FSaaS directories are in-market buyers, not random traffic.\n3. **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.\n\nBut 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.**\n\nThe full directory catalog lives in `references\u002Fdirectory-list.md`. The positioning variant library lives in `references\u002Fpositioning-variations.md`. The submission tracker template lives in `references\u002Fsubmission-tracker-template.csv`.\n\n---\n\n## The Three Hard Rules\n\n### Rule 1: Foundation before submission\nNever submit to a directory until the landing page it will link to is live, indexed, and has:\n- A single `\u003Ch1>` 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.\n- A real pricing page (even \"free while in beta\" counts — most Tier 1 directories require one).\n- Privacy policy + terms.\n- Logo assets in PNG + SVG + square 1024×1024 + favicon.\n- 5–8 real product screenshots at 1920×1080 (not marketing mockups).\n- A 60–90 second demo video — products with video on Product Hunt get **2.7× more upvotes**.\n- FAQ schema markup (AI engines heavily weight `FAQPage` JSON-LD for answer extraction).\n- Structured data: `Organization`, `Product`, `SoftwareApplication`.\n\n### Rule 2: Destination pages before directories\nDirectories are the *source* of link equity. You need *destinations* that can convert the resulting traffic. Minimum destinations before submitting to anything:\n- 3–5 competitor alternative pages (`\u002Falternatives\u002F[competitor]`) targeting \"[competitor] alternative\" keywords. Comparison\u002Falternative pages convert at **5–15%** vs 0.5–2% for generic content.\n- 3–5 use-case pages (`\u002Ffor\u002F[audience]` or `\u002Fuse-cases\u002F[use-case]`).\n- Template gallery with 20+ entries (if applicable — this was Typeform's largest SEO growth driver, generating 30K non-branded signups and $3M\u002Fyear LTV).\n- 1 \"best of\" blog post you wrote yourself about your own category, including honest coverage of competitors.\n\n### Rule 3: Positioning varies by directory type\nNever copy-paste the same description everywhere. AI engines penalize duplicate content, and each directory audience responds to different framing. See `references\u002Fpositioning-variations.md` for the full variant library. Short version:\n\n| Surface | Lead with | Why |\n|---|---|---|\n| Startup directories | **Outcome** | Audience is other founders. They care what it does. |\n| SaaS directories | **Alternative framing** | People search \"[competitor] alternative\" — meet them there. |\n| AI directories | **AI-first architecture** | TAAFT\u002FFuturepedia audiences explicitly want AI tools. |\n| Agent\u002FMCP directories | **Agent\u002FMCP angle** | Niche but high-intent. A real moat. |\n| No-code directories | **Ease + power** | Audience values speed-to-build over depth. |\n| Dev directories | **Technical depth** | Dev audiences reward technical substance. |\n| B2B review sites | **ROI + use case** | Buyers want outcomes and case studies. |\n\n---\n\n## Workflow\n\n### Step 1: Readiness assessment (Phase 0)\n\nAsk the user these 9 questions. If any are \"no\", they're not ready — help them build the missing piece first.\n\n1. Is the product publicly accessible (no password wall)?\n2. Is there a pricing page (even \"free while in beta\")?\n3. Are privacy policy + terms live?\n4. Logo assets in PNG + SVG + square + favicon?\n5. 5–8 real screenshots + 60–90s demo video?\n6. Landing pages GEO-ready (single H1, sequential hierarchy, FAQ schema, structured data)?\n7. At least 3 alternative pages and 3 use-case pages live and indexed?\n8. Template gallery or lead magnet asset (if applicable to category)?\n9. At least 20 beta\u002Fearly users who could leave a review on G2?\n\nA \"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.\n\n### Step 2: Choose the tiers\n\nFull catalog in `references\u002Fdirectory-list.md`. Summary:\n\n| Tier | When | Examples | Typical count |\n|---|---|---|---|\n| **Tier 1 — Flagship launch** | Launch week only | Product Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt | ~15 |\n| **Tier 2 — Startup\u002FSaaS** | Week 1 + rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot | ~50 |\n| **Tier 3 — AI directories** | Week 1–3 | TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage | ~40 |\n| **Tier 4 — Agent\u002FMCP registries** | Week 1–3 (if MCP) | Glama, APITracker, LF MCP Registry, AI Agents List | ~10 |\n| **Tier 5 — No-code directories** | Week 1–3 (if no-code) | NoCodeFinder, No Code MBA, We Are No Code, MakerPad | ~8 |\n| **Tier 6 — \"Best of\" listicles** | Rolling outreach | Cold outreach to DR 40+ blog posts | ~10 inclusions |\n| **Tier 7 — Integration marketplaces** | When integrations ship | Zapier, HubSpot, Slack, Airtable, Notion | ~5 |\n| **Tier 8 — Profile & content platforms** | Rolling | GitHub, WordPress.com, Substack, Dev.to, SlideShare, Behance | ~50 |\n| **Tier 9 — Local business directories** | Rolling (if applicable) | Manta, Hotfrog, Locanto, MerchantCircle | ~20 |\n| **Tier 10 — Forums & communities** | Rolling (participate first) | SitePoint, GrowthHackers, Warrior Forum, Designer News | ~13 |\n| **Tier 11 — Press release & article sites** | Launch + milestones | PRLog, PR.com, EzineArticles, Feedspot | ~25 |\n| **Tier 12 — Social bookmarking** | Rolling | Scoop.it, Diigo, Pearltrees | ~5 |\n| **Tier 13 — Niche vertical directories** | When vertical fits | Justia (legal), Porch (home), LandBook (design), etc. | ~20 |\n\n**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.\n\n### Step 3: Prepare asset variations\n\nFor each tier, prep a distinct description variant (pulled from `references\u002Fpositioning-variations.md`):\n- **Tagline** under 10 words\n- **Short description** at 60 chars\n- **Long description** at 150 words\n- **5–8 category tags**\n- **Logo** assets\n- **Screenshots** + demo video URL\n- **Founder story** (2–3 sentences)\n\n**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.\n\n### Step 4: Batch submit\n\nSet up the tracker spreadsheet (`references\u002Fsubmission-tracker-template.csv`). Work left-to-right through it. 2–3 hours per batch is realistic.\n\nPer submission:\n1. Copy the tier-appropriate positioning variant.\n2. Fill in the form.\n3. Upload assets.\n4. Submit.\n5. Log: date, URL, status, moderator notes.\n6. Once live, verify the backlink exists and is dofollow: `curl -sIL https:\u002F\u002Fdirectory.com\u002Fyour-listing | grep -i rel=`. If absent, the link is dofollow.\n\n---\n\n## Product Hunt Deep Dive (The Anchor Event)\n\nProduct 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.\n\n### 3-week prep timeline\n\n- **Day -21 to -14:** Warm up hunter account. Upvote + thoughtfully comment on 3 launches\u002Fday. Follow 100+ active makers. Build history so your account looks real to the algorithm.\n- **Day -14:** Create \"Upcoming\" page on PH. Drive traffic to it to collect \"notify on launch\" subscribers.\n- **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.\n- **Day -7:** Draft launch-day assets: gallery images (1270×760), tagline, 260-char description, first comment from you, first comment from a customer.\n- **Day -3:** Email list warm-up. \"We're launching Tuesday. Here's what to expect. Reply if you want a heads up.\"\n- **Day -1:** Final check — product works in incognito, video autoplays, CTA goes to signup, PH listing preview looks right.\n\n### Launch day execution\n\n- **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.\n- **First 2 hours are everything.** Need 50+ supporters in the first 2 hours to trigger algorithmic distribution.\n- **Post the first comment yourself** with the story: why you built it, what's different, what to try first.\n- **Reply to every comment** in under 30 minutes. PH measures maker responsiveness.\n- **Share the link to:** Twitter\u002FX thread, LinkedIn long-form post, personal Slack\u002FDiscord communities, your email list, Indie Hackers, every power user via DM.\n- **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.\n- **Don't message strangers.** The community flags this and moderators will hide your post.\n\n### Post-launch\n\n- Write a launch recap blog post with numbers + lessons. Honest, not bragging. Publish on day 2.\n- Cross-post the recap to Indie Hackers and r\u002FSaaS (where promotion is allowed).\n- 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.\n\n---\n\n## Reviews Playbook (G2 \u002F Capterra \u002F TrustRadius)\n\nG2 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.\n\n### The 10-in-30 protocol\n\n1. **Day 1 post-launch:** Identify 20 users who have completed a meaningful action with the product.\n2. **Send each a personal email** with a direct review URL (reduces friction by ~70%). No forms, no landing pages — direct link.\n3. **Offer a modest thank-you.** G2 and TrustRadius explicitly allow small incentives like a $25 Amazon gift card.\n4. **Follow up once** after 5 days. Don't follow up twice — it becomes annoying and damages the relationship.\n5. **Target:** 50% conversion → 10 reviews from 20 asks.\n\n### Critical deadlines\n\n- **G2 Summer reports:** cut off ~April 28. Plan review drives to land before this.\n- **G2 Fall reports:** cut off ~July 28.\n- Missing a cutoff means waiting 3 months for the next grid update.\n\n### Badges and paid plans\n\n- **\"Users Love Us\" badge** is still free: requires 20 reviews at 4.0+ average.\n- **Grid, Momentum, Index, and Award badges** require a paid G2 plan ($2,999+\u002Fyear starting Summer 2025).\n- **Do not spend on paid G2 in year one.** The free listing + Users Love Us badge is sufficient.\n\n### Cross-platform\n\n- TrustRadius follows similar mechanics but smaller volume.\n- Capterra auto-syncs from Gartner Digital Markets in some categories — may populate without direct action.\n\n---\n\n## Destination Pages Strategy (What the Backlinks Point At)\n\nDirectories are useless if the backlinks land on a generic homepage. Build these destination pages *before* submitting:\n\n### 1. Alternative pages (highest ROI)\n\nCompetitor alternative pages convert at **5–15%**, often hitting 15–30% for bottom-of-funnel queries. One page per top competitor:\n\n- `\u002Falternatives\u002F[competitor-1]`\n- `\u002Falternatives\u002F[competitor-2]`\n- `\u002Falternatives\u002F[competitor-3]`\n- `\u002Falternatives\u002F[competitor-4]`\n\nEach 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.\n\n**Critical:** Be honest. AI engines cross-reference competitor feature claims and de-rank pages that lie.\n\n### 2. Use-case \u002F ICP pages\n\nEvery ICP gets a dedicated landing page:\n- `\u002Ffor\u002F[audience]` — coaches, agencies, ecommerce, SaaS, consultants, etc.\n- `\u002Fuse-cases\u002F[use-case]` — lead qualification, onboarding, product recommendations, etc.\n\n### 3. Template \u002F asset gallery (if applicable)\n\nTypeform's template library generated **30,000 non-branded organic signups and $3M\u002Fyear LTV**. The pattern:\n- One indexable page per template at `\u002Ftemplates\u002F[slug]`.\n- H1 with the keyword, 150+ word description, screenshot, \"when to use this,\" \"use this template\" CTA.\n- Related templates at the bottom of each page (internal linking = SEO compounding).\n- 100 templates by day 30, 300 by day 90 is the realistic target.\n\n### 4. \"Best of\" listicles you wrote yourself\n\nWrite honest roundups of your own category: `\u002Fblog\u002Fbest-[category]-tools-2026`. Include yourself + 10 competitors with real reviews. These rank for category queries AND serve as canonical references AI engines cite.\n\n### 5. Integration pages (when integrations ship)\n\nEvery integration = one landing page at `\u002Fintegrations\u002F[partner]`. Follows the Zapier playbook: Zapier gets **~2.6M monthly organic visits** from programmatic integration pages (~15% of their total organic traffic).\n\n---\n\n## GEO (Generative Engine Optimization)\n\nIn 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.\n\n### Tactics that get pages cited\n\n1. **One H1 per page, sequential heading hierarchy.** 2.8× higher citation rate. 87% of cited pages use a single H1.\n2. **Dense, factual content with citable stats.** AI engines prefer specific numbers (\"3× faster than X\") over vague claims.\n3. **FAQ schema on every landing page.** AI engines heavily weight `FAQPage` JSON-LD for answer extraction.\n4. **Comparison tables.** Extractable, structured — exactly what an AI answer needs.\n5. **Explicit \"what it is\" paragraph in the first 100 words.**\n6. **Get cited on Reddit and Hacker News.** Claude and Perplexity index these heavily. Genuine mentions on r\u002FSaaS and HN count as training fuel.\n7. **Publish original research.** \"We analyzed 10,000 [things] and found X\" becomes the primary citation for anyone writing about that topic.\n8. **Claim Crunchbase, LinkedIn company page, and Wikidata entries.** All three feed AI training corpora.\n9. **If applicable, list on MCP registries with A\u002FB grades** (Glama in particular). LLMs pull from these when answering MCP questions.\n\n### Measurement\n\nManually 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.\n\n---\n\n## Community & Ongoing Distribution\n\nDirectories are one-shot. Community is ongoing. Both feed the same funnel.\n\n### Reddit (90\u002F10 rule)\n\n90% of activity must be genuinely helpful; only 10% promotional. Violating this gets shadowbanned.\n\n**High-value subs (ranked):**\n- **r\u002FSideProject** (200K+) — friendly to promo, launch announcements welcome.\n- **r\u002FSaaS** (300K+) — \"Share Your SaaS\" threads are explicit promo windows.\n- **r\u002Fstartups** (1.7M) — Feedback Friday thread.\n- **r\u002FEntrepreneur** (3.5M) — weekly promo thread.\n- **r\u002Fnocode**, **r\u002FIndieHackers**, **r\u002Falphaandbetausers** — friendly.\n- **r\u002Fwebdev**, **r\u002Fartificial**, **r\u002FLocalLLaMA** — strict, technical only.\n\n**What wins:** real numbers (MRR, signups, churn), screenshots, \"what I tried \u002F what happened \u002F 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.\n\n### LinkedIn (B2B primary channel)\n\n80% of B2B social leads come from LinkedIn. Cadence: **3–5 posts\u002Fweek** — fewer loses momentum, more causes fatigue.\n\nContent types ranked by 2026 engagement:\n1. Personal stories with business lessons (1.5–2× avg engagement)\n2. Original data \u002F research (1.3–1.5×)\n3. Contrarian industry takes (1.2–1.5×)\n4. Document carousels with 8–12 slides (1.3–1.8×)\n\n### Twitter\u002FX (indie hacker + dev channel)\n\nBuild-in-public threads on architecture, revenue, decisions. Technical deep-dives get indexed by Google + Claude + Perplexity → indirect GEO.\n\n### Indie Hackers\n\n- Launch a build-in-public thread on PH launch day.\n- Post weekly updates: revenue, ships, lessons. Zero-revenue posts work if the lesson is honest.\n- Comment 10× more than you post to build karma before your own links.\n\n### Dev.to + Hashnode\n\nEvery substantial technical post = dofollow backlink + dev audience reach. Cross-post with canonical URL back to main blog.\n\n---\n\n## KPIs & Tracking\n\nTrack weekly. If a number isn't moving, investigate — don't just submit more directories.\n\n| Metric | Day 0 | Day 30 target | Day 90 target |\n|---|---|---|---|\n| Domain Rating (DR) | 0 | 20 | 30+ |\n| Referring domains | 0 | 30 | 80+ |\n| Indexed pages | — | 50 | 200+ |\n| Organic clicks\u002Fday | 0 | 30 | 200+ |\n| Directory listings live | 0 | 50 | 70+ |\n| G2 reviews | 0 | 10 | 25 |\n| Capterra reviews | 0 | 5 | 15 |\n| AI citations (manual check) | 0 | 3 | 15+ |\n| Signups from directory referrals | 0 | 50 | 300 |\n| Signups from alt\u002Fuse-case pages | 0 | 20 | 300 |\n\n---\n\n## What NOT to Do\n\n1. **Don't pay for directory submission services** ($60–$200 packages). The whole point is these are free. It's an afternoon of copy-paste.\n2. **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.\n3. **Don't submit with the wrong positioning.** Re-read the positioning table per tier. Generic descriptions waste the listing.\n4. **Don't treat directories as your entire GTM.** They're the foundation. Content + community + reviews are what actually convert.\n5. **Don't skip reviews on G2\u002FCapterra.** Zero-review listings are dead. Run the 10-in-30 protocol or don't submit.\n6. **Don't ask for upvotes on Product Hunt.** The 2026 algorithm penalizes it. Ask for **feedback**.\n7. **Don't amend old directory listings every week.** Submit once, check quarterly.\n8. **Don't submit before the destination page exists.** Link equity needs a destination.\n9. **Don't duplicate descriptions across directories.** AI engines penalize duplicate content.\n10. **Don't lie on comparison pages.** AI engines cross-reference and de-rank lies.\n11. **Don't over-index on launch-day spike.** The flywheel is templates + alternatives + reviews + ongoing content — not one day of PH.\n12. **Don't forget Crunchbase, LinkedIn company page, and Wikidata.** These feed AI training corpora and matter for GEO.\n\n---\n\n## Task-Specific Questions\n\n1. **What are you launching?** (Category changes tier mix — AI vs traditional SaaS vs no-code vs dev tool.)\n2. **When is launch day?** (Phase 0 assets need 7 days of prep.)\n3. **Do you have destination pages built?** (Alternatives, use cases, templates — if not, build first.)\n4. **Product Hunt hunter lined up?** (Optional but adds ~15% day-one lift. 3-week warm-up required regardless.)\n5. **How many beta users can you ask for reviews?** (Need 20 to hit 10.)\n6. **Do you have an MCP or agent angle?** (If yes, Tier 4 registries are a real moat.)\n7. **Existing integrations?** (If yes, Tier 7 marketplaces are the highest-DR backlinks available.)\n8. **Email list size?** (Needed for PH launch day warm traffic — 100+ is the minimum.)\n9. **Current DR and referring domain count?** (Baseline for measuring the compounding effect.)\n\n---\n\n## Output Format\n\nWhen the user asks for a directory plan, return:\n\n1. **Readiness assessment** — which Phase 0 items are missing, which block submission\n2. **Tier selection** — which tiers apply, which to skip, why\n3. **Submission order** — week 1 \u002F week 2 \u002F week 3 batches\n4. **Destination page list** — what to build first if missing\n5. **Positioning variants** — the actual copy per tier (from `references\u002Fpositioning-variations.md`)\n6. **PH 3-week prep timeline** — mapped to calendar dates if launch day known\n7. **Reviews 10-in-30 plan** — who to ask, when, how\n8. **Weekly targets** — directories submitted, reviews, DR movement\n9. **Tracker** — link to or include the CSV from `references\u002Fsubmission-tracker-template.csv`\n\nKeep the plan actionable. Every item should be something the user can do today.\n\n---\n\n## Related Skills\n\n- **launch** — broader launch moment, ORB framework, five-phase approach\n- **programmatic-seo** — destination pages (alternatives, integrations, templates) that backlinks should flow into\n- **competitors** — `\u002Falternatives\u002F[tool]` page pattern\n- **ai-seo** — GEO optimization for AI citation\n- **content-strategy** — editorial content that attracts \"best of\" listicle inclusions\n- **free-tools** — lead magnets for destination pages\n- **community-marketing** — Reddit, Indie Hackers, Slack community mechanics\n- **schema** — FAQ + Product + Organization JSON-LD for GEO\n",{"name":5,"metadata":57,"description":7},{"version":58},"2.0.0","main","e6ee720f466a8344a52abd87679191fadde3b63f",".agents\u002Fskills\u002Fdirectory-submissions","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills","https:\u002F\u002Fgithub.com\u002Fpatinaproject","https:\u002F\u002Fwww.patinaproject.com","The best way to pick your next pair of boots or shoes.","2026-11-12 00:44:02",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add patinaproject\u002Fskills --skill directory-submissions",{"tool":73,"command":74},"bunx","bunx skills add patinaproject\u002Fskills --skill directory-submissions",{"tool":76,"command":77},"pnpm","pnpm dlx skills add patinaproject\u002Fskills --skill directory-submissions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdirectory-submissions\u002FSKILL.md",true,[81,87,91,95],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"evals\u002Fevals.json","REFERENCE","参考文档",8356,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdirectory-submissions\u002Fevals\u002Fevals.json",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fdirectory-list.md",25694,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdirectory-submissions\u002Freferences\u002Fdirectory-list.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fpositioning-variations.md",9348,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdirectory-submissions\u002Freferences\u002Fpositioning-variations.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fsubmission-tracker-template.csv","ASSET","资产文件",19812,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdirectory-submissions\u002Freferences\u002Fsubmission-tracker-template.csv",[102,110,135,147,170,193],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":109},"01M72KDQJR99954NE224VB3KZ2","code-review","Review the changes since a fixed point (commit, branch, tag, or merge-base) along five axes: Standards (does the code follow this repo's documented coding standards?), Spec (does the code match what the originating issue\u002Fspec asked for?), Evidence (does each claim in the pull request have evidence that shows it?), Bugs (does the changed code have logic errors, unhandled states, races, or regressions?), and Security (does the change open injection, auth, secret, input, or CI workflow holes?). Runs the reviews in parallel sub-agents, tags every finding Important, Nit, or Pre-existing, and reports them side by side with what blocks merge. Given an earlier reviewed head and its findings, it reviews only the newer commits, rechecks the earlier findings, and never repeats one. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":122,"publishedAt":52},"01M71ESEDVHD9EXN6787XHP7HD","writing-for-pstack","Write or tighten an operator prompt for a patina-mode run. Use when the operator asks to write, revise, or review a prompt that will be passed to patina-mode.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwriting-for-pstack\u002FSKILL.md",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":120,"categoryName":121,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[38,123,124,125,126,127,128,129,130,36,131,132,133,134],"pstack","writing","writing for pstack","review","run","mode","write","operator","tighten","prompt","when","revise",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":143,"publishedAt":52},"01M71ESCJ0SSJFFENF8HYDKBTJ","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[141,142],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":120,"categoryName":121,"taxonomyType":29,"taxonomyTypeDesc":30},[144,38,124,145,36,146,133],"writing for agents","editing","documents",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":52},"01M71ESA1NN9WVMD2HA5Z1RRDY","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwizard\u002FSKILL.md",[],[149,154,155,156,157,158,133,159,160,161,162,163,36,164,165,166,38,167,168,169],"interactive","can","credentials","one","Bash","invoke","dashboard","generate","human","secrets","provisioning infrastructure","ci","up","setting","running","only",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":52},"01M71ES8FAN567N3JEPG8W6AS1","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[172,177,178,179,180,181,182,183,184,185,186,187,188,47,189,190,191,155,192,157],"more","true","decision","session","time","chunk","as","shared","map","tickets","destination","at","plan","work","agent session","one at a time",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":52},"01M71ES6PWJPKBW8R24YFH4PY6","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[200,201,202,203,204,205,206,207,178,208],"wait","wait what","stop","it","land","re","pitch","message","last"]