fix(seo): align JSON-LD BlogPosting image with per-article OG images across all journal articles#52
Open
VaultSparkStudios wants to merge 1 commit into
Open
Conversation
…s all journal articles All 9 journal articles had a stale generic image URL (og-image.png or og-journal.png) in their BlogPosting schema.org image field while their og:image meta tags already pointed to the correct article-specific images. Google rich results use the JSON-LD image, so this mismatch caused generic placeholders to appear in search rather than the actual article artwork.
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
2 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.
What
All 9 published Signal Log articles had a stale generic image URL in their
BlogPostingJSON-LD structured data, while theirog:imagemeta tags already pointed to the correct per-article artwork.assets/og-image.png(site-wide generic)assets/og/og-journal-first-sparks.pngassets/og-image.png(site-wide generic)assets/og/og-journal-studio-os-public.pngassets/og-image.png(site-wide generic)assets/og/og-journal-vault-opened.pngassets/og-journal.png(journal generic)assets/og/og-journal-community-enters-the-vault.pngassets/og-journal.pngassets/og/og-journal-dreadspike-origins.pngassets/og-journal.pngassets/og/og-journal-nine-ranks-of-the-vault.pngassets/og-journal.pngassets/og/og-journal-q1-2026-dispatch.pngassets/og-journal.pngassets/og/og-journal-roadmap-goes-public.pngassets/og-journal.pngassets/og/og-journal-signal-log-launches.pngWhy it matters
Google's Article / BlogPosting rich results use the JSON-LD
imagefield, not theog:imagemeta tag. With mismatched images, Google Search would show a site-wide placeholder instead of the actual article artwork in rich snippets, Discover cards, and AI Overviews. All 9 per-article PNG files already existed inassets/og/; this PR just wires the JSON-LD to the correct ones.What to verify
imagein the BlogPosting result should now match the article-specific OG image, not the generic placeholder.og:imagemeta tags were changed (only the JSON-LD<script>blocks).Out of scope
archive/anddispatches/are listing pages with no BlogPosting schema — not affected.building-vault-membership/already usedog-journal.pngin both OG and JSON-LD (consistent), left as-is.Generated by Claude Code