Repository navigation
feat(seo): technical foundation - structured data, OG cards, bundle diet, FAQ - #20
Merged
Merged
Conversation
…unknown doc slugs
…me for clean dev 404s
5 of 6 tasks
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.
What
Workstream A of the SEO plan (owner-approved; zero product/UI behavior change): structured data across docs, per-guide social cards, a 562KB bundle reduction, and a new landing FAQ section with matching FAQPage schema.
Why
Post-routes-restructure (#19) SEO foundation: rich results eligibility (FAQ/breadcrumbs/articles), better share CTR via branded cards, and page-speed as a ranking signal. FAQ added after owner sign-off on the one visible exception.
How
Four atomic commits:
opengraph-image.tsxprerenders a branded 1200x630 card per guide at build (title, category chip, wordmark); metadata auto-wires them, replacing generic /og.png for doc shares.Testing
Checklist
make lintpassesuv run python -m pytestis green (300 passed)