Wikidata, ORCID, Crunchbase, LinkedIn. The usual E-E-A-T suspects. GitHub keeps getting left off the list, and it shouldn't. AI models, especially the ones with code-aware training (Claude, GPT, Copilot's underlying stack) weigh a GitHub profile about the same as a LinkedIn one. And higher than a Medium one. If you've built anything, your repo is a provenance anchor nothing else matches.
The GitHub Authority Score runs the audit. Paste a profile, org, or single-repo URL and get scored against 14 signals in about 3 seconds (the GitHub public API is fast, though rate-limited to 60 requests/hour unauthenticated. Don't bulk-audit from one IP).
What gets checked
Profile signals first. Bio filled in. Location or company declared. A public website (the blog field. That's the sameAs target you'll use from your main site's Person schema). Contact method visible. Avatar uploaded. Follower count in context.
Then the pinned-repo signals, because that's what a visitor. Or an AI crawler. Actually looks at. README size (2 KB minimum to signal that someone cares). License declared (MIT, Apache, GPL. An unlicensed repo is a red flag). Topic tags (three or more). Description substantive. Homepage URL pointing back to your brand domain. Tagged releases. Stars and forks in context.
Finally, the cross-profile signals. How many repos were updated in the last six months? How many distinct topic tags across the profile? An AI model reading your profile wants to see active maintenance, not a graveyard of abandoned side projects.
The schema block
The tool emits a copy-paste Person (for users) or Organization (for orgs) or SoftwareSourceCode (for repos) JSON-LD block. This is the piece you drop into your main site's <head> to tell Google's entity graph that the GitHub identity belongs to the domain identity. It's the same sameAs linking pattern the E-E-A-T Generator uses for LinkedIn and Wikidata. GitHub just isn't in most default templates.
What the fix prompt does
For each failed or weak check, the generated prompt asks Claude for concrete content: the README section to paste, the topic tags to add, the commit-message style to adopt, the release-notes template to publish your next tag with. Everything copyable; no generic advice.
The book reference
Chapter 2 of The $97 Launch. GitHub as Your Content Engine. Argues for treating GitHub as a content channel, not a private dump. This tool is the measurement layer for that chapter's discipline. Chapter 37 of The $100 Network. Entity-Based SEO. Is where the sameAs strategy lives.