Most articles about user research methods for website design are written for teams with a dedicated researcher, a recruitment budget and three months to spare. That is not how a 6-person company works. If you run a small business, your research budget is usually whatever is left after hosting, ads and the designer’s invoice.

The good news: the methods that produce the biggest design decisions are also the cheapest ones. You do not need a lab, an incentive budget of thousands, or a statistically significant sample. You need five users, a support inbox, and a willingness to watch people struggle with the thing you built.

Below are seven research methods a small business can genuinely run, often inside a single working week. For each one you get: how long it takes, what you need, what it costs, and most importantly which design decision it should inform. That last part is where most research dies. Data that does not change a design is just expensive reassurance.

Quick comparison: the 7 methods at a glance

Method	Time	Typical cost	Best for deciding
1. Five-user usability test	1 to 2 days	0 to 250 EUR	Page layout, labels, form and checkout friction
2. Support ticket mining	3 to 4 hours	Free	FAQ content, product page copy, self-service flows
3. Exit survey (micro-survey)	1 hour setup, 2 weeks collecting	0 to 30 EUR/month	Missing information, objections, pricing clarity
4. Open card sorting	Half a day setup, 1 week collecting	0 to 100 EUR	Navigation structure and menu grouping
5. Tree test / first-click test	2 to 3 hours	0 to 100 EUR	Menu labels, validating a new IA before build
6. Analytics and session replay review	3 hours per month	Free tier usually enough	Where to focus, which page to fix first
7. Customer interviews (5 to 7)	1 week	0 to 350 EUR	Messaging, page order, what belongs above the fold

First, a rule that saves you money

Before you choose a method, decide what the research is allowed to change. Write one sentence:

“After this study, we will decide whether to ______.”

If you cannot complete that sentence, do not run the study. This single habit is the difference between research that produces a redesign and research that produces a 40-slide deck nobody opens.

Research methods split into two broad families, and you need both over time:

• Attitudinal (what people say): interviews, surveys, card sorting
• Behavioural (what people do): usability tests, analytics, session replays, tree tests

Small businesses tend to over-invest in the first family because it is easier to run. Behaviour is where the money is.

1. The five-user usability test

The single highest-return research method for website design. You give five people a realistic task, watch them attempt it on your site, and keep your mouth shut. The classic Nielsen Norman finding still holds: five participants surface roughly 80% of the usability problems in a given flow. Testing fifteen people mostly means watching the same three problems happen ten more times.

How long it takes

One to two days total. Thirty minutes per session, five sessions, plus two hours to write the script and two hours to synthesise.

What you need

• Five participants who resemble your actual buyers (customers, prospects, people from a local business group, or a recruitment panel)
• A video call tool with screen sharing and recording
• A script with 3 to 5 tasks, written as scenarios, not instructions
• A note-taking template or a second person taking notes

How to run it

1. Pick one flow, not the whole site. Example: “Find a service that fits my problem and request a quote.”
2. Write tasks as situations: “You manage a small warehouse and need to know if this product works with your existing system. Find out.” Never say “click the Compatibility tab”.
3. Ask participants to think aloud. Remind them every time they go quiet.
4. When they ask you a question, answer with another question: “What would you expect to happen?”
5. Record everything. Note the exact moment of hesitation, not just the failure.

What design decision it informs

Concrete, page-level changes: button labels, form field order, which content block goes above the fold, whether your pricing table is readable, whether the checkout needs an account step. If three of five people hesitate at the same point, that is not an opinion, that is a defect.

Common mistake

Testing your own site with your own team. Internal testers know where everything is. Their results are worthless. Also avoid testing with friends who want to be nice. Brief people explicitly: “We are testing the site, not you. Confusion is useful data.”

2. Customer support ticket mining

You already paid for this research. It is sitting in your inbox, your live chat transcripts and your WhatsApp Business history. Support tickets are a record of every point where your website failed to answer a question on its own.

How long it takes

Three to four hours for a first pass over 90 days of tickets.

What you need

• Export of the last 3 to 6 months of support conversations
• A spreadsheet with four columns: question asked, where the answer lives today, how many times it came up, and the page that should have answered it

How to run it

1. Pull every pre-sale question. Ignore post-purchase account issues for this exercise.
2. Tag each one with a theme: delivery, compatibility, pricing, returns, sizing, timelines, legal.
3. Count the themes. Sort descending.
4. For your top five themes, open the page where that question should have been answered. Usually the answer is absent, buried in a PDF, or written in your internal vocabulary rather than the customer’s.
5. Steal the customer’s exact wording. If 20 people wrote “how long until it arrives”, your heading should not say “Logistics information”.

What design decision it informs

Content hierarchy and page copy. The top three recurring questions almost always belong on the product or service page itself, above the fold or in the first content block, not in a separate FAQ page. This method also tells you which fields to add to product data and whether you need a comparison table.

3. Exit surveys and micro-surveys

An exit survey is one question that fires when someone is about to leave a key page without converting. It is the cheapest way to learn why people who were interested enough to arrive were not interested enough to act.

How long it takes

One hour to set up. Leave it running for two weeks or until you have 100 responses.

What you need

• A survey widget (most have a free or low-cost tier) or a simple custom modal
• One question, maximum two
• Exit-intent or scroll-depth trigger on pricing, product, or checkout pages

Questions that actually work

• On a pricing page: “What is stopping you from getting started today?”
• On a product page: “What information were you looking for that you could not find?”
• After purchase: “What nearly stopped you from buying?” (this one is gold)
• On a blog post: “Did this answer your question? If not, what were you looking for?”

Use open text fields. Multiple choice only confirms what you already assumed.

What design decision it informs

What is missing. Exit surveys rarely tell you to move a button, they tell you that your shipping costs are invisible until checkout, that people cannot tell which plan fits them, or that there is no proof you are a real company. Those are content and trust decisions: testimonials placement, guarantee badges, a cost calculator, a comparison module.

Warning

Do not trigger an exit survey on every page for every visitor. One page, one question, one trigger. Then turn it off. ixdf.org makes the same point with more data.

4. Open card sorting for navigation

If your menu was designed around your org chart or your internal product names, card sorting will show you exactly how wrong it is. Participants group your content the way it makes sense to them, and you discover that the category you call “Solutions” means nothing to anyone outside the building.

How long it takes

Half a day to prepare, one week to collect responses from 15 to 20 people, two hours to analyse.

What you need

• 30 to 50 cards, each one a page or content topic, written in plain language
• An online card sort tool, or physical index cards if you are doing it in person
• 15 to 20 participants (more than usability testing, because you are looking for patterns in grouping)

Open vs closed

Type	What participants do	Use it when
Open	Create their own groups and name them	You are building a new navigation from scratch
Closed	Sort cards into categories you provide	You want to validate categories you already chose
Hybrid	Use your categories or create new ones	You have a draft structure but suspect gaps

What design decision it informs

Your top-level menu, your sub-menu grouping, and your category names. Pay special attention to the labels participants invent. Those are the words your customers use, and they belong in your navigation and in your page titles, which has the convenient side effect of improving search visibility.

5. Tree testing and first-click testing

Card sorting tells you how to build the structure. Tree testing tells you whether the structure works, before you spend money building it. You show participants a text-only version of your menu and ask them to find something. No visuals, no search bar, no rescue.

How long it takes

Two to three hours including setup, collection and analysis. Participants complete it in under five minutes.

What you need

• Your proposed site structure written as a nested text outline
• 5 to 8 realistic find-it tasks
• 20 to 30 participants (it is quick and asynchronous, so volume is cheap)
• A tree testing tool, or a simple multiple-step form if you are improvising

What to measure

• Success rate: did they land on the right page? Target above 80%
• Directness: did they go straight there, or wander back and forth? Backtracking signals an ambiguous label
• First click: research consistently shows that users who get the first click right succeed far more often than those who do not

What design decision it informs

Whether to ship the new navigation or rename three categories first. It is the cheapest possible insurance against a redesign that tanks your conversions. Run it before the designer starts, not after.

6. Analytics and session replay review

Analytics will never tell you why. It tells you where to look, which is exactly what a small team needs when it can only afford to fix one thing this quarter.

How long it takes

Three hours per month, booked as a recurring calendar slot. The recurrence matters more than the depth.

What you need

• A working analytics setup with conversion events defined (not just page views)
• A session replay tool on a free tier
• A heatmap on your three most important pages

What to look at, in order

1. Landing pages with high traffic and low engagement. These are your biggest quick wins.
2. Drop-off between steps in any multi-step flow: form, booking, checkout.
3. Internal search queries. The most under-used research source on any website. People are literally typing what they cannot find.
4. Mobile vs desktop split for your top conversion pages. If mobile is 70% of traffic and 20% of conversions, you have a mobile layout problem, not a copy problem.
5. Ten session replays of users who reached the key page and did not convert. Watch them at normal speed.

What design decision it informs

Prioritisation. Analytics answers “which page do we fix first”, then you run a five-user test on that page to answer “what exactly is broken”. The two methods are a pair. Using either one alone is how teams end up redesigning pages nobody visits.

7. Short customer interviews

Five to seven conversations of 20 to 30 minutes with recent customers and recent lost deals. Not a focus group. One person at a time, because groups produce consensus, and consensus is the enemy of insight.

How long it takes

One week, including scheduling. Budget 90 minutes of your own time per interview including notes.

What you need

• A list of customers who bought in the last 60 days (memory fades fast)
• A discussion guide with 6 to 8 open questions
• Recording permission and a transcription tool
• A small thank-you: a voucher, a discount, or a donation in their name

Questions worth asking

• “Walk me through what happened the day you decided to look for this.”
• “What did you try before you found us?”
• “What other options did you look at, and how did you compare them?”
• “What almost made you choose someone else?”
• “What did you need to know before you felt comfortable paying?”

Avoid “would you like a feature that…”. People are generous and inaccurate about hypothetical futures. Keep every question anchored in something that already happened. growthdrivendesign.com makes the same point with more data.

What design decision it informs

Messaging hierarchy and page order. Interviews tell you what has to be resolved first, second and third on a page, and in which words. They are also where you discover that your main competitor is not another company but a spreadsheet, a manual process, or doing nothing at all. That changes your entire homepage.

A realistic 90-day research plan

You do not run all seven at once. Here is a sequence that works for a small team with limited time, and it carries you through a full redesign cycle.

Weeks	Methods	Output
1 to 2	Support ticket mining + analytics review	A ranked list of problem pages and unanswered questions
3 to 4	Five-user usability test on the worst flow	A defect list with severity ratings
4 to 6	Customer interviews + exit survey running in parallel	Messaging priorities and objection list
7 to 8	Card sorting	Draft navigation structure
9	Tree test the draft structure	Validated or corrected navigation
10 to 12	Design and build, then re-test with five users	Confirmation before launch

Turning findings into actual design decisions

Research only pays off if every finding is attached to a decision and an owner. Use a table like this and keep it in whatever tool your team already opens daily.

Finding	Source	Severity	Decision
4 of 5 users could not find delivery times	Usability test	High	Add delivery estimate block under the price
31% of exit survey replies mention unclear pricing	Exit survey	High	Publish starting prices on the service pages
Nobody grouped cards under “Solutions”	Card sort	Medium	Rename top-level item to “What we do”

Severity, in plain terms

• High: blocks a purchase or a contact request. Fix this sprint.
• Medium: causes hesitation or extra clicks. Fix this quarter.
• Low: cosmetic or preference-based. Fix when you are already in that file.

Five mistakes that waste a small research budget

1. Asking people what they want. Observe what they do. The gap between the two is enormous.
2. Recruiting the wrong participants. Five people from your target market beat fifty random panel respondents who will never buy from you.
3. Running one big study instead of six small ones. Continuous small studies compound. A single annual study goes stale in three months.
4. Testing after launch. Tree tests and prototype tests cost a fraction of post-launch repairs.
5. Never closing the loop. If you change something because of research, tell the team which finding caused it. That is how research becomes a habit instead of a project.

Frequently asked questions

How many users do I need for a usability test?

Five per user group for qualitative testing. If you have two genuinely distinct audiences, for example buyers and administrators, run five of each. For quantitative studies such as tree tests or card sorts, aim for 15 to 30 participants because you are looking for statistical patterns rather than individual struggles.

What are the main types of user research methods?

They are usually split along two axes. Qualitative vs quantitative (why something happens vs how often it happens) and attitudinal vs behavioural (what people say vs what people do). Interviews and surveys are attitudinal. Usability tests, analytics, tree tests and session replays are behavioural. A healthy research mix pulls from all four quadrants over the course of a year.

Can I do user research without a budget?

Yes. Support ticket mining, internal search query review, analytics review and session replays cost nothing but your time. Even usability testing can be free if you recruit from your existing customer list and offer a small discount instead of a cash incentive. The real constraint is calendar time, not money.

How often should a small business run user research?

Something small every month beats something large once a year. A sensible rhythm: a three-hour analytics review monthly, one five-user test per quarter, a support ticket audit twice a year, and an exit survey running continuously on your most important conversion page.

Should I use AI tools for user research?

Use them for the grunt work: transcription, tagging open-text survey responses by theme, clustering support tickets, summarising interview transcripts. Do not use synthetic or simulated participants as a substitute for watching a real person fail to find your contact form. The value of usability testing lives in the hesitation, the sigh and the wrong click, and none of that can be generated.

What is the difference between user research and A/B testing?

A/B testing tells you which of two options performs better. User research tells you what the options should be in the first place, and why the losing one failed. Most small businesses do not have enough traffic for statistically valid A/B tests, which makes qualitative research methods far more practical and far more informative.

Where to start this week

Pick one. Open your support inbox, export the last 90 days of pre-sale questions, and tally the themes. It takes an afternoon, costs nothing, and will almost certainly hand you three page changes worth more than your next round of ad spend.

Then book five usability sessions for next week. The combination of those two methods, run honestly, gives a small business more useful direction than most expensive discovery phases ever deliver.

Most small business websites do not fail because they look ugly. They fail because of a handful of repeatable, fixable errors that quietly send visitors back to Google. After running hundreds of client audits, we keep finding the same patterns: a phone number buried three clicks deep, a hero slider nobody waits for, body text set at 11px on mobile, a services page with zero pricing context.

This guide walks through the 12 most common web design mistakes we see, what each one actually costs you in leads, and the specific fix to apply. Treat it as a diagnostic checklist: open your own site in a second tab and score yourself as you read.

Quick diagnostic: score your site in 10 minutes

Before the detail, run this fast triage. Open your homepage on a phone (not a desktop browser resized to look like a phone) and answer honestly.

Check	Pass condition	Your score
The 3 second test	A stranger can say what you sell and to whom within 3 seconds	Pass / Fail
Contact visibility	Phone or enquiry button visible without scrolling	Pass / Fail
Mobile readability	Body text readable at arm’s length, no pinch zoom	Pass / Fail
Load speed	Main content visible in under 2.5 seconds on 4G	Pass / Fail
Price context	A visitor can estimate whether they can afford you	Pass / Fail
Trust signals	Real reviews, real photos, real address above the fold or close to it	Pass / Fail

Three or more fails means you are almost certainly losing qualified enquiries every week. Here is the full list.

1. Hiding your contact details

This is the single most frequent issue in our audits, and the most expensive. Businesses put the phone number only on a “Contact” page, render it as an image so it cannot be tapped, or hide it behind a generic form with eight required fields.

Why it costs you leads

Ready-to-buy visitors are the impatient ones. A plumber, an accountant, a B2B service firm: when someone is ready, they want to call now. Each extra click between intent and contact drops conversion. Forms also filter out older demographics and anyone on a commute.

The fix

