Choosing a website developer: a supplier checklist

Check whether a supplier can handle the requirements of your project. Ask to see a comparable order form, catalogue or customer account and have them explain how support and bug fixes work.

Agree on the work before signing

Describe the visitor's main journey and what staff should do when an enquiry arrives. For each integration, name the system, data fields, direction of transfer and response to failure. For example, a website enquiry can be sent to KeyCRM; confirm the connection through documentation and a test request.

Assign responsibility for copy, photography and design approval. Agree on review time and record requirements for language versions and page editing.

Plan changes to an existing website

Request a page inventory and migration plan. Retain useful URLs and map redirects for addresses that change. Google's migration guidance covers redirects, internal links and checks after launch. A written plan gives you a concrete basis for discussing search traffic risks.

Test complete journeys

• A customer submits an order and sees a clear confirmation.
• The responsible employee receives all enquiry fields without duplicates.
• An editor updates a page through the content management system.
• The team demonstrates a backup and the recovery procedure.

The estimate should describe each stage's deliverable, terms for additional work and support scope. Before final payment, check that access and documentation have been handed over as agreed.

Related resources and services

• Main

Sources

• Google Search: site migrations
• KeyCRM