parasite-seo
When the user wants to choose or execute third-party platform SEO (high-authority sites for rankings or backlinks). Also use when the user mentions "parasite SEO," "parasitic SEO," "barnacle SEO," "hosted content," "third-party publishing," "Medium SEO," "Reddit SEO," "GitHub parasite SEO," "LinkedIn Pulse SEO," "high-authority platforms," "distributed authority," "borrow domain authority," or "rank without own website." For GitHub-specific playbooks, use github. For Medium.com posts, use medium-posts. For Grokipedia, use grokipedia-recommendations. For AI answer-engine visibility (not platform selection), use generative-engine-optimization.
Best use case
parasite-seo is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to choose or execute third-party platform SEO (high-authority sites for rankings or backlinks). Also use when the user mentions "parasite SEO," "parasitic SEO," "barnacle SEO," "hosted content," "third-party publishing," "Medium SEO," "Reddit SEO," "GitHub parasite SEO," "LinkedIn Pulse SEO," "high-authority platforms," "distributed authority," "borrow domain authority," or "rank without own website." For GitHub-specific playbooks, use github. For Medium.com posts, use medium-posts. For Grokipedia, use grokipedia-recommendations. For AI answer-engine visibility (not platform selection), use generative-engine-optimization.
Teams using parasite-seo should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/parasite-seo/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How parasite-seo Compares
| Feature / Agent | parasite-seo | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to choose or execute third-party platform SEO (high-authority sites for rankings or backlinks). Also use when the user mentions "parasite SEO," "parasitic SEO," "barnacle SEO," "hosted content," "third-party publishing," "Medium SEO," "Reddit SEO," "GitHub parasite SEO," "LinkedIn Pulse SEO," "high-authority platforms," "distributed authority," "borrow domain authority," or "rank without own website." For GitHub-specific playbooks, use github. For Medium.com posts, use medium-posts. For Grokipedia, use grokipedia-recommendations. For AI answer-engine visibility (not platform selection), use generative-engine-optimization.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# SEO: Parasite SEO Guides parasite SEO (also "barnacle SEO")—publishing optimized content on high-authority third-party platforms (Medium, Reddit, LinkedIn, Grokipedia, etc.) to leverage their domain strength for rankings and backlinks, bypassing the need to build your own site's authority from scratch. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## What Is Parasite SEO **Parasite SEO** = Placing content on high-authority platforms to leverage their domain strength for rankings and AI citation. Part of "Distributed Authority Engineering." Instead of waiting months for your own domain to gain trust, you publish on established platforms that Google already trusts. Content can rank on page one within days rather than months because Google crawls these platforms frequently and inherits their domain trust. **Best for**: Beginners testing niches; local businesses needing quick leads; demand validation; supplementing traditional SEO. ## Why It Works | Factor | Effect | |--------|--------| | **Domain authority** | Platforms (DA 90+) rank faster than new sites | | **Crawl frequency** | Google crawls Reddit, Medium, LinkedIn often | | **AI citation** | ChatGPT, Perplexity cite Reddit, Quora, wikis | | **UGC preference** | Algorithm updates favor UGC platforms as trustworthy | | **Technical foundation** | High-authority sites have strong technical SEO, fast load, good UX | ## Platform Tiers *Platform examples are illustrative only. No endorsement implied.* | Tier | Platform type | Examples | GEO / AI citation | |------|---------------|----------|-------------------| | **Tier 1** | GEO authority | Medium, Reddit, LinkedIn Articles, Quora | Very high | | **Tier 2** | Technical authority | GitHub, Stack Overflow, Dev.to | High; expertise signals | | **Tier 3–6** | Controlled / entity / wiki | WordPress.com, Blogger, HN, Grokipedia | Varies | ### Platform Notes | Platform | Use case | Notes | |----------|----------|-------| | **LinkedIn Pulse** | B2B, agencies, professional content | Keywords in headlines; often ranks above corporate blogs | | **Medium** | How-to, thought leadership | Use canonical link if reposting; storytelling works | | **Reddit** | Product reviews, alternatives, discussions | Comprehensive guides; upvoted threads rank well | | **Quora** | Q&A, long-tail informational | Answer industry questions; link to resources naturally | | **YouTube** | Video search, how-to, reviews | Titles, descriptions, tags; watch time matters | | **GitHub** | Repos, README, Pages, gists, awesome lists | Tier 2 technical authority; very high AI citation; see **github** | | **Grokipedia** | AI encyclopedia | See **grokipedia-recommendations** for contribution flow | | **Free web builders** | WordPress.com, Wix | Indexable content; lower authority than above | ## Keyword & Content Strategy | Element | Practice | |---------|----------| | **Keyword targeting** | Intent-driven; mid-competition and long-tail; clear monetization potential | | **Content depth** | 1,500+ words for competitive keywords; comprehensive coverage | | **Keyword placement** | Primary keyword in title and first 100 words; headers, subheadings, body | | **Semantic relevance** | Natural language; avoid keyword stuffing | | **Content clustering** | Create clusters around topics; link related articles within platform | ## On-Page Optimization | Element | Practice | |---------|----------| | **Title** | Target keyword; platform + search-optimized | | **Meta / description** | Where allowed; keyword usage | | **Internal links** | Link to other parasite content on same platform | | **Visuals** | Images, infographics, videos improve engagement | | **CTA** | Strong, relevant call-to-action | ## Link Building Through Parasite SEO | Tactic | Purpose | |--------|---------| | **Tier-2 backlinks** | Build links from Web 2.0s, guest posts pointing to your parasite content | | **Strategic linking** | Link from parasite content to owned site; natural, not spammed | | **Cross-platform linking** | Link related content across platforms; network effect | ## Advanced Techniques | Technique | Use | |-----------|-----| | **Content clustering** | Multiple related articles on same platform; topical authority | | **Cross-platform syndication** | Adapt core content per platform; different keywords; avoid duplicate content | | **Keyword layering** | Multiple related keywords in one piece; maximize ranking potential | ## Risks & Compliance | Risk | Mitigation | |------|------------| | **Google Site Reputation Abuse (2024)** | Targets manipulative third-party content. Ensure genuinely useful content; not purely for link/mention manipulation. | | **Platform bans** | Spammy, promotional content gets removed; accounts suspended | | **Duplicate content** | Use canonical when republishing; avoid thin content | | **Over-optimization** | Prioritize user value over aggressive optimization | ## Common Mistakes | Mistake | Avoid | |---------|-------| | **Quality neglect** | Low-quality, thin content doesn't sustain; harms SEO | | **Policy violations** | Check platform guidelines; adhere to policies | | **Short-term tactics** | Build sustainable relationships; create value consistently | ## Output Format - **Platform selection** (match to intent and audience) - **Keyword strategy** (intent, long-tail, placement) - **Content structure** (depth, clustering, per-platform format) - **Link strategy** (tier-2, cross-platform, owned property) - **Related platform skills** (reddit-posts, grokipedia-recommendations, etc.) ## Related Skills - **github**: GitHub for parasite SEO; repos, README, Pages, gists, awesome lists - **grokipedia-recommendations**: Add recommendations/links to Grokipedia; parasite SEO + GEO - **reddit-posts**: Reddit post copy; high-authority community for parasite SEO - **medium-posts**: Medium publishing; parasite SEO; canonical setup - **generative-engine-optimization**: GEO strategy; parasite SEO complements AI citation - **link-building**: Parasite SEO as link acquisition tactic; tier-2 backlinks - **directory-submission**: Directory and curated list submission; similar placement logic - **community-forum**: Forum and community promotion; HN, Indie Hacker - **indie-hacker-strategy**: Indie hacker growth; Indie Hackers, Reddit as channels - **seo-strategy**: SEO workflow; parasite SEO as alternative strategy
Related Skills
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
growth-funnel
When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.
conversion-optimization
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy.
cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.