Low Text-to-HTML Ratio (Diagnostic for Thin Main Content or Code Bloat, Not a Ranking Factor)
In Neova Runs from the crawl itself: nothing to set up.
Rule last reviewed October 17, 2026
Text-to-HTML ratio is a tool metric, not an engine signal: John Mueller answered 'no' when asked whether it affects Google rankings.
How Neova Finds It
Neova reads the HTML of every page it crawls and looks for this.
Why It Matters
The ratio itself changes nothing for Google, Bing or AI engines. What it can point to does matter: thin main content for users and Google's helpful content guidance, and heavy HTML that slows rendering or is cut at Googlebot's 2MB.
The Ticket It Writes
ON-049 · Low Text-to-HTML Ratio (Diagnostic for Thin Main Content or Code Bloat, Not a Ranking Factor)
Expected Result: All in-scope pages pass 'Low text-to-HTML ratio (diagnostic for thin main content or code bloat, not a ranking factor)'.
How to Check the Fix: 1. Run the check again in Neova 2. Spot-check sample URLs across affected templates 3. Record the re-check date and period label next to the baseline 4. Known limits of this check: Mueller's answer is a 2018 hangout reported by Search Engine Journal (video linked there), not Google documentation. Bing and AI vendors say nothing about the ratio. Conductor says low density makes meaning hard for AI to extract, a vendor claim. Pages with inline JSON, SVG or large scripts score low with no content problem. 5. Sources: https://www.semrush.com/kb/542-site-audit-issues-list | https://www.searchenginejournal.com/ranking-factors/code-to-text-ratio/ | https://help.netpeaksoftware.com/en/support/solutions/articles/103000243642-what-seo-issues-does-netpeak-spider-detect-
Neova writes this ticket for every affected page group and sends it to Jira, Linear, Asana and the rest, after you approve it.