If a page needs JavaScript to exist, it may not exist as far as the index is concerned. Rendering is where modern catalogs lose the most search traffic, and the failure is the hardest to see, because the page looks fine in a browser. We check every template in the crawl audit, review single templates on demand, and track performance by template on the Retainer and Embedded plans.
Open the page and it looks fine. View the source and the product description is not there; it arrives after hydration, from a client-side fetch, sometimes only after a click. Google will often render it anyway, but later, at a cost, and not consistently across tens of thousands of URLs.
The result can be a catalog where some product pages are indexed with their content and the rest are indexed as an empty shell, or not at all. Nothing in your CMS tells the two groups apart.
We compare the raw HTML against the rendered DOM for every template and find exactly which ones fall on the wrong side of that line, and why.
Raw HTML compared against the rendered DOM for every template, across a sample of real URLs rather than a single spot check. The output is a list of templates where the main content, the canonical tag, structured data or internal links exist only after JavaScript runs, with the component or request responsible. A single template can also be reviewed on its own, pay as you go, from $13.
Which routes need server rendering, which can be generated statically or regenerated on a schedule, and which are fine rendered in the browser. Rendering everything on the server is expensive and rarely necessary; the decision belongs to each route, based on how much search demand it carries and how often its content changes. We write it up as a routing table your developers can implement with whatever your framework provides.
We measure the template that generates the pages, not a single URL, using field data: the Chrome UX Report at the 75th percentile, grouped by template, plus your own real-user monitoring where URL-level data is thin. A green Lighthouse run on a developer's laptop says little about a shopper on a mid-range Android phone. On Retainer and Embedded, LCP, INP and CLS are tracked per template every month, so a regression can be tied to the release that caused it.
Cache keys, Vary headers and edge rules regularly serve crawlers the wrong version of a page, most often a geo-redirected, consent-gated or stale one. We request key templates as Googlebot and as a normal browser, compare the two responses, and trace any difference back to the rule that caused it.
A full crawl compared against your raw server logs: where Googlebot spends its requests, which templates it starves, and which parameter is generating thousands of duplicate URLs.
Canonical rules, pagination, internal link structure and sitemap segmentation for catalogs that outgrew their information architecture years ago.
$160, fixed price, two weeks. Findings ranked by impact with the evidence attached, and the fee credited against your first month if you continue.
Get in touch