We build Umbraco sites for clients, so our own site should show how we work. In 2026 we rebuilt splatdev.com on Umbraco 17. This case study covers the migration, the problems our SEO crawls found, and one incident that taught us to trust the CMS's version history.
The starting point
The old splatdev.com ran on Umbraco 11, which was out of support, with a design that had grown over the years. Instead of upgrading through every major version, we built a new Umbraco 17 site on .NET 10 alongside it, with a fresh content model, and moved the content across.
The migration
A new content model with separate document types for services, products and blog posts
Multilingual content with localized URLs and hreflang
A staging site where we reviewed every page before launch
A cut-over on 9 July 2026, switching the domain from the old site to the new one at the proxy, with the old site kept ready for rollback
What the first SEO audit found
An Ahrefs site audit in August 2026 scored the new site 16 out of 100, with 1,218 issues. Most came from one decision: we had launched in ten languages. One of them used a language code that hreflang does not accept, and that alone produced 462 errors. The other languages had no organic traffic.
We cut the site to English, Brazilian Portuguese and Spanish, added 301 redirects from the retired language URLs, and fixed the sitemap, which had been reading its language list from a different place than the rest of the site.
The incident
In November an automated publishing job renamed our Blog page while trying to create a post. Every navigation link to the blog started redirecting to a page that returned 404, and the audit health score dropped from 100 to 27 in a week.
Umbraco's version history made the fix quick: we restored the page from its last good version, removed the stray pages the job had created, and the next crawl was back at 100. While checking the blog we also found post bodies that an earlier import had emptied, and restored them from version history too.
What we changed afterwards
Structured data for blog posts, products and the organization, so search engines understand each page type
Titles, meta descriptions and headings written for the keywords each page targets
Long-form content on every service page in all three languages
Redirects for old URLs that still had rankings and backlinks
Weekly crawls, so problems surface in days, not months
Lessons for your own migration
Launch with fewer languages. Add a language when there is demand and content to support it.
Crawl right after launch, and then on a schedule.
Keep version history, and know how to restore a page before you need to.
Be careful with automation that writes to your CMS. Give it the narrowest permissions it needs.
Planning your own move? Read our Umbraco 17 upgrade guide, see our Umbraco 17 upgrade and migration services, or contact us.