Why “website design” is not one thing

“We need a website” sounds simple. In practice, it hides dozens of decisions: who the site is for, what they must do on page one, how they find you, what you sell, how you prove trust, and what you can maintain over time.

Good design is not primarily about taste. It is about fit: the right structure, content, and interaction model for your business model, your customers’ intent, and the outcomes you measure (leads, sales, support reduction, recruitment, credibility).

This guide explains the major site types, common layout patterns, how people actually read screens, where key elements usually belong, the look vs functionality question, and how to think about results. It closes with how NZDH typically works with clients on these decisions, what you should prepare, and a checklist you can use before you start.

1. The main website types (and what each one must do)

Think in terms of jobs: what is the visitor trying to accomplish, and what must the site make easy?

Brochure website (credibility and contact)

Job: “I heard your name—prove you’re real, explain what you do, and make it easy to get in touch.”

Typical contents: Home, About, Services (or Industries), maybe a small portfolio, Contact, Privacy. Strong emphasis on clarity, trust, and a clear primary action (call, book, email).

Design implications:

Fewer templates, more story and proof (team, process, guarantees, certifications).
Fast answers beat clever animation.
SEO is often local and service-based (“plumber Hamilton”, “accountant Wellington”).

Risk: Beautiful pages with thin content rank poorly and convert weakly.

Business / corporate website (multiple audiences, structured information)

Job: Serve customers and partners, investors, media, or staff—without chaos.

Typical contents: Clear service lines, case studies, resources, careers, investor/news, compliance pages, segmented navigation.

Design implications:

Information architecture matters as much as visuals (menus, hubs, cross-links).
Consistent components (cards, lists, filters) reduce cognitive load.
Often needs role-based paths (“I’m a homeowner” vs “I’m a specifier”).

Risk: Navigation grows until nobody can find anything; the homepage becomes a billboard instead of a map.

Catalogue website (browse and compare, not always buy online)

Job: Show a large range (products, parts, courses, properties) with consistent data so people can compare and shortlist.

Typical contents: Categories, listing pages, detail pages, spec tables, downloads (PDFs, manuals), sometimes “request a quote” instead of checkout.

Design implications:

Listing pages are a product: filters, sort, search, facets.
Detail pages need structured fields (dimensions, compatibility, SKU, availability messaging).
Photography and consistent naming matter enormously.

Risk: Treating a catalogue like a brochure—pretty grids with no filtering or weak product data.

E-commerce / shop website (transactional)

Job: Help someone buy with confidence: find → evaluate → trust → pay → fulfil.

Typical contents: Category navigation, product pages, cart/checkout, policies (shipping, returns), support, account area, transactional email flows.

Design implications:

Checkout friction is measured in dollars.
Product pages need answers to objections (delivery time, sizing, warranty, compatibility).
Performance and mobile UX directly affect revenue.

Risk: Over-designing the homepage while cart/checkout is fragile, slow, or confusing.

Hybrid reality (most real projects)

Many businesses need brochure + catalogue, or business site + shop, or lead-gen + member area. The design task is to prioritise primary journeys and avoid forcing every visitor through the same funnel.

2. Layout types: patterns, not fashion

Layouts are tools. The right one depends on content volume, scanning behaviour, and the device mix.

Single-column narrative layout

Best for: Story-driven pages (About, service explainer, campaign landing pages). Strength: Linear flow; strong for mobile. Weakness: Poor for dense comparison unless broken into sections.

Multi-column grid layout

Best for: Dashboard-like density, cards, product grids, team pages. Strength: Scannable; supports repetition. Weakness: Can feel busy if hierarchy is weak.

Split layout (text + visual)

Best for: Heroes, feature sections, “problem/solution” blocks. Strength: Pairs proof with explanation. Weakness: Easy to break on small screens if the visual dominates.

Magazine / editorial layout

Best for: Blogs, guides, news, authority content. Strength: Supports long reads with sidebars, pull quotes, related links. Weakness: Needs disciplined typography and spacing or it becomes noisy.

Dashboard / app-style layout

Best for: Logged-in experiences, tools, configurators. Strength: Efficiency and repeat use. Weakness: Requires UX discipline; not a substitute for a marketing site.

“Landing page” layout

Best for: Paid ads with one goal. Strength: Focus. Weakness: Can starve SEO if it replaces a proper site architecture.

