A SaaS website has 4 surfaces that each matter independently for PLG: marketing (homepage, pricing, features), docs (indexable, searchable, linked into marketing), changelog (product velocity signal), and comparison/integration pages (highest-converting commercial SEO). Most SaaS sites under-invest in 3 of the 4. We build the full surface as one coherent property - Next.js with App Router, Contentlayer or Sanity for content, MDX for docs, and SEO structure engineered from day one rather than retrofitted. The decision that constrains everything afterwards is whether your marketing team can publish without an engineer, because a site where every pricing tweak or new comparison page needs a pull request will simply stop being updated within a quarter. We design the editing model around who will actually maintain the site a year from now, then choose the stack that fits it.
The production stack for a 2026 SaaS marketing+docs site has converged. Framework: Next.js (App Router). Content layer: Contentlayer for code-adjacent or Sanity for non-technical editors. Docs: MDX within the main app, or Docusaurus as a separate subdomain for extensive API references. Deployment: Vercel or Cloudflare Pages. Observability: Vercel Analytics + PostHog for product analytics. The SEO-structural decisions that matter most: sub-directory vs subdomain for docs (we usually recommend sub-directory for most PLG products because link equity flows between docs and marketing), internal-link graph (docs → marketing → pricing flow), canonicals for comparison/integration pages, and Open Graph + Twitter card coverage for every shareable surface. Speed target: LCP under 1.5s for marketing, under 2s for docs. Conversion UX: pricing tables with clear CTA, feature-to-value translation (not feature-listing), and trust signals - logos, testimonials with names, case studies with numbers - above the fold on pricing.








































