A webdesigner hard at workd building designs
A webdesigner hard at workd building designs

Before you build your website, do this first

Most NZ businesses build a website and then wonder why it is not generating enquiries. The order is wrong. The website is built before anyone has answered the questions that determine whether it will work. Here is what to do first, and why it changes everything about how the website gets built.

A headshot portrait photo of Jake Siddall Creative Director and founder of Kyttn

Jake Siddall

Creative Director & Founder, Kyttn

Before you build your website, do this first

Most NZ businesses build a website and then wonder why it is not generating enquiries. The order is wrong. The website is built before anyone has answered the questions that determine whether it will work. Here is what to do first, and why it changes everything about how the website gets built.

A headshot portrait photo of Jake Siddall Creative Director and founder of Kyttn

Jake Siddall

Creative Director & Founder, Kyttn

The decisions that determine whether a website generates enquiries are made before the first design brief is written.

The question most businesses never ask before they build.

Is there a gap in my market that a properly built website can actually capture?

This sounds obvious. In practice almost nobody answers it properly before commissioning a website. They brief a developer on the pages they want, the design they like, and the features they need. The developer builds it. The site launches. And then the question becomes: why is nobody finding us?

The answer is almost always that the site was built without knowing what it needed to rank for, who it needed to attract, or what it needed to say to make those people act.


What a diagnostic tells you before you build.

Before Kyttn builds or rebuilds any website, we run Sphynx 2.0 on the market. The diagnostic tells us five things that directly determine how the site should be structured:

Which terms your customers are actually searching in NZ, not what you assume they are searching, but what the data says. This determines the H1s, the page structure, and the URL slugs.

Which competitors are ranking for those terms and how strong they actually are, real domain authority, backlink quality, content depth. Most NZ competitors are beatable. You need to know which ones.

Which gaps exist that nobody is targeting, the terms with meaningful search volume and low competition that a properly built site can realistically rank for within months.

What search intent the arriving visitor has, what they expect to find when they click. This determines the copy, the structure, and the conversion architecture of each page.

Whether Google Ads makes sense in parallel with organic, and at what budget the economics work.

A website built around those five answers is fundamentally different from one built around design preferences and feature lists.

How Sphynx 2.0 works


The conversion architecture has to be in the brief, not retrofitted after.

The most expensive mistake in website builds is treating conversion as something you fix after the site is live. Adding a stronger CTA. Rewriting the headline. Moving the contact form.

Conversion architecture is not a cosmetic fix. It is the structure of the site, which pages exist, what each one says, how they link to each other, where the friction points are in the journey from landing to enquiry.

En Beauty launched with conversion architecture built into the brief from day one. The site was designed to convert before the first visitor arrived. The result was a 6.5% conversion rate against a 2% industry average.

If conversion architecture is retrofitted, you are solving a problem that was created at the brief stage. It is slower and more expensive than getting it right the first time.

What conversion rate optimisation actually involves


The SEO architecture has to be in the build, not bolted on later.

Most websites are built and then handed to an SEO person to optimise. The SEO person looks at the URL structure, the page hierarchy, the H1 tags, and the internal linking, and finds that the architecture does not support the keyword strategy.

Fixing this after the site is live is possible but slow and expensive. The right page structure, the right URL slugs, the right H1s, the right schema markup, the right internal linking, these are build decisions, not afterthoughts.

Japan360 went from zero NZ rankings to position 1 within 24 hours of rebuilding the architecture properly. The underlying site was well designed. The structure was wrong. One session fixed it.

Read the Japan360 case study


So what should you do before you brief a developer?

Run a diagnostic. Find out what the market is actually searching for. Identify which terms are genuinely winnable. Understand what the site needs to say to make the right people act.

Then brief the developer. With keyword targets. With page structure. With conversion requirements. With the SEO architecture already designed.

The website that comes out of that brief will be fundamentally more effective than one built on assumptions. And it will not need to be retrofitted six months later.

What an SEO consultation covers before a build

How the Kyttn diagnostic works

A website is not a deliverable. It is an asset that either generates enquiries or it does not. The decisions that determine which one it becomes are made before the first design brief is written.

Get those decisions right first.

Talk to Kyttn before you build