Web development FAQs: scope, ownership, mobile use, and launch checks
Questions to ask when planning a service-business website, including forms, content, accessibility, ownership, and maintenance.
By SIFTRIXWhat should a website brief include?
List the audiences, pages, services, and actions visitors need to complete. Identify the destination for every form submission and who follows up. Separate launch requirements from later ideas. A short site map and a written description of each key user journey help establish a realistic scope.
Does a website package include copy, photos, and hosting?
Not necessarily. Ask for those responsibilities to be listed separately, along with domain management, email, analytics, and ongoing costs. Confirm who provides the content and what happens if it is late. A page count alone does not tell you what is included in delivery.
Who should control the domain and site accounts?
Agree on account ownership, administrative access, and handover arrangements before work begins. Ask how you can export content or move the site later. Keep business access under accounts you control, and request a clear process for granting contractors only the access needed for their work.
What should be tested before launch?
Test the main pages and forms on desktop and mobile, including error states and confirmation messages. Verify that an actual test enquiry reaches its intended inbox. Check links, headings, readable text, and key keyboard interactions. Review accessibility during development; W3C guidance describes structured evaluation rather than treating one automated score as proof.
Will a new website automatically rank in Google?
No. Google’s SEO guidance explains how useful content, discoverability, and technical accessibility help search engines understand a site, but a new design does not guarantee indexing or rankings. Ask which search-related work is included and how its results will be checked separately from the design approval.
What maintenance should I plan for?
Ask who handles software updates, form failures, content changes, backups or recovery, and account access changes. Define the support response and what work costs extra. Keep a record of integrations and renewal responsibilities so a future business change does not leave a form or service connected to an unused account.