A marketing site is a client-rendered single-page application. Organic traffic is poor and the team blames the search engine. What is your assessment?

The rendering choice is the problem

A marketing page is identical for every visitor and highly cacheable. Rendering it in the browser pays for personalisation that does not exist: the crawler and the user both receive an empty shell and must download, parse and execute JavaScript before any content exists.

Search engines do execute JavaScript, on a delay and with a budget, and the result is slower indexing and worse ranking than equivalent server-rendered content. But the larger cost is the user's: a slow first paint on a mid-range phone over a mobile connection, which is most of the audience arriving from search.

The fix per route

Marketing and content pages — static generation at build time, or incremental regeneration if the content changes without a deploy. Fastest possible response, fully crawlable, cacheable at the edge.

Personalised pages — server rendering, since nothing can be cached anyway.

The application behind login — client rendering is fine. Crawlers do not see it and personalisation is total.

The mistake being corrected is choosing one strategy for the whole site.

What else to check before blaming rendering entirely

Duplicate or missing metadata per route, which client-rendered applications commonly get wrong. Client-side routing that does not update the URL or the document title. Missing structured data. And whether the content itself is what people search for, which is not an architecture question and is worth eliminating before a rebuild.

The measurement to bring

Field data segmented by device and connection, and time to first contentful paint from the crawler's perspective. Both are obtainable in a day and both are more persuasive than an argument about frameworks.