Old specification PDFs outrank current ones
No version control in the media library means a superseded document often keeps its search ranking after being replaced.
Everything below is ours and on our servers. Nothing follows you to another site.
Who
How we work
Rebuild
FROM WORDPRESS · ENGINEERING CONSULTANCY
WordPress's media library has no version control, so a superseded specification often keeps its search ranking after being replaced, and a tender request submitted through a plain contact form lands in a shared inbox with nobody tracking who owns it. The two failures together are how a consultancy loses a pre-qualification it never actually saw.
WHAT ACTUALLY BREAKS
Document versioning, discipline structure and tender workflow, not generic WordPress complaints.
No version control in the media library means a superseded document often keeps its search ranking after being replaced.
A contact-form submission with no workflow attached is easy to miss, and a missed submission deadline is a lost opportunity, not a minor delay.
A category taxonomy built for blog posts rarely maps onto structural, MEP, civil and geotechnical the way procurement search actually needs.
Registration body and chartered status, the thing that actually wins pre-qualification, usually sits as unstructured text on a generic team page.
Client type and sector are rarely stored as filterable fields, so a procurement search cannot match capability to requirement across the archive.
WHAT CARRIES ACROSS
Content and process are separate problems, migrated separately.
Every project's scope, sector and completion data carries across intact. What does not carry across is how documents and tender requests were handled: unversioned uploads and an untracked contact form are rebuilt as a proper document library and a real intake workflow.
WHAT IT COSTS
A range, not a fixed price, because document volume and project count move the number.
Depending on document volume and project count.
From brief to launch.
The single costliest failure when an untracked request goes unanswered.
HOW IT RUNS
Versioning and discipline structure audited first, since that is where the actual risk sits.
We identify which documents are actually current, which superseded ones are still ranking, and how discipline navigation currently works.
Every project page is mapped against Search Console, since technical case studies often carry earned rankings worth preserving.
A superseded document is retired properly, discipline navigation matches how clients actually search, and sector data becomes filterable.
Every project and document URL redirected to its new address, with Search Console watched daily for the first two weeks after launch.
STRAIGHT ANSWERS
The ones that come up before anyone signs anything.
WordPress's media library has no version control. When a specification is updated, the old file usually stays live at its own URL, still indexed, and Google has no way of knowing the new one is the one that matters.
They usually arrive through a plain contact form into a shared inbox, with no workflow tracking who is handling what. A request that needs a same-day response to make a submission deadline can sit unread for a day.
A client searching for a structural engineer is not the same search as one looking for MEP, and a WordPress category taxonomy built for blog tags rarely maps cleanly onto the discipline structure a procurement search actually uses.
Between
Two days, no charge, no obligation, and you keep the report whether or not you hire us.
One tap, then your app opens with it written.