Does your content depend on JavaScript?
It reports indexable pages whose initial HTML lacks their main content.
What Check Engine measures
The check reads the crawler's JavaScript-dependent flag and leaves out URLs recognised as intentionally excluded from search. Any remaining affected pages can produce a finding. Severity is high when their share of indexable pages is greater than 0.5, and medium otherwise. The ratio uses the indexable page set, so it does not treat failed responses as readable content. For example, an affected share of exactly 0.5 stays in the medium-severity group.
The check uses the crawler's record of pages that need JavaScript. It covers pages intended for search. Script execution time and interactive controls need separate tests.
How to read the result
The finding lists affected URLs and their share. A loaded browser view may show text absent from the original response. Inspect both views when reviewing the result.
Why it matters
Content can be present after loading and absent from the first response. That distinction explains the check without assuming that every reader executes the same scripts or that a missing initial body means the page has no useful content at all.
How to fix it
Compare source HTML with the loaded page. Serve the main text, links and essential details from the server or a static build where practical. Test the affected templates after changing their rendering path. Keep scripts for interaction while making the information they enhance available in the first response.
How to run a JavaScript SEO audit
What we found in field audits
Problems in Content quality were found on 14 of the 14 sites we audited. These are area totals. Read the field-audit method.
Method note
backend/seo_engine/checks/content.py, js_rendering, revision 0bb8e8d3.
Common questions
When does JavaScript-dependent content become a high-severity finding?
High severity applies above a 0.5 share of indexable pages. At the boundary, the affected pages stay in the medium group.
Do deliberately noindex URLs count toward JavaScript content problems?
The test sets aside pages intentionally excluded from search. Its reported set concerns content meant to be found.
Does the JavaScript content check measure interactive controls?
No. Interactive controls need separate tests. This result follows the crawler's record of missing initial content.