fix(website): fit meta descriptions to the search-snippet budget - #880
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
blove
enabled auto-merge (squash)
August 30, 2026 22:06
Contributor
GSC follow-up to #826: descriptions over ~160 chars get re-truncated by Google mid-sentence, and the docs fallback path hard-sliced the first paragraph at 177 chars mid-word with '...'. - New clampMetaDescription in site-metadata.ts: ≤160 chars, prefers a sentence boundary past 60% of the budget, otherwise cuts at a word boundary with a real ellipsis. Applied centrally in createPageMetadata and at the docs/blog description sources so each page's JSON-LD stays byte-identical to its meta description. - Docs extracted-paragraph path now uses the clamp (no more mid-word '...' cuts on the 111 pages without frontmatter descriptions). - Rewrote the 5 over-budget blog descriptions and the pricing page description by hand so the author-chosen copy fits without clamping. - Specs: clamp unit tests, a docs sweep (every page ≤160, no legacy '...', guarded against an empty slug list), and a real-content blog frontmatter gate in site-metadata.spec.ts (blog.spec.ts mocks fs). The clamp immediately caught the pricing page description losing its '$29 per developer per month' claim — shortened at the source instead. nx test green (371 passing), lint 0 errors, production build green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
force-pushed
the
blove/docs-meta-descriptions
branch
from
August 30, 2026 22:06
60b0937 to
2aef07b
Compare
Contributor
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
1 participant
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
GSC follow-up to #826 (the pending CTR fix): meta descriptions over ~160 chars get re-truncated by Google mid-sentence with its own ellipsis, and the docs fallback path hard-sliced the first paragraph at 177 chars mid-word with
....clampMetaDescriptioninsite-metadata.ts: ≤160 chars, prefers ending on a sentence boundary once past 60% of the budget, otherwise cuts at a word boundary with a real…. Never cuts mid-word.createPageMetadata(every page's meta/OG description) and at the docs/blog description sources, so each page's JSON-LD stays byte-identical to its meta description (a docs spec asserts that identity)...., guarded against passing vacuously on an empty slug list); a real-content blog frontmatter gate insite-metadata.spec.ts(placed there becauseblog.spec.tsmocksfs).Verification
Runtime sweep across all 130 docs pages: max description length exactly 160, all cuts on word boundaries, zero legacy
...endings.nx test websitegreen (371 passing), lint 0 errors, production build green.🤖 Generated with Claude Code