[Pages] Add SEO descriptions to framework guide pages#28513
Open
speedcoder430 wants to merge 1 commit intocloudflare:productionfrom
Open
[Pages] Add SEO descriptions to framework guide pages#28513speedcoder430 wants to merge 1 commit intocloudflare:productionfrom
speedcoder430 wants to merge 1 commit intocloudflare:productionfrom
Conversation
speedcoder430
requested review from
a team,
GregBrimble and
aninibread
as code owners
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
3 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.
Summary
Adds missing SEO description frontmatter to all 28 framework guide pages under
framework-guidesthat lacked them. Previously only 5 of 33 files had descriptions (Next.js, Nuxt, Analog, SvelteKit, static Next.js). This improves search snippets, click-through rates, and metadata consistency across the docs.Closes #28509
Screenshots (optional)
N/A — frontmatter-only changes with no visual impact on page content.
Documentation checklist
The change adheres to the
documentation style guide.If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.