One truthful description
Describe the real Codex plugin and MCP server capabilities in plain language; do not stack unrelated keywords.
Public discovery measurement
Measure discovery before claiming growth.
GitHub visibility is a combination of repository metadata, rolling traffic, referrals, releases, Pages surfaces, and volatile repository-search order. Capsule records those signals without turning a snapshot into a ranking promise.
Use comparable snapshots
Compare the same repository and metric at multiple points in time. Keep a timestamp and the workload or release beside any result, and treat a missing or delayed signal as unknown rather than zero. Search order is volatile; it is a diagnostic input, not a Google-ranking or adoption claim.
What the audit records
| Signal | Meaning | Limit |
|---|---|---|
| Topics and description | Controlled relevance and entry-point metadata. | They influence discovery but do not guarantee ranking. |
| Traffic and referrals | Rolling repository views, clones, and referring domains when GitHub makes them available. | Windows are limited and may lag; unavailable data stays unknown and is never treated as zero or as unique people. |
| Repository social preview | The GitHub link card and the Pages social image are separate surfaces. | A social card improves link recognition but does not establish ranking or usage. |
| Repository search | First-100 presence, rank, total result count, and null-safe deltas for fixed queries. | Order is volatile and is not Google ranking, billing, or quota telemetry. |
| Releases and assets | Tagged source archives, checksums, and release links. | Asset requests are not unique users or installations. |
Use ethical discovery surfaces
Substantive pages
Keep the Pages guides, canonical links, sitemap, RSS feed, and machine-readable summary useful to people and crawlers.
Reproducible releases
Attach a source archive and checksum when they correspond exactly to a tagged release.
Useful answers
Answer real user questions with reproducible examples and limitations; do not manufacture stars, comments, or referral traffic.
Repository social preview
Pages metadata and the GitHub repository link card are separate. Owners can upload docs/social-card.png in repository Settings → General → Social preview and verify the API flag afterward.
Repository owners may verify the Pages property in Google Search Console or Bing Webmaster Tools and submit the published sitemap. Verification tokens belong to the owner and should never be invented or committed.
Interpret a 100x target
A 100x target is a project direction, not an observable guarantee. A defensible result needs a named baseline, the same query set, a timestamp, the current repository state, and separate reporting for metadata, search order, traffic, and referral signals. A change in one field must not be presented as a 100x increase in users or search ranking.
For product measurements, see the benchmark methodology guide and the share and cite guide. Publish only sanitized, workload-specific results with their limitations.