3. How customers read a website (and why it changes your design)

People rarely read websites like books. They scan until something matches their intent.

Scanning patterns

F-pattern: Common on text-heavy and search-result style pages—strong attention across the top, then down the left edge, with decreasing horizontal sweeps. Implication: headings and first words carry disproportionate weight.
Z-pattern: Common on simpler pages with a hero and a few focal points—eye moves top-left → top-right → diagonal → bottom-right. Implication: logo/top nav, primary headline, supporting visual, primary CTA placement should align with that motion.
Layer cake / “block” scanning: On mobile, users often scroll in chunks, stopping at headings, images, and buttons. Implication: each screen section should make sense on its own.

Intent beats decoration

A visitor usually arrives with a question:

“Can you do X?”
“Do you serve my area?”
“How much / how fast?”
“Are you legitimate?”
“Can I buy it now?”

Design succeeds when those answers are easy to locate without hunting.

4. Where things should go (practical placement principles)

Exact placement varies by brand, but strong sites tend to share a logic.

Top of the page (header)

Purpose: Orientation + navigation + immediate utility.

Logo links home.
Primary navigation shows the main buckets (not every page).
Contact or Book often appears as a persistent button for service businesses.
Phone can be prominent for emergency/trade businesses.

Hero (first screen)

Purpose: Confirm “I’m in the right place” + primary action.

A clear headline stating who it’s for and what you offer.
One primary CTA (the next step you want).
Optional secondary CTA (lower commitment: “View services”, “See pricing guide”).
Proof near the hero only if it’s real and specific (awards, certifications, “20 years”, “500+ installs”), not vague superlatives.

Above the fold vs below

“Everything important must be above the fold” is outdated on mobile. Better rule: the first screen must earn the scroll—a credible promise, a reason to continue, and a visible path forward.

Body sections

Order by importance to decision-making:

Clarify the offer (what you do, for whom).
Differentiation (why you, why now).
Evidence (case studies, testimonials with context, logos if meaningful).
Process (what happens after they contact you—reduces anxiety).
FAQs (objections and specifics).
Final CTA (repeat the next step).

Footer

Purpose: Trust, compliance, recovery navigation. Contact details, hours, legal links, sitemap-like links, associations, and sometimes local signals (service areas).

5. Look vs functionality: the real trade-off

This is often framed wrongly as “pretty vs usable”. The more accurate frame is:

Aesthetic choices must not undermine comprehension, performance, accessibility, or task completion.

When “look” matters a lot

Premium brands where perceived quality is part of the product.
Fashion, hospitality, creative services—where visual language signals taste and standards.

When functionality matters more

Shops (especially mobile checkout).
Catalogues with many SKUs.
Regulated or technical services where clarity reduces risk.

The best outcome

Distinctive visual identity + disciplined UX. Great sites feel branded and obvious: you know where to click, what it costs in time, and what happens next.

6. Is an “ugly” site with traffic and sales better than a gorgeous site with none?

If your definition of success is business outcomes (qualified leads, revenue, margin, retention), then yes—a modest site that ranks, loads fast, and converts is more valuable than a portfolio piece nobody finds.

But be careful with the word “ugly”:

Ugly-but-effective often means plain, familiar, frictionless—not actually repellent. Craigslist-like brutality can work in specific niches; for most New Zealand service and retail brands, extreme ugliness erodes trust and caps price positioning.
Pretty-but-empty usually fails on distribution (SEO, ads, referrals), offer clarity, or proof—not merely because it’s beautiful.

The useful question is not beauty alone; it is whether design choices are paid for with measurable gains or needless friction.

A strong approach:

Make tasks easy (function).
Make trust visible (proof).
Make the brand coherent (look).
Make performance non-negotiable (speed, mobile, accessibility baseline).

7. The design decisions you have to make (a decision stack)

Treat these as an ordered set of choices. Skipping early decisions forces expensive rework later.

Strategy and measurement

Primary goal: leads, sales, support deflection, hiring, authority.
Success metrics: form submissions, call volume, revenue, AOV, booking rate, page speed, rankings for target queries.

Audience and journeys

Who is primary vs secondary?
What are the top three tasks they must complete?

Content and structure

Site type (brochure, business, catalogue, shop, hybrid).
Page list and navigation model.
Content ownership: who writes, who approves, who maintains?

