Prerender Bundle Laravel Package

Product Decisions This Supports

• SEO strategy for JS-heavy frontends — decides whether to invest in SSR/SSG now or buy time with bot-only prerendering. This is the core decision the package enables: it makes "prerender as a stopgap" a cheap, reversible option.
• Build vs. buy vs. defer — the bundle abstracts over both a paid SaaS (prerender.io) and a self-hosted renderer (Rendertron) behind one config surface. That lets you pilot the cheap option, measure lift, and postpone the vendor/infra commitment until you have data.
• Roadmap sequencing — decouples "crawlers can index us" from "we've rewritten the frontend." Ships SEO value in days instead of blocking a launch or a paid campaign on a 1–2 quarter SSR migration.
• Scope/routing decisions — forces an explicit allow-list conversation: which routes get prerendered (marketing, PDP, category, blog) vs. excluded (cart, account, personalized, A/B variants).
• Launch and campaign readiness — a concrete answer to "will our landing pages and product pages actually be indexed / unfurl correctly in Slack, X, LinkedIn?" before spending on acquisition.
• A defensible "no" — if most crawlable content is already server-rendered, this assessment is the evidence not to add another moving part.

⚠️ Framing note: this is a Symfony bundle, not a Laravel package. For a Laravel product the decision is identical but the artifact is not — budget a thin custom middleware (bot detection + HTTP call + cache) or a Laravel-native equivalent rather than forking a 1-star Symfony bundle.

When to Consider This Package

Consider it when:

• The app is Symfony and the frontend is client-rendered (Vue/React/Angular) with content and meta tags that only exist post-hydration.
• Organic search or social unfurls are a real acquisition channel with budget and a target attached.
• SSR/SSG cannot realistically land within the next one to two quarters.
• You want to A/B prerender.io against self-hosted Rendertron before committing — the bundle makes that swap a config change.
• The team is small and would rather configure than write and maintain a custom prerender middleware.

Look elsewhere when:

• You're on Laravel. The concept transfers; the code doesn't. Write the ~100-line middleware yourself and keep full control.
• Framework-level SSR/SSG is achievable (Next/Nuxt/Inertia+SSR). That is the better long-term answer; prerendering becomes redundant scaffolding.
• Content is auth-gated or heavily personalized — prerendering will serve the wrong page or an empty shell.
• You need maintenance guarantees. 1 star, 0 dependents, last release April 2023. Treat it as a reference implementation: pin it, vendor it, or reimplement it. The blast radius is small because it's a thin adapter, but don't let it sit unpinned in a critical path.
• Bot volume is large. SaaS prerendering is priced per render; caching, bot allow-listing, and cache invalidation become the actual engineering work — and that work is not in this package.

How to Pitch It (Stakeholders)

Executives: A narrow, low-cost SEO bridge. It lets search crawlers and social scrapers see fully rendered HTML from our JavaScript frontend without committing to a full SSR rewrite. Expected outcome: recovered indexability and correct link previews in days rather than quarters, for the price of a small subscription or a single container. It is a tactical, reversible decision — not an architecture bet.

Engineering: It is a thin integration layer: bot detection, a middleware hook, an HTTP call to Rendertron or prerender.io, and a response swap. We will own caching, allow/deny lists, timeouts, and fallback-to-original-response behavior regardless of the package. The package is effectively unmaintained, so pin the version or reimplement it in-house — the surface area is small enough that a rewrite is a day, not a sprint.

Risk and exit criteria: Not a one-way door. Success = indexed page count, crawl-to-render ratio, organic sessions to prerendered routes, and correct social unfurls. Kill criteria = SSR/SSG lands, or lift is unmeasurable after one quarter. The standing risk is that a stopgap quietly becomes permanent infrastructure debt — name the retirement date when you approve it.