Technical SEO
Client-side rendering
Client-side rendering is building a page’s content in the browser with JavaScript after the initial HTML, which is often close to empty, has loaded.
What is client-side rendering?
Client-side rendering is building a page’s content in the browser with JavaScript after the initial HTML, which is often close to empty, has loaded. It is the default in several popular front-end frameworks.
Why this is worth knowing
Content, internal links and structured data that exist only after JavaScript runs are visible to some systems and invisible to others.
How it works in practice
The exposure is measured by fetching the page without JavaScript and comparing what is present. Mitigations are server-side rendering, pre-rendering, or dynamic rendering as a fallback.
The usual mistake
It is not automatically fatal for search, because the main crawler does render. It is a problem for everything else that reads the web, which is now a long list.
That is the whole of it. Anything more specific depends on the site in front of you.
Where this comes up in the work
It is part of App Store Optimization, and more specifically of App creative and screenshot testing. Across the rest of the work it shows up in:
- Marketplace Marketing, in which it is the first thing checked before finding the categories where you are mis-filed and invisible
- Content and Editorial, which cannot be done properly without it
- Lifecycle and Email, where getting it wrong shows up in finding the moment in the journey where people go quiet
- Analytics and Measurement: it is the reason annotating the graph so a change has a cause beside it is scoped the way it is
What to check
Two questions that establish whether this is actually in order on a given site:
- Whether it is enforced by the build or maintained by discipline
- Whether the figure quoted for it came from a measurement or from a benchmark
More in Technical SEO
Common questions
Will fixing client-side rendering move rankings?
Not on its own, and claims that it does are usually overselling. Content, internal links and structured data that exist only after JavaScript runs are visible to some systems and invisible to others.
How do you check client-side rendering on a site?
The exposure is measured by fetching the page without JavaScript and comparing what is present. Mitigations are server-side rendering, pre-rendering, or dynamic rendering as a fallback. Start at FAQ and Q and A schema systems if nothing has been built yet, Featured answer capture if something has and it is not working.
Whose job is client-side rendering?
Whoever is accountable for making the stock feed and the site agree before the customer finds out. Problems with this tend to persist because nobody is. The short version is here. Singapore and Surat are the long ones.
Is client-side rendering expensive to get right?
It depends entirely on where the problem originates. Establishing that is the first piece of work.
How urgent is client-side rendering?
It comes before work that assumes it is already handled, and after anything actively blocking indexation.
What is the evidence for client-side rendering mattering?
The symptom is usually downstream: content, internal links and structured data that exist only after JavaScript runs are visible to some systems and invisible to others, showing up as something else entirely in the reporting. Two of these come up often enough to be worth reading first: Automotive and B2B services.
See what the first ninety days would cover
Most accounts have one thing holding them back. The useful first conversation is about finding which one.