Contact
What are you interested in?
JavaScript SEO.
JavaScript SEO deals with making sure that websites whose content is generated wholly or partly by JavaScript can be read in full by search engines and AI crawlers. The core question is whether the relevant content is already in the delivered HTML or only comes into being in the browser.
JavaScript SEO — Explained in Detail
Modern websites are often built with JavaScript frameworks such as React, Vue or Angular. With pure client-side rendering, the server delivers an almost empty HTML page, and the actual content is only assembled in the browser. To people, the result looks the same. To crawlers, it makes a big difference whether they can read the text directly or first have to execute a script.
Google renders JavaScript with an up-to-date Chromium browser, but in an additional step that costs time and resources. According to publicly available analyses, many AI crawlers, by contrast, do not execute JavaScript and only see the original HTML. Content that only appears after a click, on scrolling or after logging in remains invisible to all crawlers.
An example: a start-up builds its website as a single-page app. Service descriptions and FAQs are loaded from an API. In Google Search the pages appear with a delay, and in ChatGPT and Perplexity answers not at all, because their crawlers only see an empty shell. Switching to server-side rendering or static generation solves this without changing the design.
Rendering options at a glance
With client-side rendering, the content is created in the browser; with server-side rendering, on the server for every request; with static generation, once at build time. For pages that are meant to be found, server rendering or static generation is the safe choice: the full text sits in the HTML, loads faster and is readable by every crawler. Frameworks such as Next.js combine this with interactive components.
It is also important that links are genuine `<a href>` elements. Crawlers cannot follow navigation built on click handlers without an address, so the linked pages are never discovered.
Checking JavaScript SEO
A simple test: open the page in the browser with 'View page source' (not the developer tools). If the main content appears there in plain text, the page is readable for crawlers. The URL Inspection tool in Google Search Console additionally shows what Google sees after rendering.
We build our websites on Next.js with server-side rendering, so that Google and AI systems receive the full content without a detour. For existing JavaScript websites we check this in the website audit; accessibility for AI systems is shown by the AI visibility check.
Related Page
Web Development ZurichFrequently Asked Questions About JavaScript SEO
Yes. Google renders pages with an up-to-date Chromium browser and can index content generated by JavaScript. This happens in an additional step, however, and can be delayed. Content that only appears after clicks or logins is not seen by Google.
According to publicly available analyses, many AI crawlers do not execute JavaScript and only read the delivered HTML. Whatever is only created in the browser is missing for them. For visibility in AI answers, server-rendered content is therefore the safe choice.
Not in itself. The problem is pure client-side rendering, where the content only comes into being in the browser. With frameworks such as Next.js, React websites can be rendered on the server or generated statically, so that the content sits directly in the HTML.
More Terms Starting with "J"
Ready for Your Project?
Apply this knowledge to your website — DLM Digital will help you.