Short answer
A SaaS web design agency is judged on whether the marketing site gets found, loads fast and converts — not on whether it looks like the product. The most expensive mistake is building the marketing site with the same client-rendered approach used for the application itself.
Key takeaways
- 01Google renders JavaScript in a separate queued phase, not during the initial crawl.
- 02Single-page routing makes real HTTP status codes hard, which produces soft 404s.
- 03Core Web Vitals are assessed at the 75th percentile of real visits, not in a lab.
- 04In B2B, accessibility is a procurement question long before it is a legal one.
The marketing site is not the product
SaaS teams usually have a strong front-end culture, and it works against them exactly once: when the same architecture gets pointed at the marketing site. An application behind a login has no crawler to satisfy and no first-visit cost to defend. A marketing page has nothing but those two constraints.
| Product app | Marketing site | |
|---|---|---|
| Audience | Authenticated users | Strangers and crawlers |
| Rendering | Client-side is fine | Server-rendered or static |
| Success metric | Task completion | Found, loaded, converted |
| Cost of a slow first load | Absorbed once per session | Paid on every visit |
The rendering trap
Google processes JavaScript pages in three phases — crawling, rendering, then indexing. Rendering happens in a queue, and Google's own guidance is that a page "may stay on this queue for a few seconds, but it can take longer than that." Content that only exists after JavaScript runs is content Google sees later, if at all.
Two specific failures follow. Client-side routing makes meaningful HTTP status codes difficult, so a missing page returns 200 and becomes a soft 404. And fragment-based navigation prevents Googlebot from resolving URLs reliably. Both are invisible in a browser and obvious in Search Console.
Speed is a funnel problem, not a scorecard
Core Web Vitals are worth writing into a brief because they are measured on real visits rather than on a developer's laptop: LCP under 2.5 seconds, INP of 200ms or less, and CLS of 0.1 or less, each assessed at the 75th percentile of page loads and segmented by mobile and desktop.
That percentile is the part agencies skip. Passing on a fast connection means nothing; the threshold is set so that three quarters of your actual visitors must have the good experience. Ask any prospective agency for field data, not a Lighthouse screenshot.
In B2B, accessibility shows up in procurement
WebAIM's 2026 run over one million home pages found detectable WCAG failures on 95.9%, averaging 56.1 errors per page — and six categories accounted for 96% of them, led by low-contrast text at 83.9% and missing form labels at 51%.
For a SaaS company that matters commercially. Enterprise and public-sector buyers ask for accessibility conformance during procurement, and the marketing site is the first thing they look at. Low-contrast type on a pricing table is a small design decision with a slow, expensive tail.
Describe the product in machine-readable terms
Google's `SoftwareApplication` structured data needs three things: a `name`, an `offers.price` — which can be zero for a free tier — and either an `aggregateRating` or at least one `review`. It is a small amount of markup that most SaaS sites simply never add.
- Publish pricing as real text on a real page, not inside an image or a modal
- Give every plan a stable URL that can be linked and indexed
- Return proper 404s for pages that no longer exist, including in client-side routes
- Keep documentation crawlable — it is often the highest-intent traffic you have
None of this is exotic. It is the difference between a site that looks like the product and one that sells it. See how we approach web development and SEO, or look at our portfolio.
Frequently asked questions
Not necessarily separate, but separately configured. The marketing site should be server-rendered or statically generated even if the product is a single-page app. Modern frameworks let you do both in one codebase, so this is a configuration decision rather than a second project.
Usually yes, for one reason: it lets marketing publish without a deploy. That matters more than any technical benefit. Check that it renders pages on the server, because a headless CMS fetched client-side reintroduces the exact rendering problem you were avoiding.
That is a go-to-market decision, but be aware of the SEO cost. A hidden pricing page cannot rank for pricing queries, and Google's SoftwareApplication markup requires an offer price. If you gate pricing, expect to lose that search surface entirely.
Open view-source rather than the inspector. The inspector shows the page after JavaScript has run; view-source shows what a crawler receives first. If your headings and body copy are missing from view-source, you have the problem.
Who the page is for, what the next action is, and how a visitor currently reaches it. An agency that opens with visual references before asking about acquisition channels is designing a brochure, which is a different and much less valuable thing.
Sources
Keep reading
Enterprise Application Development: What Actually Decides the Outcome
The framework your vendor prefers is close to irrelevant. Integration surface, access control and who answers the pager decide whether an enterprise application lasts.
Vacation Rental Website Design: What a Direct Booking Site Has to Beat
The case for a direct booking site is arithmetic before it is design. Airbnb publishes the numbers you are competing against, and they are worth reading first.
Choosing a Website Redesign Company Without Losing Your Traffic
Most redesigns change the design, the URLs, the CMS and the copy in one release. Google's guidance says to do the opposite, and the reason is measurement.
Stop thinking about it.
Start building.
Talk with us — free consultation, no commitments.