When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.
metadata
{"version":"1.3.0"}
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
flowchart LR
discovery[Discovery or referral]
home[Repository home]
readme[README and About]
outbound[Site or docs]
discovery --> home
home --> readme
readme --> outbound
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."
Micro-content; long-tail keywords; link to repos or external resources
Wiki
Keyword-rich documentation
Issues
Q&A, discussions; indexable
GitHub Pages vs README
Surface
Role
README
First impression; Stars/forks; short pitch and deep links
Pages
Multi-page static site: long docs, blog, changelog
Default URL patterns: A user or organization site often uses a username.github.io repository and serves at https://username.github.io. A project site is published from a given repo and typically appears at https://username.github.io/repository/ (path may vary with settings). See About GitHub Pages.
Limits: Build size, bandwidth, and build-frequency caps change over time—cite GitHub Pages limits when users need numbers, not hard-coded figures from this skill.
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; see entity-seo
Consistency
Active maintenance; engagement (stars, forks, watchers)
Repository archetypes
Archetype
Intent
First-screen emphasis
Product / library
Installable software, SDK, CLI, service
Install, quickstart, proof (CI, license), support path
Curated / resource
Awesome-style lists, indexes
Scope, curation bar, contribution rules
Match metrics to type: curated lists optimize for trust and backlinks; product repos optimize for adoption and issue quality.
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.
