kostja94/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.
npx skills add https://github.com/kostja94/marketing-skills --skill parasite-seoGuides 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.
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.
| 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 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 | 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
Take kostja94/parasite-seo from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.