• Put a clickable phone number in the header on every page, using <a href="tel:...">.
• Add a sticky bottom bar on mobile with two actions: Call and Message or Book.
• Repeat full contact details in the footer, including a physical address and opening hours.
• Cut forms to the minimum: name, contact method, and one free text field. Add fields only when sales genuinely needs them.

2. Auto-playing hero sliders and carousels

The rotating hero banner refuses to die. We still find sites where four messages fight for the same 600 pixels, each one visible for five seconds before sliding away.

Why it costs you leads

Carousels dilute the message. Visitors read slide one, start processing it, and the layout moves. Interaction rates on slides two, three and four are typically negligible. Sliders also hurt Largest Contentful Paint and cause layout shift, both of which affect Google Core Web Vitals and therefore rankings.

The fix

Replace the slider with one static hero: one headline stating what you do and for whom, one supporting line, one primary button, one secondary link. If you have four messages, you have four landing pages, not four slides.

3. Unreadable text on mobile

Text sized for a 27 inch monitor, light grey on white, lines running edge to edge with no margin, paragraphs of nine lines. More than half of your traffic is reading that on a phone in daylight.

Why it costs you leads

If reading feels like work, people skim, miss your value proposition, and bounce. Low contrast is also an accessibility failure and an increasing legal risk in both the EU and North America.

The fix

Element	Recommended value
Body text size (mobile)	16px minimum, 17 to 18px preferred
Line height	1.5 to 1.7
Line length	50 to 75 characters on desktop
Contrast ratio	4.5:1 minimum for body copy
Paragraph length	2 to 4 lines on mobile
Tap target size	44 x 44px minimum

4. No pricing context anywhere on the site

“We prefer to discuss budget on a call.” We hear it in every discovery session. Meanwhile the visitor leaves and checks three competitors who are willing to give a number.

Why it costs you leads

Price silence does not create curiosity, it creates suspicion. It also floods your inbox with unqualified enquiries from people who were never in your bracket, which wastes sales time. Hidden pricing is one of the most common web design mistakes in professional services precisely because it feels safe.

The fix

• Publish a starting from figure: “Projects typically start at 4,500 EUR.”
• Or publish ranges per package with what is included and excluded.
• Or publish a worked example: “A 12 page site for a local clinic, delivered in 6 weeks, came to X.”
• Add the variables that move the price so the number feels honest rather than arbitrary.

5. Confusing navigation

Menus with 11 top level items. Clever labels like “Solutions”, “Our Universe” or “The Approach”. Dropdowns that disappear when the cursor slips. Important pages reachable only from the footer. forumweb.hosting published something useful on the subject.

Why it costs you leads

Navigation is how people judge whether a site is worth their time. If they cannot build a mental map in a few seconds, they leave. Deep or orphaned pages also get crawled and indexed less effectively.

The fix

1. Limit the main menu to 5 to 7 items.
2. Use plain labels: Services, Pricing, Work, About, Contact.
3. Keep every important page within two clicks of the homepage.
4. Give the primary action a button style distinct from text links.
5. On mobile, make sure the menu icon is labelled “Menu” and opens instantly.

6. Weak or duplicated calls to action

Common patterns we flag: the only CTA says “Submit”, five different CTAs compete on one page, or the page simply ends with no next step at all.

Why it costs you leads

Interested visitors will not invent a next step for you. And when every element shouts equally, nothing is primary, so decision making stalls. com.sg published something useful on the subject.

The fix

• One primary CTA per page, repeated at the top, middle and end.
• Write the outcome, not the mechanic: “Get my free site audit” beats “Submit”.
• Add a risk reducer next to it: “No obligation. Reply within one business day.”
• Offer one low-commitment secondary option, such as a downloadable checklist or a pricing page link.

7. Slow loading pages

The usual culprits: uncompressed 4MB photos straight from a camera, five tracking scripts, three font families with nine weights, a page builder loading CSS for blocks that are not used.

Why it costs you leads

Mobile users on patchy connections abandon fast. Speed also feeds directly into Core Web Vitals, which influences rankings, and slow sites are perceived as less trustworthy even when the content is identical.

The fix

• Serve images in WebP or AVIF, resized to their display dimensions, with width and height attributes set.
• Lazy load everything below the fold, but never the hero image.
• Cut to one or two font weights, self-hosted.
• Audit plugins and third party scripts quarterly and remove what is not earning its keep.
• Test with PageSpeed Insights on the Mobile tab, using field data where available.

8. Stock photos and generic copy

The handshake in a glass lobby. The diverse team laughing at a laptop. Copy that says “We deliver innovative solutions tailored to your needs” and could belong to any company in any industry.

Why it costs you leads

Visitors scan for evidence that you are real and specifically relevant to them. Generic signals suggest a business that is either tiny and hiding it, or impersonal. Either way, trust drops.

The fix

• Commission one short photo session: your team, your premises, your work in progress.
• Name the customer type in the first headline: “Websites for independent clinics in Brussels.”
• Replace adjectives with specifics: numbers, timeframes, named deliverables.

9. Missing or fake-looking trust signals

No reviews, or reviews attributed to “Sarah M., Client” with a stock headshot. No company registration details. Certification logos that link nowhere.

Why it costs you leads

Unverifiable social proof is worse than none. It actively signals that something is being hidden.

The fix

• Use full names, company names, roles and, where possible, links to the client site.
• Embed live Google review ratings rather than retyping them.
• Publish two or three case studies with a problem, an action and a measurable result.
• Show legal identity in the footer: registered name, company number, VAT number, address.

10. Dead end 404s and broken internal links

Sites that have been redesigned once or twice almost always carry broken links, old URLs with no redirects, and a default 404 page with no navigation.

Why it costs you leads

Every broken link is a visitor stopped mid journey, plus wasted crawl budget and lost link equity.

The fix

• Crawl the site with a tool such as Screaming Frog or Ahrefs Site Audit each quarter.
• 301 redirect every retired URL to the closest relevant page, not blindly to the homepage.
• Design a useful 404: search box, top five pages, contact button.

11. Intrusive popups and interstitials

A newsletter popup at two seconds. A cookie wall covering half the screen with no visible decline option. A chat widget that opens itself and hides the content.

Why it costs you leads

Intrusive interstitials on mobile are explicitly penalised by Google, and they frustrate the exact people who were about to read your offer. Non-compliant consent banners also carry regulatory risk in the EU.

The fix

• Trigger popups on exit intent or after meaningful scroll depth, never on arrival.
• Make the close button large and obvious.
• Give “Accept” and “Reject” equal visual weight in the cookie banner.
• Keep chat widgets collapsed by default on mobile.

12. No clear information hierarchy or whitespace

Everything the same size. Sections jammed together with 10px of padding. Six colours competing. Three headline styles on one page.

Why it costs you leads

People do not read pages, they scan them in an F or Z pattern. Without hierarchy there is nothing to scan, so the brain treats the page as noise and disengages.

The fix

• Define a type scale and stick to it: H1, H2, H3, body, small.
• Use a spacing system (8, 16, 24, 40, 64, 96px) rather than arbitrary values.
• Give each section 60 to 100px of vertical breathing room on desktop.
• One accent colour reserved exclusively for actions.
• Break long content into blocks with subheadings, bullets and summary boxes.

Priority order: what to fix first

You will not fix all 12 this week. Fix them in order of revenue impact.

Priority	Mistake	Effort	Typical impact
1	Hidden contact details	Low	High
2	Weak calls to action	Low	High
3	Mobile readability	Low	High
4	Auto-playing slider	Low	Medium to high
5	No pricing context	Medium	High
6	Page speed	Medium	High
7	Confusing navigation	Medium	Medium
8	Trust signals	Medium	Medium
9	Popups and interstitials	Low	Medium
10	Broken links and 404s	Low	Medium
11	Stock photos and generic copy	High	Medium
12	Hierarchy and whitespace	High	Medium

How to validate your fixes

Design opinions are cheap. Evidence is not. After each change, check these:

• Google Analytics 4: engagement rate and key event completions by landing page, compared month on month.
• Search Console: impressions versus clicks, to spot pages ranking but not earning the click.
• Heatmaps and session recordings: watch 10 mobile sessions. You will learn more in 20 minutes than from any checklist.
• Five second tests: show the homepage to someone outside the business for five seconds, then ask what the company does.
• Call tracking: if phone is your main channel, measure it. Otherwise you are optimising blind.

FAQ

What are the top 10 web design mistakes?

The ten that cost the most leads are: hidden contact details, auto-playing sliders, unreadable mobile text, missing pricing context, confusing navigation, weak calls to action, slow load times, generic stock imagery, missing trust signals, and intrusive popups. Nielsen Norman Group’s classic list focuses on usability fundamentals such as bad search and non-scannable text, and those still apply, but on small business sites the contact, pricing and mobile issues are usually the bigger revenue leak.

What are the 7 C’s of website design?

They are context, content, community, customisation, communication, connection and commerce. The framework is a useful audit lens: for each C, ask whether your site actively delivers it or merely assumes it.

What is the 3 second rule in website design?

It is the working assumption that a visitor decides within roughly three seconds whether a page is relevant to them. In practice that means your headline, supporting line and primary action must communicate what you do, who it is for, and what to do next, without scrolling.

What are the most common problems in website design?

In our audits the recurring problems cluster into four groups: clarity (visitors cannot tell what you sell), friction (contact and conversion paths are too long), performance (slow pages, especially on mobile) and trust (no verifiable proof that you are a real, capable business). Almost every mistake in this article belongs to one of those four.

How often should a small business redesign its website?

A full redesign every four to five years is typical, but continuous iteration beats big-bang rebuilds. Review content quarterly, review performance and broken links quarterly, and reassess the overall structure annually. If your site still relies on a carousel hero and a desktop-first layout heading into 2027, it is already overdue.

Does fixing design mistakes improve SEO as well as conversions?

Yes, and the two overlap more than people expect. Page speed, mobile usability, intrusive interstitials, broken links and clear internal navigation are all signals Google evaluates. Improving them generally lifts both rankings and conversion rate at the same time.

Next step

Work down the priority table above and fix the top three this week. They are low effort and high impact, and you will usually see the difference in enquiry volume within a month. tilda.education has covered this at length.

If you would rather have someone else diagnose it, we run structured website audits covering every point in this article and deliver a prioritised action list you can hand to any developer. Get in touch and tell us your URL.

“How long will my new website take?” is the first question almost every client asks, and the honest answer is: most professional website design projects take 8 to 12 weeks from kickoff to launch. Not 3 days. Not 6 months. Somewhere in that window, assuming the project stays on track.

The problem is that “8 to 12 weeks” tells you nothing about what actually happens inside those weeks, when you will be asked to review something, or why some projects quietly slide into month five. So instead of another vague phase list, here is a genuine website design project timeline broken down week by week, including what we do, what we need from you, and where projects usually stall.

Quick Answer: The Website Design Project Timeline at a Glance

Phase	Typical Duration	Main Deliverable	Client Time Needed
Discovery & strategy	Week 1	Brief, goals, sitemap draft	2 to 4 hours
Information architecture & wireframes	Weeks 2 to 3	Sitemap, page layouts	2 to 3 hours
Visual design	Weeks 3 to 6	Homepage then inner pages	3 to 5 hours
Development	Weeks 6 to 9	Working staging site	1 to 2 hours
Content population	Weeks 8 to 10	Real copy and images in place	Varies, often the biggest ask
Testing & QA	Weeks 10 to 11	Bug list cleared, UAT sign-off	3 to 4 hours
Launch & handover	Week 12	Live site, training, docs	1 to 2 hours

Important: these phases overlap. Development often begins before the last inner page design is approved, and content work runs in parallel from week 2 onward. A timeline is not a relay race.

Week 0: The Week Most Timelines Forget

Before week 1 even begins, a few things have to be in place. We call it week 0 because it is real time on the calendar but rarely appears on a project plan:

• Proposal accepted and contract signed
• Deposit invoice paid
• Kickoff call booked with every decision maker confirmed as attending
• Access gathered: current hosting, domain registrar, CMS logins, analytics, brand assets

If your legal team needs two weeks to review the contract, your 10-week project is now a 12-week project. Factor it in.

Weeks 1 to 2: Discovery, Strategy and Structure

Week 1: Discovery

The kickoff call is usually 60 to 90 minutes. We are trying to understand things that no brief ever captures properly:

• What does a successful website look like in numbers, not adjectives (leads per month, demo bookings, reduced support emails)?
• Who actually buys from you, and what stops them?
• Which pages on the current site earn their place, and which are dead weight?
• Who signs off, and who has a veto?

Alongside the call we review analytics, audit the existing site, look at 3 to 5 competitors, and check keyword data so the structure is built for search from day one.

What we need from you in week 1: analytics access, a list of stakeholders, brand guidelines, and three sites you admire with a sentence explaining why for each.

Week 2: Sitemap and Content Plan

We deliver a sitemap showing every page, how they nest, and what each one is supposed to do. This is the single most under-rated document in any website design project timeline, because changing a sitemap in week 2 costs an hour. Changing it in week 9 costs a week. This is handled with some care by one outfit doing this properly.

We also issue the content plan: which pages need new copy, who is writing it, and the deadline. Content deadlines sit in week 5 or 6, not week 11.

Your job: approve the sitemap within 3 working days and confirm who owns copywriting.

Weeks 3 to 6: Wireframes and Visual Design

Week 3: Wireframes

Wireframes are grey-box layouts for key templates: homepage, service or product page, blog article, contact, and any unusual template. No colour, no photography, no fonts. That is intentional. We want feedback on hierarchy and messaging order before anyone argues about a shade of blue.

Expect one round of revisions here. Two is normal on larger sites.

Week 4: Homepage Design Concept

The first full visual design lands. This is the emotional high point and the biggest risk point of the whole project. We present it live rather than emailing a PDF, because unexplained design gets picked apart by whoever has the strongest opinion in the room.

Good feedback sounds like: “the offer is not clear enough above the fold.” Unhelpful feedback sounds like: “my wife does not like it.”

How to give feedback that does not cost you a week

1. Collect all internal opinions before sending anything to us
2. Send one consolidated list, not six separate emails
3. Reference the business goal, not personal taste
4. Mark each item as must-change, nice-to-have, or question

Weeks 5 to 6: Inner Pages and Design Sign-Off

Once the homepage direction is approved, the visual language rolls out across remaining templates, plus mobile layouts, form states, button states, empty states and error messages. At the end of week 6 we ask for a written design sign-off. The team at codevix.com reached a similar conclusion.

Sign-off matters. After this point, design changes are change requests with cost and time attached, because code is being written against approved layouts.

Weeks 6 to 9: Development

This is the quietest stretch for you and the busiest for us. Typical work includes:

• Building templates on a staging server
• Setting up the CMS so your team can edit without breaking layouts
• Responsive behaviour across mobile, tablet and desktop breakpoints
• Forms, integrations, CRM or email platform connections
• Performance work: image handling, caching, script loading
• Accessibility basics: contrast, focus states, alt text structure, keyboard navigation
• SEO foundations: metadata fields, schema, clean URL structure, 301 redirect map

Around week 8 we usually share a staging link so you can see progress. Expect it to look unfinished, because it is. Reviewing a half-built site as if it were finished creates panic that helps nobody.

What we need from you during development: final copy, images, logos, team photos, and any third party account details. This is where most schedules break.

Weeks 8 to 10: Content Population

Real content replaces placeholders. If copy arrives on time, this phase is smooth. If it does not, everything behind it shifts by the same number of days, because we cannot test pages that have no content and we cannot build redirects for pages that do not exist yet.

A rough guide on content volume:

Site Size	Copywriting Time (client-written)	Population Time
5 to 8 pages	2 to 3 weeks	2 to 3 days
15 to 30 pages	4 to 6 weeks	1 week
50+ pages or ecommerce	6 to 10 weeks	2 to 3 weeks

Weeks 10 to 11: Testing, QA and Client Review

