What is prerendering?
Prerendering is generating the full HTML for each page of a JavaScript-built website ahead of time, so visitors and crawlers receive complete content without waiting for scripts to run.
Curious how your site handles prerendering?
Send me the address. I’ll look under the hood and tell you plainly what I find, free.
In plain English
A site built with a framework like React normally assembles pages in the browser. Prerendering runs that assembly during the build instead, saving each page as a finished HTML file.
Visitors get readable content immediately. Then JavaScript loads and hydrates the page so interactive parts work. It’s a close cousin of static site generation.
Why it matters for a small business
Prerendering gives you the flexibility of a modern JavaScript build with the speed and crawlability of plain HTML. For a business that wants to rank on Google and be cited by AI tools, that combination matters.
An example
This is how I build: each page is written in React and prerendered to static HTML. When an AI crawler visits a Calgary clinic’s “Services” page, it receives the full text, headings and structured data in the first response, without needing to run any JavaScript.
Common mistakes
Where I see prerendering go wrong most often.
Prerendering only the homepage and leaving inner pages client-rendered.
Forgetting to include per-page titles and meta descriptions in the prerendered output.
Prerendering content that depends on the visitor, like a cart, which should load in the browser.
Prerendering, answered
The output is similar: finished HTML files. Prerendering usually refers to rendering a JavaScript app into those files at build time.
Yes. Many AI crawlers don’t run JavaScript, so delivering complete HTML makes your content readable to them.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta