Restaurant JSON-LD: Nobody Catches opens: "eleven"
I added Restaurant structured data to my restaurant-discovery PWA, then fed the same three defects to three validation layers to measure which one catches what.
Tags
6 posts
I added Restaurant structured data to my restaurant-discovery PWA, then fed the same three defects to three validation layers to measure which one catches what.
A JSON-LD parser passes markup no search engine can read: schema.org sets @vocab, so typos and wrong casing expand into valid JSON-LD. A 60-line schema-aware validator catches them in CI, with real logs.
The same Product entity in three syntaxes, bytes and fragility measured. Google treats them equally, so the reason to choose JSON-LD is coupling, not ranking.
A 5-day audit of my 4-language blog: 12 broken links, 4 hreflang pairs, 405KB blocking CSS, 21 drifted translations, all fixed and locked in with build gates.
I aimed a 30-line checker at my build output: 248 posts passed their hreflang clusters, the homepage failed. Google's reciprocity rules, run logs, and the fix.
Inject LocalBusiness JSON-LD with JavaScript and the raw HTML has zero ld+json blocks. I compare it with server-side output, Google's stance and ranking limits.