On sites built with React, Vue or Angular, what the server sends and what the user sees can be very different. Google renders JavaScript, but later and not always the same way; if the title, canonical or links only exist after rendering, the risk is high.

AD2SPIDER can render every page and compare the raw HTML with the result: it flags tags that only appear after rendering or that JavaScript changes, links and content added by scripts, noindex or nofollow mismatches and console errors.

JavaScript SEO errors

They stop the page from working or being indexed properly. Fix them first.

Noindex only in original HTML

Why it matters
The original HTML has noindex and JavaScript removes it. Google does not render pages with noindex: the page will not be indexed even though the final result lacks it.
How to fix it
If the page should be indexed, remove noindex from the HTML the server sends.

Priority: highDocumented by GoogleDocumentation ↗

Nofollow only in original HTML

Why it matters
The original HTML has nofollow and JavaScript removes it: Google may not follow the page's links.
How to fix it
Pick one directive and put it in the server HTML.

Priority: mediumDocumented by GoogleDocumentation ↗

Canonical mismatch after rendering

Why it matters
The canonical in the original HTML and the one in the rendered HTML point to different URLs: Google may use either.
How to fix it
Keep a single canonical, the same before and after JavaScript (preferably in the server HTML).

Priority: highDocumented by GoogleDocumentation ↗

JavaScript SEO warnings

Real problems worth fixing.

Canonical only in rendered HTML

Why it matters
The canonical is added by JavaScript. Google processes it when rendering, but it is not guaranteed.
How to fix it
Include the canonical in the HTML the server sends.

Priority: mediumDocumented by GoogleDocumentation ↗

Title only in rendered HTML

Why it matters
The title is set by JavaScript: search engines that do not render miss it and Google sees it later.
How to fix it
Put the title in the server HTML.

Priority: mediumDocumented by GoogleDocumentation ↗

Title updated by JavaScript

Why it matters
The title in the original HTML and in the rendered HTML differ: Google may use either.
How to fix it
Make the server HTML carry the final title.

Priority: lowDocumented by GoogleDocumentation ↗

Meta description only in rendered HTML

Why it matters
The meta description is added by JavaScript.
How to fix it
Put the meta description in the server HTML.

Priority: lowDocumented by GoogleDocumentation ↗

Meta description updated by JavaScript

Why it matters
The meta description in the original HTML and in the rendered HTML differ.
How to fix it
Make the server HTML carry the final meta description.

Priority: lowDocumented by GoogleDocumentation ↗

H1 only in rendered HTML

Why it matters
The H1 is added by JavaScript.
How to fix it
Put the H1 in the server HTML.

Priority: lowDocumented by GoogleDocumentation ↗

H1 updated by JavaScript

Why it matters
The H1 in the original HTML and in the rendered HTML differ.
How to fix it
Make the server HTML carry the final H1.

Priority: lowDocumented by GoogleDocumentation ↗

Contains JavaScript content

Why it matters
A relevant part of the page text only appears after JavaScript runs.
How to fix it
Serve the main content in the HTML (server-side rendering or prerendering).

Priority: lowDocumented by GoogleDocumentation ↗

JavaScript redirect

Why it matters
The page sends users to another URL with JavaScript. Google may follow it when rendering, but a server redirect is more reliable and faster.
How to fix it
Use a 301 redirect on the server.

Priority: mediumDocumented by GoogleDocumentation ↗

Pages with blocked resources

Why it matters
robots.txt prevents fetching page resources (JavaScript, CSS, images…): Google renders without them and may miss the real content or layout.
How to fix it
Allow in robots.txt the resources needed to display the page.

Priority: mediumDocumented by GoogleDocumentation ↗

Pages with JavaScript errors

Why it matters
The browser console logs errors while loading the page: an error can stop content or links from showing.
How to fix it
Check the errors in the browser developer tools and fix them.

Priority: mediumDocumented by GoogleDocumentation ↗

Pages with JavaScript warnings

Why it matters
The browser console logs warnings while loading the page.
How to fix it
Review them: they often anticipate compatibility or performance problems.

Priority: lowDocumented by GoogleDocumentation ↗

Rendering failed or timed out

Why it matters
The page did not finish rendering in time or the browser failed: the data comes from the original HTML or a partial load.
How to fix it
Check load time and slow resources; if needed, raise the wait after load in Configure › Rendering.

Priority: mediumDocumented by GoogleDocumentation ↗