How to Fix a Low Code-to-Text Ratio
To fix a low code-to-text ratio, cut the HTML, CSS and JavaScript bloat on the page and add more genuine visible text — aim for a healthy share of readable content versus markup. In practice that means removing unused code, moving styles and scripts to external files, and making sure the page actually says something substantial.
What code-to-text ratio means (and how much it matters)
Code-to-text ratio is the proportion of a page that is visible text versus HTML markup. It's a minor, indirect signal — Google has no fixed threshold — but a very low ratio usually points to two real problems: bloated code (which slows the page) or thin content (too little for anyone to rank or cite). Fix those underlying problems and the ratio takes care of itself.
Reduce the code
- Move inline
<style>and<script>blocks to external, cacheable files. - Minify CSS and JavaScript; remove unused rules and dead code.
- Strip bloated markup from page builders (nested wrapper
<div>s, empty elements). - Lazy-load heavy widgets and avoid giant inlined data blobs.
Add real text
The more common and more valuable fix: the page is simply too thin. Add genuinely useful content — explanations, examples, an FAQ — that answers what the visitor (and an AI engine) is actually looking for. Check how much readable text a page has with our free keyword density analyzer, which shows the word count and how it's distributed.
A quick before-and-after
Imagine a service page that's one hero image, a three-word headline and a contact button — maybe 40 words of text inside hundreds of lines of builder markup. Its ratio is tiny, and there's nothing for Google or an AI engine to understand or quote, so the page gets 'discovered but not indexed.' Add a real explanation of the service, who it's for, how it works, what it costs, and a short FAQ — 600 words of useful text — and the page can now be indexed, rank, and be cited. The ratio rose, but that's a side effect; the real change is that the page now answers something.
Check a page's real text with the free keyword density analyzer, or run a full audit with PatchMySEO to find thin and bloated pages across your site.
Frequently asked questions
What is a good code-to-text ratio?
There's no official target. Many SEOs cite a rough guideline of 10% or more visible text, but Google sets no fixed threshold. Treat a very low ratio as a symptom of bloated code or thin content, and fix those instead of chasing a number.
Does code-to-text ratio affect rankings?
Only weakly and indirectly. It's not a direct ranking factor, but the things that cause a low ratio — slow, bloated pages and thin content — do hurt rankings and indexing.
How do I increase the ratio?
Two ways: reduce code (externalize and minify CSS/JS, remove unused markup) and add real content (useful text, examples, an FAQ). Adding genuine content is usually the higher-value fix.
Is a low ratio why my page isn't indexed?
It can be a sign. Pages that are mostly markup with little real text are often judged thin and left 'discovered but not indexed.' Adding substantial content is the fix.