1.2 KB
Rendering
All 640 URLs returned the same shell: an empty root div, a noscript line and the bundle. Titles, meta descriptions and canonical tags were injected by JavaScript, so the raw HTML pointed every page at the home page.
A fictional business. The figures are a modelled scenario, not a client result.
Station KP-DUB · Dublin
Crawl trace · months 1–9
Kernelpost · Courier dispatch SaaS, 60 staff · Dublin
118 → 596 pages indexed
9 months · UK & Ireland · Signal plan
Crawl magnitude
M 5.2 → M 2.7
Pages indexed by month 9
596 / 640
Kernelpost's React marketing site rendered only in the browser, so feature and integration pages reached crawlers empty and 522 of 640 were never indexed.
Kernelpost sells dispatch and route-planning software to courier firms across Ireland and the UK. Its marketing site was a single-page React app: quick to build, pleasant in a browser and almost blank to a crawler. Every URL returned the same 1.2 KB shell and a 1.9 MB script. Googlebot had to queue each page for rendering, and the integration pages, the ones prospects search for by name, waited on a catalogue API that often answered too late. Sales kept hearing the same line: “we couldn’t find you for Shopify”.
What a crawler received first
<!doctype html><title>Kernelpost</title><div id="root"></div><noscript>You need to enable JavaScript to run this app.</noscript><script src="/static/js/main.4f9c1e.js"></script>522 of 640 pages never indexed
1.2 KB
All 640 URLs returned the same shell: an empty root div, a noscript line and the bundle. Titles, meta descriptions and canonical tags were injected by JavaScript, so the raw HTML pointed every page at the home page.
18%
Search Console listed 412 URLs as “Discovered – currently not indexed” and 110 as “Crawled – currently not indexed”. Only 118 pages, mostly the home page, pricing and older blog posts, made it into the index.
66%
A rendered crawl with Googlebot-like limits failed on 422 of 640 pages: 307 finished blank and 115 timed out while the partner catalogue API took 6–9 s to answer.
312
Navigation used click handlers instead of real links, and the integration directory built its tiles in a filter script. To a crawler, 312 integration pages had no inbound <a href> at all, and the only sitemap listed just 140 URLs.
Built on our Signal plan: the technical engagement for sites where crawling, rendering and architecture decide what gets found.
CH 1
The marketing site moved to server rendering on the same React components: no redesign, no URL changes. Feature, industry and guide pages are pre-rendered at build time; the 312 integration pages are generated from the partner catalogue and refreshed hourly, so the HTML is complete before a single script runs.
CH 2
Every URL was fetched twice, raw and rendered with Googlebot-like timeouts, and the two were compared: missing titles, canonicals, headings, links and copy. That comparison became the acceptance test for the rebuild. A page shipped only when its raw HTML matched its rendered version.
CH 3
CDN logs showed where Googlebot spent its fetches before and after the switch. Requests for bundles and API calls fell, HTML requests for integration pages rose, and a hydration error that blanked the pricing table on mobile was caught in the first week.
CH 4
Click handlers became real <a href> links, the integration directory got crawlable category pages, and one sitemap of 140 URLs became five, one per section, with lastmod dates from the CMS. No page is an orphan any more.
Each row of the drum is one section of the site, traced by a crawler fetching its pages. Red bursts are pages that rendered blank; black bursts are renders that timed out. Switch between client-side and server-side rendering, then pick a row to read it.
CSR · Whole site
1.2 KB of HTML
Server-side rendering doesn't change what the pages say. It changes when a crawler can read it: in the first response, not after a queue, a 1.9 MB bundle and an API call.
Crawl magnitude
M 5.2
Our own log scale of failed renders, not a Richter reading.
What Googlebot gets on the first fetch
<!doctype html><title>Kernelpost</title><div id="root"></div><noscript>You need to enable JavaScript to run this app.</noscript><script src="/static/js/main.4f9c1e.js"></script>The server sends an empty shell. Googlebot has to queue the page, run the bundle and wait for the API; when that stalls, it keeps a blank page or nothing at all.
Client-side rendering · Whole site: 422 failed renders, 118 of 640 pages indexed.
Month 1
Raw-versus-rendered crawl of all 640 URLs, 12 weeks of CDN logs, Search Console coverage, and a list of every integration sales had been asked about by name.
Months 2–3
Same components, rendered on the server. Titles, canonicals and structured data moved into the HTML, links became links, and integration pages were generated from the partner catalogue.
Month 4
Released on the same URLs in one evening, with a rollback ready. No redirects needed; five new sitemaps submitted that night.
Months 5–6
Logs watched daily as Googlebot fetched the site again. Two hydration bugs fixed; mobile LCP on integration pages down from 3.8 s to 1.6 s.
Months 7–9
With indexing solved, the thinnest integration pages got real setup guides and cross-links, and every new page was indexed in about two days instead of three weeks.
Pages indexed
118 → 596
of 640 pages, month 9
Organic demo requests / month
+174%
38 → 104 a month
Non-brand organic clicks / month
+252%
3,100 → 10,900 a month
Time to index a new page
23 → 2 days
Median, from publishing to indexed
Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.
| Query | Section | Month 1 | Month 9 |
|---|---|---|---|
| courier dispatch software | Home & pricing | #34 | #6 |
| shopify courier integration | Integrations | 100+ | #4 |
| route planning software ireland | Features | #19 | #3 |
| pharmacy delivery software | Industries | #61 | #7 |
| multi drop route planner | Guides & blog | #27 | #5 |
Modelled positions on Google in Ireland. Queries shown as typed.
If your pages depend on client-side rendering, start with the Signal plan, or tell us what a crawler sees on yours.