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.
What this skill does
# 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 in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".