Our testing

• Cross-browser checks on current versions of Chrome, Safari, Firefox and Edge
• Real device testing on iOS and Android
• Form submissions, autoresponders and CRM delivery
• Core Web Vitals and page speed scoring
• Broken links, redirect map validation, 404 handling
• Accessibility audit against WCAG 2.2 AA where in scope
• Analytics and conversion tracking verification

Your review (UAT)

You get a fixed window, normally 5 working days, to review everything and submit one consolidated bug and amend list. The critical distinction:

• Bug: something does not work as designed. Fixed free, inside the timeline.
• Change request: something works but you now want it different. Quoted separately or scheduled post-launch.

Being clear about this in advance prevents the single most common launch-week argument.

Week 12: Launch Week

Launch day is deliberately boring when the preparation is right. A typical sequence:

1. Final backup of the existing site
2. DNS changes scheduled for a low-traffic window, ideally Tuesday to Thursday morning
3. Site pushed live, SSL verified, redirects tested in bulk
4. Search Console and sitemap submission, robots.txt checked so nothing stays blocked
5. Analytics and tracking confirmed firing on the live domain
6. Smoke test of every form and key user journey
7. CMS training session recorded for your team, plus handover documentation

Never launch on a Friday. DNS propagation can take up to 48 hours and nobody wants to discover a broken checkout on a Saturday night.

Weeks 13 to 14: Post-Launch Stabilisation

Rankings can wobble for a few weeks after a redesign, especially if URLs changed. We monitor Search Console for crawl errors, watch analytics for anything unexpected, fix small post-launch issues, and review early conversion data.

What Actually Causes Website Project Delays

Delay Cause	Typical Cost	Prevention
Late or missing content	2 to 6 weeks	Start writing in week 1, or buy copywriting
Slow feedback rounds	1 to 3 weeks	Agree a 3-day response rule up front
A late stakeholder appearing at design stage	1 to 4 weeks	Identify all approvers in week 1
Scope creep after design sign-off	1 to 5 weeks	Park ideas in a phase two list
Missing hosting, domain or API access	3 days to 2 weeks	Collect credentials during week 0
Holidays and peak trading periods	1 to 3 weeks	Map absences onto the plan at kickoff

Notice the pattern. Almost none of these are development problems. Roughly 8 out of 10 delayed web projects are delayed on the client side, and content is the usual culprit.

How Project Size Changes the Timeline

Project Type	Realistic Timeline	Main Variable
Single landing page	2 to 3 weeks	Copy and offer clarity
Small business site, 5 to 10 pages	6 to 8 weeks	Feedback speed
Standard business site, 15 to 30 pages	8 to 12 weeks	Content volume
Ecommerce store	12 to 20 weeks	Catalogue, payments, shipping rules
Custom web application or portal	16 to 30+ weeks	Integrations and user roles

Your Client-Side Checklist to Stay on Schedule

• Name one decision maker who consolidates all internal feedback
• Commit to a 3 working day turnaround on every review
• Deliver content by the week 5 or 6 deadline, not launch week
• Book a professional photography session in week 1 if you need new imagery
• Hand over all credentials before design begins
• Keep a running phase two list so good ideas are captured, not crammed in
• Flag holidays, board meetings and busy seasons at kickoff

Frequently Asked Questions

How long does a website design project take on average?

Most professionally built business websites take 8 to 12 weeks from kickoff to launch. Simple brochure sites can finish in 6 weeks, while ecommerce and custom builds regularly run 12 to 20 weeks or more.

What are the main stages of a website design project timeline?

Discovery and strategy, information architecture and wireframes, visual design, development, content population, testing and QA, then launch and handover. A post-launch monitoring period of 2 to 4 weeks should follow. upanup.com walks through the specifics.

Why do web design projects go over schedule?

Late content, slow feedback, new stakeholders appearing mid-project and scope creep after design approval. These four account for the overwhelming majority of overruns, and all four are avoidable with clear deadlines at kickoff.

Can a website be built faster than 8 weeks?

Yes, if content is ready on day one, feedback comes back within 24 hours, the page count is small and the scope is locked. Speed is usually bought with decisiveness rather than money.

How much of my time will the project need?

Budget roughly 15 to 25 hours in total across an 8 to 12 week project, concentrated in discovery, design review, content supply and user acceptance testing. Content creation is extra if your team is writing it.

When should design changes stop?

At design sign-off, normally around week 6. After that, code has been written against approved layouts, so changes become change requests with their own cost and schedule impact.

What happens immediately after launch?

Redirect monitoring, Search Console checks, crawl error fixes, analytics verification and small refinements. Traffic can fluctuate for two to four weeks after a redesign before settling.

Planning Your Next Website Build?

A realistic website design project timeline is not a constraint, it is what protects the quality of the final result. When everyone knows what happens in week 4, what is needed by week 6 and what is locked by week 9, projects launch on time and nobody is surprised.

If you would like a timeline mapped to your specific project scope, get in touch and we will put together a week-by-week plan with clear deliverables and deadlines on both sides. Website Redesign Timeline covers this in more depth.

You have spent years earning your rankings. Now the board wants a new name, a new look, and a new domain, and the only question keeping you awake is simple: will the rebrand destroy the organic traffic that feeds your pipeline?

It can. We have seen companies lose 60% of their organic sessions in a fortnight because a developer pushed a redesign live with no redirect map. We have also managed rebrands where traffic was flat within 3 weeks and up 18% within 90 days. The difference is never luck. It is process.

This is the exact 9-step migration plan we use to rebrand a website without losing traffic, written for business owners rather than engineers. Follow it in order and the rebrand becomes a controlled event instead of a gamble.

First, understand what actually kills traffic during a rebrand

A rebrand does not hurt rankings. Broken continuity hurts rankings. Google needs to understand that the new page is the same page, serving the same intent, with the same authority behind it. Every point of failure below breaks that continuity.

Cause of traffic loss	Typical impact	Preventable?
Missing or bulk redirects to the homepage	Severe (40% to 80% loss)	Yes
Page titles and H1s rewritten for branding, not search	Moderate to severe	Yes
Content trimmed during the redesign	Moderate, often delayed	Yes
Internal links still pointing at old URLs	Low to moderate, compounding	Yes
Staging noindex tag or blocking robots.txt left live	Catastrophic	Yes
Brand name change reducing branded search volume	Real and partly unavoidable	Mitigate, not eliminate

Notice the last row. If you are changing your company name, some loss of branded search is structural. Nobody can search for a name they have not heard yet. That is a marketing problem, not an SEO problem, and step 7 addresses it.

The rebrand timeline at a glance

Phase	When	Steps
Baseline and inventory	6 to 8 weeks before launch	1, 2
Mapping and build	3 to 6 weeks before	3, 4, 5
Pre-launch QA	1 to 2 weeks before	6, 7
Launch	Day 0	8
Monitoring and recovery	Day 1 to Day 90	9

Timing tip: launch on a Tuesday or Wednesday morning, never on a Friday, and never in your peak commercial season. If your business peaks in Q4, the window between late January and early spring 2027 is far safer than November.

Step 1: Benchmark everything before you touch anything

You cannot prove a rebrand was safe if you have no “before” picture. Export and store these, ideally in a dated spreadsheet you can hand to anyone:

• Google Search Console: 16 months of clicks, impressions, average position by page and by query
• Analytics: 12 months of organic sessions, conversions and revenue by landing page
• Rank tracking: your top 100 to 300 commercial keywords with current positions
• Backlinks: full referring domain list plus the top 200 linked pages
• Full crawl: every indexable URL with its title, meta description, H1, word count, canonical and status code

Set a written success threshold now, while everyone is calm. Ours is usually: organic clicks within 10% of baseline by day 30, at or above baseline by day 60, growing by day 90. Agreeing this in advance stops panic-driven decisions in week two.

Freeze the baseline

Take screenshots of the GSC performance graph and your key dashboards. Six weeks later, when someone claims “traffic was much higher before”, you will have evidence rather than memory. Anyone digging further should read How to Redesign a Website Without Losing SEO.

Step 2: Build a complete URL inventory

A crawl alone is not enough. Orphan pages, old landing pages and PDFs still earn links and traffic. Combine four sources into one master list:

1. Your site crawl (Screaming Frog, Sitebulb or similar)
2. XML sitemaps, including any legacy sitemaps
3. Google Search Console pages report and the full query and page export
4. Backlink tools: every URL on your domain that has at least one external link

Deduplicate, then add three columns to each URL: organic clicks (12 months), referring domains, and conversions. Sort by value. In most sites, 10% to 20% of URLs carry 80% of the value, and those are the pages that receive human attention rather than a bulk rule.

Step 3: Create a one-to-one URL map

The URL map is the single most important document of the entire project. Nothing goes live until it is complete and signed off.

Old URL	New URL	Clicks/yr	Ref. domains	Action
/services/seo-audit/	/services/seo-audit/	4,180	22	Keep URL, redesign only
/old-brand-story/	/about/	640	9	301 redirect
/blog/2019-event-recap/	n/a	3	0	Retire, return 410

The golden rule: keep URLs that do not need to change

A rebrand is a visual and naming exercise. It is not a reason to restructure every URL. If /services/seo-audit/ ranks well, it should still be /services/seo-audit/ after launch, even if the logo, colours and company name are completely different. Every URL you change is a small risk you chose to take. Change only what the new brand genuinely requires.

When the brand name sits inside URLs, for example /oldbrand-pricing/, weigh the cosmetic gain against the risk. Often the honest answer is that no customer reads the URL slug, and the safest move is to leave it alone for six months and revisit later.

Handling the “no equivalent page” problem

• Redirect to the closest topical match, not the homepage
• If the page had links and traffic but no successor, rebuild a version of it on the new site
• Only use a 410 for genuinely dead pages with zero traffic and zero links
• Never redirect dozens of deep pages into one catch-all page: Google treats mass irrelevant redirects as soft 404s

Step 4: Protect on-page signals during the redesign

Designers and copywriters rewrite everything during a rebrand. This is where invisible damage happens. Give your team explicit rules:

• Page titles: keep the keyword portion identical. Swap only the brand suffix. “SEO Audit Services | OldBrand” becomes “SEO Audit Services | NewBrand”, not “Discover Our Approach | NewBrand”.
• H1s: keep the primary term. Brand poetry belongs in a subheading or hero strapline.
• Body copy: preserve at least 80% of the word count and all key subheadings on your top 50 pages. Refresh the tone, do not delete the substance.
• Schema markup: port Organization, LocalBusiness, Product, FAQ and Article markup across, with updated name, logo and sameAs profiles.
• Images: keep descriptive alt text and file naming. Image search traffic is easy to lose and rarely missed until it is gone.
• Canonicals and hreflang: regenerate them for the new URLs. Stale canonicals pointing at old addresses are a classic post-launch bug.

A practical trick: run a pre-launch crawl of staging, then diff it against your baseline crawl. Any page whose title, H1 or word count moved by more than 20% gets a manual review before launch.

Step 5: Implement 301 redirects properly

Redirects are the load-bearing wall of a migration. Get these details right:

1. Use 301 (permanent), not 302. A 302 signals a temporary move and slows consolidation.
2. One hop only. Old URL goes straight to the final new URL. Chains of 3 or more hops waste crawl budget and dilute signals. If you have legacy redirects from a previous migration, flatten them so they point directly to the new destination.
3. Handle protocol and host variants. http, https, www and non-www must all resolve in a single hop to the canonical version.
4. Keep trailing slash behaviour consistent. Mixed handling is a silent duplicate-content generator.
5. Preserve query strings where campaign tracking or filters rely on them.
6. Keep redirects live for at least 12 months. Realistically, keep them forever. Some links only get crawled once a year, and a redirect rule costs you nothing.
7. Test before launch. Run your entire old URL list through a bulk status checker against staging. Acceptable result: 100% return a single 301 to a 200 page.

Same domain or new domain?

Scenario	Risk level	Key requirement
New design, same domain, same URLs	Low	Protect titles, content and speed
Same domain, new URL structure	Medium	Complete 1:1 redirect map
New domain, same URL paths	Medium	Change of Address tool, both properties verified
New domain and new structure	High	Everything above, plus phased QA

If you are moving domains, keep ownership of the old domain indefinitely and keep it renewed. Letting it lapse hands your entire backlink profile to whoever buys it next.

Step 6: Rewire every internal link

Redirects catch external links. Internal links should never need them. After launch, crawl the new site and confirm that zero internal links point at a redirecting URL.

Places teams forget to update:

• Body copy links inside older blog posts
• Navigation, mega menus and footer link blocks
• Hard-coded links in page builder modules and reusable blocks
• CTA buttons and banner images
• Canonical tags and hreflang clusters
• XML sitemaps (regenerate, and remove old URLs)
• Email templates, PDFs, brochures, invoices, QR codes on print and packaging
• Help centre articles and support macros

Also update your anchor text where it contained the old brand name, but do so gradually and naturally. Do not mass-rewrite thousands of anchors in one day. It is argued more carefully on jesscreatives.com.

Step 7: Update brand assets and off-site signals

Google builds an entity picture of your business from the whole web, not just your website. If the rest of the internet still calls you by your old name, the rebrand looks inconsistent and trust signals wobble.

Work through this list in the 48 hours around launch:

• Google Business Profile: business name, logo, cover photo, website URL, description. Expect a review period, so file it on launch day.
• Bing Places and Apple Business Connect
• Top 20 citations and directories: chamber listings, industry bodies, review platforms
• Review sites: Trustpilot, G2, Capterra, Glassdoor
• Social profiles: handles, display names, bios, pinned posts and link-in-bio tools
• LinkedIn company page plus a prompt for staff to update their profiles
• Wikidata and Crunchbase entries if you have them
• Organization schema: new name, an alternateName for the old brand during transition, new logo, updated sameAs
• Email: signatures, transactional templates, sending domain authentication (SPF, DKIM, DMARC) for the new domain
• Ads and tracking: final URLs, conversion tags, remarketing audiences, UTM conventions

Recovering branded search volume

People will keep searching your old name for a year or more. Protect that demand:

• Keep a permanent “OldBrand is now NewBrand” page explaining the change, and link to it from the footer
• Bid on your old brand name in paid search for at least 6 months
• Mention the former name in your About page copy and press release so search engines connect the two entities
• Ask your top 20 to 30 referring sites to update the anchor text and brand mention

Step 8: Launch day, in order

Print this and tick it off. The sequence matters.

1. Take a full backup of the live site and database
2. Deploy the new site
3. Remove the staging noindex tag and check the live robots.txt allows crawling (this is the number one catastrophic mistake)
4. Activate the redirect rules
5. Spot-check your 25 highest-value old URLs by hand in a browser
6. Run a bulk status check across the full old URL list
7. Crawl the live site for broken links, 404s, redirect chains and missing titles
8. Submit the new XML sitemap in Search Console
9. Submit the old sitemap too, temporarily, so Google recrawls the old URLs and discovers the redirects faster
10. If you moved domains, verify the new property and use the Change of Address tool
11. Confirm analytics is firing on the new templates and that goals or key events still register
12. Request indexing for your 10 most important pages
13. Check Core Web Vitals on the new templates, mobile first
14. Confirm the SSL certificate covers all hostnames

Keep the old site backed up and restorable for at least 30 days. A rollback plan you never use is cheap insurance.

Step 9: Monitor for 90 days

The rebrand is not finished at launch. It is finished when the data says it is. Here is the cadence we run.

Period	Check	What healthy looks like
Days 1 to 7 (daily)	404 logs, GSC coverage errors, crawl stats, server errors, conversion tracking	Rising crawl activity, 404s trending to near zero
Days 8 to 30 (2 to 3 times a week)	Indexed page count, rankings for top 100 terms, clicks vs baseline	Dip of 5% to 20%, then stabilising
Days 31 to 60 (weekly)	Clicks, impressions, average position, backlink migration, branded queries	Back to within 5% of baseline
Days 61 to 90 (weekly)	Revenue and conversions from organic, page-level winners and losers	At or above baseline, growth resuming

