Add factual document and breadcrumb structured data - #1266
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tanstack-com | 3b5994f | Commit Preview URL Branch Preview URL |
Sep 12 2026, 12:32 AM |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Documentation pages now identify their canonical page, technical article, publisher, and library-to-document breadcrumb in JSON-LD. Both generic and framework-specific routes use the same canonical URL they already publish in HTML. Modified dates come only from validated document freshness, and hidden libraries or missing documents emit no schema.
This is stacked on #1264 because the date metadata depends on that PR. JSON is serialized through the site's existing head scripts API with
<escaped so authored text cannot close the script element.Validation: full
pnpm testpassed, 526 tests passed and 3 skipped, TypeScript and lint clean. No-JavaScript browser checks cover both documentation routes, canonical and title agreement, undated documents, a dated fixture, safe script-like title text, and a missing-document 404. Schema.org's validator reports 0 errors and 0 warnings for the generated Start overview graph. Client navigation replaces the article and breadcrumb metadata without reloading the document or leaving duplicate article entities. All runtime checks passed in the final run.