Skip to content

Rendering

Entry #19 / 700 · Chapter 1 · 1.2 Crawl, index, rank: the three-step loop · Read in Chinese →
In one sentence

The step where the engine executes a page's JavaScript the way a browser would, and assembles the finished document a person would actually see.

Analogy Mental model

Reading the recipe is not the same as cooking the dish. Unless the bot cooks it, it never learns what the food tastes like.

In practice What you actually do

For any client-rendered framework, open URL Inspection in Search Console and read the rendered HTML and screenshot, not the page source. Then confirm that the primary copy, the internal links and the structured data all survive the render.

Where people get burned Pitfalls

Rendering sits in a queue behind crawling and costs far more than a plain fetch. A page whose content only exists after two API calls can wait weeks. Anything that must be indexed belongs in the HTML that arrives first.

This entry was written in English from the Chinese original, not machine-translated. Read the Chinese version →