36
- Client
- A1 Sure Services
- Industry
- Tree removal and arborists
- Live
- October 2026
- Agency
- Glasshouse Digital
- Services
- Webflow migrationWeb design
- Platform
- WordPressDivi → Webflow
A1 Sure Services: An arborist’s WordPress site moved to Webflow, every URL kept.
A1 Sure Services is a family-run tree removal and arborist company that has worked across Auckland since 2001. Its site ran on WordPress with the Divi theme: 36 pages and 155 blog posts built up over the years. Working as the contractor for Glasshouse Digital, the New Zealand agency that ran the project, we moved all of it to Webflow on the same addresses, redirected what was retired, and switched the domain over in October 2026.

A WordPress and Divi site moved to Webflow without losing a single address.
36 pages and 155 blog posts rebuilt in Webflow on their original URLs, with titles, descriptions and structured data carried over word for word. 257 thin tag archives closed with one redirect rule, 15 overlapping pages retired, 34 redirects verified one by one, and zero broken links on the final crawl before the domain moved.
Years of posts, all ranking on their own addresses.
A local service business lives on search. Every service page and every post on tree pruning, stump grinding or pohutukawa care was a URL Google already knew. The move to Webflow had to keep each of them working — and WordPress had put the posts at the root of the domain, where Webflow’s CMS cannot.
155
blog posts
257
tag archives
Three decisions that kept the rankings in place.
Every URL stays where it was
Posts as pages, not CMS items
Archives become one rule
155 posts, each on the address it always had.


From the WordPress sitemap to the domain switch.
The site was built through Webflow’s MCP server with an AI agent doing the repetitive work. Every change was checked on the published site, not in the editor. How we use Webflow MCP in a migration
Inventory
The URL list came from the WordPress sitemaps, not the menu, which hid several pages. Each URL was checked: a few were already WordPress redirects to other posts, so they became redirects again rather than pages.
Rebuild, measured
Pages were rebuilt in Webflow with the original as the reference — header sizes, menu breakpoints, type and spacing were measured on the old site, not guessed. Header, footer, reviews, FAQ, the quote band and the contact bar are shared components, so no block is hand-copied between pages.
Content and metadata
155 posts parsed out of the Divi markup and rebuilt from one template, with their featured images and in-article images. 111 images moved into Webflow's own asset library, so nothing loads from the old host.
Requests from the agency
Glasshouse Digital, which ran the project, sent a long list of requests to improve how the key service pages look. We built all of them: service pages rebuilt in the new layout of the redesigned tree removal page, a few slugs renamed, and 15 overlapping pages retired: nine North Shore copies of the service pages folded into one North Shore hub, the rest merged into the pages that replaced them.
Redirects and links
34 rules in Webflow's 301 list, each checked with a request after publishing. Then every internal link that pointed at an old address — over 300 of them across the blog — was repointed to the final URL, so no internal link goes through a redirect.
Crawl, then cut over
Before the domain moved, a crawl of every published page checked for broken link targets, links through a redirect and anything still pointing at WordPress. All three came back zero, and on 7 October 2026 the domain was switched to Webflow.
One layout for every service.
Glasshouse Digital, which ran the project, had many requests for improving how the key service pages look, and we carried out every one. The pages now follow the redesigned tree removal page: the offer, the reasons to choose A1 and the quote request at the top, then the detail. Tree trimming, stump grinding, palm trees, pohutukawa, land clearing, mulch and the emergency service were rebuilt in that layout, and the North Shore copies of each service were folded into one hub page.



Live on Webflow, with nothing left behind on WordPress.
190
pages live on Webflow
34
301 rules, each verified
0
broken links at launch
Alexander migrated and refreshed a very old, outdated website into something modern, clean and exceptionally fast.
Considering the scope of the job and the little input he required from us to get it done, we couldn't be happier with the results.
Jimmy Thrush-Marsh · Digital Performance Director at Glasshouse DigitalThe partner behind the project
Glasshouse Digital, an Auckland agency, ran the project and the communication with A1 Sure Services. We did the migration and every change the agency asked for along the way. It is the same arrangement as the Vines Estate campaign page and the Dawsongroup TCS homepage.
Further reading
Webflow MCP and WordPress-to-Webflow Migration: What an Agent Actually Speeds Up
Webflow's MCP server lets an AI agent build pages, restructure CMS collections and apply SEO metadata across a whole site. Here is what that changes at each stage of a WordPress-to-Webflow migration — and the parts it changes nothing about.
Webflow SEO in New Zealand (2026): What Webflow Handles and What Still Needs an Expert
Is Webflow good for SEO, and what should a Webflow SEO specialist in New Zealand actually do? What the platform handles natively, the setup mistakes we see, local and AI-search work, and what it costs in NZD.
Where We Use AI in Client Work, and Where We Don't
Plenty of business owners now read AI as a sign that a vendor cut corners. The real problem is AI output nobody checked. Here is what we hand to an agent, what stays with people, and how one real WordPress-to-Webflow migration split.
Moving off WordPress, but not off page one?
Send us your site. We start from the URL inventory, keep every address that earns traffic, redirect the rest and check the result on the published site before the domain moves.
Questions about the A1 Sure Services migration.
By crawling the published Webflow site rather than trusting the editor. Every published page was fetched and checked for broken link targets, internal links that go through a redirect, and any reference left to the old WordPress host. Each redirect was requested once to confirm it returns a 301 to the right page. The domain moved only after all of it came back clean. The full checklist is on migrating to Webflow without losing SEO.
Yes. A1 Sure Services is a typical case: a WordPress site with years of blog posts and a page builder holding the layout together. We start with the URL inventory, keep every address that earns its place and redirect the rest. See WordPress to Webflow migration and Webflow development in New Zealand.







