docs: fit meta titles and descriptions to search-engine limits - #95
Merged
Conversation
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.
Bing Webmaster's SEO analysis flags every docs page: rendered
<title>s run 90–120 chars (limit ~65) and meta descriptions 120–350 chars (limit ~160), because the keyword-rich front-matter titles get the| React Native Liquid Glasssuffix appended by jekyll-seo-tag.This trims front matter only on all 16 pages:
page.htmlnever renderspage.titleas an H1, so the long keyword-rich H1s on each page stay exactly as they wereDocs-only, so native builds skip via the changes gate.