feat: add SEO metadata to the brand site#4
Merged
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
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.
The brand-guidelines page shipped with a bare
<head>, so search engines and social platforms had nothing to index or render in link previews.This adds the full set of static SEO signals to
site/index.html: a meta description, canonical link, indexable robots directive, Open Graph and Twitter card tags, andOrganizationJSON-LD. Because the site is a single client-rendered page, all of it lives in the static HTML rather than a runtime head manager.It also adds a generated 1200×630 social share card (
og:image) built once byscripts/generate-og-image.mjsand committed as a static asset, plussitemap.xmlandrobots.txt. A Vitest spec guards the head tags and crawl files against regression.One caveat worth knowing: this deploys as a GitHub Pages project page at
openwdl.github.io/brand/, where crawlers only honorrobots.txtat the host root, not under/brand/. So the<meta name="robots">tag is what actually governs crawling today; therobots.txtis included for completeness and becomes authoritative if the site ever moves to a custom-domain root.