<b>Your JSON-LD has a render budget — and bloated graphs blow it</b>

<b>Your JSON-LD has a render budget — and bloated graphs blow it</b>

Here's the unglamorous truth: Googlebot fetches your raw HTML for structured data before full render in many cases, but if your JSON-LD is injected client-side by a tag manager, it may miss the first pass entirely. As of this week, more crawl-diagnostics threads point to GTM-injected schema as the silent reason 'no items detected' shows up despite working markup in the browser.

The rule pros follow — render JSON-LD server-side, in the initial HTML, never via deferred JavaScript. If a tag manager is your only option, accept that it's a gamble on the rendered pass.

What it means for you — view-source (not inspect-element) your pages. If schema isn't in view-source, Google's first crawl can't see it, and AI crawlers that don't execute JS definitely can't.

Watch this: JS-injected schema is the most common invisible failure of 2026.