feat: add homepage JSON-LD structured data#521
Merged
Conversation
|
|
|
Bugbot is not enabled for this team, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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.
Requested by Elliot Hesp · Slack thread
Fixes #519
Summary
Before: the marketing homepage only exposed a
<title>plus Open Graph / Twitter meta tags. There was no machine-readable entity on the page, so search engines and LLMs had no structured entity to identify or cite docs.page.After: the homepage head now emits a schema.org JSON-LD block describing docs.page as a
SoftwareApplicationpublished by Invertase, alongsideWebSiteandOrganizationnodes.How: the JSON-LD lives in
app/src/components/homepage/index.tsx, injected as a<script type="application/ld+json">inside the existingnext/head<Head>block (matching the file's current head-injection style). It is a single@graphwith three linked nodes:url,logo,sameAs→ GitHub org + X handle).publisher→ Organization.applicationCategory: DeveloperApplication,operatingSystem: Any,isAccessibleForFree: true, Apache-2.0license,codeRepository→ the GitHub repo,author/publisher→ Organization, and a free (price: "0") offer.All values are pulled from the repo (existing meta description, social image,
@invertaseiohandle, LICENSE, README asset URLs) — no fabricated ratings, review counts, or invented URLs.Scope
app/(hosted site, MCP, Ask AI)packages/cli/packages/mdx-bundler/docs/(product documentation)Type of change
Test plan
tsc --noEmitpasses on the changed filenext dev): fetched/, confirmed theapplication/ld+jsonscript renders andJSON.parsesucceeds with@graph= Organization, WebSite, SoftwareApplicationdocs/(if user-facing) — n/aNotes for reviewers
The Invertase logo URL (
static.invertase.io/.../invertase-rounded-avatar.png) is the same asset referenced in the repo README. No breaking changes.Closes #519.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DHjPAWXa8wkqtsVzJVyBne
Generated by Claude Code