illyism/seo-skills

directory-submissions

Launch and submit a startup, SaaS, AI tool, or MCP server across 50+ high-DR software review sites, startup launchpads, MCP registries, and GitHub Awesome lists using a single Product Manifest and autonomous browser/PR submission workflow.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/illyism/seo-skills --skill directory-submissions

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Startup, AI tool, and MCP directory submissions

Review sites, launchpads, AI tool directories, MCP registries, and GitHub Awesome lists all ask for the same ~25 product fields at different lengths and aspect ratios.

Prepare one submission-manifest.json, add the repo files that 15+ MCP and agent registries index, then work through the 5 waves below. Log every submission in submissions-log.json so a rerun skips what is done.

Companion resources:

Step 1: Prepare submission-manifest.json once

Before opening any form or pull request, build submission-manifest.json in the project root. Read the codebase, package.json, landing page metadata, and public /images assets first, and ask the user only for missing facts:

json
{
  "product": {
    "name": "YourProduct",
    "slug": "yourproduct",
    "domain": "yourproduct.com",
    "url": "https://yourproduct.com",
    "pricing_url": "https://yourproduct.com/pricing",
    "contact_email": "press@yourproduct.com",
    "contact_page": "https://yourproduct.com/contact",
    "privacy_url": "https://yourproduct.com/privacy",
    "terms_url": "https://yourproduct.com/terms"
  },
  "copy": {
    "tagline_40c": "Punchy plain-English value prop (<=40c)",
    "tagline_60c": "Search-intent headline naming what the tool does (<=60c)",
    "mcp_description_100c": "Strict <=100 character summary required by Official MCP Registry validator.",
    "awesome_list_bullet": "- [YourProduct](https://yourproduct.com) - Factual one-line description with zero hype.",
    "description_160c": "15-25 word summary stating who it is for, what input it takes, and what output it produces (<=160c).",
    "description_500c": "Two-paragraph factual overview (minimum 510 chars) covering the core workflow, supported integrations/formats, and concrete differentiators, with zero em dashes or AI buzzwords.",
    "key_features": [
      "Concrete input -> output capability",
      "Verification, speed, or accuracy guarantee",
      "API, CLI, SKILL.md, or MCP integration support",
      "Export formats or team controls"
    ]
  },
  "taxonomy": {
    "primary_category": "Developer Tools / AI Tools / SaaS",
    "tags": ["ai", "saas", "developer-tools", "automation", "seo"],
    "competitors_replaced": ["CompetitorA", "CompetitorB", "CompetitorC"],
    "pricing_model": "Freemium",
    "starting_price_usd": 19,
    "free_tier_details": "Exact free tier or trial allowance"
  },
  "assets": {
    "favicon_64": "https://yourproduct.com/favicon.ico",
    "logo_square_512": "https://yourproduct.com/logo-512x512.png",
    "og_image_1200x630": "https://yourproduct.com/og.png",
    "screenshots_16x9": [
      "https://yourproduct.com/screenshots/01-hero-1280x800.png",
      "https://yourproduct.com/screenshots/02-workflow-1280x800.png",
      "https://yourproduct.com/screenshots/03-output-1280x800.png"
    ]
  },
  "agent_and_mcp": {
    "mcp_endpoint": "https://yourproduct.com/mcp",
    "github_repo": "https://github.com/yourorg/yourproduct"
  }
}

Step 2: One repo, 15+ MCP and agent registries (if you ship an MCP server or SKILL.md)

Six small files in your public GitHub repo let agent marketplaces index the product:

  1. `server.json`: Keep description strictly ≤ 100 characters or the Official MCP Registry validator rejects it.
  2. `glama.json`: { "$schema": "https://glama.ai/mcp/schemas/server.json", "maintainers": ["your-github-handle"] } (required to claim on Glama and pass awesome-mcp-servers CI).
  3. `.cursor-plugin/plugin.json` + `.mcp.json`: Indexed by Cursor Marketplace (cursor.com/marketplace) and `cursor.directory`.
  4. `.claude-plugin/plugin.json` + `.mcp.json`: Indexed by Claude Code plugin directories.
  5. `gemini-extension.json` + repo topic `gemini-cli-extension`: Auto-indexed within 24 hours by Google's Gemini CLI Extensions gallery.
  6. `SKILL.md`: Auto-indexed by `skills.sh`, ClawHub (`clawhub.ai`), and MCP Market (`mcpmarket.com`).

Then publish once to the Official MCP Registry so downstream directories (glama.ai, pulsemcp.com, mcp.directory, apitracker.io, claudemcp.org) sync automatically:

bash
brew install mcp-publisher
mcp-publisher login github
mcp-publisher publish

Step 3: Work through the 5 waves (50 directories)

Wave 1: Software review sites (do first)