Visual identity

Brand assets, colour, typography, photography style.
Component style: calm corporate vs bold retail.

Interaction and features

Forms, booking, calculators, chat, logins, integrations (CRM, payments, inventory).

SEO and discovery

Local vs national targeting.
Content plan for demand you want to capture.

Compliance and trust

Privacy, terms, returns, accessibility expectations, industry rules.

Operations

Hosting, backups, updates, who fixes things when they break.

8. How NZDH can make these decisions with you (not for you, blindly)

NZDH operates as a full-stack digital partner for many New Zealand businesses: design and development, SEO, performance, hosting, and ongoing support—so the conversation stays grounded in what will actually ship and run in production. That matters because the worst projects separate “design” from “search”, “content”, and “commerce reality” until late in the process.

What collaborative design looks like in practice

Discovery before decoration: clarifying goals, audiences, offers, and constraints (budget, timeline, internal capacity).
Architecture before pixels: deciding pages, navigation, and content types—especially for catalogues and shops where structure is the product.
Prototype the journey: ensuring the critical path (contact, quote request, checkout) is coherent on mobile.
SEO and performance as requirements: not as an afterthought bolted on at launch.
A CMS you can live with: practical editing workflows for day-to-day updates.
Honest trade-offs: when a visual idea conflicts with speed, accessibility, or conversion, you get a clear explanation and alternatives.

Because NZDH combines design, build, SEO, and hosting, many decisions that normally bounce between vendors—templates vs custom, plugin choices, structured data, page speed budgets, hosting location—can be made once, consistently.

9. What you, the customer, should supply (so the project stays fast and authoritative)

You do not need to “speak designer”. You do need to bring business truth and source materials.

Must-haves (almost every project)

Business basics: services/products, service areas, hours, contact channels, legal entity details as needed.
Goals: what “winning” means in the next 3–12 months.
Audience notes: who buys, what they fear, what objections you hear.
Brand assets: logo files, colour guidance, fonts (if any), existing style guides.
Photography: real photos outperform stock when possible; at minimum, plan a shoot or curated selections.
Copy source material: even rough bullet points beat “make something up”—accuracy beats polish in early drafts.
Proof: testimonials (with names/roles where possible), case studies, certifications, memberships, awards.
Domain/DNS access (or a technical contact who can make changes).
Integrations: booking tools, email marketing, CRM, accounting, payment gateways—what must connect.

Strongly recommended for shops and catalogues

Product data model: categories, attributes, variations, SKUs, pricing rules, shipping constraints.
Product content: descriptions, specs, imagery per SKU, manuals, SDS sheets—whatever your buyers need.
Operational policies: shipping, returns, warranties, lead times.

Strongly recommended for SEO-led projects

Keyword priorities (even a rough list of what you want to be found for).
Competitors you respect (not necessarily imitate).
FAQs from real customer conversations.

10. Customer checklist (before you build or rebuild)

Use this as a pre-kickoff worksheet.

Goals

Primary goal is explicit (leads / sales / support / hiring / authority).
Success is measurable (even if simple at first).

Audience

Primary customer profile described in plain language.
Top three visitor tasks listed.

Site type

Chosen: brochure / business / catalogue / shop / hybrid—and why.

Content

Page list drafted (even rough).
Someone owns approvals and ongoing updates.

Trust

Proof collected: testimonials, projects, certifications, guarantees.

Brand

Logo + colours + fonts available.
Photo plan decided (shoot, supplied assets, or curated stock).

Technical

Domain/DNS access confirmed.
Required integrations listed.

SEO & discovery

Target locations (local/national) clarified.
Priority services/products for search identified.

Policies

Privacy, terms, returns/shipping (if selling), disclaimers as required.

Launch reality

Hosting/maintenance approach agreed.
Post-launch improvement plan (measure → iterate).

Closing: authority comes from fit, not flair

The best website for your business is the one where structure matches intent, content answers real questions, trust is visible, and critical tasks are easy—on the devices your customers actually use.

Design is how that truth is communicated. When experts like NZDH work collaboratively with you, the outcome tends to be stronger: fewer surprises, fewer rework loops, and a site that is not only presentable but built to perform in search, speed, and day-to-day operations.

Discuss your project with NZDH