SEOmise

Region and currency

  1. Home
  2. All modules
  3. Website health
  4. JavaScript rendering

Website health

JavaScript rendering

JavaScript SEO: scan sites built with React, Vue and similar as visitors see them

Some sites send an almost empty page and build the text with JavaScript. SEOmise opens their pages in a real browser, so titles, text and links that only appear after the scripts ran are checked too.

Illustration of the screen, without data.

Why it matters

From the problem to what SEOmise does

The problem

An empty page to a crawler

Sites built with React, Vue or Angular, and some shop and site-builder themes, send a page whose text is added by scripts. A plain scan sees little text and few links, so the report misses most of the site.

What JavaScript rendering does

JavaScript SEO: scan sites built with React, Vue and similar as visitors see them

  • A real browser. Headless Chromium runs the page's scripts, then SEOmise reads the page.
  • Links found by scripts. Links that only appear after the scripts ran are followed like any other link.
  • Capped and queued. A set number of pages per scan, a time and memory limit per page, on the queue so the scan is never held up for long.

How it works

Three steps, start to finish

  1. Switch it on for the projectWebsite health: tick "Render JavaScript" next to the scan button.
  2. Scan as usualThe scan reads every page as before; the start page and the pages that look built by JavaScript (or every page, if you choose) are then opened in a browser on the queue.
  3. See what only scripts addIssues → Only after JavaScript lists the text, links, titles and tags that only appear once the scripts ran, page by page, with three ways to fix each.

Features

What you get with JavaScript rendering

A real browser

Headless Chromium runs the page's scripts, then SEOmise reads the page.

Links found by scripts

Links that only appear after the scripts ran are followed like any other link.

Capped and queued

A set number of pages per scan, a time and memory limit per page, on the queue so the scan is never held up for long.

A fallback when the browser cannot run here Beta

Pages that arrive almost empty can be read again through the Zyte API, a rendering service, when SEOmise's own browser is not used for the scan: only after your robots.txt allows it, within a monthly number of pages per workspace, and through a bot wall only on a site you have verified. The Zyte API fallback is in early access: ask for it and our team switches it on once its key and check are in place.

Every request checked

Each request a page makes is checked before it is made: only public addresses, never your server's own network. Redirects are checked hop by hop, robots.txt is followed and no cookies are kept.

The page as sent beside the page as shown

Words, links, title, main heading, description, canonical and robots tag, side by side for every rendered page.

Only where it is needed

By default only pages that arrive almost empty with a framework's marks are rendered, plus the start page to compare; choose "Every page" when the whole site is built in the browser.

Browser check in your reports

Audit reports, the free audit and the paid report show the page on a computer and a phone, what crawlers that don't run scripts see compared with a browser, how much the page depends on JavaScript, script errors, parts that failed to load and the outside services it uses.

Our phone check

Does the page fit a phone screen, is the text big enough, are links easy to tap, does a pop-up cover the page? Google retired its Mobile-Friendly Test in December 2023; this is our own check.

Three ways to fix

Steps for your platform to put the content in the page your server sends, a guided walk through them, or our team does it for you.

Before and after

What changes with JavaScript rendering

Before: a plain scan of a JavaScript site. After: with JavaScript rendering. Drag the handle, or use the arrow keys, to compare.

A plain scan of a JavaScript site

  • Pages that look empty
  • Links the scripts add never found
  • Reports that miss most of the site

With JavaScript rendering

  • Text and headings as visitors see them
  • Links added by scripts followed
  • Pages that rely on JavaScript counted
BeforeAfter

Illustration of the difference, not a measured result.

What it needs

No surprises after you sign up

Turn a card over for the detail.

Website health

Website health

JavaScript rendering is part of the site scan.

Every platform

Whatever your site runs on

What JavaScript rendering does on each kind of website, from SEOmise's site connectors to step-by-step guidance.

WordPress

WordPress and WooCommerce
Fully supported

Works on any public website, whatever it is built on.

Laravel

Sites built on Laravel
Fully supported

Works on any public website, whatever it is built on.

Any PHP site

Custom PHP, CodeIgniter, Symfony, Drupal, Joomla
Fully supported

Works on any public website, whatever it is built on.

Every other platform

Shopify, Wix, Squarespace, Webflow, static sites and the rest
Fully supported

React, Vue, Angular, Next.js and Nuxt sites, Shopify, Wix, Webflow and every other platform: nothing to install.

About the site connectors

Where JavaScript rendering is included

JavaScript rendering is not part of a public plan at the moment.

See pricing

Not sure it fits?

Ask Mise, our assistant, in the help centre, or book a call and we will show you JavaScript rendering on a site like yours.

Questions

JavaScript rendering: common questions

Do I need it?

Only if your site builds its text with JavaScript. If a scan of your site shows pages with very little text that look full in a browser, switch it on.

Is every page rendered?

By default the start page and the pages that look built by JavaScript; choose "Every page" to render them all. Either way a set number per scan, the same for every plan, closest to the home page first. It is included on every plan. The rest are read as the server sends them.

Why does it matter what only appears after JavaScript?

Search engines that do not run scripts, and AI assistants, read your page as your server sends it. Google renders pages later and not always. Text, links and tags that only scripts add may never count.

Is the browser check a speed test?

No. It shows what a browser sees: errors, broken parts, outside services and how the page looks on a phone. Speed comes from Google Lighthouse. A page that rendered only partly is marked "Needs a re-check" and costs nothing.

Is it safe for my site?

It opens your pages like a visitor's browser, a few at a time, and follows your robots.txt like every scan.

Which plans include JavaScript rendering?

Plans and add-ons are on the pricing page. If JavaScript rendering is not listed there yet, ask us how to get it.

Try JavaScript rendering on your own site

Add your site; your first scan becomes your Day 0 baseline. Nothing is bought or published without your approval.

No ranking guarantees: just clear work, with the evidence.