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

Use Cases

Surfaces: profile vs repository

Changing a normal repo README does not change the profile banner unless that content is the profile README repo or linked from it.

Profile README (username/username)

Not the same as a product repo README. Optimize for identity + navigation in ~15–40 lines of rendered content unless the user explicitly wants a long-form CV. Official setup: Managing your profile README.

Minimal outline (typical profile):

1. Title + answer-first tagline (+ slim badge row).
2. ### What I do — identity, proof link(s), without repeating the same URLs again later.
3. ### Open source — bold repo links + pitches + optional one code fence.
4. ### Find me — single line of deduped links (site · bio · cases · social · email).
5. ### Activity (optional) — small github-readme-stats + star-history; alt text on <img>.

Reference pattern (high-signal, low-noise): scan-first profiles such as alchaincyf — short ### blocks, bold product/repo names, one “find me” cluster.

Entity hub pattern: When the person has a canonical site, lead with it in the opening line and mirror the same URL in Pinned / profile About (if used) so site ↔ GitHub OSS stay aligned for entity-seo.

Profile README checklist (short)

• H1 + one answer-first tagline (keywords: role, stack, domain)
• Canonical outbound links (site, social, email) deduplicated
• Pinned repos (≤6) match the story told in the README
• Optional: Activity section — group stats / star-history under one heading instead of scattering widgets
• Last updated footnote for freshness (GEO signal)

Repository home: layout map

Website field: Maintained via repo Settings / About edit; prefer one canonical docs or product URL aligned with README links.

In-site discovery (high level)

UI and URLs evolve; verify on github.com.

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

About Section (Description)

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

Topics

Underutilized but highly effective for discoverability and GEO.

README Structure & Components

Targets repository (project) READMEs unless noted. Profile README overrides: shorter, fewer sections—see Profile README (username/username) above.

Word count: No hard limit; 500–1,500 words typical for product / library repos. Lead with value; expand later. Profile README: prefer dense brevity—long-form belongs on the canonical site or in pinned repos’ own READMEs.

README GEO / AI Citation

Entity signals: Clear project name, author, maintainer; consistent identity. See entity-seo.

README Checklist — repository (default)

• 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

(For profile username/username, use the shorter Profile README checklist under Surfaces—not every row above applies.)

Parasite SEO on GitHub

Key Surfaces

GitHub Pages vs README

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.

Optimization

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

Repository archetypes

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.

Examples by Category

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)

Getting Listed vs. Creating

Discovery

• sindresorhus/awesome — Master list of awesome lists
• AwesomeSearch — Search across awesome lists
• more-awesome — Directory of awesome lists

Common Mistakes

Output Format

• Use case (parasite SEO / GEO / curated list)
• Surface scope (profile vs specific repository; README vs Pages)
• Repository name, About, Topics (if optimizing metadata)
• Surface (README, Pages, gist, awesome repo)
• README structure (sections, word count, GEO practices if applicable) — if profile README, cite short outline + deduped links + optional widgets per Profile README section above
• 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
• open-source-strategy: Open source commercialization; GitHub as primary distribution
• directory-submission: Directory and curated list submission; awesome lists as curated lists
• link-building: GitHub as link acquisition; repos, gists, awesome lists
• entity-seo: Entity signals (project, author); Organization, Person