Google's Knowledge Graph, ChatGPT, and Perplexity cross-check these domains when users search "best X" or "X alternatives":

DirectoryDRSubmit URLNotes
Awesome Tools80https://awesome.tools/submitFree verified dofollow listing (badge) or instant Featured Launch; supports JSON API & WebMCP
AlternativeTo81https://alternativeto.net/manage-item/Free dofollow link · 1–5d moderator review · Top LLM citation source for "X alternatives"
SaaSHub80https://www.saashub.com/submitFree dofollow link (2–4w) or paid fast-track
GoodFirms86https://www.goodfirms.co/get-listedFree vendor profile · 3–7 business days
G291https://sell.g2.com/create-a-profileFree vendor profile · #1 B2B citation source in ChatGPT & Perplexity
Capterra / GetApp / Software Advice90https://www.gartner.com/en/digital-markets/Role-SelectionOne Gartner Digital Markets application lists on all 3 sites
ProvenExpert81https://www.provenexpert.com/en-us/registration/Free profile · Live right after registration
StackShare78https://stackshare.io/submitFree developer tool profile · 1–5d review
SoftwareWorld74https://www.softwareworld.co/register/Free vendor listing · 3–7 business days
Alternative.me73https://alternative.me/how-to/submit-software/Free software listing · 3–7d review
LibHunt72https://www.libhunt.com/repo/submitFree developer & open-source tool tracking
Tekpon68https://tekpon.com/get-listed/Free SaaS vendor profile · 3–7 business days

