THIN_CONTENT

Page content is too thin

Synviber can fix this automatically for a connected domain

What this check looks at

Whether a page's script/style-stripped text is under scorer.py's minimum character threshold and has no headings — a page can look complete in a browser and still trip this if the real content only renders after client-side JavaScript runs.

Why AI answer engines care

An AI crawler doing a plain HTTP GET sees no meaningful content on a page like this, even though a human visitor with JavaScript enabled sees a complete page.

Does Synviber fix it for me?

Yes, for a connected domain — the dashboard publishes the fix live at the gateway and re-scans to confirm it worked. Not available without a connected domain.

How to fix it manually

High severity

Scanner message: "Page content is too thin and may be rendered entirely by JavaScript, so a plain HTTP GET from an AI crawler sees no content"

Best fix: switch this page to server-side rendering (SSR) or static generation (SSG) so the HTML already contains the content. If a full rewrite isn't feasible right now, use 'dynamic rendering' instead: detect AI crawler user agents (GPTBot, ClaudeBot, PerplexityBot, CCBot, etc.) on your server and serve them a prerendered HTML snapshot of this page (e.g. generated once with a headless browser like Playwright and cached), while real visitors keep getting the normal JS app unchanged.

← Back to all issues