Platforms: GitHub

Guides GitHub for parasite SEO, GEO (AI citation), and curated list creation. GitHub is a Tier 2 Technical Authority platform—high domain authority, fast indexing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation lists.

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.

Why GitHub for SEO

Factor Effect

Domain authority High DA; repos, gists, Pages rank well

Fast indexing Search engines crawl GitHub frequently

AI citation ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework

Technical expertise Strong expertise signals; structured docs become AI reference material

Cross-platform Share across Dev.to, Stack Overflow, forums; amplifies visibility

Use Cases

Use case Format Purpose

Parasite SEO Repos, README, Pages, gists Leverage GitHub authority for rankings and backlinks

GEO Documentation, tutorials, curated lists AI tools cite GitHub for technical answers

Curated / navigation lists Awesome-style repos Topic-specific resource directories; backlinks, discovery

Repository Name, About & README (SEO/GEO Priority)

Ranking weight (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high.

Repository Name

Practice Guideline

Descriptive Hint at what the project does

Keyword-rich Include primary keywords (markdown-editor not my-project )

Hyphens Separate words (react-component-library )

Concise Shorter = memorable, shareable

About Section (Description)

Limit Guideline

350 chars Hard limit; GitHub enforces

~128 chars Optimal for brevity; often displayed fully

Content Primary keyword + natural variations; what it does, who it's for; link to website or docs if space

Example: "A fast, lightweight markdown editor for React with live preview, syntax highlighting, and export to PDF. Built with TypeScript."

Topics

Limit Guideline

6–20 topics Max 20; 6–10 recommended

~50 chars each Per topic

Format Lowercase, hyphens, numbers only

Mix Technology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest)

Underutilized but highly effective for discoverability and GEO.

README Structure & Components

Section Purpose SEO/GEO

Title + tagline H1 + 1–2 sentence summary; keywords in first paragraph Critical; first 100 words weighted

Table of contents Links to H2/H3; for READMEs >500 words Navigation; crawlability

Installation / Quick start Prerequisites; exact commands; copy-paste ready Use-case clarity

Usage examples Code blocks; common scenarios Citable; extractable

Screenshots / GIFs Demo, output; alt text required Engagement; accessibility

Badges Build, version, license Trust signals

Contributing Link to CONTRIBUTING.md Community signal

License Link to LICENSE Completeness

Word count: No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later.

README GEO / AI Citation

Practice Guideline

Answer-first Direct answer in first 1–2 sentences (40–60 words)

Short paragraphs 2–3 sentences max; extractable clarity

Question-style headings H2/H3 as questions where relevant

Data inclusion Stats, numbers; cited content ~40% more likely to include data

Freshness Update regularly; ~76% of cited content updated within 30 days

Entity signals: Clear project name, author, maintainer; consistent identity.

README Checklist

• Project title with keywords

• Concise description in first paragraph

• H2/H3 structure; alt text for images

• Installation + usage examples

• Screenshots or demo

• Badges; Contributing; License

• Internal links to related docs/repos

• 6–20 topics on repo

Parasite SEO on GitHub

Key Surfaces

Surface Use

README Landing page for repo; keyword-optimized summary, headings, links

GitHub Pages Static site; blog, FAQ, docs; additional ranking opportunities

Gists Micro-content; long-tail keywords; link to repos or external resources

Wiki Keyword-rich documentation

Issues Q&A, discussions; indexable

Optimization

Element Practice

Repository title Primary keywords; descriptive; hyphens

About 350 chars max; keyword-rich; primary keyword + natural variations

Description Secondary keywords; link to website or resources

README Keyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorials

Topics / tags 6–20 relevant topics; 50 chars each

GitHub Pages Mobile-friendly; metadata; blog/FAQ for extra keywords

Gists for Micro-Content

• Target specific long-tail keywords

• Link back to larger repos or external resources

• Share code snippets, small utilities

Community Engagement

• Respond to issues and PRs; builds trust

• Contribute to popular projects; backlinks, visibility

• Keep repos updated; outdated = lower credibility

GEO on GitHub

Factor Practice

README clarity Clear, citable paragraphs; direct answers

Documentation Structured; AI tools parse well

Entity signals Clear project, author identity

Consistency Active maintenance; engagement (stars, forks, watchers)

Curated / Navigation Lists (Awesome-Style)

Awesome lists = Curated, topic-specific resource lists on GitHub. Function like navigation directories; high traffic, backlinks, discovery. sindresorhus/awesome (441K+ stars) is the master list; 6,500+ curated lists exist across topics.

Examples by Category

Category Examples

Master list sindresorhus/awesome — hub of all awesome lists

SEO / Marketing awesome-seo, awesome-ai-seo, bmpi-dev/awesome-seo

AI / ML awesome-ai-tools, AITreasureBox, awesome-ai

Dev tools awesome-tools, awesome-cli, awesome-nodejs

Languages awesome-python, awesome-javascript, awesome-go

Frontend / Backend awesome-react, awesome-vue, awesome-django

Other awesome-security, awesome-gaming, awesome-databases

When to Create

• You have a niche with many quality resources to curate

• Existing lists lack coverage of your topic

• You want a backlink asset and topical authority

List Structure (sindresorhus/awesome guidelines)

Element Practice

Title Clear, focused (e.g., "Awesome SEO," "Awesome AI Tools")

Description Succinct; scope clear

Sections Categorized (e.g., Tutorials, Tools, Articles)

Items Curated, not collected; only include what you recommend

Item format

• Name - Brief description of why it's awesome

License CC0 or similar

Contributing contributing.md for PR process

Getting Listed vs. Creating

Action Use

Submit to existing list PR to awesome-* repos; follow list format; contact maintainer

Create new list When no list exists for your niche; follow awesome guidelines

Link between lists Link to other awesome lists that cover subjects better

Discovery

• sindresorhus/awesome — Master list of awesome lists

• AwesomeSearch — Search across awesome lists

• more-awesome — Directory of awesome lists

Common Mistakes

Mistake Avoid

Ignoring engagement Not responding to issues/PRs reduces trust

Irregular updates Outdated repos signal inactivity

Incomplete docs Lack of clear descriptions frustrates users

Generic titles Missing keywords reduces discoverability

Thin awesome lists Low-quality or uncurated items hurt credibility

Output Format

• Use case (parasite SEO / GEO / curated list)

• Repository name, About, Topics (if optimizing metadata)

• Surface (README, Pages, gist, awesome repo)

• README structure (sections, word count, GEO practices if applicable)

• Optimization (keywords, structure, links)

• Ready-to-use copy or structure where applicable

Related Skills

• parasite-seo: Parasite SEO strategy; GitHub as Tier 2 technical platform

• generative-engine-optimization: GEO strategy; GitHub for AI citation

• directory-submission: Directory and curated list submission; awesome lists as curated lists

• link-building: GitHub as link acquisition; repos, gists, awesome lists