Wave 2: MCP and AI agent registries

  • GitHub MCP Registry (https://github.com/mcp · DR 98, pulls from Official MCP Registry)
  • OpenAI ChatGPT App Directory (https://platform.openai.com/plugins · DR 93, verify /.well-known/openai-apps-challenge)
  • Cursor Marketplace (https://cursor.com/marketplace/publish · DR 84) & `cursor.directory` (https://cursor.directory/ · DR 69)
  • ClawHub Skills Registry (https://clawhub.ai/ · DR 83)
  • Official MCP Registry (https://modelcontextprotocol.io/registry/quickstart · DR 82)
  • Smithery (https://smithery.ai/ · DR 79), Glama (https://glama.ai/mcp/servers · DR 77), LobeHub MCP (https://lobehub.com/mcp · DR 76)
  • `mcpservers.org` (https://mcpservers.org/submit · DR 71) & MCP Market (https://mcpmarket.com/submit · DR 62)

Wave 3: Startup and developer launchpads

  • Hacker News (`Show HN`) (https://news.ycombinator.com/submit · DR 91) & Product Hunt (https://www.producthunt.com/posts/new · DR 91)
  • Fazier (https://fazier.com/submit · DR 84), Twelve Tools (https://twelve.tools/submit · DR 83), Findly.tools (https://findly.tools · DR 82)
  • Peerlist Launchpad (https://peerlist.io/user/projects/add-project · DR 78), BetaList (https://betalist.com/submit · DR 77), PeerPush (https://peerpush.com/submit · DR 77)
  • Uneed (https://www.uneed.best/submit-a-tool · DR 76), LaunchIgniter (https://launchigniter.com/submit · DR 75), DevHunt (https://devhunt.org/account/tools/new · DR 68)

Wave 4: AI tool directories

  • ShowMeBest.AI (https://showmebest.ai/submit · DR 77), Good AI Tools (https://goodaitools.com/submit · DR 75), AI Agents Directory (https://aiagentsdirectory.com/submit-agent · DR 75)
  • Supertools / The Rundown (https://www.therundown.ai/tools · DR 72), Insidr.ai (https://www.insidr.ai/submit-tools/ · DR 71), `aidirectori.es` (https://www.aidirectori.es/submit-ai-tool · DR 71)
  • AItrendytools (https://www.aitrendytools.com/submit · DR 69), Foundr.ai (https://foundr.ai/submit · DR 64), DokeyAI (https://dokeyai.com/submit · DR 62), Easy With AI (https://easywithai.com/submit-tool/ · DR 60)

Wave 5: Web design galleries (once the landing page is polished)

  • One Page Love (https://onepagelove.com/submit · DR 79), Land-book (https://land-book.com/submission-guidelines · DR 66), Recent Design (https://recent.design/signup · DR 64)
  • Lapa Ninja (mailto:hi@lapa.ninja · DR 61), Minimal Gallery (https://minimal.gallery/submit/ · DR 61), Hover States (https://www.hoverstat.es/about/ · DR 56)
  • Curated Design (https://www.curated.design/submit · DR 52), Footer Design (https://www.footer.design/submit · DR 52), TOOOLS.design (https://www.toools.design/submission · DR 48)

The full database of 856+ directories comes with any backlink order at linkdr.com/resources/directories.

Step 4: Rules for agent submissions

When you run browser or GitHub PR submissions as an agent, follow all 10:

  1. No unapproved spend. Submit only to free tiers unless the user explicitly approves a paid fast-track checkout. If a submission lands on a Stripe/PayPal paywall with no free path, record status: "skipped_paid_only" and continue.
  2. Contact privacy. Directories get scraped across 500+ aggregator sites. Never submit personal phone numbers, home/registered-agent street addresses, or internal holding LLC names. Always use the product brand name, "Media Relations", a generic role email (press@<domain>), empty phone/address fields, and https://<domain>/contact.
  3. Factual copy. Never use em-dashes, emojis, or hype buzzwords ("unleash", "revolutionize", "seamless", "game-changing"). Editors and Awesome-list maintainers reject copy that reads as AI marketing.
  4. Agent endpoints before browser forms. Check whether the directory exposes a JSON, MCP, or agent endpoint (for example https://awesome.tools/api/tools/submit, /agent, /api/mcp, or /llms.txt) before driving a browser UI.
  5. Honeypots. Never fill any input that is hidden (!isVisible(), aria-hidden="true", tabindex="-1", type="hidden", style*="scale(0)", display:none) or carries spam-trap names/labels (opl_hp_field, _honeypot, bot-field, website_url alongside a visible url field, or "Leave this empty").
  6. Embedded forms. If a /submit page renders an embedded widget ([data-paperform-id], tally.so, typeform.com, airtable.com, embed.fillout.com), open the standalone form URL directly in a top-level tab so inputs and file uploads work.
  7. Assets. Keep 512×512 PNG + 48×48 WebP logos, a 1200×630 OG image, and three 1280×800 screenshots (<300 KB WebP + PNG) ready before starting batch submissions.
  8. Email verification. Check press@<domain> for magic links and 6-digit codes right away so listings don't stall in unverified state.
  9. GitHub Awesome PRs. Before opening any Awesome-list PR:
  • Read CONTRIBUTING.md, .github/PULL_REQUEST_TEMPLATE.md, .github/workflows/, and the last 3 merged PRs. Respect any repo that restricts AI-submitted PRs or SaaS products.
  • Edit the real source-of-truth file (README.md, applications.json, data/*.csv, or multi-locale READMEs), match exact ordering (alphabetical vs. end-of-section) and dash/punctuation style, and strip all ?ref= / UTM parameters.
  • Use a collision-safe fork name (<repo>-<upstream-owner>).
  1. `submissions-log.json`. Check submissions-log.json before every target and append a structured receipt after each attempt:
json
{
  "name": "Awesome Tools",
  "url": "https://awesome.tools",
  "submissionUrl": "https://awesome.tools/submit",
  "wave": 1,
  "status": "submitted",
  "liveOrPrUrl": "https://awesome.tools/t/yourproduct",
  "submittedAt": "2026-11-11T16:00:00Z",
  "notes": "Free verified dofollow path"
}
같은 저장소의 Skills

더 많은 Skills

모든 Skills
illyism
커뮤니티

blitz-seo

Runs a focused 30-day SEO sprint that concentrates search-intent alignment, internal link equity, first-hand proof, and targeted backlinks onto a single money page to push it into the Top 3. Use when a high-value page is stuck on Page 2, the user mentions "blitz seo" or a 30-day SEO sprint, or SEO effort is spread too thin across dozens of URLs.

1시간 설치 수
3
GitHub Stars
1.8천
업데이트
11월 20일
illyism
커뮤니티

blog-refresher

Refresh and improve existing blog posts to outrank competitors using a 6-phase content audit and SERP gap analysis. Use when the user wants to update, refresh, or improve an existing blog post, recover lost rankings, or asks why a post fell behind competitors.

1시간 설치 수
3
GitHub Stars
1.8천
업데이트
11월 20일
illyism
커뮤니티

internal-linking

Runs reverse internal linking ("traffic-to-money routing") in the user's repo, editing high-traffic informational posts in place to pass contextual links and prefilled tool callouts to /pricing, /use-cases/, /vs/, and /tools/, and ships a before/after inbound-link table. Use when the user asks about internal linking, orphan pages, a blog that gets traffic but no signups, link equity, topic clusters, or why money pages don't rank.

1시간 설치 수
3
GitHub Stars
1.8천
업데이트
11월 20일
illyism
커뮤니티

proof-kb

Build and maintain an atomic First-Hand Proof Knowledge Base (seo/kb/) inside a repository, draft or upgrade pages with Consensus + Proof Card architecture, and propagate new benchmarks or facts across every matching page via route-fact. Use when scaffolding seo/kb/, extracting founder proof from transcripts or interviews, upgrading thin SEO posts with real receipts, or routing a new benchmark, customer win, or pricing change across multiple pages.

1시간 설치 수
3
GitHub Stars
1.8천
업데이트
11월 20일