The questions that matter
Ask these before you hire.
Use the answers to judge scope and fit—not a generic promise to rank first for every keyword.
01 / Discovery and local intentWho will find this website, and why?
Ask how a developer will organize public documents, accessibility obligations, program information and visitor-facing calls to action. A content migration must account for established documents and the URLs people rely on.
Ask the builder to show which customer questions deserve a dedicated page, which need a FAQ, and which belong in a booking or contact flow. The map should follow actual services and travel logistics, not only a list of search phrases.
02 / Structure and editingWhat must the website actually do?
For a civic organization, test search, downloadable material and mobile readability. For an attraction or operator, emphasize timing, pickup details, booking and changes to service caused by schedules or weather.
Confirm who maintains the information, how visitors interact with it, and what integrations are genuinely needed. Use a content model and design system that editors can keep current.
03 / Proof and launchHow will you judge the work?
Review whether the studio has handled document-heavy websites or transactions. Require a plan for readable typography, alternate text, plain-language navigation and a content owner after launch.
Before launch, review mobile pages, form delivery, major URL redirects, accessibility and the ownership of your domain, source code, analytics and accounts. Request dated evidence for any claimed traffic or performance gain.