chore(seo): npm + GitHub discoverability metadata (0.6.1)#65
Merged
Conversation
Registry metadata is immutable per version, so the SEO work ships as a metadata-only patch release. npm (packages/cli — the published `ui-lineage`): - description rewritten to lead with the terms people search (React & TypeScript static analysis, data lineage, MCP, AI coding agents). - keywords 9 -> 20, adding the previously-absent MCP/AI cluster (mcp, mcp-server, model-context-protocol, ai-agents, codebase-context, llm, claude) plus typescript, code-analysis, dependency-graph, impact-analysis. - added repository (with monorepo `directory`), homepage, and bugs — these were missing entirely, so npm rendered no source link and forfeited quality-score credit and link equity. - added LICENSE (MIT was declared in package.json but no file existed); it now ships in the tarball (22 files). README (the npm package page, and what Google indexes): - keyword-bearing H1, npm/downloads/license/node badges. - MCP server surfaced in the intro with the clients it works with, instead of being buried mid-document. - new "Use it to" section written around real search intents. GitHub: repo description aligned with npm, homepage set, and 15 topics added (there were none). No functional change: eval 341/0/0 + determinism 1.000, full suite, typecheck and lint all green; packed bin reports 0.6.1. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SEO / discoverability pass — ships as 0.6.1
npm registry metadata is immutable per version, so none of this reaches npm until a new version is published. Hence a metadata-only patch release.
What was wrong (verified against the live registry)
repository,homepage, orbugs— npm rendered no source link, forfeiting quality-score credit, referral traffic, and link equity to Google.ui-lineage-mcp) — the fastest-growing search cluster, and where the closest competitors (trace-mcp, Agentation, OpenTrace) are positioned.package.jsondeclared MIT — GitHub showed no license, npm quality lost a point.npm (
packages/cli)mcp,mcp-server,model-context-protocol,ai-agents,codebase-context,llm,claude) plustypescript,code-analysis,dependency-graph,impact-analysis.repository(with monorepodirectory),homepage,bugs.README — the npm page body, and what Google indexes
GitHub
Repo description aligned with npm, homepage set, and 15 topics added.
Verification
No functional change: eval 341/0/0 · determinism 1.000, full unit suite, typecheck and lint all green; packed bin reports
0.6.1;npm packclean.npm publishleft to the maintainer — required for any of this to take effect on the registry.🤖 Generated with Claude Code