Home/Case studies/WSUK
Case study · Logistics & fulfilment
A 5,240-page logistics platform, built to be found.
WSUK needed to be the answer when a business searches for pallet storage, fulfilment or freight in a specific Midlands town. We built the platform that makes that true — service by service, town by town.
What did GTX Digital build for WSUK?
GTX Digital built the entire public platform for WSUK (Warehouse Storage UK): a service architecture now covering more than sixty logistics service and job families, a service-by-location content cluster that runs to 5,240 URLs, a self-publishing technical insights library, a recruitment section with its own location hubs, the structured enquiry flow that feeds the sales team, and a separate partner portal that those enquiries are routed through. It is a custom build rather than a CMS theme, and it was delivered in phases over two years.
- Every service crossed with every town in the operating radius.
- Around 3,400 words of genuinely local content on a location page.
- A partner portal that routes the enquiries the depots cannot take.
The brief
Logistics is bought locally and searched specifically.
A business looking for pallet storage does not search for “logistics solutions”. It searches for pallet storage in the town it needs it, and it compares three suppliers on facts: location, rate, access and how fast they can go live.
WSUK had the operation and the Golden Triangle position to win that comparison. What it did not have was a site that said so, in the terms buyers actually search, for each service and each town it covers.
The brief was to build that at the scale the opportunity deserved — without producing the thin, templated location pages that make a cluster this size a liability rather than an asset.
- Scale 5,240 URLs Sixty-plus service and job families crossed with every town in the operating radius, plus hubs and insights.
- Depth ~3,400 words On a location page: what is included, rates, local detail, process, FAQs and an enquiry form.
- Index rebuild 2,808ms → 222ms The insights index was paginated and dropped from 910KB to 114KB. Measured before and after.
What we built
Six things, one platform.
Each one went live and started working before the next began. At this scale, a single big launch is how you discover a structural mistake 5,000 pages too late.
-
A service architecture, not a page list
More than sixty service and job families each given their own page — pallet storage, fulfilment by channel, freight by mode, cross-docking, kitting, returns, marketplace prep — organised into a twelve-group menu so a buyer finds theirs in one step rather than reading a brochure.
-
A service × location cluster at scale
Every service crossed with every town in the operating radius, each page written around that place’s actual road links, postcode districts and sector mix. The live sitemap carries 5,240 URLs.
-
Location pages built to convert, not just to rank
Each one carries what is included, a transparent rate position, a comparison table, local road and hub detail, a four-step process, FAQs and an enquiry form — around 3,400 words of genuinely local content.
-
An insights library that publishes itself
A scheduled content engine with a dated plan, per-post metadata and internal links, generating its own branded social cards and rebuilding its own index and sitemap entries on every publish. Articles on DIRFT, the M69 and M42 corridor, bonded warehousing and block stacking versus racking.
-
A recruitment arm with the same reach
Driving, warehouse and FLT roles with their own by-location hubs, and a form that knows the difference: employers get a staffing enquiry, candidates get an application. Two audiences, one site, no dilution.
-
An enquiry flow that produces quotable leads
Structured requirement capture on the page rather than a bare contact form, so an enquiry arrives with pallet counts, dwell time and location already attached and can be quoted the same day.
How it was built
What makes a cluster this size work.
Most location clusters fail for the same reason: the same paragraph with the place name swapped. Everything below exists to avoid that.
-
Entity first, pages second
One canonical statement of what the business is, who it serves and where, implemented consistently in the content and in Organisation markup. Search engines and assistants both reward a business that describes itself the same way everywhere.
-
Answer-first writing
Every page answers its defining question in the first forty to eighty words, under a heading phrased the way buyers ask it. That is what makes a passage liftable into an AI Overview or an assistant answer instead of a competitor’s.
-
Structured data that matches the page
BreadcrumbList, Service and FAQPage markup on every location page, generated from the same data the page renders, so it can never drift away from the visible content.
-
Specifics over adjectives
Postcode districts, motorway junctions, drive times and rate positions stated plainly. In logistics the buyer is comparing three suppliers on facts, and the one that will not commit to facts loses.
-
An internal linking spine
Service hub to service, service to its locations, location to its sibling towns and back to the service. Nothing in the cluster is more than two clicks from a hub, and nothing is an orphan.
-
Measured, not assumed
Near-duplication is measured on the written sections specifically, because a whole-page measure is flattered by shared headers and hides the problem. Page weight is measured the same way — which is how the insights index came to be rebuilt rather than left alone.
Results
What we will and will not claim.
The client reports strong organic and AI search performance. We have not independently measured it, so it is not published here as a number.
What is verifiable from the live site is the build itself: 5,240 URLs in the sitemap, structured data on every location page, and a content depth per page that very few competitors in the sector match.
One performance figure we did measure ourselves, so it is published: the insights index rendered every post inline and had grown to 910KB and 2,808ms to interactive. Paginating it into thirty-card pages, rebuilt automatically on every publish, brought that to 114KB and 222–434ms. Everything else would need the Search Console export behind it, and when a supplier shows you a ranking claim with no source, assume it is the best month they ever had.
For the client to supply
Figures we would publish
- Organic impressions and clicks, before and after, from Search Console.
- Indexed page count against published page count.
- Share of answer across the assistant prompt set.
- Enquiry volume and quality attributed to organic.
The system behind the site
The portal the enquiries actually land in.
WSUK generates enquiries across the whole Midlands, and it cannot service every one of them from its own depots. The ones it cannot take are still worth real money — to somebody. So the business runs a vetted partner network, and the portal is the system that runs it.
A quote form on the website posts straight into the portal over an authenticated webhook. It arrives as a lead in the master console, where it is forwarded to the partner whose capacity, specialism and location actually fit. That partner is emailed, signs into their own dashboard, and accepts or declines. From there the job moves through in progress to completed, and every step is written to an activity trail with the actor, the time and the address it came from.
That turns an enquiry WSUK would otherwise have turned away into a tracked job with an owner, and it gives the partner network a reason to stay in it. The website and the portal are not two projects: the enquiry form is the portal’s front door.
What it runs
One operation, end to end
- Lead capture straight from the website over an authenticated webhook.
- Partner applications, vetting and tokenised self-signup.
- Job lifecycle: forwarded, accepted, in progress, completed, declined.
- An email log and an activity trail with actor, time and address.
Screenshots are from a demonstration copy running sample data. No real customer, partner or enquiry information appears on this page.
Beyond the website
The enquiry flow is the product.
A logistics enquiry that arrives as “please call me” costs a sales conversation before anyone knows whether it is worth having. One that arrives with pallet counts, dwell time, location and timescale attached can be quoted the same day.
So the enquiry capture is structured rather than a bare contact form, and it is on the page the buyer is already reading rather than two clicks away. On the recruitment side the same modal asks a different set of questions, because an employer needing twelve pickers and a candidate looking for a shift are not the same enquiry and should never land in the same inbox shape.
That is the difference between a website that generates enquiries and one that generates quotable ones — and it is usually worth more than another thousand visitors.
Why it matters
Enquiry quality over volume
- Requirement captured at the point of interest, not after a call.
- Location and service already attached, so routing is automatic.
- Employer and candidate enquiries kept structurally separate.
- The same structure across 5,240 entry points.
Questions
The WSUK build, answered.
What people ask when they see a site this size.
What did GTX Digital build for WSUK?
The whole public platform: a service architecture covering more than sixty logistics service and job families, a service-by-location content cluster that now runs to 5,240 URLs, a self-publishing technical insights library, a recruitment section with its own location hubs, and the structured enquiry flow that feeds the sales team. It is a custom build rather than a CMS theme.
How big is the site?
The live sitemap lists 5,240 URLs. That is the product of crossing every service with every town in the operating radius, plus the service hubs, the insights articles and the recruitment pages. Each location page runs to roughly 3,400 words of content written for that place rather than templated across it.
How do you build a cluster that size without it being thin?
By carrying real local data and measuring the result. Each town has its own road links, postcode districts and sector mix, and each service frames that material differently, so two pages about the same town or the same service do not converge. We measure near-duplication on the written sections specifically, because a whole-page measure is flattered by shared headers and footers and hides the problem.
Does a site that size stay fast?
Only if someone keeps measuring it. The insights index was rendering every post inline and had reached 910KB and 2,808ms to interactive. We paginated it to thirty cards a page, built the pagination into the publish step so it survives every new post, and brought first load to 114KB and 222–434ms. That is the kind of problem that only shows up at scale, and only if page weight is on someone’s dashboard.
Does a page like that work for AI search as well as Google?
They reward overlapping things, which is why the same build serves both. Answer engines lift a self-contained passage that answers the question directly; generative assistants draw on a business that describes itself consistently everywhere and is corroborated by third-party sources. Answer-first structure, honest specifics and clean entity data serve all of it.
What is the partner portal?
A separate application on its own subdomain that runs WSUK’s partner network. Enquiries from the website post into it over an authenticated webhook; an administrator forwards each one to the partner whose capacity, specialism and location fit; that partner accepts or declines it in their own dashboard; and the job is tracked through to completion with an email log and an activity trail behind it. It exists because a logistics business generates more enquiries than its own depots can service, and the overflow is worth more routed than refused.
Can you do the same for our business?
If the shape fits: a real service range, a defined operating area and buyers who search by capability and location. It is not a fit for every business, and a cluster built where that demand does not exist is a liability rather than an asset. The first conversation is about whether the shape is there.
Client voices
What clients say.
-
GTX Digital has been brilliant to work with. They took the time to understand what we needed and built a solution that actually works for the business. The communication has been excellent throughout and it’s clear they understand both the technology and the commercial side.
Tony ShinglerOmnia Resourcing -
Really impressed with GTX Digital. They took the time to understand how our business works before recommending a solution. The whole process was clear, professional and much easier than expected.
James Wilson -
GTX Digital helped us connect several systems that were previously working separately. It has saved our team a lot of manual work and made our processes much more efficient. Great experience overall.
Daniel Harris -
We needed a bespoke software solution for our business and GTX Digital understood exactly what we were looking for. The communication throughout the project was excellent and the finished system works really well.
Sophie Mitchell -
Very professional team. They took the time to understand the problem before suggesting a solution, which we really appreciated. Everything was explained clearly and the project was handled extremely well.
Michael Thompson -
GTX Digital made a complicated technology project feel very straightforward. They kept us updated throughout and were always available when we had questions. Very happy with the final result.
Oliver Bennett -
We approached GTX Digital to replace an outdated system and they handled the whole process brilliantly. The new platform is much easier for our team to use and has made our day-to-day work considerably smoother.
Emily Carter -
Really good experience from start to finish. The team listened to what we needed, explained the technical side in simple terms and delivered a solution that works perfectly for our business.
Ryan Edwards -
GTX Digital helped us automate several repetitive tasks that were taking up far too much of our team’s time. Their approach was practical and the improvements have made a noticeable difference.
Charlotte Morgan -
We had several systems and APIs that needed to work together, and GTX Digital handled the technical side extremely well. They were organised, responsive and professional throughout the project.
Thomas Cooper -
Very happy with the service from GTX Digital. They didn’t try to sell us things we didn’t need. Instead, they focused on understanding our business and finding the right solution.
George Richardson -
GTX Digital helped us turn an idea into a working digital platform. The team were knowledgeable and easy to communicate with, and they made sure we understood everything throughout the development process.
Hannah Walker -
Excellent experience with GTX Digital. The project was well organised and we always knew what was happening next. The final system has made our internal processes much more efficient.
Jack Anderson -
We needed a technology partner who could understand both our business requirements and the technical side of the project. GTX Digital were a great fit and delivered exactly what we needed.
Lauren Parker -
The team at GTX Digital were fantastic to work with. They took a complicated requirement and broke it down into manageable stages. The final solution has saved us a lot of time and reduced repetitive work.
Ben Foster -
Highly recommended. GTX Digital combines strong technical knowledge with a very practical approach to business problems. Communication was excellent and we were very pleased with the finished product.
Olivia Collins
Services used
What this build drew on.
-
Build
Web Platforms
Logged-in platforms that carry real transactions, not brochure websites.
Explore -
Grow
Technical SEO
The engineering half of search: crawling, indexing, rendering and speed.
Explore -
Grow
Answer Engine Optimisation
Being the answer that gets extracted, not the tenth link nobody clicks.
Explore -
Grow
Conversion & Analytics
Measuring what happens after the click, then fixing where it leaks.
Explore
Next step
Does your business have the same shape?
A real service range, a defined operating area and buyers who search by capability and location. If that is you, this approach works. If it is not, we will tell you rather than sell you 5,000 pages nobody needs.