What a website specification is
A specification is the written plan for the website. It answers questions such as: what the site is for, who the customers visiting it are, which pages it needs, what a visitor can do on each page, and how you will know the site is working. It does not decide what the site looks like. That is the job of the design, which comes afterwards.
This guide explains what goes into one, and ends with a complete example for a small business website.
Who writes it? For a small business website, the studio or developer usually writes it after a conversation with the owner, and the owner approves it. On larger projects, with complex systems or several types of user, a separate specialist is sometimes hired. Either way, you bring the business knowledge: what you sell, to whom, and what customers need to know before they get in touch. The professional side turns that into a list of pages and requirements.
Why a specification saves money and arguments
Quotes you can compare
When several suppliers receive the same document, every quote covers the same work. Without a specification, a cheaper quote may simply include less.
Fewer changes halfway through
Changing the document takes a few minutes. The same change after a page has been designed and built means redoing work, and usually paying extra.
Content on time
When it is written down who supplies each text and photo, and by when, the site does not stall waiting for materials.
A clear definition of "done"
Every stage has a sign-off point. Both sides know when the work is finished and what counts as an extra.
Clear ownership
The specification states whose name the domain, hosting and accounts are registered in. That saves trouble on the day you want to change supplier.
What goes into a website specification
| Section | What to write |
|---|---|
| Goals and audience | What the site has to achieve (enquiries, bookings, sales), who the customers are, where they come from and what they need to know before getting in touch. |
| Site structure and pages | A list of every page and how they connect: home page, a page for each service, about, FAQ, contact, accessibility statement and privacy policy. |
| Content for each page | What appears on each page and who supplies it: texts, photos, videos, testimonials. If the supplier writes the copy, how many rounds of revisions are included. |
| Functionality | Forms and where they are sent, appointment booking, online payment, a WhatsApp button, a CRM connection. For each one: exactly what happens when the visitor clicks. |
| Integrations | External systems the site works with: calendar, card payments, invoicing, newsletters, customer management. Who opens the account and who grants access. |
| Languages | Hebrew only, or English and other languages too. Hebrew and English on the same site need a design that works both right to left and left to right. |
| Accessibility | An explicit requirement to build to IS 5568 at level AA and to publish an accessibility statement. The legal background is covered in the guide to the website accessibility law. |
| SEO | Readable URLs in Latin characters, a title and description for every page, and if there is an old site: a list of redirects from every old URL to its new one. |
| Analytics and conversions | Google Analytics 4 and Search Console, and which actions count as an enquiry: a form submission, a tap on the phone number, a tap on WhatsApp. |
| Hosting and domain | Where the site will be hosted, whose name the domain and hosting are in, and who receives admin access at the end of the project. |
| Timeline and approvals | Stages with a sign-off point at each: structure and content, design, full site for review, launch. Who approves on the business side. |
Replacing an old site? Redirects and SEO in the specification
If you already have a site that appears in Google, the specification has to cover the move to the new one. Google Search Central's guidance on site moves recommends redirecting each old URL to its matching new URL with a permanent server-side redirect (301 or 308), straight to the final destination. Do not send lots of old pages to the home page. Keep the redirects for as long as possible, generally at least a year.
In practice this is a table in the specification: a column of old URLs, a column of new URLs, and who checks that every redirect works after launch. Mark the pages that bring the most traffic and enquiries today, so their content makes it to the new site rather than getting lost.
The specification should also say which system the site will be built on. If you have not decided yet, read the guide on how to choose a content management system.
Sample website specification
| Section | Example: a fictional Pilates studio in Holon |
|---|---|
| The business | A reformer Pilates studio in Holon with two instructors, offering group and private sessions. The business is fictional. |
| Goal | Sign-ups for a trial class. Secondary goal: enquiries about private sessions. |
| Audience | Residents of Holon, Bat Yam and Rishon LeZion who arrive from Google searches, Instagram and friends' recommendations. |
| Pages | Home (including an introduction to the instructors), reformer Pilates, private sessions, timetable, FAQ, contact, accessibility statement, privacy policy. Eight pages in total. |
| Content | The web developer writes the texts after a conversation with the owner, with two rounds of revisions. Photos at the studio: the owner's responsibility, by a date set in the quote. |
| Functionality | A trial-class form (name, phone, preferred time) sent to the studio's email. A fixed WhatsApp button on mobile. The timetable is embedded from the booking software the studio already uses. |
| Payment | No online payment at this stage. Class passes are sold at the studio. |
| Languages | Hebrew only. English possibly in a second phase, so the design is planned to allow adding it. |
| Accessibility | IS 5568 at level AA, tested before launch, an accessibility statement page with a contact person. |
| SEO | English URLs, for example /reformer-pilates/. No old site, so no redirects. A title and description for every page. |
| Analytics | GA4 and Search Console. An enquiry is a form submission, a tap on WhatsApp or a tap on the phone number. |
| Hosting and domain | The domain is registered in the owner's name and the hosting is in her account. Admin access is handed over to her at the end of the project. |
| Approvals | Stage 1: site structure and content. Stage 2: design of the home page and one inner page. Stage 3: full site for review. Stage 4: launch. Each stage is approved in writing. |
How to write a specification in five steps
- 01
Start with the goal
Write in one sentence what the site has to deliver: enquiries, bookings or sales. Every other section follows from that.
- 02
List pages and content
A list of pages, and three or four lines for each: what is on it and who supplies the materials.
- 03
Spell out actions and integrations
Forms, bookings, payments, WhatsApp, CRM. For each one: what happens on click, and where the data goes.
- 04
Set stages and owners
Who approves each stage, what counts as "done", and whose name each account is in.
- 05
Send it to suppliers
The same document to every supplier. Questions and suggested changes go into the document itself, not just a phone call.
The specification in a project with us
When we build a business website, the project starts with a specification call: what the business sells, to whom, and what needs to happen on the site. From that call we write a quote listing what is included, a fixed price and a timeline. If you have already written a specification, write to us through the contact page and we will ask you for the document. Starting prices for each type of site are in the price list.