Schema markup with Claude Code: JSON-LD that Google still rewards
Point it at a page and it reads the page first, then writes JSON-LD that matches what is actually there. It knows Google's current gallery, not 2021's: it will tell you FAQ rich results ended on 7 May 2026 and HowTo in 2023, and it will not fabricate a rating to get you stars. We ran it on a page of ours that sells a $9.99 pack.
What you get
- It knows what Google retiredFAQ rich results ended 7 May 2026, HowTo in 2023, sitelinks search box in 2024. It says so before writing the markup, and separates 'valid schema.org' from 'Google will show it'.
- It refuses to inventNo aggregateRating appeared, because there is no rating on the page. That is the one field that puts stars in search, and the easiest thing for a tool to fake.
- It found a result we were giving awayBreadcrumbs are still supported and the page had none.
- One @graph, not four script tagsCombines the types cleanly, which is what Google recommends.
- It pairs with a checkerThe skill writes the markup and hands you a checklist. The check.py on this page runs that checklist for you, offline, and fails a build when a required field is missing.
How we tested itPrompt, model, time, cost and what went wrong
Use the schema skill on https://glintmake.com/sketch-to-3d-model/. It is a tool page that sells a one-off $9.99 pack of 10 3D models and has a free tier. It already has WebApplication and FAQPage markup. Tell me what rich results it currently qualifies for, what it is missing, and write the markup. Do not invent anything the page does not say.
- Agent · model
- Claude Code · Opus 5 (1M context)
- Time
- 1 min 22 s
- Cost
- about $0.20
- Tested
- Oct 21, 2026
It is advice plus code, not an edit: it hands you the JSON-LD and you paste it. On a page with existing markup you have to decide yourself whether to merge into one @graph or keep separate blocks.
It asks five questions up front (page type, target rich results, available data, existing schema, stack). Answer them in the prompt or you will do a round trip first.
Nothing in it checks the markup against the live page afterwards. We validated the required fields ourselves; the skill gives you a checklist and expects you to run Google's Rich Results Test.
Questions
Will this get me star ratings in search?
Only if your page really has ratings. The skill will not mark up a rating that is not on the page, and Google penalises markup that does not match visible content.
Does FAQ schema still do anything?
Not for Google rich results — those ended on 7 May 2026. It is still read by AI answer engines, so the skill keeps it and tells you the distinction instead of silently deleting it.
Does it edit my files?
In our run it produced the JSON-LD and the reasoning; pasting it in was ours to do. On a codebase it can write the file if you ask.
What did it cost?
About $0.20 and 1 minute 22 seconds for one page, on Opus 5.
Which rich results has Google retired?
FAQ rich results ended on 7 May 2026 and the documentation was removed that June. HowTo rich results were retired in September 2023. The sitelinks search box (WebSite SearchAction) went in November 2024. All three are still valid schema.org and still read by answer engines — they just no longer change how your page looks in Google.
How do I check the markup without a Google account?
Google's Rich Results Test has no API, so nothing can automate it. The check.py on this page does the part a script can: every field Google documents as required, ISO 8601 dates, absolute URLs, bare prices, real availability values, and a warning for each retired type. It runs offline with no dependencies and exits non-zero on errors, so it drops into a build. It also prints the two things it cannot know, rather than implying it checked them.
What did it catch on your own site?
On 21 October 2026, one pass across five pages: four selling pages were missing availability and url on their offers, and image-to-stl had carried a HowTo block since launch — retired by Google in September 2023, so it had produced nothing for two years. The offers are fixed; the HowTo is kept and labelled.
Credits
Made by coreyhaines31/marketingskills (MIT license, created Sep 14, 2026, 55.8k stars). We tested version e85f3cb on Oct 21, 2026, and it has not changed since. The star count and version here are refreshed from GitHub, not typed in. One of 52 marketing skills in that repo.