Quick answer
NOTABIS reports JavaScript-rendered content when a page looks nearly empty in its initial HTML but a bounded browser sample finds important text, headings, links, or metadata after scripts run. JavaScript is not automatically bad for SEO; the concern is relying on it as the only delivery path for content that users and crawlers need. Keep SEO-critical content in the initial response where practical, then use rendering as an enhancement.
What the issue means
Server-rendered pages send their main content in the first HTML response. Client-rendered pages send a shell and populate it later with JavaScript. A client-rendered application can work well, but its crawlability depends on script execution, timing, resources, and the crawler's rendering support.
The useful question is not whether a framework appears in the source. It is whether the initial response contains the page's meaningful content and links, and whether the rendered page adds information that matters.
Why it matters for SEO
Search systems vary in when and how they execute JavaScript. If a title, heading, copy, internal links, canonical, or structured data appears only after a script runs, it may be discovered later or missed by a crawler that cannot render the page. Delivering important content in the initial HTML makes the page's purpose and navigation clearer to more clients.
Rendering also has a cost for users and infrastructure. A practical architecture can still use JavaScript for filters, interactions, and progressive enhancement while keeping the primary page useful before scripts finish.
How NOTABIS detects it
The HTTP analysis first records signals such as very little meaningful text, an empty application container, a script-heavy document, framework indicators, or few content elements. A bounded browser sample is then selected from pages that look likely to depend on JavaScript. NOTABIS compares initial and rendered measurements for meaningful text, H1s, internal links, title, and other fields.
The finding is created only when the rendered sample provides evidence such as a new H1, new internal links, a large text increase, or a title that was absent from the initial HTML. Browser evidence is bounded and may be unavailable, so a clean result does not prove that every page is fully server-rendered.
How to check it yourself
- View source, disable JavaScript, and read the page's initial HTML.
- Check whether the title, main content, headings, canonical, links, and structured data are present before scripts run.
- Enable JavaScript and compare the rendered DOM with the source.
- Test slow networks, blocked scripts, and common crawlers in a staging environment.
- Inspect browser console and network logs for failed bundles or API requests.
- Use rendered screenshots or a crawler that records both raw and rendered HTML for representative templates.
How to fix it
Render the page's core title, text, headings, links, canonical, and structured data in the initial HTML response where practical. Use server-side rendering, static generation, or a hybrid route for content pages, and keep JavaScript for interactions and enhancements. Ensure APIs and bundles are cacheable and resilient, and avoid hiding the only copy behind a client-side request.
Re-test both source and rendered output after changing the delivery model. Confirm that the page still works with scripts enabled and that interactive features have not been removed unnecessarily.
When this is intentional or does not need fixing
A dashboard, authenticated application, map, or interactive tool may need JavaScript for its private or task-focused interface. A small client-side enhancement that does not replace important page content is not a reason to rewrite the application. Keep public, indexable content and discovery paths available in the initial response when they matter.
Related issues
Read crawl coverage and audit limitations, missing H1 tags, missing title tags, and structured data and JSON-LD. Google’s JavaScript SEO basics explains rendering and crawlable content. Core Web Vitals vs markup heuristics explains why markup signals do not measure user-facing performance.
Run a NOTABIS audit
Run a NOTABIS SEO audit with rendered evidence enabled where available to compare initial HTML with the bounded browser sample.