Diagnose losses page by page, not site-wide

Site-wide graphs hide the story. Export GSC clicks by page for the 28 days before launch and the 28 days after, put them side by side, and sort by biggest loss. Nine times out of ten the cause is one of these:

• The page is not redirected, or redirects to the wrong destination
• The title or H1 lost its keyword
• Content was cut during the redesign
• The page lost internal links because it was dropped from the navigation
• The page is blocked, noindexed, or canonicalised to something else

When to worry

• Normal: a 5% to 20% dip in weeks 1 to 4, with steady recovery
• Investigate: no recovery trend at all by day 30
• Emergency: a drop of more than 40% in the first week, or a collapse in indexed pages. Check robots.txt, noindex tags and redirect rules immediately, in that order.

The mistakes we see most often

1. Redirecting everything to the homepage. Fast to implement, and the most reliable way to lose half your traffic.
2. Treating the rebrand as a content cull. If a page ranks, it earned its place. Port it.
3. Launching in peak season. There is never a good reason to gamble your busiest quarter.
4. Letting the design system dictate page titles. Brand voice is fine in the hero, not in the title tag.
5. No single owner. Someone must own the URL map and hold veto power over launch.
6. Skipping the staging crawl. Thirty minutes of QA prevents six weeks of recovery work.
7. Removing redirects after a few months. Keep them. They cost nothing.

A realistic expectation to set with your board

Even a flawless migration typically shows a short dip while Google recrawls, reprocesses and reconsolidates signals. On a small site of a few hundred pages, that settles in 2 to 4 weeks. On a large site of tens of thousands of URLs, allow 8 to 12 weeks. If you are also changing the company name, branded search recovery is a marketing timeline of 6 to 12 months, driven by PR, ads and customer communication rather than technical SEO.

Say this out loud before launch. A predicted dip is a project milestone. An unpredicted dip is a crisis.

Frequently asked questions

Can you really rebrand a website without losing traffic?

Yes, if URLs are mapped one to one, 301 redirects are single-hop, page titles and content are preserved, and internal links are updated. Expect a temporary dip of up to 20% for a few weeks. Permanent loss is almost always the result of a skipped step, not of the rebrand itself.

How do I redesign a website without losing SEO?

A redesign on the same domain is the lowest-risk scenario. Keep the existing URLs, keep the keyword portion of every title tag and H1, keep at least 80% of the body copy on your best pages, maintain internal linking depth, and make sure the new templates are at least as fast on mobile as the old ones.

Should I change domains during a rebrand?

Only if the new name genuinely requires it. If you do, run the domain move and the redesign as two separate launches where possible: move the domain first with an identical site, confirm stability for 4 to 6 weeks, then deploy the new design. Combining both makes diagnosis much harder when something goes wrong. For the wider picture, see Website Redesign Without Losing SEO.

How long should I keep 301 redirects in place?

Google consolidates signals within roughly 6 to 12 months, but old links, bookmarks and printed materials persist for years. Treat redirect rules as permanent infrastructure.

How do I rebrand without losing customers?

Communicate early and repeatedly: email your list before launch, keep a permanent “we changed our name” page, keep old social handles pointing to the new ones, brief your sales and support teams with a simple script, and bid on your old brand name in paid search during the transition.

What is the 80/20 rule in SEO during a migration?

Roughly 20% of your URLs generate around 80% of your organic traffic and links. During a rebrand, those URLs get individual human attention, manual redirect mapping and manual QA. The remaining 80% can be handled with pattern-based rules and spot checks.

Is SEO still worth investing in during a rebrand?

It is arguably the highest-leverage spend of the entire project. A rebrand puts existing organic revenue at risk, and migration QA protects an asset you already paid for. Losing 30% of organic traffic costs far more than the audit that would have prevented it.

What tools do I need?

A crawler (Screaming Frog or Sitebulb), Google Search Console on both old and new properties, your analytics platform, a backlink tool for referring domains, a bulk status code checker, and a shared spreadsheet for the URL map. That is genuinely enough.

Ready to rebrand without the traffic anxiety?

Most rebrands fail on SEO for boring, preventable reasons: nobody owned the URL map, nobody QA’d staging, nobody watched the data after launch. If you want a second pair of eyes on your migration plan, or a full pre-launch and post-launch audit, get in touch with our team and we will pressure-test your plan before it goes live rather than after.

Ask any agency what really delays a website launch and you will get the same answer: missing content. Not design revisions. Not development bugs. Content. A project quoted at six weeks quietly stretches into five months because nobody can find the original logo file, the product photos are screenshots from Facebook, and the “About” page copy is still sitting in a draft email.

The good news is that this is entirely preventable. If you prepare content for your web designer before the kickoff meeting, you remove the single biggest bottleneck in the entire process. This guide walks you through exactly what to gather, what format each asset should be in, and how to hand it all over so your designer can actually start designing on day one.

Why Unprepared Content Is the Number One Cause of Delayed Launches

A web designer cannot design a page without knowing what goes on it. Layout decisions depend on the length of your headline, the number of services you offer, the shape of your photos, and whether you have three testimonials or thirty. When content is missing, one of two things happens:

• The designer uses placeholder text and images. You approve a beautiful mockup, then real content arrives and breaks the layout. Everything gets redesigned.
• The project stalls. The designer moves on to another client, and your slot in their schedule disappears. Getting it back can take weeks.

Both outcomes cost you money and momentum. Preparing your content in advance is the cheapest project insurance you will ever buy.

Before You Gather Anything: Define the Site Structure

You cannot collect content for pages you have not decided on. Spend an hour sketching a simple sitemap: a list of every page you need, organized by hierarchy. For a typical small business site that looks like this:

• Home
• About
• Services (with a sub-page per service)
• Portfolio or Case Studies
• Testimonials
• Blog
• Contact
• Privacy Policy and Terms

Write this list in a document and use it as the spine for everything below. Every asset you collect should be labelled with the page it belongs to. This single habit saves hours of back and forth.

The 10-Item Content Prep List

1. Brand Assets and Logo Files

This is where most projects trip at the first hurdle. A logo copied from your old website is typically 200 pixels wide and will look blurry on a modern screen. Your designer needs the original.

What to send:

• Vector logo files: .svg, .ai, .eps or a vector .pdf
• A transparent .png version at a minimum of 1000px wide as a backup
• Horizontal, stacked, and icon-only variations if they exist
• A light version for dark backgrounds and a dark version for light backgrounds
• Your favicon source (a square version of your mark)

If you cannot find the vector files, contact whoever designed the logo. If that is a dead end, tell your designer early so they can quote for a redraw. Do not discover this in week four.

2. Brand Guidelines, Colours and Fonts

Even a one-page brand sheet helps enormously. If you do not have formal guidelines, provide:

