No Brainer

Web Design31 Jul 20268 min read

Published by No Brainer Creative

Moving from Wix or Squarespace: A NZ Website Planning Guide

A website redesign and a platform migration are different decisions. You may be able to improve a Wix or Squarespace website without moving it. If a move is justified, plan what happens to the content, URLs, business tools and customer journey before deciding how the new site should look.

This guide is written by No Brainer Creative, an Auckland web design and digital marketing agency. It is a practical planning framework for NZ businesses, not an independent platform ranking or a promise that a rebuild will improve search positions or enquiries.

First decide what needs to change

Write down the specific problems you want the project to solve. Examples might include service information that is hard to maintain, an enquiry route that does not fit staff workflow, a genuine integration requirement, or a layout that does not present the business clearly on a phone.

Then ask what prevents the current site from meeting those needs. Is the limitation in the platform, plan, configuration, content or implementation? A vague statement that you have “outgrown the builder” is not enough to compare a targeted repair with a rebuild.

Do not assume that every template site is slow or every custom site is fast. Review the actual page, its content and the conditions of the test. Likewise, a business’s age, profession or previous design budget does not automatically decide whether it should migrate.

Check platform capabilities against your requirements

Some older platform comparisons make claims that are too broad. Wix documents how to add structured data to site pages. Squarespace describes its built-in SEO features, including automatically generated structured data. That does not prove either platform meets every requirement, but it does rule out a blanket claim that these sites cannot use structured data.

For a booking, shop, membership area or CRM connection, write down the actual workflow. Which system is the source of truth? What information is transferred? Who maintains it? Ask the provider to demonstrate the required capability and explain any plan, integration or development dependency before choosing a destination platform.

For Google’s AI search features, avoid sales claims about a special markup requirement. Google’s AI features guidance says there are no additional technical requirements or special schema needed for AI Overviews and AI Mode. Eligibility does not guarantee inclusion. A platform change alone is not evidence of an AI visibility gain.

Build an inventory of the website you are replacing

Record the pages and assets the business still needs. Include service pages, articles, product information, downloads and images that people use or link to. Note the owner and the reason each item matters, rather than treating every old page as equally valuable.

Keep copies of approved content and the existing public-page details before editing. Preserve original publication dates and authorship where appropriate. Identify inaccurate or duplicate material separately so a migration does not become an unexplained loss of useful information.

Business systems need their own inventory. A shop may have product options, customer accounts, order records, discounts or fulfilment tools. A service business may depend on booking calendars, enquiry notifications or a CRM. Do not assume a visual rebuild transfers those functions or records automatically.

Make URL decisions explicit

Where an important URL can remain useful at the same address, keeping it avoids an unnecessary change. When an address must change, record the relevant destination and who will implement and test it. Give removed or merged content an intentional treatment rather than sending every old route to the homepage.

Google’s site-move guidance recommends mapping old and new URLs, using appropriate permanent redirects for changed addresses, updating internal links and checking canonical and indexing settings. It also explains that rankings can fluctuate while Google processes a significant move. These are migration practices, not a guarantee that every position stays unchanged.

A practical mapping sheet can be simple: old URL, intended action, new URL if applicable, reason, responsible person and verification status. Mark a route as verified only after checking the live outcome. Keep the original inventory so an overlooked page can be investigated.

Plan the enquiry or purchase journey separately from the design

List what a visitor should be able to do and what staff must receive. A contact button, a submitted form, an inbox notification and a retained CRM record are different steps. Decide which ones are in scope and how each will be tested.

For a shop, agree how product data, stock, payment, shipping, tax settings and transactional messages will be checked. Tests involving orders or messages need an agreed method and clearly identified test records. A screenshot of a checkout does not prove that an actual customer can complete the purchase and receive the expected follow-up.

For a service website, agree the enquiry destination, acknowledgement, staff ownership and exception route. Do not quietly change email or domain settings as part of a design task. Identify dependencies and involve the provider responsible for them when a change is necessary.

Use a launch checklist the business can review

