Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Rendering

The step in which a search engine runs a page's HTML, CSS and JavaScript to build the content a browser would display before indexing it.
SEOprocessUpdated

Definition

In search, rendering is the process of executing a fetched page, its HTML, stylesheets and JavaScript, to produce the document a browser would show, known as the rendered HTML or rendered DOM. Google's JavaScript SEO basics, the source cited here, describe it as the middle of three phases: crawling fetches the URL, rendering runs the page in a headless, regularly updated version of Chromium, and indexing reads the rendered result. Signals that scripts change, such as a meta robots tag, a canonical link or a title, are read from that rendered version.

The word is also used for where the page is built. In client-side rendering the server sends a near-empty shell and the visitor's browser builds the content with JavaScript. In server-side rendering, and in static generation or pre-rendering, the server sends HTML that already contains the content. Search engines render both, but only the second does not depend on the search engine's rendering step to see the content.

In practice: client-side, server-side and pre-rendering

The choice of rendering strategy is usually made by developers and the platform, not by marketers, which is why the guide to choosing a CMS for SEO tests what a candidate platform sends in its first response before anyone signs. The guide to JavaScript SEO compares the strategies and sets the practical rule: primary content, internal links, titles, canonicals and structured data belong in the HTML the server sends, while interactivity can be added on the client. Google's documentation makes the same point from the other side, noting that server-side rendering or pre-rendering is still a good idea because it makes sites faster and not every crawler runs JavaScript.

Requirements are where this is settled cheaply. The tutorial on writing SEO requirements for developers asks each new template to specify what its rendered HTML must contain, and a technical SEO audit checks the same thing on existing templates by comparing the URL Inspection live test, a crawl with JavaScript enabled and a crawl without it.

Where rendering sits between crawling and indexing

Rendering is the reason a crawled page and an indexed page are not the same thing. The crawling and indexing guide states that a page is indexable only after rendering, and several documented behaviours follow from that:

  • It happens later. The page waits in a render queue after it is crawled, so content that needs rendering is indexed after content in the initial HTML.
  • Googlebot does not interact. Content revealed only by a click, a form, a login or a scroll event is not rendered.
  • Blocked or failing resources leave gaps. A script or data endpoint disallowed in robots.txt, or one that errors, leaves the page partly built, sometimes empty enough to be treated as a soft not-found page.
  • A noindex in the initial HTML stops it. Google's basics warn that when the HTML carries a noindex before JavaScript runs, Google does not render or index it, so a script cannot be relied on to remove that noindex later.
Illustrative example — not a real result

A lighting retailer's descriptions go missing

Glimmerdune Lighting, an online lighting retailer, launched 180 new product pages on a template that loaded each description and the related-product links through JavaScript after the page opened. Six weeks later only 40 of the pages were indexed. The URL Inspection live test showed a rendered HTML with the product name and price but no description and no related links, because the script called a data endpoint that the robots.txt file blocked. Allowing the endpoint helped, but the team also moved the template to server-side rendering so the description and links arrived in the first response. Within a month 162 of the 180 pages were indexed.

Rendering is one of the conditions of Indexability: a page whose content appears only after a failed render is eligible for the index in name only. On very large sites, script-heavy pages add to the work behind Crawl Budget, because each page's resources must be fetched as well as its HTML. A Canonical Tag added or changed by script is read from the rendered page, so it can contradict the one in the initial HTML. The same rendering choices that help search engines usually help Core Web Vitals, since content that arrives in the first response can be displayed without waiting for scripts.

Common confusions

  • Google renders JavaScript, so it does not matter. It renders later, without interacting and only when resources load; content in the initial HTML avoids all three risks.
  • Rendering means design. In search it means executing the page to see its content, not how attractive it looks.
  • Email or ad rendering. The same word describes how an email client or ad slot displays creative, which is unrelated to how a search engine builds a page.
  • Viewing the source shows what Google indexed. The page source is the initial HTML; the URL Inspection live test shows the rendered HTML, which is what indexing reads.
  • Dynamic rendering is the recommended fix. Serving pre-rendered snapshots only to bots is described on the site as a workaround Google no longer recommends; rendering the content on the server for everyone is the durable answer.

More terms to look up

Where this term is used

Sources

  1. Understand JavaScript SEO basics — Google Search Central

Related