• Hex codes for your primary and secondary colours (for example #1A3D6B, not “our blue”)
• The names of your fonts, plus licence files if they are paid fonts
• Any rules you already follow, such as never stretching the logo or always using sentence case headings

3. Page Copy, Written and Final

This is the heaviest item on the list and the one people underestimate. Write your copy in a single shared document, with one clear heading per page that matches your sitemap. There is a practical rundown of it online.

Best practice for delivery:

• Use Google Docs or a single .docx file, never a PDF and never copy pasted into the body of an email
• Structure it with real heading levels (H1, H2, H3) so the designer understands hierarchy
• Mark clearly where you want buttons, and what they should say (“Book a free consultation”)
• Include the page title and meta description you want for SEO, or flag that you want help with these

A realistic guide to length:

Page type	Suggested word count	Must include
Home	300 to 600	Headline, what you do, who it is for, main call to action
About	400 to 800	Story, team, credentials, values
Service page	600 to 1200	Problem, solution, process, pricing or pricing guidance, FAQ
Contact	100 to 200	Address, phone, email, hours, form fields you need
Legal pages	As required	Privacy policy, terms, cookie notice

Not a writer? Say so at the quoting stage. Hiring a copywriter, or paying your designer to handle copy, is far cheaper than a three month delay.

4. Photography: Team, Premises and Lifestyle

Stock photos are fine as filler, but original photography is what makes a site feel credible. If you can schedule a photo session before the design starts, do it. A similar approach shows up on thecrazypixel.com.

What to send:

• High resolution JPG or PNG, minimum 2000px on the longest side
• Original camera files, not versions that have been emailed or sent through WhatsApp
• A mix of landscape and portrait orientations, plus a few wide shots with empty space where text can sit
• Confirmation that you own the rights or have a licence

5. Product Images or Portfolio Work

For e-commerce, this is make or break. Inconsistent product photography is visible immediately and no amount of design can hide it.

• Shoot every product on the same background, at the same angle and crop
• Use square images for grids, typically 1500 x 1500px
• Name files logically: sku-1234-blue-front.jpg, not IMG_0483.jpg
• Supply a spreadsheet (.csv or .xlsx) with SKU, title, description, price, stock, weight, and variant options

For portfolio or case study work, bundle each project into its own folder containing images, a short write up, the client name, and the result achieved.

6. Testimonials, Reviews and Social Proof

Collect these early, because chasing clients for quotes takes longer than you expect. Aim for six to ten strong testimonials before launch.

Each testimonial should include:

• The quote itself, ideally two to four sentences and specific about results
• Full name, job title and company
• A headshot or company logo, with permission to use it
• Written permission to publish (an email reply is enough)

Also gather your Google review link, industry association badges, certifications, awards, and any “as featured in” logos.

7. Video and Audio Assets

If you want video on the site, decide now. Video changes layout decisions and load times.

• Upload finished videos to YouTube or Vimeo and share the links rather than sending large files
• For background videos, supply a short .mp4 clip, under 10 seconds, under 5MB, with no audio
• Provide captions or a transcript for accessibility

8. Domain, Hosting and Account Access

The most common eleventh hour panic is a client who cannot log into their own domain registrar. Track this down at the start.

Access needed	Why the designer needs it
Domain registrar login	To point DNS records at the new site
Hosting control panel	To deploy files, set up SSL and email routing
Existing CMS admin	To export current content, posts and images
Google Analytics and Search Console	To preserve tracking history and monitor the migration
Google Business Profile	To update the website link and keep local SEO consistent
Email marketing platform	To connect newsletter signup forms
Payment gateway	To configure checkout on e-commerce sites

Never send passwords by email. Use a password manager with shared vaults, or create a separate admin user for your designer that you can revoke after launch.

9. Reference Sites and Design Direction

Your designer is not a mind reader. Give them a starting point.

• Three to five websites you like, with a sentence on what you like about each (the typography, the spacing, the tone, the navigation)
• Two or three sites you dislike, and why. This is often more useful than the first list
• Your two or three closest competitors
• Any hard constraints: colours you cannot use, elements that must appear above the fold, brand rules from a parent company

10. Business Goals, Legal Details and Technical Requirements

Finally, the practical details that affect how the site is built:

• The primary goal: phone calls, form submissions, online sales, bookings, or downloads
• Integrations needed: booking system, CRM, live chat, inventory software, accounting tools
• Legal information: registered company name and number, VAT number, registered address, complaints procedure
• Existing URL list if you have a current site, so old pages can be redirected instead of returning 404 errors
• Who will update the site after launch, and what level of training they need

How to Hand Everything Over

Format matters as much as content. Here is a delivery structure that works:

1. Create a single shared cloud folder (Google Drive, Dropbox or OneDrive) named after your project
2. Inside it, create subfolders: 01-Logo-Brand, 02-Copy, 03-Photos, 04-Products, 05-Testimonials, 06-Video, 07-References
3. Put the copy document at the top level so it is easy to find
4. Give the designer edit access, not view only, so they can add notes and flag gaps
5. Send one message when the folder is complete rather than drip feeding assets over several weeks

Avoid sending assets through WhatsApp, iMessage or social media. These platforms compress images heavily and the quality loss is permanent.

Quick Reference: File Formats at a Glance

Asset	Preferred format	Minimum size
Logo	SVG, AI, EPS	Vector, any size
Photography	JPG	2000px longest edge
Product shots	JPG or PNG on white	1500 x 1500px
Icons and graphics	SVG or transparent PNG	512px square
Page copy	Google Doc or .docx	One document, headed by page
Product data	CSV or XLSX	One row per SKU
Video	MP4, or YouTube/Vimeo link	1080p
Documents for download	PDF, optimized	Under 5MB each

A Realistic Timeline for Getting Ready

If you are starting from zero, budget three to four weeks of preparation before the design work begins. A workable schedule:

• Week 1: Sitemap, goals, reference sites, chase down logo and brand files
• Week 2: Book photography, request testimonials, collect account logins
• Week 3: Write and edit page copy, gather product data
• Week 4: Photo shoot delivered, organise the shared folder, final review

Yes, it feels like extra work up front. It also routinely cuts a month or more off the total project timeline and dramatically reduces the number of revision rounds you pay for.

Common Mistakes to Avoid

• Sending content in batches over many weeks. Designers work in blocks. Fragmented delivery means restarting repeatedly.
• Approving a design with placeholder text. What looks balanced with dummy copy often collapses with real copy.
• Using images pulled from Google Images. This is a copyright risk and the resolution is almost always too low.
• Leaving legal pages until the end. Privacy policies and cookie notices are legal requirements, not optional extras.
• Forgetting the old URL list. Losing redirects from an old site is one of the fastest ways to lose search rankings overnight.
• Having no single decision maker. If five people must approve every headline, the project will stall. Nominate one person.

Frequently Asked Questions

What are the 7 C’s of website design?

The 7 C’s are commonly listed as Context, Content, Community, Customization, Communication, Connection and Commerce. They come from e-commerce design theory and are a useful checklist when reviewing whether a site does its job. Notice that Content is second on the list, which reinforces why gathering it properly before design begins matters so much.

How do I prepare website content if I am not a writer?

Start by recording yourself answering the questions a customer would ask: what do you do, who do you help, how does it work, what does it cost, why should someone choose you. Transcribe the recording and edit it down. If you still struggle, hire a copywriter or ask your web designer whether they offer copywriting. Handing over rough but complete notes is far better than handing over nothing.

What is the 3 second rule in website design?

The 3 second rule says a visitor should understand what you offer, who it is for, and what to do next within roughly three seconds of landing on your page. This is a content problem more than a design problem. Your headline, subheadline and main call to action need to be written and ready before the designer builds the hero section.

Is hiring a web designer still worth it in 2026?

Yes, for most businesses. AI tools and templates have lowered the cost of producing something that looks acceptable, but they do not solve positioning, information architecture, conversion strategy, accessibility compliance or technical SEO. A good designer earns their fee in the decisions they make about structure and clarity, not just in visuals. That said, the value you get depends heavily on how well prepared your content is.

Who owns the content once the site is live?

You should. Make sure your contract states that you own the copy, photography and final design files, and that you hold the accounts for your own domain and hosting. Register domains in your own name, not your designer’s.

What if my content is not ready when the project starts?

Tell your designer immediately. Most will happily agree a phased approach: design the key templates first using a realistic content outline, then populate as content arrives. What causes real damage is silence, missed deadlines, and a designer who has blocked out time they cannot now use.

Next Step

Copy the ten items above into a checklist, share it with your team, and set a deadline for each one. When you can tick every box, you are ready to brief a designer with confidence, and your launch date becomes a date you can actually keep.

If you would like a second opinion on whether your content is ready, or you want help writing it, get in touch and we will review your list before your project begins.

If you run a small business, your website is probably your best salesperson. It works nights, weekends and holidays. So it is worth spending one afternoon making sure it does not get hijacked, defaced or wiped out.

The good news: website security basics for small business owners are not technical. Most of the protection comes from about ten decisions, and most of them are handled once and then left running in the background. This guide explains each one in plain English: what it does, roughly what it costs, and who should actually do it (you, someone on your team, your hosting company, or your web agency).

Why small business websites get attacked in the first place

A common objection sounds like this: “We are a five person plumbing company, nobody is targeting us.” Correct. Nobody is targeting you personally. That is exactly the problem.

The overwhelming majority of website attacks are automated. Bots scan millions of sites looking for one known weakness: an outdated plugin, a login page with no protection, a password like admin2024. They do not care what you sell. Once they get in, they typically:

• Inject spam links or redirect your visitors to scam pages
• Use your server to send bulk email, which destroys your email deliverability
• Install a card skimmer on your checkout page
• Encrypt or delete your files and ask for money
• Sit quietly and use your site to attack other sites

The real cost is rarely the ransom. It is the downtime, the Google “this site may be hacked” warning, the lost enquiries, and the invoice to clean it up. Prevention is dramatically cheaper than recovery.

The 10 website security basics every small business should cover

1. HTTPS with a valid SSL certificate

What it does: An SSL certificate encrypts the connection between your visitor’s browser and your website, so contact form details, passwords and card numbers cannot be read in transit. It also turns on the padlock and the https:// prefix.

Why it matters beyond security: browsers now actively warn visitors on pages without HTTPS, and HTTPS has been a Google ranking signal for years. A site without it looks broken and untrustworthy.

Typical cost: free. Almost every decent host includes a Let’s Encrypt certificate at no charge and renews it automatically. Paid certificates (roughly 50 to 200 per year) only make sense in specific cases, such as an Organisation Validated certificate for finance or healthcare trust requirements.

Who handles it: your host or your agency. You just need to confirm it exists and that every page redirects to the HTTPS version, including old URLs.

How to check in 30 seconds

1. Type your domain without “https” and press enter. It should jump to the secure version.
2. Click the padlock and check the certificate expiry date.
3. Look for a “mixed content” warning, which means some images or scripts are still loading insecurely.

2. Hosting that takes security seriously

What it does: Your host is the foundation. Cheap shared hosting often means hundreds of sites on one server, outdated PHP versions, no isolation between accounts, and support that cannot help you when something breaks.

What good hosting includes:

• Account isolation so a neighbour’s hacked site cannot infect yours
• Current PHP and database versions, updated regularly
• Server level firewall and malware scanning
• Daily off-server backups you can restore yourself
• A staging environment for testing updates
• Free SSL and automatic renewal
• Real humans in support, ideally 24/7

Typical cost: 5 to 15 per month for basic shared hosting, 25 to 60 per month for quality managed hosting. For a business that generates leads or sales, managed hosting is the single highest value upgrade on this list.

Who handles it: the business owner decides and pays; the agency recommends and migrates.

3. A real admin password policy

What it does: Stops the most common attack of all, which is a bot simply guessing your login. Weak and reused passwords remain the number one way small business sites are compromised.

The rules that actually matter:

• Long beats complicated. A 16 character passphrase such as coffee-tuesday-anchor-92 is stronger and easier to remember than P@ssw0rd!
• Never reuse a password between your website, your email and your bank
• Delete the username “admin” and any old accounts from former staff or freelancers
• Use a password manager so nobody stores logins in a spreadsheet or on a sticky note
• Give each person their own account with the lowest role they need. Your content writer does not need administrator access, an Editor account is enough

Typical cost: 0 to 4 per user per month for a password manager. Free tiers are fine for very small teams.

Who handles it: you. This is the one item you cannot outsource, because it depends on team behaviour. Put it in writing, one page, and have everyone follow it.

4. Two factor authentication on everything that matters

What it does: Adds a second step to login, usually a six digit code from an app on your phone. Even if a password leaks, the attacker is stuck. Reference: https://kaspersky.com.

Turn it on for your website admin, hosting account, domain registrar, business email and payment gateway. The domain registrar is the one people forget, and losing control of your domain is worse than losing the site.

Typical cost: free. Use an authenticator app rather than SMS where you have the choice, since SMS codes can be intercepted.

Who handles it: agency sets it up on the website, you enable it on the accounts you own.

5. Plugin, theme and core updates on a schedule

What it does: Closes known holes. When a plugin vulnerability is published, automated scanners start hunting for unpatched sites within hours. Outdated plugins are the leading cause of WordPress compromises.

A sane routine for a small business:

• Security patches: apply within 24 to 72 hours
• Everything else: a scheduled monthly maintenance window
• Always take a backup first, and test major updates on staging if you run e-commerce or bookings
• Delete what you do not use. An inactive plugin is still code sitting on your server. Fewer plugins means a smaller attack surface
• Only install from official repositories or the developer’s own site. Free “nulled” premium plugins are the most reliable way to get malware

Typical cost: free if you do it yourself and accept the risk of a broken layout, or 40 to 150 per month as part of an agency care plan that includes checking the site afterwards.

Who handles it: your agency, or one clearly named person internally. “Everyone” means nobody.

6. Automated backups stored somewhere else

What it does: Backups are your insurance policy. Every other measure on this list reduces the chance of a disaster. Backups are what turn a disaster into an inconvenience.

What a usable backup looks like:

• Automatic, daily at minimum, and more often for shops taking orders
• Off-server, meaning stored somewhere other than the hosting account itself. A backup on a hacked server is not a backup
• Retained for at least 30 days, because some infections stay hidden for weeks
• Includes both files and database
• Tested. Restore one to a staging site at least twice a year. An untested backup is a hope, not a plan

Typical cost: often included with managed hosting, otherwise 5 to 25 per month for a dedicated backup service.

Who handles it: host or agency configures, you verify the restore test actually happened.

7. A web application firewall

What it does: A Web Application Firewall (WAF) sits in front of your site and filters traffic before it arrives. Think of it as a doorman who recognises known troublemakers and turns them away. It blocks common attack patterns such as SQL injection and cross site scripting, filters out bad bots, and absorbs traffic floods.

A cloud WAF has a useful side effect: it usually comes with a CDN, which makes your pages load faster around the world.

Typical cost: capable free tiers exist and are genuinely good enough for a brochure site. Paid plans run roughly 20 to 30 per month and add stronger rules, bot management and better reporting. Some managed hosts include a WAF in the plan.

Who handles it: agency or host. This one needs a small amount of configuration to avoid blocking legitimate visitors, so it is not a good DIY project. me.uk has covered this at length.

8. Login page protection

What it does: Your login page is the front door and bots knock on it constantly. Login protection makes brute force guessing pointless.

The measures worth having:

• Rate limiting: block an IP address after a handful of failed attempts
• Change the default login URL so automated scanners cannot find it easily
• CAPTCHA on login and on contact forms, which also cuts spam enquiries
• Restrict admin access by IP if your team all works from one office
• Disable file editing from the dashboard, so a stolen login cannot be used to edit code
• Alerts on new admin accounts, one of the clearest signs of a breach

Typical cost: free to 100 per year. Reputable security plugins cover most of this in one place.

Who handles it: agency, or a confident in-house person following documentation.

9. Malware scanning and uptime monitoring

What it does: Tells you there is a problem before your customers do. A scanner checks your files for injected code and unexpected changes. An uptime monitor pings your site every few minutes and emails or texts you when it stops responding.

Also worth doing: add your site to Google Search Console. It is free and Google will notify you directly if it detects malware or spam on your pages.

Typical cost: free monitoring tools cover the basics; scanning plus monitoring bundles run 10 to 30 per month.

Who handles it: agency sets up, alerts go to two people so nothing is missed during holidays.

10. Access hygiene and a one page incident plan

What it does: Limits the damage a single compromised account can do, and stops panic from making things worse.

Access hygiene, twice a year:

• Review who has access to the website, hosting, domain and analytics
• Remove ex-employees, ex-freelancers and any test accounts
• Confirm you, not your agency, are the registered owner of the domain and hosting. This is a critical point that catches a lot of businesses out
• Downgrade anyone who does not need administrator rights

Your incident plan needs only four things:

1. Who to call first, with the phone number written down offline
2. Where the backups live and who can restore them
3. Logins for host, registrar and website, stored in the password manager and accessible to a second person
4. What you will tell customers if data was exposed, and any reporting obligations you have

Typical cost: an hour of your time.

Who handles it: you, with input from your agency.

Cost and ownership at a glance

Measure	Typical cost	Best owner	Priority
SSL / HTTPS	Free	Host or agency	Essential
Secure hosting	25 to 60 / month	Owner decides	Essential
Password policy	0 to 4 / user / month	Owner and team	Essential
Two factor authentication	Free	Owner and agency	Essential
Updates and maintenance	Free to 150 / month	Agency or named person	Essential
Automated backups	0 to 25 / month	Host or agency	Essential
Web application firewall	0 to 30 / month	Agency or host	High
Login protection	0 to 100 / year	Agency	High
Scanning and monitoring	0 to 30 / month	Agency	Medium
Access review and plan	Your time	Owner	Medium

Costs are indicative ranges in your local currency for a typical small business site and will vary by provider and by how much traffic you get.

A realistic 30 day rollout

You do not need to do all ten at once. Here is the order that removes the most risk for the least effort.

Week 1: the free wins

1. Confirm HTTPS works site-wide and the certificate auto-renews
2. Enable two factor authentication on website, hosting, domain and email
3. Change every admin password to a long unique passphrase in a password manager
4. Delete unused accounts and any account named “admin”

Week 2: the safety net

1. Set up or verify daily off-server automated backups
2. Actually restore one backup to staging to prove it works
3. Add uptime monitoring and connect Google Search Console

Week 3: the walls

1. Install and configure a web application firewall
2. Add login rate limiting, CAPTCHA and a non-default login URL
3. Remove every plugin and theme you are not using

Week 4: make it a habit

1. Book a recurring monthly maintenance window, or sign a care plan
2. Write your one page incident plan and share it with a second person
3. Diarise a six-monthly access review
4. Review whether your hosting is genuinely good enough for what the site earns you

Warning signs your site may already be compromised

• Google shows a “this site may be hacked” or deceptive site warning
• Pages redirect somewhere strange, but only for visitors arriving from search or on mobile
• Admin accounts you did not create
• Sudden unexplained slowness or server resource spikes
• Your business email starts landing in spam folders everywhere
• New files with random names in your site directories
• Search results showing pages you never published, often in another language

If you see any of these, do not simply delete files and hope. Take a full copy for evidence, change all passwords from a clean device, and get a professional clean-up. Attackers usually leave a hidden way back in, and missing it means you get hacked again a week later.

What you can safely skip

Small business security advice often drifts into enterprise territory. For a typical site with a few hundred visitors a day, you almost certainly do not need penetration testing every quarter, a dedicated security operations service, an expensive Extended Validation certificate, or five overlapping security plugins fighting each other.

Ten fundamentals done consistently will stop the automated attacks that cause the vast majority of small business incidents. Consistency beats sophistication every time.

Frequently asked questions

What is the best security for a website?

There is no single product. The strongest setup is layered: HTTPS, quality hosting, unique passwords with two factor authentication, prompt updates, tested off-site backups, a web application firewall and login protection. If you can only do one thing today, enable two factor authentication. If you can only do two, add automated off-server backups.

What are the 5 basic security principles?

Most frameworks come down to five ideas: confidentiality (only the right people see data), integrity (data is not altered without permission), availability (the site stays online), authentication (people are who they claim to be) and non-repudiation or accountability (actions are logged and traceable). Every item in this guide serves at least one of them.

What are the 5 C’s in security?

The 5 C’s are commonly listed as change, compliance, cost, continuity and coverage. In practical terms for a small business: can you adapt when threats evolve, do you meet the rules that apply to you, is the spend proportionate, can you keep trading after an incident, and are all your important assets actually protected rather than just the obvious ones.

What is the 80/20 rule in cybersecurity?

Roughly 20 percent of the effort prevents about 80 percent of the incidents. For websites, that 20 percent is strong unique passwords, two factor authentication, keeping software patched and having working backups. Those four cover the bulk of real-world attacks and cost very little.

Do I need a security plugin if my host already provides security?

Usually a light one, yes. Host level protection guards the server; a security plugin guards the application layer, adding login limits, file change detection and user alerts. Just do not run several at once, as they conflict and slow the site down.

How much should a small business budget for website security?

A reasonable range is 40 to 120 per month all in, covering quality hosting, backups, a firewall and maintenance. Compare that to a professional malware clean-up plus lost enquiries during downtime, which typically costs several hundred to a few thousand in one go.

Is a website builder platform safer than WordPress?

Hosted platforms handle patching for you, which removes one big risk, but they also limit your control and portability. WordPress is not inherently insecure; the problems come from neglected plugins and weak logins. A well maintained WordPress site is safer than an abandoned site on any platform. For the wider picture, see Secure Your Business.

Who should be responsible for website security in a small business?

Split it clearly. The owner owns passwords, access reviews, domain ownership and the budget. The host owns server hardening, SSL and platform backups. The agency owns updates, firewall configuration, login hardening, monitoring and clean-up. Write down who does what, because unclear ownership is itself a vulnerability.

Next step

Run through the Week 1 list on your own site this morning. It takes under an hour and closes the doors attackers use most. If you would rather have someone confirm your site is properly protected, or you want updates, backups, firewall and monitoring handled for you, get in touch and we will review your setup and tell you exactly what is missing.

Most advice about calls to action obsesses over wording. Change “Submit” to “Get My Free Quote” and watch conversions climb. That helps, but it ignores a simpler problem: a well-written button nobody sees converts nothing. Call to action placement decides whether your offer appears at the exact moment a visitor is ready to act, or three screens after they lost interest.

This guide is deliberately placement-first. No redesign required. You can open your existing pages, compare them against the nine positions below, and move or duplicate buttons this afternoon.

Why Placement Beats Copywriting for Quick Wins

Visitors do not read pages. They scan them in a predictable path, then stop scrolling once they have either found what they wanted or decided they have not. Three behavioural realities drive every recommendation in this article:

• Scroll depth drops off fast. A large share of visitors never reach the bottom of a long page. If your only CTA lives in the footer, you are asking the minority to carry your whole conversion rate.
• Readiness is not linear. Some visitors are ready in four seconds because a colleague already recommended you. Others need pricing, proof and a FAQ first. A single CTA position can only serve one of those groups.
• Attention follows visual flow. Eyes travel along an F or Z pattern on desktop and straight down a single column on mobile. CTAs placed off that path get ignored even when they are large and brightly coloured.

The practical conclusion: place CTAs at every natural decision point, not just at the start and the end.

The 9 Highest-Converting CTA Positions

1. The Hero Button, Above the Fold

The first screen is the only placement guaranteed to be seen by close to 100% of visitors. It should carry your single most important action, written as an outcome rather than a mechanic.

Placement rules that matter more than colour:

• Position the button directly under the headline and subheadline, left-aligned on text-heavy layouts, centred on centred layouts. Keep it inside the same visual block so the eye never has to hunt.
• Keep it fully visible at a 1366×768 laptop resolution, not just on your 27-inch monitor.
• If you need two actions, make the secondary one a ghost button or text link placed to the right of the primary. Two equally weighted buttons split attention and reduce clicks on both.

Common mistake: pushing the hero CTA below the fold with an oversized announcement bar, cookie banner and 120px of padding stacked on top of each other. A similar approach shows up on dentalmarketingrecipes.com.

2. The Sticky Navigation Button

A persistent button in the top right of a sticky header is the cheapest conversion insurance you can install. It follows the visitor for the entire session and costs no vertical space.

• Use it for the same primary action as the hero, so the message stays consistent.
• Give it a solid fill so it reads as a button, not a menu item. A plain “Contact” text link in the nav is not a CTA.
• On desktop, top right is the conventional position. Do not get creative here; convention is what makes it findable.

3. Right After the First Proof Block (roughly 20 to 30% scroll depth)

This is the most commonly missing CTA on business websites. A visitor reads your headline, scrolls past the “what we do” section, sees a client logo strip or a short benefits row, and is briefly convinced. Then they scroll into a wall of service descriptions and the moment passes.

Insert a CTA immediately after the first piece of evidence: logo bar, key statistic, short testimonial, or the three-column benefits row. It captures fast-moving visitors who are already sold.

4. Inline Contextual Links Inside Body Copy

Not every CTA needs to be a button. Inside long paragraphs, a bolded contextual text link converts remarkably well because it appears exactly where the relevant idea is explained.

• Use them on blog posts, service pages and documentation, where readers are in reading mode rather than scanning mode.
• Anchor the link to the specific promise in the sentence, for example a link on “book a 20-minute audit call” rather than on “click here”.
• Limit yourself to two or three per 1,000 words so they still feel like recommendations rather than ads.

5. Mid-Page, After Social Proof or a Case Study

Trust peaks right after a visitor finishes a detailed testimonial, a before-and-after result or a case study summary. That emotional peak decays within a screen or two.

Place a full-width CTA band directly beneath the proof section. On longer landing pages, repeat the offer every three to four screens using varied formats (band, card, inline link) so it does not feel like the same banner copy-pasted five times.

6. The Sticky Mobile Bottom Bar

Since mobile traffic dominates most service and local business sites, this is often the single highest-value placement on the entire site. A fixed bar at the bottom of the mobile viewport sits inside the natural thumb zone and stays available at every scroll depth.

• Keep it to one action, or two at most (for example “Call Now” and “Get a Quote”).
• Height should stay around 56 to 64px so it does not eat the content area.
• Make sure it never covers form fields, the last line of content or the footer. Add matching bottom padding to the page body.
• Test it against iOS Safari’s own bottom UI bar, which is where most implementations break.

7. The Sticky Sidebar Card (Desktop, Long Content)

On blog articles, resource pages and documentation, a sidebar card that sticks as the reader scrolls keeps the offer permanently in peripheral vision without interrupting the text. See figma.com for their take.

• Works best with a soft offer: checklist, template, newsletter, calculator.
• Keep the card short, roughly a heading, one line and one button.
• Remember it disappears entirely on mobile, so never make it your only CTA.

8. The End-of-Content CTA Block

Readers who reach the bottom of a page are your most qualified audience. They deserve the most explicit ask on the page.

• Make it visually distinct: contrasting background band, larger button, more whitespace.
• Restate the benefit in one sentence above the button. Do not simply drop a naked button at the end of a paragraph.
• On blog posts, match the CTA to the article topic. A generic “Contact us” at the end of a specific how-to guide wastes the intent you just built.

9. The Footer as the Last-Chance CTA

The footer is not glamorous, but it is where a certain type of visitor deliberately goes looking for contact details. Give them a repeated primary button plus the practical alternatives: phone number, email, booking link, address.

Treat it as a safety net for the deliberate visitor, not as your main conversion mechanism.

Bonus Positions Worth Testing

• Under the pricing table: one button per plan, plus a single “Not sure which plan?” link underneath.
• After the FAQ section: objections have just been handled, which is a natural moment to ask again.
• Scroll-triggered or exit-intent overlay: effective, but use once per session, desktop only, and never on top of a page the visitor just started reading.

Which Positions Matter Most by Page Type

Page type	Must-have placements	Optional	Avoid
Homepage	Hero, sticky nav, after proof block, footer	Mobile sticky bar	Multiple competing primary offers
Service or product page	Hero, mid-page after proof, end of content, mobile sticky bar	After FAQ, under pricing	Sidebar cards that distract from the offer
Blog article	Inline links, end of content	Sticky sidebar, mid-article card	Hero CTA above the article title
Dedicated landing page	Hero, repeated every 3 to 4 screens, end of page	Mobile sticky bar	Navigation links that leak traffic away
Local business page	Hero, mobile sticky call bar, footer with map and hours	Sticky nav button	Contact form buried below the fold only

How to Audit Your CTA Placement in 30 Minutes

1. Load each key page on a phone first. Screenshot the first viewport. If no action is visible, that is your first fix.
2. Scroll slowly and count the screens between CTAs. More than four screens without an ask on a sales page is a gap.
3. Mark every decision point. End of the benefits section, end of testimonials, end of pricing, end of FAQ. Each one should be followed by an ask within a screen.
4. Check for competing actions. If a single screen contains a newsletter box, a chat bubble, a download link and a booking button, choose one and demote the rest.
5. Verify scroll depth in your analytics. Find the depth where 50% of visitors drop off, then make sure at least two CTAs appear before that point.
6. Test tap targets. Minimum 44×44 pixels, with at least 8px of spacing from other clickable elements.
7. Change one placement at a time. Moving three CTAs in the same week makes the results unreadable.

Placement Mistakes That Quietly Cost Conversions

• Only one CTA on a 4,000 pixel page. You are relying on the visitor to scroll back up.
• CTAs stacked back to back. Two buttons in consecutive sections read as noise. Space them with real content.
• Different offers in every position. Book a call, download a guide, subscribe, request pricing. Pick one primary path per page and keep secondary offers visually smaller.
• Buttons that look like decoration. Flat, borderless, low-contrast rectangles are frequently skipped entirely. Contrast is a placement issue too: an invisible button is effectively not on the page.
• Sticky elements that cover content. A mobile bar over the last line of a form is worse than no bar at all.
• Popups that fire immediately. Delay to at least 40% scroll depth or 25 seconds, and never on mobile entry.

A Simple Rule to Remember

Ask once where attention is highest (the hero), keep the ask permanently available (sticky nav and mobile bar), and repeat the ask after every moment of persuasion (proof, pricing, FAQ, end of content). That single pattern covers the fast decider, the researcher and the returning visitor without cluttering the page.

Frequently Asked Questions

Where should a CTA be placed on a website?

At minimum: above the fold in the hero, once mid-page after a proof element, and at the end of the content. On mobile, add a sticky bottom bar. Persistent placements such as a sticky header button cover the visitors who decide at unpredictable moments.

How many CTAs should one page have?

One primary action repeated in several positions. A short homepage might carry three or four instances; a long landing page can comfortably hold six to eight. The number matters less than the consistency: multiple placements, single offer.

Does above the fold still matter?

Yes, but not exclusively. The first viewport is the only one everyone sees, so it should always contain an action. However, visitors who need more information convert lower down the page, which is why below-the-fold placements often produce more total conversions on considered purchases.

What makes a good CTA button beyond position?

Strong contrast against the background, a button shape that is visibly clickable, adequate whitespace around it, first-person or outcome-based wording, and a supporting line of microcopy that removes risk (“Free”, “No card required”, “Reply within one business day”). More at https://manypixels.co.

What are examples of calls to action?

“Book a free 20-minute audit”, “Get my quote”, “Start my free trial”, “Download the checklist”, “See pricing”, “Call now”. Match the commitment level to the position: soft offers work well in sidebars and inline links, high-commitment offers belong in the hero and at the end of the page.

Are sticky CTAs bad for SEO or page experience?

Not if they are sized responsibly. Problems arise when sticky elements cover a large portion of the mobile viewport or behave like intrusive interstitials. A slim bottom bar that leaves the main content readable is fine. A fuller account is out there.

Next Step

Pick your highest-traffic page, run the 30-minute audit above, and fix the single biggest gap you find. In most cases that is either a missing mobile sticky bar or the absence of any ask between the hero and the footer. Both are afternoon-sized changes with measurable results within a few weeks.

If you have ever hired a web developer, you have probably seen words like Git, repository, branch, commit or pull request in an email or an invoice. Most explanations online are written for developers, by developers. This guide is written for the person paying the invoice.

By the end of this article you will understand what version control actually does, why it is the single biggest protection your website has against broken updates, and the exact questions to ask your developer before, during and at the end of a project (especially the uncomfortable one: who owns the code repository?).

What is version control in web development? The short answer

Version control in web development is a system that records every change made to your website’s code, who made it, when, and why, so that any version can be recovered at any time. The most widely used version control system today is Git, usually hosted on a platform such as GitHub, GitLab or Bitbucket.

Think of it as an unlimited, permanent undo history for your website. Not just for the last edit, but for every edit ever made, by every person who ever touched the project, going back to day one.

From a business point of view, version control gives you four things:

• Recovery: a broken update can be reversed in minutes instead of rebuilt from scratch.
• Accountability: you can see who changed what and when.
• Collaboration: several developers can work on the same site without overwriting each other.
• Continuity: if your developer disappears, the full history of your website does not disappear with them.

The Google Docs analogy (the easiest way to understand it)

You already use a simplified form of version control every day. Open a Google Doc and click “Version history”. You will see a list of saved states with names and timestamps, and you can restore any of them.

Version control for a website works the same way, with three important differences:

1. It tracks hundreds or thousands of files at once as one single snapshot, not one document.
2. Each saved point has a written explanation attached (“fixed checkout button on mobile”).
3. Developers can create parallel copies of the whole project, experiment freely, and only merge the work back in once it is proven to work.

That third point is the one that protects your revenue. Nobody has to experiment on your live website.

The five words your developer keeps using, translated

Developer word	What it means in plain English	Business equivalent
Repository (repo)	The project folder containing your code plus its complete history	The master filing cabinet for your website
Commit	A saved snapshot of the project with a note explaining the change	A dated, signed entry in a logbook
Branch	A parallel copy of the project used to build or test something new	A working draft kept separate from the signed contract
Merge	Folding the tested work from a branch back into the main version	Approving a draft and filing it as final
Rollback / revert	Returning the site to a previous working state	Pulling last week’s known-good version out of the cabinet

Repository: where your website really lives

Your live website is a copy. The repository is the source of truth. It holds the code, the configuration, the theme or template files, and every change ever recorded. If your live server is wiped tomorrow, a healthy repository means the site can be redeployed. If the repository does not exist, or you cannot access it, you are relying entirely on backups and luck.

Commit: the paper trail

Every commit answers three questions automatically: what changed, who changed it, and when. A good project history reads like a maintenance log:

• “Add GDPR cookie banner”
• “Fix contact form not sending on iPhone”
• “Update payment plugin to 4.2.1”

That log is genuinely useful to you as an owner. When something breaks on a Tuesday, the first question is always “what changed recently?” and the commit history answers it in seconds. Source: https://van-ons.nl.

Branch: why your site does not have to be the test lab

This is the concept most business owners find the most reassuring. When a developer needs to rebuild your checkout, add a booking system or redesign your homepage, they create a branch. The live site keeps running untouched while the new work is built and tested in parallel. Only when it is approved does it get merged and deployed.

No branches usually means one thing: someone is editing files directly on your live website. That is how sites go down at 3pm on a Friday.

How version control protects your website from broken updates

Here are the real-world scenarios where version control pays for itself.

1. A plugin or dependency update breaks the site

Without version control: panic, manual reinstalls, guesswork, hours of downtime.
With version control: the update was a commit. Revert the commit, redeploy, site is back. Then diagnose calmly. Originally covered on https://git-scm.com.

2. Two developers work on the same site in the same week

Without version control: one developer uploads files by FTP and silently overwrites the other’s work.
With version control: Git detects the overlap and forces the conflict to be resolved deliberately, before anything reaches the live site.

3. A change looked fine but tanked your conversions

Without version control: you try to remember what the page looked like three weeks ago.
With version control: you restore the exact previous version and compare properly.

4. Your developer becomes unavailable

Without version control: a new developer starts by reverse engineering a mystery. Expect to pay for that discovery time.
With version control: the new team clones the repository, reads the history, and is productive in days rather than weeks.

5. Something suspicious appears on your site

Without version control: you cannot tell modified files from original ones.
With version control: any unexpected change to tracked files stands out immediately, which makes cleanup after a security incident far faster.

Important: version control is not the same as a backup

This confusion causes real damage, so let us be precise. Both matter, and they protect different things.

	Version control (Git)	Backups
Protects	Code, templates, configuration	Database, uploaded media, orders, customer data
Granularity	Every individual change, with an explanation	Whole-site snapshots at set intervals
Answers	“What changed and why?”	“Can we get everything back to yesterday?”
Typical use	Reversing a bad deployment	Recovering from server loss or data corruption

You need both. A repository will not bring back last night’s orders. A backup will not tell you which of forty changes broke the checkout. Any developer who says “we don’t need version control, we have backups” is telling you they do not have a recovery process, only a reset button.

What to ask your developer: 10 questions that take five minutes

You do not need to understand Git commands to run a professional check. Ask these, and listen for confident, specific answers.

About version control and process

1. Is my website’s code in a Git repository? Where is it hosted? (Expect GitHub, GitLab, Bitbucket or a self-hosted equivalent.)
2. Are changes tested somewhere other than my live site before going live? (You are asking about a staging environment and branches.)
3. How do changes get deployed to the live site? (Automated deployment from the repository is the professional answer. “I upload by FTP” is a warning sign.)

About backups and rollbacks

4. How often are backups taken, and do they include the database as well as the files?
5. Where are backups stored, and are they held somewhere separate from the web server?
6. When was a restore last tested? An untested backup is a promise, not a safety net.
7. If an update breaks the site, how long does a rollback take, and who is authorised to trigger it? Get a number in minutes or hours, and put it in your maintenance agreement.

About ownership and access

8. Who owns the repository and the code in it?
9. Is my company the owner of the repository account, or is it inside your personal or agency account?
10. At the end of the project, how is the repository, with its full history, transferred to me?

Who owns the code repository at the end of a project?

This is where businesses get hurt, and it is almost always avoidable. Ownership of code is a contractual matter, not a technical one. If your agreement is silent, you may find you have paid for a website whose source code and history you cannot legally or practically take with you.

Put these points in writing before work starts

• IP assignment: custom code written specifically for you is assigned to your company on final payment.
• Repository ownership: the repository lives in an organisation account owned by your company, with your developer added as a collaborator. This is the single most effective clause you can add.
• Full history transfer: you receive the repository with its complete commit history, not a zip file of final files. History is the documentation.
• Third-party components: a written list of any licensed themes, plugins, libraries or APIs used, and who holds those licences.
• Credentials handover: hosting, domain registrar, DNS, repository, deployment tools, analytics, and any environment variables or keys.
• Access removal: departing collaborators lose access at handover, and any shared secrets are rotated.

Handover checklist you can copy

Item	Received?
Repository under our company account, with full history
Admin access to hosting, domain and DNS
Written deployment instructions (how code reaches the live site)
Documented rollback procedure and target recovery time
Backup schedule, storage location and a tested restore
List of licences and third-party services
Signed IP assignment for custom code

Red flags that suggest version control is missing

• Files are edited directly on the live site, or uploaded manually by FTP.
• Nobody can tell you what changed last week.
• Fixing a broken update means “rebuilding” rather than “reverting”.
• There is no staging or test environment at all.
• Folders on the server named index-old.php, backup-final-v3 or site_copy_new. That is version control by superstition.
• Your developer cannot show you where the repository is.

Does this apply to WordPress, Shopify and no-code sites?

Yes, with nuance. On a WordPress site, the custom theme, custom plugins and configuration should be in version control, while the database and media library are protected by backups. On Shopify, theme code can and should be version controlled. On hosted no-code or website builder platforms you may have limited or no access to code, in which case your protection comes from platform versioning plus documented, exported backups. The principle never changes: every change should be recorded, reviewable and reversible.

Frequently asked questions

What is version control in simple terms?

It is a system that saves a dated, labelled snapshot of your project every time something changes, so any earlier version can be restored and you can always see who changed what and why.

Is GitHub a version control system?

Not exactly. Git is the version control system. GitHub is a hosting platform for Git repositories that adds collaboration features such as access control, code review and issue tracking. GitLab and Bitbucket are alternatives. Simple analogy: Git is the engine, GitHub is the garage. The reasoning is set out in this piece.

What are the main version control systems used today?

Git dominates modern web development. Others still in use include Subversion (SVN), Mercurial, Perforce Helix Core (common in games and large binary projects) and Azure DevOps repositories. For a typical business website, if your developer is not using Git, ask why.

Is SVN better than Git?

For web development, Git is the standard choice because it is distributed, fast, and makes branching cheap and safe. SVN uses a centralised model that some organisations still prefer for very large binary assets or strict central control. For your website, Git is almost certainly the right answer.

Do I need version control for a small five page website?

Yes, and it costs almost nothing to set up. Small sites still break, still get updated, and still change hands between developers. The smaller the site, the smaller the effort and the bigger the relative benefit.

Does version control cost extra?

The tooling itself is free or very cheap, and private repositories are included in the free tiers of the major platforms. What you are paying for is a developer’s disciplined process, which reduces downtime, shortens fixes and lowers the cost of every future change.

Can I see the repository myself without being technical?

Absolutely. Ask for read access. You will see a plain list of dated changes with descriptions, and you can browse them in a browser without installing anything.

The takeaway

Version control is not developer housekeeping. It is operational insurance for a business asset. It determines how fast a broken update gets fixed, how easily a new team can take over, and whether you actually own what you paid for.

You do not need to learn Git. You just need to ask three questions and get clear answers: Where is the repository? How fast can we roll back? Who owns it when the project ends?

If your current setup cannot answer those, that is worth fixing before your next update, not after your next outage. Get in touch and we will review how your website’s code, backups and rollback process are handled.

Product page optimization is the process of improving every element on a product detail page so that more visitors add the item to their cart and complete the purchase. It is the single highest-leverage work most store owners can do, because product pages are where buying decisions actually happen: your ads, SEO and email campaigns all funnel traffic here, and every percentage point of conversion you gain applies to that entire traffic volume.

This guide breaks the product page down into 11 concrete components. Take your own product template, open it side by side with this article, and audit it element by element. By the end you will have a prioritised list of what is quietly costing you sales.

First, a quick clarification: two different meanings

If you searched for “product page optimization”, you may have landed on results about Apple’s App Store feature. The term is used in two contexts:

Context	What it means	Who it is for
Ecommerce (this guide)	Improving the layout, content and UX of a product detail page (PDP) on your online store to increase conversion rate and organic visibility	Store owners, ecommerce managers, CRO and SEO specialists
Apple App Store (PPO)	Apple’s built-in A/B testing tool that lets you test alternate icons, screenshots and app previews (up to three treatments) against your original listing	App publishers and ASO teams

If you are here for the App Store feature, the short answer is at the bottom of this article in the FAQ. If you sell physical or digital products online, keep reading: everything below applies to Shopify, WooCommerce, Magento, BigCommerce and custom builds alike.

Why product page optimization matters more than more traffic

Most stores convert somewhere between 1% and 4% of their sessions. Product pages usually see far higher intent than category or blog pages, yet they are often the least tested template in the whole store. Consider the arithmetic:

• A store doing 50,000 sessions a month at a 2% conversion rate and a 70 EUR average order value earns 70,000 EUR.
• Lifting product page conversion to 2.6% (a realistic 30% relative gain from a serious audit) earns 91,000 EUR from the exact same traffic.
• Buying that extra 21,000 EUR through paid media would cost you real money every single month. The optimization is a one-time build cost.

Product page optimization also feeds SEO. Pages that answer questions fully, load fast, carry review markup and keep users engaged tend to hold rankings better than thin template pages with a manufacturer description pasted in.

The 11 elements that influence buying decisions

1. The image gallery

Images are the closest thing to picking the product up in a shop. On most stores, the gallery is the most-interacted element on the page, and shoppers who engage with it convert at a much higher rate than those who do not.

What a strong gallery contains:

1. Hero shot on white or neutral background so the product reads instantly in search results and social previews.
2. Scale reference: the product held, worn or placed next to a known object. Size confusion is a leading cause of returns.
3. Detail macros: stitching, material texture, ports, closures, finish.
4. In-context lifestyle shots showing the product in the environment the buyer imagines it in.
5. An “in the box” shot listing everything included.
6. A short video or 360 spin. Video on the PDP consistently outperforms static-only galleries.
7. An infographic image with the three key specs written on it, because many people never read the description.

Technical rules: minimum 1,500 px on the longest side for zoom, WebP or AVIF format, lazy loading for everything except the first image, and descriptive alt text (“walnut oak dining chair with black steel legs” rather than “IMG_4821”). On mobile, use a swipeable carousel with visible dot indicators and never hide images behind a thumbnail strip that requires two taps.

Quick audit

• Do you have at least six images per product?
• Can a first-time visitor understand the size without reading anything?
• Does zoom work with one tap on a phone?

2. The product title and H1

The title does double duty: it is the strongest on-page SEO signal and the first line of reassurance that the shopper landed on the right item.

A reliable formula: Brand + Product name + Key differentiator + Variant or size. For example, “Aveto Merino Crew Sweater, Machine Washable, Men’s”. Keep it readable rather than keyword-stuffed, aim for 50 to 70 characters, and make sure the H1 on the page matches what the visitor clicked in Google or in your ad. Mismatch between ad copy and page title is one of the most common sources of instant bounces.

3. Pricing display

Price is the element shoppers look at second, right after the main image. How you present it changes the perception of value more than the number itself.

• Show the total price context: if VAT, duties or eco-fees apply, say so next to the price rather than revealing them at checkout. Surprise costs remain the number one cause of cart abandonment.
• Anchor discounts honestly: display the reference price with the saving expressed both in currency and percentage (“79 EUR, was 99 EUR, save 20 EUR / 20%”). Fake or permanent “was” pricing is now a legal and trust risk in most markets.
• Unit pricing for consumables (“0.42 EUR per capsule”) helps buyers justify larger pack sizes.
• Payment splitting: if you offer instalments, show the monthly figure under the price, not in the cart.
• Free shipping threshold: “Add 12 EUR for free delivery” directly under the price is one of the highest-return micro-copy changes you can make.

4. Variant selection (size, colour, quantity)

Variant pickers break more purchases than most owners realise, especially on mobile.

Problem	Fix
Colour shown as a dropdown of names	Use visual swatches that update the gallery on selection
Out-of-stock variants hidden	Show them greyed out with a back-in-stock email capture
No sizing help	Inline size guide link plus a fit note (“runs small, size up”)
Tap targets under 44 px	Enlarge buttons and add spacing to prevent mis-taps
Price does not update with variant	Update price, image, stock and SKU on every selection

Rule of thumb: a shopper should never be able to press Add to Cart without having made a required choice, and should never be punished with a page reload for making one.

5. The add-to-cart button

The button is the conversion event. Treat it as the most important 200 pixels on your site.

• Contrast: the button colour must be unique on the page. If your brand colour is used for headers, links and badges, the button disappears.
• Copy: “Add to Cart” and “Add to Bag” are clear and safe. “Buy Now” suits single-product or high-impulse stores. Avoid vague verbs like “Continue” or “Select”.
• Position: visible without scrolling on desktop, and pinned in a sticky bar on mobile once the user scrolls past the original button. A sticky mobile bar showing price plus button is one of the most reliably positive tests in ecommerce.
• Feedback: when clicked, confirm with a slide-out drawer that shows the item, the subtotal, a clear checkout button and a link back to continue shopping. Never force a full page redirect to the cart unless your data says otherwise.
• Express payment buttons (wallet-based one-tap checkout) placed just below the main button reduce friction for returning mobile shoppers.
• Micro-reassurance under the button: a single line covering delivery estimate, returns window and secure payment.

6. Description structure

Nobody reads a wall of text. They scan for the one detail that answers their private objection. Structure the description so that detail is findable in under five seconds.

A structure that works:

1. One-sentence value proposition at the very top, above the fold if possible.
2. Three to five benefit bullets, each starting with the benefit and ending with the feature that proves it.
3. Expandable sections for full description, materials and care, specifications, compatibility, and delivery and returns.
4. A specification table with exact dimensions, weight, materials, power, capacity and warranty.
5. Use cases: who it is for, and honestly, who it is not for. Stating who should not buy builds more trust than any badge.

Write in your own words. Copying the manufacturer description creates duplicate content across dozens of retailers and gives Google no reason to rank you. Include the terms real customers use, not internal product codes.

Specification table example

Dimensions	48 x 32 x 15 cm
Weight	1.2 kg
Material	Recycled polyester, YKK zips
Warranty	3 years

7. Reviews and ratings placement

Reviews are the strongest external proof you have, and placement matters as much as volume.

• Star rating and review count directly under the product title, linked by anchor to the full reviews block. This is the single most common placement in high-converting stores.
• Full review section below the description, not buried under recommendations and footer widgets.
• Filter and sort options: by rating, by most recent, and where relevant by attribute (“Was the fit accurate?”).
• Photo and video reviews given visual priority. User-generated images convert better than studio images for many categories.
• Show the negative reviews. Pages with only five-star reviews read as fake. A blend that averages 4.2 to 4.7 typically converts better than a flawless 5.0.
• Reply to criticism publicly. A calm, helpful response to a two-star review sells to every future reader.
• Add Product and AggregateRating structured data so stars can appear in Google results and lift click-through rate.

If a product is new and has no reviews, borrow proof: brand-level testimonials, press mentions, warranty length, or a count of units sold.

8. Shipping, delivery and stock information

Uncertainty about delivery kills more sales than price. Answer these questions on the product page, not in a policy page nobody opens:

• How much does shipping cost to my location?
• When will it arrive, expressed as a date, not “3 to 5 business days”?
• Is it in stock right now?
• What happens if I need to return it, and who pays?

Best practice implementation: a short block under the add-to-cart button reading something like “In stock, dispatched today. Free delivery, estimated arrival Monday 24 August. Free returns within 30 days.” Dynamic delivery dates based on the visitor’s location and your cut-off time are worth the development effort in almost every category.

Low-stock indicators (“only 3 left”) can add urgency, but only use them when they are accurate. Fabricated scarcity is increasingly penalised by consumer protection rules and destroys repeat purchase rates.

9. Trust signals and risk reversal

Every product page has to overcome the same silent question: what happens if this goes wrong? Place answers where the doubt occurs, which is around the button.

• Returns window and who pays return shipping
• Warranty or guarantee length
• Secure payment icons showing the methods you actually accept
• Customer service contact, ideally with response time or live chat availability
• Certifications relevant to your category (safety, organic, sustainability, compatibility)
• Company legitimacy cues: physical address, VAT number, real About page linked in the footer

Keep these compact. A row of twelve badges looks like a spam site. Three specific, verifiable claims beat a wall of generic seals.

10. Cross-sells, upsells and related products

Placement discipline is everything here. Recommendations placed above or beside the add-to-cart button pull attention away from the purchase decision and can reduce conversion even while raising page views.

• “Frequently bought together” or accessory bundles: place just below the buy box, keep it to two or three items with checkboxes and a combined price.
• “You may also like”: place at the bottom of the page, after reviews. This is a rescue mechanism for people who have decided this specific product is not right.
• Upsell to a better version: a simple comparison table of two or three tiers beats a carousel, because it helps the buyer decide rather than distracting them.

11. Speed, mobile layout and technical health

The most persuasive page in the world fails if it loads in six seconds on a mobile connection. Product pages are usually the heaviest templates in a store because of galleries, review widgets and recommendation scripts.

• Target a Largest Contentful Paint under 2.5 seconds and an Interaction to Next Paint under 200 ms.
• Preload the hero image, lazy load everything below the fold.
• Audit third-party scripts. Review widgets, chat, heatmaps, pixels and upsell apps compound quickly. Remove anything you have not looked at in the last quarter.
• Reserve space for images and widgets to avoid layout shift, which causes mis-taps on the add-to-cart button.
• Test the full flow on a real mid-range Android phone, not just a desktop browser resized.

Do not forget the SEO layer: a unique title tag and meta description per product, clean canonical handling for variants, Product schema with price, availability, brand, GTIN and reviews, breadcrumb markup, and internal links from relevant blog content and category pages. The team at apple.com reached a similar conclusion.

Your product page audit scorecard

Score each element from 0 to 3, where 0 means missing, 1 means basic, 2 means solid and 3 means best in category. Anything scoring 0 or 1 with a high impact rating goes to the top of your roadmap.

Element	Impact on conversion	Effort	Your score (0-3)
Image gallery	Very high	Medium
Title and H1	Medium	Low
Pricing display	High	Low
Variant selection	High	Medium
Add-to-cart button	Very high	Low
Description structure	Medium to high	High
Reviews placement	Very high	Medium
Shipping and stock info	Very high	Medium
Trust and risk reversal	High	Low
Cross-sells placement	Medium (AOV)	Medium
Speed and mobile	Very high	High

How to test your changes without fooling yourself

Optimization without measurement is redecoration. A simple process:

1. Gather evidence first. Session recordings, scroll maps, on-site surveys (“What almost stopped you from buying today?”) and support ticket themes will tell you which of the 11 elements is actually broken on your store.
2. Form a hypothesis. “Because 62% of mobile users never scroll to the buy button after opening the gallery, adding a sticky add-to-cart bar will increase mobile add-to-cart rate.”
3. Run an A/B test if you have the traffic. As a rough guide you need a few hundred conversions per variant to detect realistic effects. Below that, use before-and-after comparisons over equal periods and accept more uncertainty.
4. Measure the right metric. Add-to-cart rate for buy box changes, checkout completion for shipping and trust changes, revenue per session as the tiebreaker. An upsell that raises AOV while lowering conversion may still lose money.
5. Roll winners into the template, not just one product, and document what you learned so you stop retesting the same idea every year.

Five mistakes we see on almost every audit

• Manufacturer copy pasted verbatim, identical to fifty competitors, with zero unique content to rank on.
• Delivery cost hidden until checkout, then a spike in abandonment that gets blamed on “the market”.
• Review widget loading three seconds after the page, pushing the button down and causing mis-taps.
• Recommendation carousels above the fold that send buyers on a loop between products instead of into the cart.
• No answer to the obvious objection. If your product is more expensive than the alternative, the page must say why, explicitly.

A 30-day action plan

1. Days 1 to 5: score your top 10 revenue-generating products against the scorecard above. Watch 20 mobile session recordings.
2. Days 6 to 10: ship the low-effort, high-impact fixes: sticky mobile add-to-cart bar, delivery date under the button, star rating under the title, free shipping threshold message.
3. Days 11 to 20: rebuild the image gallery and description structure for your top sellers, add a specification table and a size or compatibility guide.
4. Days 21 to 25: fix technical health. Remove unused scripts, compress images, add or repair Product structured data.
5. Days 26 to 30: launch a review collection flow by post-purchase email, then set up your first A/B test on the buy box.

FAQ

What is product page optimization?

In ecommerce, product page optimization is the practice of improving the content, layout, speed and persuasive elements of a product detail page so that a higher percentage of visitors add the item to their cart and buy. It combines conversion rate optimization, UX design, copywriting and technical SEO.

What does page optimization mean?

Page optimization means adjusting a single web page so it performs better against a defined goal. For a product page, the goals are usually conversion rate, revenue per session and organic ranking. It covers on-page content, structured data, load speed, mobile usability and the clarity of the call to action.

What is product optimization?

Product optimization is a broader term. It can refer to improving the product itself (features, packaging, pricing) or to improving how the product is presented and merchandised online. In an ecommerce context it usually means optimising the product listing data: titles, images, attributes, descriptions and feed quality across your store and marketplaces.

How do I improve my product page conversion rate quickly?

The fastest wins are almost always: add a sticky add-to-cart bar on mobile, show a concrete delivery date and shipping cost near the price, place star ratings under the product title, add three more images including a scale reference, and remove any script that slows the page. These can typically be shipped in a week. Reference: https://apptweak.com.

Is Apple’s Product Page Optimization the same thing?

No. Apple’s Product Page Optimization (PPO) is an App Store Connect feature that lets app publishers A/B test up to three alternate treatments of their app icon, screenshots and previews against the original listing, with results reported by conversion rate. It applies only to App Store listings, not to ecommerce product pages. The underlying philosophy is the same though: test your visual assets rather than guessing.

How many images should a product page have?

Six to ten for most categories, including at least one scale reference, one detail macro, one lifestyle shot and ideally a short video. Fashion, furniture and technical equipment usually justify the higher end of that range.

Should reviews go above or below the product description?

Show the star rating and review count above the description, immediately under the title, with an anchor link. Place the full review content below the description so it does not push the buy box and key specifications down the page. It is argued more carefully on mobileaction.co.

How long should a product description be?

Long enough to answer every purchase objection, structured so nobody has to read all of it. In practice, 150 to 300 words of scannable copy plus expandable sections and a specification table works for most products. Complex or high-ticket items justify significantly more.

Need a second pair of eyes on your product template?

Most stores lose sales in the same three or four places, and they are rarely the places the owner suspects. If you would like a structured product page optimization audit of your store, with a prioritised list of fixes and expected impact, get in touch with our team and we will take a look at your top-selling pages.

Most accessibility checklists are written for developers. They talk about ARIA roles, semantic landmarks and success criterion 1.4.11, and they assume you already know what a screen reader does. If you own a small business and just want to know whether your site is going to get you sued or lose you customers, that is not much help.

This website accessibility checklist is different. It is written for the person who paid for the site, not the person who built it. You can work through it yourself, on your own site, in about ninety minutes, using nothing but a browser and a keyboard. At the end you will have a list of problems you can hand to your developer, along with a rough sense of how urgent each one is.

Why This Matters (The Short Version)

Two reasons: legal exposure and lost revenue.

Legal. Accessibility is no longer a nice-to-have in most markets. In the European Union, the European Accessibility Act obligations became applicable in June 2025 and now cover e-commerce, banking, transport ticketing and a range of consumer-facing digital services. In the United States, the Department of Justice rule under Title II of the ADA set WCAG 2.1 Level AA as the technical standard for state and local government entities, with compliance dates falling in 2026 and 2027, and private businesses under Title III continue to face thousands of web accessibility lawsuits every year. The UK Equality Act 2010 and Canada’s Accessible Canada Act create similar duties. The common thread in nearly all of them is the same reference document: the Web Content Accessibility Guidelines, or WCAG, at Level AA.

Commercial. Roughly one in six people worldwide lives with a significant disability. Add temporary and situational limitations (a broken wrist, bright sunlight on a phone screen, a noisy train, a 62-year-old’s eyesight) and the number of people affected by a badly built site on any given day is far larger. Every one of these barriers is a person who wanted to buy from you and could not.

There is a third reason nobody mentions: almost everything on this list also improves your SEO. Headings, alt text, descriptive links and clean page titles are exactly what search engines parse.

How to Use This Checklist

1. Pick your five most important pages: homepage, a service or product page, contact page, checkout or enquiry form, and your most-read blog post or FAQ.
2. Work through the checklist below on each one.
3. Mark each item Pass, Fail or Not sure.
4. Send the Fail and Not sure items to your developer, quoting the item number.

You do not need to install anything. Two free browser tools will make it faster, though: WAVE (wave.webaim.org) and the Lighthouse panel that is already built into Chrome. Both catch a portion of issues automatically. Neither replaces the manual checks below, because roughly two thirds of accessibility problems can only be found by a human.

Section 1: Colour and Visual Design (Items 1 to 4)

1. Text has enough contrast against its background

What to check: Look at your body text, your button labels, your footer, and any text sitting on top of a photo or coloured banner. Light grey text on white is the single most common failure on small business websites, usually because a designer thought it looked elegant.

The rule: normal text needs a contrast ratio of at least 4.5:1. Large text (roughly 24px, or 19px if bold) needs 3:1.

How to test without technical skills: use the free WebAIM Contrast Checker, paste in your text colour and background colour hex codes (your developer or your brand guidelines will have them), and read the pass or fail result.

Why it matters: this is the most commonly cited issue in accessibility demand letters, and it affects anyone over 40 reading your site on a phone outdoors.

2. Colour is never the only way you communicate something

What to check: Do you have “required fields in red”? A pricing table where the recommended plan is only marked by a green border? A chart where the lines are distinguished purely by colour? Links inside paragraphs that are a different colour but not underlined?

The fix is usually trivial: add an asterisk, a label, a pattern, an icon, or an underline.

Why it matters: around 1 in 12 men has some form of colour vision deficiency. They are not a niche audience.

3. The site still works at 200% zoom

What to check: press Ctrl and + (Cmd and + on Mac) five or six times until the page is at 200%. Then read it. Does text overlap? Do buttons fall off the screen? Does a horizontal scrollbar appear that forces you to scroll left and right to read a sentence? Does a fixed header eat half the screen?

Why it matters: magnification is the single most used accessibility adjustment on the web, far more common than screen readers.

4. You can always see where you are when tabbing

What to check: click on the very top of a page, then press the Tab key repeatedly. A visible outline or highlight should move from link to link to button. If the outline disappears, or you cannot tell what is selected, you have a failure.

Common cause: a designer or theme added outline: none to the CSS because they thought the blue ring was ugly. This is one of the most damaging one-line decisions in web design.

Section 2: Images, Video and Media (Items 5 to 7)

5. Meaningful images have useful alt text

What to check: in WordPress, Shopify, Wix or Squarespace, open your media library or click each image and look at the “alternative text” field. Is it filled in? Is it actually descriptive?

Image	Bad alt text	Good alt text
Photo of your team	IMG_4471.jpg	Our six-person team outside the Bristol workshop
Product shot	product image	Walnut dining chair with black steel legs, side view
Logo in header	logo	Peter Avey, home
Text inside a graphic	banner	The exact words shown in the graphic

Rule of thumb: if you removed the image and the page lost meaning, describe it. Keep it under about 125 characters. Do not start with “image of”, the screen reader already announces that.

6. Decorative images are marked as decorative

What to check: background flourishes, dividers, abstract shapes and stock photos that add nothing should have an empty alt attribute, not a description. Most CMS platforms have a “mark as decorative” tick box.

Why it matters: a screen reader user forced to listen to “blue swirl graphic, blue swirl graphic, blue swirl graphic” will leave your site.

7. Video has captions and audio has a transcript

What to check: every embedded video with speech needs accurate captions. Auto-generated YouTube captions are a starting point but they are not compliant on their own because of accuracy and punctuation problems. Edit them. Podcasts and audio need a text transcript on the page.

Bonus: transcripts are indexable text, so this item pays for itself in search traffic.

Section 3: Structure and Navigation (Items 8 to 11)

8. Headings follow a logical order

What to check: every page should have exactly one H1 (the page title). Sub-sections use H2, sub-sections of those use H3, and so on. You should never jump from H2 to H4. And headings should never be chosen because of how big the text looks, which is the mistake almost every non-technical editor makes.

Quick test: install the free “HeadingsMap” browser extension, or simply read your page’s outline in the WordPress block editor’s document overview panel. If the outline reads like a sensible table of contents, you pass.

Why it matters: screen reader users navigate by jumping between headings the way sighted users skim. A broken heading structure means they have to listen to the whole page in order.

9. Link text makes sense on its own

What to check: scan your page for the words “click here”, “read more”, “learn more” and bare URLs. Assistive technology can list every link on a page in isolation. A list of fourteen links all saying “read more” is useless.

• Instead of: To see our pricing, click here.
• Write: See our pricing and packages.

Also flag any link that opens a PDF or a new window without warning you.

10. The entire site works with a keyboard only

This is the most revealing test on this list and it costs you nothing.

What to do: put your mouse to one side. Using only Tab, Shift+Tab, Enter, Space and the arrow keys, try to:

1. Open your main navigation menu, including any dropdown submenus
2. Reach and activate your primary call-to-action button
3. Open and, crucially, close any popup, cookie banner or newsletter modal
4. Complete your contact form and submit it
5. Add an item to the cart and reach checkout, if you sell online

Red flags: focus getting trapped inside a popup with no way out, dropdown menus that only open on hover, a custom slider or date picker you cannot operate, or focus jumping to a strange place after you close something.

11. There is a “skip to main content” link

What to check: load your homepage, click at the very top, press Tab once. In a well-built site, a small link saying “Skip to content” appears. Without it, a keyboard user has to tab through your entire navigation menu on every single page. canada.ca goes into the numbers.

Section 4: Forms (Items 12 to 14)

Forms are where money changes hands, so failures here are the most expensive on your whole site.

12. Every field has a visible, permanent label

What to check: click into each field and start typing. Does the label disappear? Placeholder-only forms (where the grey text inside the box is the only label) fail on two counts: the text vanishes when you type, and placeholder grey usually fails contrast. Labels should sit above or beside the field and stay there.

Second test: click on the label text itself. In a correctly coded form, clicking the word “Email” puts the cursor into the email box. If nothing happens, the label is not properly connected and screen readers will not announce it.

13. Errors are explained in words, next to the problem

What to check: submit your form with deliberate mistakes: blank required fields, a malformed email address, a phone number with letters in it.

• Does an error message appear in text, not just a red border?
• Does it say what is wrong and how to fix it (“Enter a date in the format DD/MM/YYYY”) rather than just “Invalid”?
• Does the message sit next to the field that caused it?
• Is the user’s already-entered data preserved rather than wiped?

14. Nothing moves, autoplays or times out on you

What to check: carousels that rotate automatically, videos that play with sound on load, animated backgrounds, and session timeouts on booking or checkout pages. A comparable breakdown sits on a11yproject.com.

• Any motion lasting more than five seconds needs a visible pause control.
• Nothing should flash more than three times per second, ever.
• Time limits need a warning and an option to extend.

Why it matters: beyond compliance, auto-rotating hero sliders have measurably poor conversion rates. Removing one often improves both accessibility and sales.

Section 5: Content, Code Basics and Governance (Items 15 to 18)

15. Page titles and language are set correctly

What to check: look at your browser tab on each page. Does it say something unique and descriptive (“Contact Us | Peter Avey”) or does it say “Home” on all nine pages? Unique page titles are both an accessibility requirement and a basic ranking factor.

Language: your site needs to declare its language in the code so screen readers use the right pronunciation. Ask your developer to confirm the lang attribute is set. If you have pages in a second language, they need their own declaration.

16. Text is readable and written in plain language

• Body text at 16px minimum
• Paragraphs left-aligned, not justified (justified text creates rivers of white space that are hard to track)
• Short paragraphs, generous line spacing
• Expand acronyms the first time you use them
• Avoid idioms and heavy metaphor where a plain word will do

This item helps everyone: people with dyslexia, people with cognitive disabilities, non-native speakers, and anyone reading on a phone while distracted, which is most of your audience.

17. It works on a phone, including touch targets

What to check: open the site on an actual phone. Are buttons and links big enough to hit with a thumb (aim for at least 24 by 24 CSS pixels, ideally 44 by 44)? Are two links so close together that you keep tapping the wrong one? Does the site work in both portrait and landscape, since some users have their device fixed in a mount?

18. You have an accessibility statement and a way to report problems

What to check: do you have a page that states which standard you are working towards (WCAG 2.2 Level AA is the current benchmark), what you know is not yet fixed, and how someone can contact you if they hit a barrier?

Why it matters: in the EU this is a formal requirement for many organisations. Everywhere else, a dated, honest statement with a working contact route demonstrates good faith and is frequently the difference between a complaint that gets resolved by email and one that gets escalated.

Warning about overlays: the plugin widgets that promise “instant ADA compliance” for a monthly fee do not fix underlying code, are frequently detected and bypassed by screen reader users, and companies using them have still been sued. Treat them as a red flag, not a solution.

Priority Table: What to Fix First

Priority	Checklist items	Typical effort
Critical (fix now)	10 Keyboard access, 12 Form labels, 13 Error messages, 1 Contrast, 5 Alt text	Hours to a few days
High	4 Focus indicator, 8 Headings, 9 Link text, 14 Motion and timeouts, 3 Zoom	Mostly quick CSS and content edits
Medium	2 Colour dependence, 7 Captions, 11 Skip link, 15 Titles and language, 17 Touch targets	Ongoing content work
Governance	6 Decorative images, 16 Plain language, 18 Accessibility statement	Policy and process

What to Send Your Developer

A vague “can you make the site accessible” brief produces a vague quote. Instead, send something like this:

• The page URL for each failure
• The checklist item number from this article
• A screenshot or a one-line description of what you saw
• Your target: WCAG 2.2 Level AA
• A request that they retest with a real screen reader (NVDA on Windows or VoiceOver on Mac) rather than relying on automated scores alone

Ask for a fixed-price remediation on the critical items first, then a smaller retainer or an annual re-audit. Accessibility is not a one-time project, because every new blog post, product photo and landing page can reintroduce problems.

Keeping It Accessible After Launch

1. Add alt text and heading checks to your content publishing routine. Two extra minutes per post.
2. Run WAVE or Lighthouse on any new template before it goes live.
3. Re-run this full 18-item checklist twice a year, and after any redesign or theme update.
4. Test any new third-party tool (booking widget, chat bot, review plugin, payment embed) with the keyboard before you install it. Third-party embeds are the most common source of new failures on otherwise compliant sites.

Frequently Asked Questions

Which WCAG version should a small business aim for in 2026?

WCAG 2.2 at Level AA. It is the current W3C recommendation and is backward compatible with 2.1 AA, which is the version written into most current legislation. If you meet 2.2 AA, you meet 2.1 AA.

Can I just run an automated scan and be done?

No. Automated tools reliably catch around 30 to 40 percent of issues, mostly contrast and missing alt attributes. They cannot tell you whether your alt text is meaningful, whether your keyboard order makes sense, or whether your error messages are understandable. The manual checks in this list are the ones that matter most.

Do accessibility overlay widgets make my site compliant?

They do not. Overlays sit on top of existing code and cannot repair structural problems such as missing form labels or broken keyboard navigation. Numerous businesses using overlays have still received legal complaints, and many disabled users actively disable them. Fix the underlying site.

How much does it cost to fix a small business website?

For a brochure site of 10 to 20 pages built on a mainstream platform, the critical items on this list are usually a few days of developer time. Costs rise sharply for custom e-commerce, booking systems and interactive tools. Fixing issues before launch is dramatically cheaper than retrofitting later, which is the entire point of self-auditing now.

Does accessibility actually help SEO?

Yes, in overlapping areas. Descriptive alt text, logical heading hierarchy, unique page titles, meaningful link text, video transcripts and fast mobile-friendly layouts are all things search engines use. Accessibility work and technical SEO work are not the same job, but they share a lot of the same tasks.

My site is on Wix, Squarespace or Shopify. Am I covered?

Partly. Mainstream platforms have improved their core templates, but the accessibility of your specific site still depends on the theme you chose, the apps you installed, and the content you added. Every item on this checklist still applies to you.

Next Step

Work through the 18 items on your five key pages this week. Most business owners find between six and ten failures on a first pass, and roughly half of them are content fixes they can make themselves in an afternoon. The rest is a short, specific brief for a developer, which is a far better position than a vague worry about compliance.

This article is general guidance, not legal advice. Requirements vary by country, sector and organisation size. If you are unsure of your obligations, speak to a qualified adviser in your jurisdiction.