The website design questionnaire that shapes the build
A website questionnaire is only useful if its answers change something: a line in the proposal, a page in the sitemap, a requirement in the build. This one has 36 questions in eight sections, and next to each is the decision it feeds, so you can cut the ones your projects never use.
By Raj Kumar, Founder, Zunoform

Short answer
A website design questionnaire should cover eight areas: the business, the audience, goals, content, features, SEO, technical setup, and budget and timeline. Each answer should map to a proposal line or a build decision. Redesigns need extra questions about URLs, integrations and data that must survive the move.
- Send it before you write the proposal, not after kickoff.
- Branch it: new sites skip the migration questions.
- Ask who writes and approves each page's content; the timeline depends on it.
- Never collect hosting or CMS passwords in the form.
What is a website questionnaire, and when should you send it?
A website questionnaire (also called a website design questionnaire or web design client questionnaire) is the set of questions a client answers before a site is scoped and priced. Most agencies send a short version with the first inquiry and a fuller version once the client is serious enough to expect a proposal.
The fuller version is a discovery tool, not a design brief. The UK government's service manual makes the same point about digital projects generally: understand the problem, users and constraints first, and do not start building during discovery. Treat the answers as evidence for a proposal you will then discuss, not as a specification the client has signed.
Source: GOV.UK Service Manual: How the discovery phase works
36 website questionnaire questions, by section
The right-hand column is where the answer ends up. If you cannot name a destination for a question, drop it.
| Section | Question | What the answer changes |
|---|---|---|
| Business | What does the organization do, and for whom? | Homepage headline and service page structure |
| Business | What makes you the better choice over the alternatives customers compare you with? | Messaging hierarchy; which proof points get prominence |
| Business | Which three competitor or peer sites should we look at, and what do you like or dislike about each? | Design references; features to match or avoid |
| Business | Do you have brand guidelines, logo files and fonts? | Whether brand work is a prerequisite line item |
| Audience | Who are the main visitor groups? | Navigation and separate journeys |
| Audience | What is each group trying to do when they arrive? | Primary calls to action per page |
| Audience | What questions do customers ask before buying or booking? | FAQ content and service page sections |
| Audience | Which languages, regions or devices matter most? | Translation scope; mobile-first priorities |
| Goals | What should the new site change for the business? | Success criteria in the proposal |
| Goals | Which single action matters most (call, booking, purchase, sign-up)? | Conversion design and tracking setup |
| Goals | How will you measure success, and what is the current baseline? | Analytics configuration; reporting line item |
| Goals | What is wrong with the current site, specifically? | Redesign priorities; what not to repeat |
| Content | Which pages must exist at launch, and which can wait? | Sitemap and phase boundary |
| Content | Who writes, supplies and approves copy for each page? | Copywriting line item; content deadlines in the timeline |
| Content | Do you have photography and video, and who owns the rights? | Photography or stock budget |
| Content | How often will content be updated, and by whom? | CMS choice and editor training |
| Features | Which features are needed: forms, booking, shop, member area, search, blog? | Build estimate; third-party costs |
| Features | Which tools must the site connect to (CRM, email, payments, booking)? | Integration line items |
| Features | Do you need to take payments online, and in which currencies? | Payment provider setup; checkout scope |
| Features | Are there legal features to include (cookie consent, terms, accessibility statement)? | Compliance tasks and who drafts the text |
| SEO | Which search terms do customers use to find you today? | Page titles and content priorities |
| SEO | Do you have access to Search Console and analytics data? | Baseline for the migration plan |
| SEO | Which pages bring most traffic or leads now? | Pages to protect in a redesign |
| SEO | Do you serve local areas that need their own pages? | Location page scope |
| Technical | Is this a new site or a redesign of an existing one? | Branches the migration questions |
| Technical | Where is the domain registered and the site hosted, and who has admin access? | Launch plan; access requests |
| Technical | Do you have a preferred platform, or one you must avoid? | CMS decision; build method |
| Technical | Which accessibility standard, if any, must the site meet? | Design and QA requirements |
| Technical | Who will maintain the site after launch? | Support retainer or handover training |
| Technical | What must carry over: URLs, documents, integrations, user accounts? | Migration and redirect work |
| Budget and timeline | What budget range is set aside for this project? | Scope options (good, better, best) |
| Budget and timeline | Is there separate budget for hosting, plugins, stock media or copy? | Which costs sit outside your fee |
| Budget and timeline | What is the target launch date, and what depends on it? | Hard versus soft deadline |
| Budget and timeline | Who approves the design and the finished site? | Review rounds in the schedule |
| Budget and timeline | How many people will give feedback, and who consolidates it? | Revision limits in the contract |
| Budget and timeline | What would make this project a failure for you? | Risks to address in the proposal |
Question wording is original to this guide. Show the ‘Technical: what must carry over’ and ‘Goals: what is wrong with the current site’ questions only to redesign projects.
How do questionnaire answers map to the proposal?
Illustrative mapping. Each answer pattern becomes a scope line, a price driver or an assumption you state in writing.
| Answer pattern | Proposal line | Build decision |
|---|---|---|
| Client writes all copy, no writer named yet | Content deadline and a copywriting option | Design with realistic placeholder lengths |
| 12 service pages, 4 needed at launch | Phase 1 and Phase 2 scopes priced separately | Templates built for the other 8 |
| Booking and CRM connection required | Integration line item with named tools | Test submissions end to end before launch |
| Redesign of a site with years of blog posts | URL audit and redirect mapping | Redirect map signed off before switch-over |
| Sells online to EU consumers | Accessibility review and statement | WCAG-based QA pass in the schedule |
| Five people give feedback, no consolidator | Revision rounds defined; one named approver | Feedback collected in one place per round |
| Budget below the feature list | Priced options, not a discounted everything | Phase the features |
What extra questions does a website redesign need?
A redesign carries risks a new site does not: losing pages that bring traffic, breaking links other sites point to, and dropping integrations nobody remembered. The questionnaire cannot solve those, but it can make sure someone is assigned to them.
Google's own guidance on site moves is to map every old URL to its new equivalent, starting with the important ones from sitemaps, logs and analytics, to use permanent server-side redirects, and to keep them for at least a year. So ask: which pages bring the most traffic and leads, who has Search Console access, and who owns the redirect map. If the answer to the last one is nobody, that is a line item.
Which accessibility and performance questions should you ask?
Ask which accessibility standard applies rather than assuming. WCAG 2.2 is the current W3C Recommendation and the usual reference. Some clients have a legal reason to name one: in the US, the Department of Justice's 2024 rule requires state and local governments to meet WCAG 2.1 AA, with deadlines extended in April 2026 to April 2027 for larger entities and April 2028 for smaller ones. In the EU, the European Accessibility Act has applied since June 28, 2025 to services such as online shops, with an exemption for service micro-enterprises (fewer than 10 staff and under €2 million turnover).
For performance, agree targets you can test. Google's Core Web Vitals give concrete ones: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. A questionnaire answer like ‘fast’ is not a requirement; one of those numbers is.
Source: W3C: Web Content Accessibility Guidelines (WCAG) 2.2
Source: ADA.gov: Fact sheet on the Title II web and mobile app rule
Source: Your Europe: Accessibility requirements for products and services
Source: Google Search Central: Understanding Core Web Vitals
How do you ask about budget and timeline?
Use ranges. Four or five bands in the client's currency, plus ‘not sure yet’, get more honest answers than an empty number field, and let you shape a proposal with options instead of one take-it-or-leave-it price.
For timing, the useful question is not ‘when do you want it?’ but ‘what depends on the date?’ A trade show or product launch makes a date fixed; ‘before summer’ does not. Pair it with who approves the design, because approval time is the part of the schedule you control least.
Before you send the questionnaire
- Every question has a destination in the proposal or build.
- New-site clients never see redesign questions.
- Budget and timeline questions use ranges and reasons.
- The form asks who grants access, not for passwords.
- Long-text answers have examples in the help text.
- A named person will review answers within two working days.
Website templates to start from
The website design questionnaire template asks whether there is an existing site and only then asks for its URL.
Define a website's goals, page scope, content ownership and launch requirements before design begins.
Project type, page count, features, platform, and existing assets for scoping a website build.
Collect one page's copy, image links, approval state and content owner for a website build.
Collect positioning, audience, brand values and visual references before a brand strategy workshop.
Package final deliverables, transfer responsibilities, outstanding work and training needs into a client handoff record.
Where Zunoform fits (and where it doesn't)
Zunoform handles the questionnaire itself: conditional logic to hide redesign questions from new-site clients, file upload for logos and existing content (10 MB per file on Free, 100 MB on Pro), a document layout that reads like a brief with questions inline, partial responses saved as the client goes, and a meeting scheduler question to book the follow-up call. Answers can flow into Google Sheets on every plan.
It will not audit a current site, map redirects or write the proposal. Free is capped at 500 responses a month, which is plenty for client questionnaires but worth knowing; Google Forms has no monthly cap if all you need is a plain list of questions.
Questions people ask
What questions should I ask a client before designing a website?
Ask what the business does and for whom, what visitors need to do, what the site should change and how success will be measured, which pages are needed at launch, who writes and approves content, which features and integrations are required, whether it is a redesign, the budget range, the launch date and what depends on it, and who approves the work.
How long should a website design questionnaire be?
Around 20 to 30 visible questions is workable for a client who expects a proposal. A 36-question bank like this one shrinks to that with branching: new-site clients skip migration questions, and simple brochure sites skip e-commerce and member-area questions. For a first inquiry, send only five to eight.
What is the difference between a website questionnaire and a website brief?
The questionnaire collects the client's inputs. The brief is what your team writes after reviewing them: agreed goals, page list, features, constraints, owners and dates. Clients sometimes call the questionnaire a brief; the distinction matters because the brief is the document both sides agree to.
Should the website questionnaire ask about SEO?
Yes, briefly. Ask which search terms customers use, which pages currently bring traffic or leads, and who has Search Console and analytics access. For a redesign those answers decide which URLs need redirects. Detailed keyword research belongs in a separate SEO engagement, not the questionnaire.
Should I send the questionnaire before or after the discovery call?
Before. Clients answer factual questions (pages, features, dates, budget) better in writing, and you arrive at the call with the gaps already visible. Use the call for trade-offs the form cannot resolve, like conflicting priorities between stakeholders or a budget that does not match the feature list.
Is there a free website questionnaire template?
Yes. Zunoform's website design questionnaire template is free to use on the free plan and asks for a current URL only when there is an existing site. Jotform and other form builders also publish templates. Whichever you use, edit it so every question maps to a decision you will make; unedited templates tend to ask about favorite colors and little else.
Raj Kumar · Founder, Zunoform
Raj Kumar is the founder of Zunoform, the form builder made by Symphonic Grow. He builds the product and writes these guides, checking every competitor price and feature claim against the vendor's own pages before publishing.
Raj Kumar on LinkedInKeep reading
Agency operations
Branding process
Agency workflow
Agency guides
Agency operations

Ready when you are
Better forms.
Better data.
Start with a conversation, a document or a single page.
Unlimited forms and 500 responses per month on Free.
No card required.
- No credit card
- Unlimited forms
- 500 responses / month