Begin with the job the website must do
A website can introduce a company, generate leads, sell products, support clients, present a portfolio, publish information, or operate as part of a wider business system.
The development company should understand the objective before discussing pages, colors, or animations. A visually impressive site can still fail when visitors cannot understand the offer or take the next step.
Decide whether you need a redesign or a correction
Not every weak website needs to be replaced. The problem may be outdated content, poor mobile performance, unclear services, slow hosting, broken forms, weak search setup, or missing proof.
A useful audit should distinguish between a visual refresh, content improvement, technical rebuild, conversion project, and complete new website.
Review websites with similar requirements
Look beyond appearance. Test the sites on a phone. Open service pages. Use the forms. Review speed, navigation, readability, and clarity.
Ask what the developer was responsible for. A portfolio item may involve design, coding, strategy, content, hosting, or only one part of the final site.
A professional business website needs more than a homepage
Most established businesses need a clear company definition, service pages, About and leadership information, proof of work, reviews, contact routes, legal pages, mobile accessibility, search foundations, analytics, and a secure technical structure.
Additional needs may include a newsroom, articles, booking, ecommerce, client portals, application features, or AI support.
Content and design should be planned together
Design controls how the information is experienced. Content determines what the visitor understands.
The proposal should identify who writes the copy, who provides facts and images, how approvals work, and whether search-focused page structure is included. Placeholder text should not survive into the final site.
Check the technical foundation
Ask about mobile responsiveness, browser support, accessibility, speed, security, backups, forms, analytics, redirects, canonical settings, structured data, sitemap creation, and search indexing.
The developer does not need to promise rankings. The site should still be built so search systems can access and understand it.
Understand the development process
A clear process may include discovery, sitemap, content planning, design direction, development, review, testing, launch, and post-launch support.
The agreement should explain how many revisions are included, how major scope changes are handled, and who gives final approval.
Ask what happens after launch
Websites need updates, security maintenance, backups, content changes, and technical support. Hosting and maintenance may be included, optional, or managed by another provider.
The client should understand response times, ongoing fees, software licenses, and the process for transferring the website if the relationship ends.
Know when appearance is hiding a business problem
A good-looking site may still fail because the offer is unclear, there is no evidence, calls to action are weak, traffic is missing, or enquiries receive no follow-up.
The website company should be able to identify which problems belong to the site and which require marketing, sales, or operational work.
Choose a partner that can connect the website to the objective
The best website is not the one with the most movement or the largest number of pages. It is the one that explains the company, supports trust, works properly, and gives the intended audience a clear path forward.