A better website should move the business forward without losing what already works. I plan, redesign and migrate websites around your customers, your content and your control.
A website redesign is a chance to fix the way your business presents itself, explains its services and turns interest into an enquiry. It can also remove the daily friction of a platform you cannot update. The useful starting point is not a new theme. It is knowing what to retain, what to change and what must survive the move.
I work with New Zealand businesses on website structure, content, design and the practical migration to WordPress, Shopify or Wix where the platform fits. That includes the less visible decisions: URL continuity, important downloads, forms, domain access, analytics and the handover your team needs to maintain the finished site.
A refresh is enough when the foundations work. A rebuild makes sense when the foundations are the problem.
Every service update, photo or correction depends on someone else. Start by confirming ownership, access and which parts of the current platform are actually restricted.
Your offer, customers or standard of work has changed. The site still represents the business you were, with a structure that hides what you do now.
Mobile layouts, navigation, content and forms need more than isolated repairs. A coordinated rebuild may be more useful than adding another layer of workarounds.
The build is organised around a documented scope, not a promise that everything can be carried across automatically.
Inventory pages, useful search landing pages, forms, downloads and integrations. Review available analytics and Search Console data. Decide which URLs stay, which need a relevant replacement and which content should genuinely disappear.
Restructure services and content around the questions customers need answered. Keep distinct pages where the offer warrants them; consolidate repetition where it does not. Agree the main actions before choosing the layout.
Choose the platform against your catalogue, content and maintenance needs. Design reusable components, test mobile layouts and make the agreed everyday edits manageable for the people who will actually do them.
Map changed URLs, configure relevant redirects, test forms and key integrations, check indexability and canonical signals, and verify analytics. Launch checks are followed by a defined review of the live site rather than an assumption that staging tells the whole story.
Illustrative applications: the migration plan changes with what the website has to protect.
An electrical business has an old agency-controlled site and cannot update its offer.
The approachConfirm domain and hosting access, retain useful service URLs, rebuild editable service templates and test the enquiry route on a phone.
What to checkCheck that staff can complete agreed edits and that real enquiries reach the right inbox.
A landscape business has strong projects scattered across galleries with little context.
The approachCreate a project structure that explains the brief, service and finished work; migrate approved images and connect each project to the right service.
What to checkReview project-to-service journeys and the relevance of project enquiries.
An association needs a clearer public website without breaking member resources or application pathways.
The approachSeparate public and member-only requirements, inventory documents, confirm any member-system dependencies and test key tasks before switching.
What to checkVerify resource access and application completion, not simply that the homepage looks new.
Old pages need an intentional destination. Sending every retired URL to the homepage is not a migration strategy.
| Existing page | Decision | Reason |
|---|---|---|
| A useful service page with the same offer | Keep its URL where practical; improve the page in place. | A redesign does not require changing every address. |
| Two overlapping pages becoming one clearer service | Map both to the genuinely relevant consolidated page. | The replacement should answer the original visitor’s intent. |
| An obsolete offer with no relevant replacement | Remove it deliberately and return an appropriate not-found response. | A misleading redirect is not useful to the visitor. |
| A frequently linked PDF or resource | Retain its address or map it to the updated resource. | Navigation menus are not the only way people reach your content. |
Review the current site, access, content and available performance data. Identify what is known, what needs investigation and whether a full rebuild is warranted.
Set the platform, page inventory, content responsibilities, design direction and migration scope. Document dependencies before the build starts.
Work through the approved design, content and functionality on staging. Test the customer’s tasks as well as the appearance of each page.
Use the agreed launch plan, verify the live site and hand over access and editing guidance. Define the follow-up support period in the proposal.
The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.
Page count is only one factor. Content rewriting, platform changes, catalogue or membership data, custom functionality and the condition of the current site determine the work. I scope those before quoting.
Access, approved content and integration decisions are often the critical dependencies. Agree the build sequence and launch window after the audit; avoid changing platform and business-critical systems without a coordinated plan.
You provide authorised access, business facts, licensed assets and timely approvals. I plan and deliver the agreed build and migration. Domain, platform and analytics ownership should remain with your business.
AK Electrical needed to move beyond a hard-to-update website. Living Landscapes needed a presentation that better reflected its established business. These case studies show the brief, design decisions and completed website work.
An editable WordPress website, clearer services and control over future updates.
A WordPress rebuild for an established Melbourne landscaping business.
Yes, where the existing platform supports the required design, editing and functionality. I review the restrictions first. Moving systems should solve a real problem, not be a default condition of working together.
It can. Changes to URLs, content, internal links and technical signals may affect search performance. Keeping useful URLs, planning relevant redirects and checking the live site reduces avoidable risk, but no migration can promise unchanged rankings.
Start with the facts: who owns the domain, who pays for hosting, which accounts you control and what your agreement allows you to export. I can identify the access needed and plan the rebuild around what is legitimately available.
Yes, if you have the rights to use them and they still do the job. Content is reviewed rather than copied unquestioningly. Important business facts may stay; weak structure, old offers and unclear messages may need work.
Usually the new build can be developed on staging while the current site remains live. The cutover plan depends on hosting, domain access, transactions and integrations. We agree those details before launch.
The agreed everyday content should be editable, and the handover covers those tasks. More complex design or functionality changes may still need specialist work. We define what your team needs to manage before choosing the build approach.
Choose the service that solves the problem in front of you.
Plan the catalogue, checkout and fulfilment requirements of a store.
A practical guide to the search considerations behind a website move.
Work directly with Dan Smith. Based in Christchurch, working with businesses across New Zealand.
Send the current website and tell me what you cannot change, what no longer fits and what the next version needs to do.
Good websites work harder. Cookies help us see what’s working.
Essential cookies keep things running. With your permission, analytics cookies help us understand how you use the site, and marketing cookies help us measure ads and show relevant ads. Optional tracking stays off until you say yes. You can change your mind in Cookie Preferences.
The essentials keep this site working. Analytics and marketing cookies are optional. Choose what suits you and change your mind here at any time.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Optional analytics cookies help us understand visits and interactions using browser identifiers. They run only if you accept Statistics and the relevant service.
Google Analytics 4 measures page visits and meaningful interactions after you accept analytics cookies. We do not send contact form answers, names, email addresses or phone numbers in analytics events.
Service URL: policies.google.com (opens in a new window)
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Measures page visits and successful enquiries and helps Daniel James show relevant ads on Facebook and Instagram after you visit. This runs only if you accept Marketing and Facebook Pixel.
Service URL: www.facebook.com (opens in a new window)