fix(seo): route-specific OG images per Artemii spec (PILOT-26)#11
Merged
Conversation
Per Artemii's comment on PILOT-26, each top-level route gets its own 1200×630 Open Graph image. This PR wires up the routing structure; the actual JPGs need to be dropped in /public/og/ by hand: / → /og/main.jpg /plans → /og/plans.jpg /docs/... → /og/docs.jpg /blog/... → /og/blogs.jpg (fallback for individual posts too) Until the JPGs land, the og:image meta tags will 404. The fallback default in BaseHead.astro stays /img/pilot.png for any page that doesn't override. public/og/README.md spells out the expected filenames + dimensions. Changes: - index.astro: ogImage → /og/main.jpg - plans.astro: ogImage added → /og/plans.jpg - blog/index.astro: ogImage added → /og/blogs.jpg - DocLayout.astro: ogImage prop with /og/docs.jpg default; pass-through so individual doc pages can override if needed BaseHead already emits og:image, twitter:image, twitter:card=summary_large_image. Closes PILOT-26
TeoSlayer
force-pushed
the
fix/pilot-26-og-images-153052
branch
from
34ca4d7 to
ce45b2c
Compare
hank-pilot
approved these changes
May 29, 2026
Contributor
hank-pilot
left a comment
hank-pilot
left a comment
There was a problem hiding this comment.
Approving PILOT-26 OG image routing.
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.
Per Artemii's comment — each top-level route gets a dedicated 1200×630 OG image.
Wires the routing in BaseHead/DocLayout. JPGs themselves need to be dropped at
/public/og/{main,plans,docs,blogs}.jpg(README in that dir explains).//og/main.jpg/plans/og/plans.jpg/docs/*/og/docs.jpg(DocLayout default; overridable per page)/blog/*/og/blogs.jpg(per Artemii's fallback note)Blast radius: small. Until the JPGs land the og:image URLs 404 — same as today for any page that uses the BaseHead
/img/pilot.pngdefault but with the right per-route structure ready. Twitter/Facebook crawlers will fall back to scraping the page itself.Verification:
npm ci && npm run buildpasses on this branch.Closes PILOT-26