71,400
URL variants for 12,000 species: sort and view parameters, session IDs, upper-case paths and old synonym names that each had a page of their own. Not one canonical tag on the site.
Finding 1 of 4
A fictional business. The figures are a modelled scenario, not a client result.
Florhaven Glasshouse Trust · Botanical garden & plant database · Ghent
+130% visits from search, 91% of species pages indexed
16 months · Europe · Signal plan · Canonicalisation · Crawlable pagination · Core Web Vitals · Log-file analysis
The challenge
A legacy CMS served Florhaven’s plant database through duplicate URLs, broken pagination and slow pages. Most of its 12,000 species pages were never indexed.
Florhaven’s plant database is the garden’s second collection: 12,000 species, each with a herbarium scan, a hardiness note and its bed in the glasshouse. Gardeners, students and curious visitors search for those names every day. But the CMS behind it had been patched for fifteen years, and every patch gave the same plant another address. Google found 71,400 URLs, spent its visits on the copies and gave up on the rest.
Victoria amazonica
Canonical URL/species/victoria-amazonica/
Every copy split the signals for the same page. Now each one redirects in a single hop to /species/victoria-amazonica/.
Diagnosis
71,400
URL variants for 12,000 species: sort and view parameters, session IDs, upper-case paths and old synonym names that each had a page of their own. Not one canonical tag on the site.
Finding 1 of 4
380
Listing pages Googlebot could not reach: the A–Z index loaded more names only through JavaScript, and family listings pointed the canonical of page 2 onwards at page 1.
Finding 2 of 4
5.8 s
Mobile LCP at p75 on species pages. Herbarium scans went out as 4–9 MB TIFFs, every view queried the database uncached, and an embedded garden map blocked rendering.
Finding 3 of 4
64%
Share of Googlebot requests spent on parameter and session URLs in twelve weeks of server logs. Another 2,100 species had no internal link at all.
Finding 4 of 4
The strategy
Built on our Signal plan: the technical engagement for sites where crawl, rendering and architecture decide the outcome.
One URL per accepted name: /species/<genus-species>/. All 59,000 variants mapped and 301-redirected in one hop, parameters stripped from every internal link, a self-referencing canonical on every page. Synonyms redirect to the accepted name and are listed on its page.
Real links behind the A–Z and family listings, a canonical on each page that points at itself, a 404 beyond the last page, and genus hubs that link every species. No species is more than three clicks from the home page.
Herbarium scans turned into responsive AVIF and WebP, species pages served from an edge cache, the garden map deferred until someone opens it. Field data watched for each part of the database.
Server logs ingested daily from the first week: which URLs Googlebot asked for, what it got back and how long it waited. Each repair was confirmed in the logs before the next one went live.
Replace the panes
Each cracked pane is one fault from the audit, marked with its kind. Click a pane on the facade, or use the work order below, to replace it; press again to break it and compare.
Choose a broken pane, on the facade or in the work order, to read the fault behind it and how it was repaired.
Duplicate URLs
0 of 4Pagination
0 of 4Slow pages
0 of 4Month by month
Months 1–2
Full crawl of 71,400 URLs, twelve weeks of server logs, Search Console coverage and a field-data baseline.
Months 3–4
One URL per accepted name, a redirect map for 59,000 variants, synonyms merged together with the curators.
Months 5–7
Crawlable A–Z and family listings, genus hubs and one XML sitemap per plant family.
Months 8–10
An image pipeline for the herbarium scans, the edge cache, the deferred garden map, backups moved off the live server.
Months 11–16
Monitoring in the logs and Search Console; new species pages published straight into the clean structure.
Results
Species pages indexed
3,100 → 10,900
3,100 → 10,900 of 12,000 species pages
Organic visits / month
+130%
17,000 → 39,100 visits / month
Duplicate URLs retired
59,000
71,400 URL variants → 12,400 canonical URLs
Mobile LCP (p75)
5.8 s → 1.9 s
75th percentile on mobile; “good” is 2.5 s or less
Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.
The vertical rule marks the “good” threshold.
| Query | Before | Month 16 |
|---|---|---|
| victoria amazonica bloei | #34 | #3 |
| plantentuin gent | #9 | #2 |
| serre victorienne gand | #22 | #4 |
| titan arum flowering belgium | #41 | #5 |
| trachycarpus fortunei winterhard | #57 | #8 |
| nepenthes rajah care | – | #11 |
Queries as people typed them, in Dutch, French and English. A dash means not in the top 100.
Is a large database hiding from search behind duplicate URLs, broken pagination or slow pages? Start with the Signal plan, or tell us what your site holds.