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#

FactorEffectDomain authorityHigh DA; repos, gists, Pages rank wellFast indexingSearch engines crawl GitHub frequentlyAI citationChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO frameworkTechnical expertiseStrong expertise signals; structured docs become AI reference materialCross-platformShare across Dev.to, Stack Overflow, forums; amplifies visibility

Use Cases#

Use caseFormatPurposeParasite SEORepos, README, Pages, gistsLeverage GitHub authority for rankings and backlinksGEODocumentation, tutorials, curated listsAI tools cite GitHub for technical answersCurated / navigation listsAwesome-style reposTopic-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#

PracticeGuidelineDescriptiveHint at what the project doesKeyword-richInclude primary keywords ( markdown-editor not my-project)HyphensSeparate words ( react-component-library)ConciseShorter = memorable, shareable

About Section (Description)#

LimitGuideline350 charsHard limit; GitHub enforces~128 charsOptimal for brevity; often displayed fullyContentPrimary 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#

LimitGuideline6–20 topicsMax 20; 6–10 recommended~50 chars eachPer topicFormatLowercase, hyphens, numbers onlyMixTechnology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest)

Underutilized but highly effective for discoverability and GEO.

README Structure & Components#

SectionPurposeSEO/GEOTitle + taglineH1 + 1–2 sentence summary; keywords in first paragraphCritical; first 100 words weightedTable of contentsLinks to H2/H3; for READMEs >500 wordsNavigation; crawlabilityInstallation / Quick startPrerequisites; exact commands; copy-paste readyUse-case clarityUsage examplesCode blocks; common scenariosCitable; extractableScreenshots / GIFsDemo, output; alt text requiredEngagement; accessibilityBadgesBuild, version, licenseTrust signalsContributingLink to CONTRIBUTING.mdCommunity signalLicenseLink to LICENSECompleteness

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

README GEO / AI Citation#

PracticeGuidelineAnswer-firstDirect answer in first 1–2 sentences (40–60 words)Short paragraphs2–3 sentences max; extractable clarityQuestion-style headingsH2/H3 as questions where relevantData inclusionStats, numbers; cited content ~40% more likely to include dataFreshnessUpdate regularly; ~76% of cited content updated within 30 days

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

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#

SurfaceUseREADMELanding page for repo; keyword-optimized summary, headings, linksGitHub PagesStatic site; blog, FAQ, docs; additional ranking opportunitiesGistsMicro-content; long-tail keywords; link to repos or external resourcesWikiKeyword-rich documentationIssuesQ&A, discussions; indexable

Optimization#

ElementPracticeRepository titlePrimary keywords; descriptive; hyphensAbout350 chars max; keyword-rich; primary keyword + natural variationsDescriptionSecondary keywords; link to website or resourcesREADMEKeyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorialsTopics / tags6–20 relevant topics; 50 chars eachGitHub PagesMobile-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#

FactorPracticeREADME clarityClear, citable paragraphs; direct answersDocumentationStructured; AI tools parse wellEntity signalsClear project, author identity; see entity-seo****ConsistencyActive 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#

CategoryExamplesMaster listsindresorhus/awesome — hub of all awesome listsSEO / Marketingawesome-seo, awesome-ai-seo, bmpi-dev/awesome-seoAI / MLawesome-ai-tools, AITreasureBox, awesome-aiDev toolsawesome-tools, awesome-cli, awesome-nodejsLanguagesawesome-python, awesome-javascript, awesome-goFrontend / Backendawesome-react, awesome-vue, awesome-djangoOtherawesome-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)#

ElementPracticeTitleClear, focused (e.g., "Awesome SEO," "Awesome AI Tools")DescriptionSuccinct; scope clearSectionsCategorized (e.g., Tutorials, Tools, Articles)ItemsCurated, not collected; only include what you recommendItem format- [Name](URL) - Brief description of why it's awesomeLicenseCC0 or similarContributingcontributing.md for PR process

Getting Listed vs. Creating#

ActionUseSubmit to existing listPR to awesome-* repos; follow list format; contact maintainerCreate new listWhen no list exists for your niche; follow awesome guidelinesLink between listsLink 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#

MistakeAvoidIgnoring engagementNot responding to issues/PRs reduces trustIrregular updatesOutdated repos signal inactivityIncomplete docsLack of clear descriptions frustrates usersGeneric titlesMissing keywords reduces discoverabilityThin awesome listsLow-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
• 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