What every business website must contain

Display the registered name, address, registration number, tax number and verified contact details wherever your legal form, activity and sales model require them. The exact obligations vary, so confirm the final list against current rules and professional advice. Clear details in the footer and contact page also help customers understand who operates the website.

HTTPS is the baseline for a business website. Also verify the redirect from HTTP, server and application updates, form validation, restricted administrative access, security headers and a clear error-reporting path. A certificate encrypts the connection; it does not make the whole application secure by itself.

Visitors expect a usable mobile layout and prompt loading on an ordinary connection. The page should not jump while loading, create horizontal overflow or hide essential content behind animation. Correct image dimensions, responsive formats and delayed loading of heavier media often provide the largest practical gains.

State the offer, intended customer and primary action early. Give each important service enough space to answer real questions. Use relevant work, verified testimonials and authentic photography where they are available. Every page should offer a clear next step, such as a phone call, message, booking or accessible enquiry form.

A business serving local customers should keep its real name, address or service area, phone, opening hours and website consistent across the site and Google Business Profile. Location pages make sense only when they contain useful, truthful information for that area. Do not invent offices, references or local results.

Essential storage may support basic functions, while optional analytics and marketing tools require the appropriate legal basis and visitor choice. The privacy notice should explain which data the site receives, why it is processed, how long it is kept and whom the user can contact. Check the legal requirements against the actual website configuration and business.

Confirm who controls the domain, code repository, hosting, analytics and third-party accounts. Backups should exist outside the main server, cover the database and uploaded files, and be restored in a test rather than merely assumed to work. The handover should state how access, updates, incidents and a future provider change will be handled.