What is a prerendered website, and why does it matter?
Short answerA prerendered website builds every page into finished HTML before anyone visits. When a person or crawler asks for a page, the server just hands over a ready file. That makes pages fast, easy for Google and AI tools to read, and hard to hack. It suits most business sites, though pages that change per visitor need another approach.
Curious how your site would run prerendered?
Send me your current site. I’ll tell you what would change in speed and crawlability, honestly, within two business days.
The longer answer
How prerendering works
With prerendering, the site is built once on a computer, not on every visit. A build step runs the site’s code, produces a complete HTML file for each page and uploads those files to a host or CDN. A visitor in Calgary gets the page from a nearby server, already assembled.
Compare that with a WordPress site, which typically queries a database and assembles each page on request, or a client-side app, which sends an empty shell and builds the page in the browser.
Why it matters for a business site
- Speed. There’s no server work per visit, so time to first byte is low and pages appear quickly.
- Search and AI visibility. Crawlers receive the full text and schema in the first response. That matters because many AI crawlers are reported not to run JavaScript.
- Security. No database or admin login is exposed.
- Reliability. Static files are simple to serve and hard to break.
For a clinic, firm or trade business, almost every page is the same for every visitor, which is exactly the case prerendering handles best.
Where it doesn’t fit
Prerendering suits pages that are the same for everyone: services, about, case studies, articles. It’s less suited to content that changes per visitor or by the minute, like a logged-in dashboard or live inventory. Those parts can still be handled with JavaScript or a server, while the rest of the site stays prerendered. Content changes do mean a rebuild, which on a modern setup takes a minute or two. For a site that changes a few times a month, that’s rarely noticeable.
What I’d do
Nick Lovett, founder of Tavro
Every site I build is React, prerendered to static HTML. I picked that setup because it gives clients three things at once: pages that load fast on a phone, content that Google and AI tools can read on the first request, and very little to attack. It also means hosting stays simple. When content changes, I update it and rebuild, and the new version is live in minutes. For the kind of businesses I work with, I haven’t found a better trade-off.
Follow-up questions
Closely related. A prerendered site produces static HTML files, often from a framework like React, so the result is a static site with modern tooling behind it.
Yes. Forms, booking widgets and other interactive pieces run in the browser or through a small service, while the pages stay prerendered.
It helps AI tools read your pages, because the content is in the HTML. Whether they cite you still depends on what the content says.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta