All website guides in one quiet place.

Start with a single shared folder. Put approved logo files, the current service list, contact details and permitted photos inside it. Mark anything that is a draft so it cannot accidentally become a published claim.

• Name the person who approves copy.
• Record which photos may be published.
• Confirm the enquiry inbox before the build begins.

Consistency is something visitors can check. Compare your business name, phone, prices and service descriptions across the homepage, footer and social profiles. Resolve contradictions before adding more badges or animations.

• Use recognisable button labels.
• Make contact information easy to find.
• Publish only credentials and reviews you can support.

Agree a task list and cadence. A maintenance arrangement might include a monthly review of contact forms, broken links and outdated content, plus a defined allowance for edits. Separate urgent incident response from routine changes.

• Record response expectations in writing.
• Keep backups appropriate to the platform.
• Treat major features as separate scope.

Choose the route your team will actually monitor. A short WhatsApp conversation may suit a simple enquiry; a form can gather a project URL and requirements before a callback. Neither helps if nobody owns the response.

• Ask only for information needed to reply.
• Explain the expected next step.
• Send an agreed test message before launch.

Read the website in the order a phone visitor encounters it. A desktop layout squeezed into a narrow screen can place useful information after oversized imagery. Prioritise the offer, key details and the contact action.

• Check text without zooming.
• Keep buttons comfortably separated.
• Check that fixed bars do not cover content.

Pick one customer task and attempt it from the homepage without shortcuts. Note each point where the next action is unclear. An audit is stronger when it describes a specific obstacle instead of calling the design old.

• Check a phone and a desktop.
• List missing business information.
• Prioritise problems that block an enquiry.

A redesign has a purpose when the site no longer explains the offer or supports a necessary customer task. First inventory existing pages and useful content. Some issues can be solved with focused edits rather than a full rebuild.

• Keep useful URLs where possible.
• Agree the problem before the visual direction.
• Plan redirects for necessary URL changes.

Compare quotes against the same scope: pages, custom features, content work, revisions and handover. A low build price may exclude the integration or editing access you need. Recurring bills deserve their own line.

• Separate hosting and domain renewals.
• Confirm responsibility for copy and images.
• Ask what changes cost after launch.

A schedule depends on content, approvals and access. Mark the date each input is needed and the person responsible. If a decision is late, update the delivery estimate rather than hiding the impact until launch day.

• Agree review windows.
• Keep one consolidated feedback list.
• Confirm the final launch checklist together.

A QR menu is useful when it opens a readable menu directly. Keep the destination under an account the business controls, and plan how prices and unavailable items will be updated. Print quality and table lighting affect scanning.

• Test the printed code on multiple phones.
• Show prices and categories clearly.
• Offer a readable alternative for guests who cannot scan.

A booking page should distinguish a request from a confirmed reservation. Ask for the required date, time and party size, then explain who confirms availability. A form success message alone is not a table allocation.

• Send requests to a monitored destination.
• Explain confirmation and changes.
• Test the whole flow with staff before launch.

A catalogue lets a business show products and gather enquiries without operating a payment system. A real store adds inventory, payments, fulfilment and customer support responsibilities. Choose the model the business can operate reliably.

• Label enquiry-only flows accurately.
• Keep product information current.
• Do not represent a demonstration cart as a paid order.

Write the answers you give customers in conversation. State what you offer, who it is for, what affects the price and what happens next. Replace claims such as “best quality” with details a visitor can evaluate.

• Use actual services and locations.
• Explain exclusions in plain language.
• Read the copy aloud to catch vague wording.

A portfolio concept can demonstrate layout and interaction skills without being a commissioned project. Explain the design goal and show the working features. Keep demonstration brands separate from testimonials supplied by actual clients.

• Identify the work as a concept where relevant.
• Explain simulated forms or checkout.
• Do not invent traffic, revenue or conversion results.

Review the final deployed address, not only a local preview. Check the main customer journey, important pages and contact destinations. Make sure the team has the access and instructions needed after handover.

• Test a permitted enquiry end to end.
• Check links and images.
• Confirm current titles, sitemap and indexing settings.

A useful article answers a question your customers actually ask. Choose a specific decision, provide an example and explain the next step. A handful of maintained articles is easier to support than a large library of repeated summaries.

• Give a full article its own link.
• Connect it to a relevant service.
• Review the content when your advice or offer changes.

Choose references for identifiable reasons: readable menus, a calm colour palette or clear product browsing. Describe the audience and information hierarchy before choosing decorative effects. Use reference sites for direction rather than copying their assets or text.

• Agree typography and colours early.
• Use permitted images.
• Check the design on normal phones as well as large screens.