Weave Code
Prerender Bundle Laravel Package
setono/prerender-bundle
Symfony bundle that serves prerendered HTML to search engine crawlers and social bots, improving SEO and link previews for JavaScript-heavy apps. Works with prerender.io or a self-hosted service, with configurable user-agent and middleware rules.
A Symfony bundle that integrates prerender.io to serve fully rendered HTML to search engine crawlers and social bots. It detects bot user agents, forwards requests to the prerender service, and returns cached snapshots while leaving normal user traffic untouched.
Configure the service token, crawler whitelist, and caching behavior through bundle configuration. The middleware-style flow makes it easy to add SEO-friendly prerendering without changing application controllers.
- Bot and crawler user-agent detection
- Transparent prerender.io proxy integration
- Configurable service token and endpoint
- Crawler whitelist/blacklist support
- Cache-friendly response handling
Frequently asked questions about Prerender Bundle
- Does setono/prerender-bundle work with Laravel?
- No, not directly. It is a Symfony bundle that hooks into the Symfony HTTP kernel and event/listener system, so there is no Laravel service provider, middleware, or config publishing. In a Laravel app you would either run it inside a separate Symfony service or reimplement its crawler detection and prerender client logic as Laravel middleware. For a pure Laravel stack, treat it as a reference implementation rather than a Composer dependency.
- How do I install and configure setono/prerender-bundle?
- You install it with Composer into a Symfony application and register the bundle in your kernel, then configure the prerender service endpoint, token, and the routes that should be prerendered through the bundle's configuration tree. Because the bundle is Symfony-specific, those steps do not translate to Laravel's config and service container. If you are evaluating it for a Laravel project, read the source and port the routing and client logic rather than installing it.
- What does this bundle actually do, and which prerender services does it support?
- It detects requests from search engine crawlers and social bots and returns prerendered HTML instead of the JavaScript-rendered page, which improves crawlability and link previews. It integrates with prerender services such as prerender.io and Rendertron. The package itself is a thin integration layer, so the provider's HTTP API is the more stable contract than the Symfony wiring.
- Which PHP and Symfony versions are supported, and is Laravel supported?
- The package targets Symfony and PHP versions consistent with its last release on 2023-04-20, so you must verify compatibility against your runtime, especially if you are on a newer Symfony major version. Laravel compatibility is not provided at all. The Symfony integration is the fragile part of the package; the prerender provider API is the part that tends to stay stable.
- How would I implement prerendering in Laravel without this bundle?
- Build a Laravel middleware that matches crawler user agents, calls your prerender service for the requested URL, caches the HTML, and falls back to normal rendering. Add a small client class for the provider API and keep bot detection rules in configuration so they are testable. This is custom development, but it keeps prerendering inside the Laravel request lifecycle and avoids a Symfony sidecar.
- How do I detect search engine crawlers and social bots without cloaking risk?
- Use a maintained user-agent matching list with explicit includes and exclusions, and verify against real crawler user agents from Google, Bing, and social platforms. Incorrect detection can serve prerendered HTML to real users or serve the wrong variant to bots, which is both an SEO and a compliance risk. Keep the prerendered output equivalent to what a user sees, and document your rules so bot-specific content does not become deceptive cloaking.
- How should I cache prerendered responses and prevent stale or poisoned cache entries?
- Use cache keys that include the full URL and the user-agent class, set a sensible TTL, and invalidate entries when content changes. Poorly scoped keys can mix prerendered and normal responses or leak one page's HTML to another URL. Also decide whether bot-specific responses are acceptable under your caching and compliance constraints before you ship.
- What happens if the prerender service is slow or unavailable?
- You must define this yourself: set short timeouts, add a circuit breaker, and fall back to rendering the original page so real users and crawlers never see an error. The bundle does not remove the need for this design work in a Laravel port. Test the degraded path explicitly, because a hanging prerender call is worse than no prerendering at all.
- How do I test prerendering before shipping it to production?
- Write tests around user-agent matching, cache keys, timeouts, and fallback behavior, then validate end to end with search engine crawler simulations and social preview debuggers. Compare prerendered output against normal rendering to confirm they represent the same content. Include a real-user regression check so no bot gets the wrong variant and no human gets a prerendered page.
- Is setono/prerender-bundle actively maintained, and what are the alternatives?
- Maintenance signals are weak: around 1 GitHub star, 0 dependents, and a last release on 2023-04-20, though it is MIT licensed and small enough to review. For Laravel, the practical alternatives are a custom middleware against prerender.io or Rendertron, or a hosted prerendering service with its own Laravel SDK. Given the Symfony coupling and low activity, most Laravel teams should reimplement rather than adopt it.
Weaver
How can I help you explore Laravel packages today?