chore: SEO improvements — README opener + canonical LICENSE#108
Open
sazed-bot[bot] wants to merge 1 commit into
Open
chore: SEO improvements — README opener + canonical LICENSE#108sazed-bot[bot] wants to merge 1 commit into
sazed-bot[bot] wants to merge 1 commit into
Conversation
- Restructure README opening to lead with concrete value (94+ recipes, vendor list, deliverables) before scope/policy. Improves GitHub search snippets and first-visitor conversion. - Add canonical `LICENSE` file (copy of LICENSE-CODE = MIT) so GitHub's classifier surfaces the MIT badge instead of NOASSERTION. Dual-license split (LICENSE-CODE / LICENSE-DATA / LICENSE.md) is preserved. - Link the `good first issue` label directly from the Contributing section to surface contribution paths. Part of a broader SEO/discoverability pass — also includes: - Description rewrite (manual via Settings, requires repo admin) - Topic list expansion to 20 tags (manual via Settings) - Enable Discussions (manual via Settings)
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
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.
Summary
SEO + discoverability polish, kicked off after our first organic star landed and I audited why the repo isn't surfacing in GitHub search.
What changes
README opener restructured. Old: tagline → scope → policy → value prop. New: concrete value (94+ recipes, vendor list, deliverables) → scope → policy. First-time visitors and GitHub's search snippet now see "what you get" before "the bar we hold." No content removed — just reordered + a bit more vendor-name density.
Canonical
LICENSEfile added (MIT, copy ofLICENSE-CODE). GitHub's license classifier needs a top-level file namedLICENSE(orLICENSE.txt/COPYING) to surface the green license badge. The customLICENSE.mdexplainer +LICENSE-CODE+LICENSE-DATAdual-license setup is preserved exactly as-is — this just gives the classifier something canonical to read so we stop showing asNOASSERTIONin the repo header.What's not in this PR (requires repo admin perms)
These need Zach to do them in Settings — separate Telegram message has the copy-paste-ready values:
Why this matters
I tested 10 obvious queries someone would run to find this repo ("voice ai agent examples", "vapi templates", "pipecat example", etc.). The repo doesn't appear in the top 30 for any of them. Search ranking is
text relevance × stars × freshness × age. We can't move stars yet, but the text-relevance lever is fully under our control — and right now the description ("recipe collection") is a phrase nobody searches.Together with the manual Settings changes, this should move the repo from "invisible to GitHub search" to "ranks on vendor-specific topic pages" — meaningfully better discovery surface as we approach 100+ recipes.
Testing
LICENSEis byte-identical toLICENSE-CODE(MIT)🤖 Generated with Sazed