Skip to content

hotfix: restore TechArticle 'name' field on main (regression from cb507923) - #1392

Merged
Flotapponnier merged 1 commit into
mainfrom
hotfix/jsonld-techarticle-name-restore
Jul 24, 2026
Merged

hotfix: restore TechArticle 'name' field on main (regression from cb507923)#1392
Flotapponnier merged 1 commit into
mainfrom
hotfix/jsonld-techarticle-name-restore

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Regression

PR #1257 (commit 68453ee, 2026-07-17) added `name: benchmark.title` to TechArticle JSON-LD on all 3 relevant files:

  • `src/app/benchmarks/[slug]/page.tsx` (bench slug pages)
  • `src/app/benchmarks/[slug]/[chain]/page.tsx` (per-chain pages)
  • `src/lib/hub-jsonld.ts` (methodology hub)

The very next day, commit cb50792 (2026-07-18, hotfix for GSC Dataset warnings — cherry-picked from dev) silently DROPPED the `name` line while rewriting the JSON-LD block. Bad merge resolution, no explicit revert commit.

Prod has been shipping TechArticle nodes without `name` for a week. GSC "Item name: N/A" warnings on 5+ bench URLs (and growing as Google recrawls).

Fix

Straight cherry-pick of PR #1257 (68453ee) onto current main. Restores the 3 missing `name:` lines. Dev is already correct — this only fixes the main-side regression.

Post-merge

Run `vercel --prod`, then "Validate fix" in GSC on the affected URLs.

…ation (#1257)

GSC flagged 'Missing field name' on aggregator-head-lag JSON-LD (and by extension every bench slug page + every per-chain page + the methodology hub — all TechArticle nodes shipped only 'headline'). Schema.org Article inherits 'name' from CreativeWork; Google's Rich Results validator treats it as required even when 'headline' is present. Add 'name' alongside 'headline' with the same value on all three affected builders.

Co-authored-by: Florent Tapponnier <contact@mobula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant