Moving a product marketing site off engineering's critical path
A Salesforce static-analysis product site built on Go, migrated to WordPress with 95% visual parity — so marketing could move fast without touching a line of Go again.
The challenge
CodeScan is AutoRabit's static code analysis platform for Salesforce, scanning Apex, Lightning Web Components and metadata to catch vulnerabilities and standards violations before deployment — a serious B2B DevOps product sold into regulated, security-conscious buyers. Its marketing site, however, was built on Go, which meant every content change or landing page needed engineering time. For a fast-moving product marketing team, that dependency was the actual bottleneck, not any design flaw in the existing site.
Our approach
The brief was strict and specific: migrate the site to WordPress with the visual appearance as close to identical as possible, so the change would be invisible to visitors and prospects while giving the marketing team direct editorial control going forward. That meant precision rebuilding rather than redesigning — matching layout, typography and interaction detail from the original Go-rendered site rather than using the migration as an excuse to redesign.
What we actually did
The existing site rebuilt in WordPress to match the original Go-built version to within 95% visual fidelity — the constraint was preserving exactly what already worked, not introducing a new design under the guise of a migration.
A CMS structure that gives the marketing team direct control over content, landing pages and copy changes — removing the requirement to file an engineering ticket for a headline change.
URL structure, metadata and content mapped carefully during the move so the site's existing search visibility and inbound links continued to work exactly as before.
The outcome
The migrated WordPress site matched the original Go-built site's appearance to the exact fidelity the client specified, with no visible disruption to visitors.
Content and landing page changes are now made directly by the marketing team in WordPress, rather than queued behind an engineering backlog.
The migration preserved URL structure and metadata, so the site's existing organic visibility carried through the platform change intact.
CodeScan moved off a Go-built site that only engineering could touch, onto a WordPress build the marketing team now runs directly — without the migration itself being visible to a single visitor. For a mature B2B product site, that kind of disciplined, invisible migration is usually worth more than a redesign would have been.
Does any of this sound familiar?
This project started from a specific set of symptoms. If you recognise several of these in your own business, the problem is probably closer to CodeScan (AutoRabit)'s than it looks.
Not every migration should become a redesign — sometimes the existing site works and the platform underneath it is the only real problem. We would scope precisely what "unchanged" needs to mean for your specific case, then rebuild to that constraint rather than treating the move as licence to change things nobody asked to change.
Other client work
A tax filing service losing people mid-journey — rebuilt around clarity, trust and a single obvious next step.
Read the case study
CarZScrapA scrap car platform with no brand recognition — given an identity, a lead engine, and a site built to capture intent in one screen.
Read the case study Orbynx84An end-to-end operations platform for a café group — POS, kitchen display, inventory and reporting in one system instead of five.
Read the case study