Crystal Ball checks covered

JS_RENDERED_CONTENT, missing source markup, rendered vs raw HTML

Guide detail

Choose Your Technical Level

This setting applies to the meaning, causes, and fix sections. Your choice carries to other Fix Library guides on this device.

Practical explanations and page-specific steps. Recommended for most readers.

What the flag means

Crystal Ball may warn about JavaScript-rendered pages when key content, headings, links, or metadata appear to be missing from the raw HTML but visible in the browser after JavaScript runs.

Google can render JavaScript, but rendering is a separate processing stage and not every crawler, scanner, or preview tool runs scripts. Keeping essential content, links, and metadata in the initial or server-rendered HTML makes the page easier to discover, verify, and use when a script fails.

Common causes

Common causes include React or Vue apps, headless builds, app-injected product content, JavaScript-only navigation, delayed schema, client-side filters, embedded reviews, and builders that show content visually but do not place it clearly in the initial source.

What to check next

Check whether the issue appears on one page or every page using the same template. Review recent content, theme, plugin, deployment, and server changes, then compare the live output with a known-good page.

How to fix it

Confirm the warning first and make a backup before editing the live site. If the change involves templates, code, DNS, redirects, or server settings, switch to Intermediate or ask for help before proceeding.

  • Custom HTML/static: Put key title, meta description, canonical, robots directives, H1, body copy, and internal links in the initial HTML whenever possible. Avoid relying on JavaScript to inject core SEO signals.
  • WordPress: Most WordPress pages are server-rendered, but block plugins and page builders can inject content later. Check View Source, not only the visual page, when Crystal Ball misses content.
  • Shopify: Product and collection content usually renders in HTML, but apps may inject reviews, filters, recommendations, or schema later. Make sure core product copy and metadata are present without app JavaScript.
  • Wix: Wix renders pages dynamically, so some scanner limits are possible. Confirm important content appears in the live page and use Search Console or rendered testing for high-stakes pages.
  • Webflow: Webflow exports mostly static HTML, but custom scripts, embeds, and third-party tools may inject content later. Keep essential SEO content in native Webflow elements.

Need help?

If the fix gets murky, visit Support and send the details. Bug reports and Crystal Ball questions are free support. Implementation and development work may be paid support, but we will tell you clearly before anything becomes paid. No surprise invoices from the tower.