Skip to content
Telegram

ServicesSmall business website developmentWebsite structure

Website structure before design

Website structure before design

We agree on your website structure before design: which pages, which blocks, in what order. That way people quickly find answers and message you.

  • Every project is tailored
  • Agreed before design
  • Content first, then looks

Just write, and I’ll take it from there. I’ll estimate your task at no cost.

5.0 · 37 reviews or message me on Telegram

detailing studio · Kyiv

Showroom shine in one day

Polishing, ceramic coating, interior cleaning. We pick up and drop off your car.

4.9 · 312 reviews on Google

Services

Body polishing6 h
Ceramic coating8 h
Interior cleaning4 h

Our work

Reviews

“Picked it up in the evening. The car looks brand new”Andrii ·

“Sent a request from my phone in a minute”Iryna ·

Telegram · Viber · WhatsApp

Request
Name
Phone

Service

Thank you!Your request is with the studio. We’ll get back to you shortly.

website planning

Website wireframe: the basics before design

Before starting on design, you need to know what people see first, where they learn the price, where they see they can trust you, and where they send a request. That plan of pages and blocks is what website planning produces, and the whole site rests on it.

Usually this plan is drawn as gray boxes labeled “text goes here.” It’s hard to judge: you can’t tell how a client will read it. So instead of boxes, we agree on content: which blocks there are and what each one says. I write the copy from what you tell me.

I show the design as a live page in the browser: you scroll it on your own phone, just like a client will. Blocks are easy to move around while we’re still working on the plan. In a finished design, it’s much harder.

Gordey Fisun · updated

examples

Landing page and multi-page website structure

A landing page wireframe leads people to one action. A small business website gives each service its own page, so people land right where they need to be.

Landing page: one service, one action

  • First screen: what you do, who it’s for, request button
  • What the service includes
  • How the work goes, in a few simple steps
  • Your work or before-and-after results
  • Client reviews
  • Price or what it depends on
  • FAQ
  • Request form and messengers

Small business website: several services

  • A home page with a short overview and a path to the right service
  • A separate page for each service, with its own request button
  • Work that shows your level
  • A page about who’s behind the business
  • Reviews
  • Contacts: phone, messengers, address

common mistakes

Mistakes that make people leave without a request

I start every website structure review with these, whether it’s a new project or a rebuild of an old site.

The first screen explains nothing

Up top, a nice photo and a vague slogan. People can’t tell what you do or who it’s for, so they close the tab.

The request button is only at the very bottom

To message you, people have to scroll the whole site. The button belongs on the first screen and after every key block.

Trust comes too late

Reviews and past work come after the form, or aren’t there at all. People are asked for their contact before they believe you.

Not a word about price

No figure, and nothing on what it depends on. People feel awkward asking and go where at least something is written.

All services in one list

When different services are piled onto one page, people get lost. A big service is better off with its own page.

The copy is written after design

Then words get squeezed into empty boxes: the text doesn’t fit or sounds like filler. Content first, then looks.

in your hands

Website structure: what you get

A plan of pages and blocks

Which pages you need and what goes on each, in what order: first screen, services, work, reviews, price, questions, request. All agreed with you before design.

Real copy instead of “text goes here”

Instead of empty boxes, you approve the headings and copy for every block. You see right away whether a client will understand it all and whether anything is unnecessary.

Every block answers a question

What it is, who it’s for, what it costs, why trust you, how to book. If one answer is missing, people leave without a request.

Changes while they’re easy

Moving a block in the plan is easy, but in a finished design it’s a rebuild. So we settle the order at the start.

how we plan

From a conversation to an agreed plan

Tell me about your business the way you’d tell a friend, and I’ll turn it into the plan and the copy.

  1. You tell me about your business

    Who your clients are, what they ask most, what makes them hesitate. A voice message works.

  2. I draft the page plan

    We decide if one page is enough or you need several. I put the blocks in the order people make a decision.

  3. We agree on the content

    You read the plan and the block copy and tell me what to move, add or remove. While it’s just words, anything can change.

  4. Design as a live page

    I show the site in the browser, not a picture. The structure is already agreed, so you judge the looks.

5.0 · 37 reviews

All guarantees and reviews

Your doubts

Questions about structure and wireframes

What is a website structure, and why agree on it before design?

Structure is the list of pages and the order of blocks on each: what people see first, where the price, reviews and request button are. If you agree on it before design, you won’t have to rebuild finished pages when something turns out to be missing.

Why prototype a website if you can go straight to design?

Website prototyping is a page plan without colors or fonts: what goes where. It makes it easier to talk about content: whether everything is clear, whether anything is unnecessary, and whether it’s easy to find where to send a request.

Will you show me the site as a picture before building it?

No. First we agree on the structure and the block copy, and I show the design straight away as a live page in the browser, not a picture. You open it on your own phone, and we make changes right there.

How do I know how many pages my website needs?

If you have one service and need one action, like a booking or a request, a landing page is enough. If you have several services and clients look for them separately, it’s better to give each its own page so people land right where they need to be.

What should I prepare before we talk about structure?

Just tell me what you sell, who your clients are and what they ask most. Photos of your work, reviews or sites you like will help too, and I’ll put together the plan and the copy myself.

Can the structure change once design has started?

Yes, but late changes take more time, so we agree on the main things at the start. If the task changes, we talk it over first, and only then do I do the work.

I already have a website. Where do I start the redesign?

With the structure: what to keep from the old site, what to move and what’s missing for people to get to a request. Send me the link and briefly describe what’s wrong. I’ll ask a few questions.

Message me. I’ll handle it.

I’ll reply shortly.

5.0 · 37 reviews

More on this topic