Area Before launch Evidence after launch
Content Approved page and asset inventory with any deliberate removals recorded. Important public pages, images and downloads are present and usable.
URLs Agreed decisions for retained, moved and merged pages. The old routes lead to the intended useful outcome.
Search setup Review intended index settings, canonical URLs and sitemap coverage. Live output matches the plan; Google processing is reported separately.
Enquiries Named receiving team, test method and failure-handling process. Controlled tests establish the agreed handoff steps.
Business tools Inventory of booking, shop, CRM and other dependencies. Each required connection has its own recorded check.
Reading and navigation Agreed phone, desktop and keyboard checks. Important information and actions are usable in those checks.
Handover Account ownership, ongoing charges, support and restore arrangements. The business knows who maintains the site and how to get help.

Agree who can approve launch and who can respond if a material problem appears. Preserve the agreed rollback evidence and record what a rollback would affect. Do not describe an untested backup as a verified recovery plan.

Compare the full cost and handover arrangement

A custom website is not automatically free of continuing charges. Ask about hosting, domain renewal, software licences, care, backups and third-party integrations. Clarify the difference between project fees, recurring services and optional later work.

Record what files, content and account access will be supplied, and any licence conditions that apply to third-party material. “You own everything” is too vague if it hides dependencies or leaves the business without the access needed to operate the site. Ask for the actual arrangement in the proposal.

Choose a delivery plan around content readiness, approvals, implementation and verification. There is no universal timetable for every NZ business or every platform move. A project deadline and a future Google indexing or ranking outcome are separate things.

Measure the result without confusing the signals

Save a dated baseline for relevant pages and customer actions before launch. After launch, distinguish a verified website repair from a change in search impressions, a rank-tracker observation or an actual enquiry. Device, location, reporting period and collection method should be clear.

Small samples, seasonality, changed advertising and a different service offer can affect comparisons. If traffic or enquiries change, investigate before assigning the cause to the platform move. The question is whether the business’s requirements are being met, not whether the new dashboard looks more impressive.

Discuss a targeted repair or a planned rebuild

No Brainer’s Auckland web design service covers planning a website around the business, content and enquiry journey. If you operate a store, our ecommerce website service explains the product, checkout and fulfilment decisions to scope.

Bring the current website, important pages, required tools and the problem you want solved. Our website briefing guide can help organise those details. Contact No Brainer to discuss whether a repair, redesign or migration has the clearest reason behind it.

Frequently asked questions

Do I need to leave Wix or Squarespace to improve SEO?

No. First identify the actual problem and whether it can be addressed on the current site. Both platforms have documented SEO capabilities. A migration should solve a defined business or technical requirement; changing the platform is not a ranking strategy by itself.

Will redirects guarantee that my Google rankings stay the same?

No. Appropriate permanent redirects help users and search engines reach a changed URL, but rankings can fluctuate during a significant site change. Keep useful URLs where practical, map changed pages to relevant destinations and verify the live implementation. Do not treat a redirect list as a guarantee.

Does every page need a redirect during a rebuild?

A URL that remains unchanged does not need a redirect merely because the design or platform changes. Record what happens to each important URL. A moved page needs an appropriate destination; removed content needs an intentional treatment. Avoid sending unrelated old pages to the homepage.

Can I keep the domain and business email?

A platform move does not automatically require a new domain or email provider. Identify which services depend on the current setup and plan any necessary changes with the responsible providers. Verify website and email continuity before cancelling an existing subscription.

Does a custom website remove all ongoing costs?

No such outcome should be assumed. Compare hosting, domain renewal, support, backups, software licences, integrations and maintenance for each option. Clarify what is included in the project quote, who owns the accounts and which charges continue after launch.

How long does a Wix or Squarespace migration take?

The scope, content readiness, integrations, data-transfer requirements, approvals and testing determine the work. Ask for a project plan with dependencies and review points. A fixed delivery date does not establish when Google will process the changes or how rankings will behave.

Do I need special schema to appear in Google’s AI features?

Google says there is no special schema or additional technical requirement for AI Overviews or AI Mode. Normal search eligibility and useful content still matter, and appearing in those features is not guaranteed. Do not migrate solely because someone claims a special AI markup requirement.

What should I check before cancelling the old website plan?

Confirm the agreed content and assets are retained, important URLs work, enquiry or purchase routes have been tested, required records are accessible, and the responsible people have the necessary handover information. Check dependencies such as email, domain management and integrations before ending an old service.

Want this done for your business?

Let’s talk.

You don’t need to arrive with a marketing plan.

Tell us where the business is now, where you want it to go and what’s frustrating you.

We’ll help work out the bit in between.

No pressure. No jargon. No 84-slide presentation.Just a useful conversation about your business.