feat(seo): add organization logo, article images, and stable author ids to JSON-LD - #106
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Aug 4, 2026
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.
What
Three scoped JSON-LD enrichments, no other schema changes:
lib/structured-data.tsnow carrieslogo: https://docs.steel.dev/images/logo.png. The asset is 376x280px, comfortably above Google's 112x112px minimum for the logo rich result.buildTechArticleSchemaaccepts an optionalimage(absolute URL). Integration pages pass their OG image absolutized withDOCS_URL(https://docs.steel.dev/og/<path>). Cookbook recipes are served by the same catch-all route and get per-page OG images fromapp/og/[...slug]/route.tsx, soRecipeJsonLdnow emitsimage: https://docs.steel.dev/og/cookbook/<slug>too.getAuthorPersonId(handle)returnshttps://docs.steel.dev/cookbook/authors/<handle>#person. Both the recipe author Persons (components/recipe-jsonld.tsx) and the ProfilePage Person (components/author-profile.tsx) use it, so Google can merge the recipe author with the richer profile entity (reconciliation happens on@id, noturl).Test plan
bun test tests/structured-data.test.ts: 6 pass, 0 fail. New assertions cover the Organization logo, TechArticle image present when provided and omitted when absent, and identical Person@idin both components' emitted JSON-LD.bun test: 300 pass, 0 fail.bun run check: clean.