A public site with nothing to patch
The public side only serves pre-built HTML, so there is no PHP, WordPress core or plugin for vulnerabilities to target — and no emergency patching.
Service
We take your current site's code, domain and hosting and rebuild it as a static site whose content is managed in Sanity. Your URLs stay the same, and we hand over so your team can keep the site up to date. A straightforward migration takes two to three weeks; when a critical vulnerability makes it urgent, an expedited migration can be done in a few days.
What changes
The public side only serves pre-built HTML, so there is no PHP, WordPress core or plugin for vulnerabilities to target — and no emergency patching.
Posts and company information live in one Sanity editor. Consolidate several sites onto the same platform and security reviews and permissions are handled in one place too.
Structured data, a Markdown copy of every page and llms.txt are generated automatically, so Google's AI Mode and AI assistants such as OpenAI's ChatGPT and Anthropic's Claude read your company information accurately.
Research and drafting with AI tools such as Anthropic's Claude and OpenAI's ChatGPT (Codex), with fact-checking and publishing by people — so non-engineers can keep publishing quality content.
Case study
At an IT company with several thousand employees, a WordPress site of thousands of pages sat alongside sites and landing pages built by different teams on different systems and servers, so security reviews and operations were handled site by site. Starting with one site, we have migrated every post and page and validated a platform that can bring dozens of sites onto Sanity. That first migration took two days.
Process
STEP 1
We list pages, posts and features such as forms, and check for dynamic features and where the code lives.
STEP 2
We decide what editors will manage in Sanity and how URLs are handled. Your current design can usually be kept.
STEP 3
We build the static site and move your pages and posts into Sanity — automated, even for thousands of pages.
STEP 4
We review in a preview together, check search details such as 301 redirects, switch your domain over and train your team.
What matters is whether the site has dynamic features — member login, search, booking, payments — and whether you hold its code. The new site is built alongside the current one and switched over at the end, so your site stays online throughout.
What you provide
The full source code, including any theme or plugin customizations.
Used to switch the domain over at launch.
Used to review content and settings.
Someone to decide which pages stay and to sign off before launch.
Expedite
When a critical vulnerability like PHP2Shell makes it urgent, we work alongside your PR and web teams, and if the code and information are ready, the migration can be done in a few days. Until the switch, we recommend protecting the current site in parallel — updating PHP and restricting access.
FAQ
Yes. Moving pages and posts is automated once the tooling is in place, so page count barely affects the timeline.
We'll obtain the code from them or rebuild where necessary, which adds time. Tell us your situation and we'll suggest the quickest route.
No. We build the new site alongside the current one and switch your domain over at the end.
Yes, but Sanity's full audit trail, single sign-on (SAML) and custom roles require its Enterprise plan. We can help you choose the right plan.
We train your team on editing in Sanity, including writing with AI tools such as Anthropic's Claude and OpenAI's ChatGPT (Codex). Ongoing maintenance and improvements can be arranged to fit your needs.
Considering a move off WordPress or consolidating several sites? Let's talk.
Get in touch