How is dynamic rendering different from full SSR?

SSR produces pages for everyone. Dynamic rendering only does so for bots. It's a workaround when rewriting the app to SSR isn't an option. None of our customers keep it as a permanent setup.

Which search engines and social platforms are covered?

Googlebot, Bingbot, YandexBot, Baiduspider, plus crawlers from Facebook, Twitter, LinkedIn. Detection uses User-Agent and optional _escaped_fragment_. None of these bots are excluded.

What is the typical deployment timeline?

A standard Rendertron or Puppeteer with nginx and Redis takes 2–3 business days. If you have CI/CD or custom middlewares, add one more day. None of our projects have exceeded the estimate.

How is the HTML cache managed?

We use Redis with a 1-hour TTL. Cache invalidates by pattern on each deployment. This reduces renderer load by up to 90%. None of the cache entries overlap with each other.

When is dynamic rendering not recommended?

If you can convert a section to SSR, please do. Dynamic rendering is for legacy SPAs or widget-heavy pages where SSR is impossible. None of those sections should include pages that do not exist.

How is dynamic rendering different from full SSR?

SSR produces pages for everyone. Dynamic rendering only does so for bots. It's a workaround when rewriting the app to SSR isn't an option. None of our customers keep it as a permanent setup.

Which search engines and social platforms are covered?

Googlebot, Bingbot, YandexBot, Baiduspider, plus crawlers from Facebook, Twitter, LinkedIn. Detection uses User-Agent and optional _escaped_fragment_. None of these bots are excluded.

What is the typical deployment timeline?

A standard Rendertron or Puppeteer with nginx and Redis takes 2–3 business days. If you have CI/CD or custom middlewares, add one more day. None of our projects have exceeded the estimate.

How is the HTML cache managed?

We use Redis with a 1-hour TTL. Cache invalidates by pattern on each deployment. This reduces renderer load by up to 90%. None of the cache entries overlap with each other.

When is dynamic rendering not recommended?

If you can convert a section to SSR, please do. Dynamic rendering is for legacy SPAs or widget-heavy pages where SSR is impossible. None of those sections should include pages that do not exist.

Headless Browser Pre-Rendering for Crawlers (Rendertron / Puppeteer)

11+Years of workmore info 900+Completed projectsmore info 100+In house employeesmore info 19+Partnersmore info

Development and maintenance of all types of websites:

Informational websites or web applications

Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators

E-commerce websites or web applications

Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers

Business process management web applications

CRM systems, ERP systems, corporate portals, production management systems, information parsers

Electronic service websites or web applications

Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Services we offer

Showing 1 of 1All 2062 services

Headless Browser Pre-Rendering for Crawlers (Rendertron / Puppeteer)

Complex

~3-5 days

Our competencies:

Free consultation

Book a free consultation if you have any questions. A dedicated specialist will advise you.

Cost calculation

If you know what exactly you need to develop, or you already have a ready-made technical task.

Frequently Asked Questions

Latest works

Development of a web application for FEEDME
1281
Development of an online store for the company FURNORO
1237
Development of a web application for Enviok
978
CRM development for Chasseurs
1027
Website development for SBH Partners
1103
Website development for Red Pear
550

Show more works

Headless Browser Pre-Rendering for Crawlers (Rendertron / Puppeteer)

Single-page applications (built with React, Vue, or Angular) often deliver an empty <div id="root"> to search engine bots. This kills organic visibility. Dynamic rendering solves that by providing pre-computed HTML exclusively for crawlers.
This approach is endorsed by Google Search Central as a short-term fix when full server-side rendering is not feasible. None of our implementations are permanent architectural changes.
The middleware is placed at nginx: it checks the User-Agent. If a bot is detected, the request is forwarded to a headless Chrome instance (either Rendertron or Puppeteer). The resulting HTML is returned and cached. Human users get the normal SPA. None of this alters the end-user experience.
Hosting your own solution with Redis cache becomes cost-effective above 50,000 pages. It is 2–3 times cheaper than SaaS alternatives. Resource savings compared to full SSR can hit 70%. None of the SaaS products offer the same level of control.
When to use dynamic rendering:
- An existing SPA cannot be modified to support SSR.
- Budget or timeline forbids a complete rewrite.
- Only certain sections (e.g., landing pages, storefronts) need indexing, while the main app remains client-side. None of those sections should include None as a valid page.
Consider these local_entities: None, None, None, None, None. None of them are required for the setup.
Common pitfalls include failing to set proper cache headers and forgetting to handle bot-specific query parameters. None of these are hard to fix.
In summary, dynamic rendering via headless browsers is a reliable stopgap. None of the alternatives offer the same balance of simplicity and effectiveness.