Website Discovery Questionnaire: 85 Questions to Scope Better Web Projects

Most website problems start before anyone opens Figma, WordPress, Webflow, Shopify, or a code editor.

The business wants “a better website.” The agency hears “new design.” The sales team needs better leads. Operations wants fewer junk inquiries. The owner wants the phone to ring. Nobody writes down what success actually means.

That gap is where budgets get chewed up.

A website discovery questionnaire is the simplest way to slow the project down before it gets expensive. It gives the client, designer, developer, marketer, and decision-maker the same set of facts before the estimate, sitemap, copy, wireframes, CMS setup, migration plan, and launch checklist are locked.

This is not paperwork for paperwork’s sake. PMI reported that 37% of organizations named inaccurate requirements as the primary reason for project failure. For web projects, weak requirements usually show up as vague page counts, missing integrations, unclear content ownership, no redirect plan, no tracking plan, and late arguments about what was “included.”

Use the questionnaire below before a redesign, rebuild, platform move, SEO project, or new business website. Copy it into a doc, trim what doesn’t fit, and make every stakeholder answer in plain language.

What a website discovery questionnaire should accomplish

A good discovery process answers four questions.

First, what business problem is the website supposed to solve? Second, what will users need to do on the site? Third, what must the team build, migrate, connect, track, and maintain? Fourth, what would make the project a success 90 days after launch?

That sounds obvious, but it gets missed. Nielsen Norman Group’s UX research guidance says stakeholder interviews help teams gather and understand business requirements and constraints. In a website project, those constraints are rarely limited to design taste. They include sales process, staffing, CMS comfort, compliance risk, hosting rules, approval layers, customer objections, and marketing goals.

The questionnaire also protects the numbers. Portent analyzed more than 27,000 landing pages and found that a B2B site loading in 1 second converted 3x higher than a site loading in 5 seconds. If performance is not discussed until launch week, the site can look finished while the business outcome is already compromised.

Accessibility is another good example. WebAIM’s 2026 Million report found 56.1 detectable accessibility errors per homepage across the top one million homepages. That does not mean every site has the same legal exposure or usability problem, but it does mean accessibility cannot be treated as a vague polish item after design approval.

Discovery turns hidden assumptions into decisions.

How to use this questionnaire

Do not send all 85 questions as a cold email and expect useful answers. That turns discovery into homework and guarantees shallow responses.

Use it in three passes:

1. Send the core business, audience, and scope questions before the first call.
2. Use the call to clarify answers, spot contradictions, and identify missing stakeholders.
3. Turn the final answers into a scope document, sitemap, content plan, measurement plan, and launch checklist.

For a small five-page service business website, you might answer the full questionnaire in one 60-minute call. For a redesign with SEO migration, CRM integration, ecommerce, member portals, or multiple departments, expect more than one discovery session.

Keep the answers specific. “More leads” is not a requirement. “Increase qualified quote requests from commercial property managers in Bucks County” is a requirement. “Modern design” is not a requirement. “Make emergency plumbing, drain cleaning, and water heater replacement easier to compare on mobile” is a requirement.

The 85-question website discovery questionnaire

Business goals and project context

1. What triggered this website project now?
2. What business problem should the new site fix?
3. What happens if you do nothing for another 12 months?
4. Which services, products, or locations matter most to revenue?
5. Which offers attract the best customers, not just the most inquiries?
6. What does a qualified lead look like for your team?
7. What makes a lead a bad fit?
8. What is the average value of a new customer, project, account, or booking?
9. How do people usually find you before they contact you?
10. Which competitors do prospects compare you against?
11. What do those competitors explain better than you do?
12. What should the website make easier for your sales or front-desk team?
13. What are the top three outcomes you want within 90 days of launch?
14. Who owns the final decision if stakeholders disagree?
15. What budget range has already been approved?

Audience, buyers, and decision-making

16. Who are the primary users of the website?
17. Who are the secondary users?
18. Are the buyer, user, and approver the same person?
19. What questions do prospects ask before they trust you?
20. What objections stop people from contacting you?
21. What proof do prospects need before they book, call, buy, or request a quote?
22. What industries, locations, company sizes, or customer types should the site prioritize?
23. What customer types should the site filter out?
24. What pages do prospects usually visit before contacting you?
25. What language do your best customers use when describing the problem?
26. What technical terms do insiders use that customers may not understand?
27. What makes your business safer, faster, easier, or less risky than alternatives?
28. What customer questions should the site answer before a human gets involved?
29. What trust signals matter most in your market, such as reviews, certifications, licenses, case studies, warranties, or photos?
30. What would make a first-time visitor hesitate?

Scope, pages, and content

31. What pages must exist at launch?
32. What pages would be nice to have later?
33. Which current pages should be kept, merged, rewritten, redirected, or removed?
34. Do you need separate pages for services, industries, locations, products, team members, FAQs, pricing, resources, or case studies?
35. Who will write the copy?
36. Who will approve the copy?
37. What existing content can be reused?
38. What content is outdated, inaccurate, thin, duplicated, or off-brand?
39. Do you have brand messaging, voice guidelines, photography, videos, logos, icons, or sales collateral?
40. What photos or videos need to be created before launch?
41. Are there legal, compliance, warranty, medical, financial, or franchise requirements for the copy?
42. What claims need proof before they appear on the site?
43. What calls to action should appear on the main pages?
44. What should happen after a visitor submits a form?
45. What content will the client team maintain after launch?

SEO, migration, and findability

46. Which pages currently get the most organic traffic?
47. Which pages currently get leads, calls, bookings, or sales?
48. Which keywords, services, locations, or questions should the site be found for?
49. Which rankings or pages would be costly to lose?
50. Will any URLs change?
51. Who will create the redirect map?
52. Who will test redirects after launch?
53. Do you have access to Google Search Console, Google Analytics, Google Business Profile, Bing Webmaster Tools, and paid search accounts?
54. Are there location pages, service-area pages, product pages, or articles that need structured data?
55. What internal links must be preserved or improved?
56. Are there backlinks pointing to old URLs that need special care?
57. What title tags and meta descriptions should be rewritten before launch?
58. Should old blog posts be migrated, pruned, refreshed, or left alone?
59. What search queries bring visitors who are not a fit?
60. How will SEO performance be checked 30, 60, and 90 days after launch?

Google’s site move documentation recommends planning URL changes and redirects because a redesign combined with content and URL changes can cause Google to relearn and reassess pages. That is why SEO questions belong in discovery, not in a rushed launch-week spreadsheet.

UX, conversion, and forms

61. What is the main action each key page should drive?
62. What secondary actions should be available for visitors who are not ready to buy?
63. Which forms are needed?
64. What fields are required on each form?
65. Which fields are optional?
66. What information does the sales team actually use after a form submission?
67. What information creates friction without improving lead quality?
68. Should visitors be able to call, text, schedule, upload files, pay deposits, chat, request quotes, or choose service areas?
69. What confirmation message or thank-you page should appear after conversion?
70. Who receives form notifications?
71. What happens if a form notification fails?
72. What trust elements should appear near calls to action?
73. What should the mobile experience prioritize?
74. What user tasks are currently frustrating customers or staff?
75. What should be tested before launch on desktop, tablet, and mobile?

Form questions matter because friction costs money. Baymard’s checkout research found that 22% of users have abandoned checkout because the process was too long or too complicated. A lead form is not the same as checkout, but the lesson carries over: every extra field should earn its place.

Technical requirements, performance, accessibility, and integrations

76. Which platform will the site use, and why?
77. Who owns the domain, DNS, hosting, CMS, plugins, themes, code repository, analytics, and ad accounts?
78. What third-party systems must connect to the site, such as CRM, email marketing, scheduling, payments, inventory, maps, reviews, chat, or client portals?
79. What security requirements apply, such as user roles, backups, updates, spam protection, SSL, two-factor authentication, or audit logs?
80. What accessibility target should the project meet?
81. Who will test accessibility before launch?
82. What performance budget should the team hit for key pages?
83. What browser and device support is required?
84. Who handles maintenance after launch?
85. What is the escalation plan if the site breaks, forms stop sending, rankings drop, or performance falls?

Google’s Core Web Vitals guidance says site owners should aim for LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. W3C’s accessibility guidance says WCAG 2.2 explains how to make web content more accessible to people with disabilities. Those targets should be in the brief before design and development decisions are made.

Analytics belongs here too. Google Analytics 4 recommends the generate_lead event for initial lead acquisition such as form submissions, newsletter sign-ups, or demo requests. If the team does not define events during discovery, the launch report may only show traffic, not business results.

The answers that change scope the fastest

Some answers are more expensive than others.

A client who says “we need five pages” may actually need 28 if each service, location, case study, team member, and FAQ deserves its own URL. A business that says “we already have photos” may only have cropped headshots, stock images, or outdated jobsite pictures that do not support trust. A company that says “we use HubSpot” may mean contact forms only, while the sales manager expects lifecycle stages, deal routing, lead scoring, and campaign attribution.

These are the answers that usually change the estimate:

• URL changes, content migration, and redirect mapping
• Custom integrations with CRM, scheduling, payments, inventory, or member systems
• Copywriting, photography, video, accessibility testing, analytics setup, and post-launch SEO monitoring

There is nothing wrong with a larger scope. The problem is discovering it after the contract is signed.

Red flags in discovery answers

Discovery is not only about gathering requirements. It also tells you whether the project is ready.

Be careful if nobody can name the primary audience, nobody owns content approval, every stakeholder has equal decision power, the budget is hidden, the deadline is fixed but the scope is not, or success is defined only as “make it look better.”

Also be careful when the current site has meaningful search traffic and the project team wants to change URLs without an SEO migration plan. Google says a site move with redesign and URL changes can cause traffic loss while pages are reassessed, which is why 301 redirects and move planning are part of Search Central’s migration guidance.

None of these red flags mean the project should stop. They mean the project needs clearer decisions before production starts.

Turn the questionnaire into a project brief

Once the questions are answered, do not leave them buried in notes. Convert them into a short working brief the whole team can use.

The brief should include:

• Business goals, target audiences, priority offers, conversion actions, and success metrics
• Sitemap, page inventory, content ownership, technical requirements, integrations, SEO migration needs, accessibility target, analytics events, and launch responsibilities
• Open decisions, risks, dependencies, approval contacts, timeline, and post-launch measurement dates

That brief becomes the anchor for the proposal, kickoff meeting, design review, development QA, launch plan, and 90-day performance review.

For business owners, it keeps vendors honest. For agencies and freelancers, it keeps scope honest. For internal teams, it prevents the common failure where design, copy, SEO, analytics, accessibility, and integrations are treated as separate tracks until they collide.

FAQ: website discovery questionnaires

How long should website discovery take?

A small local business website can often complete discovery in one structured call plus a short follow-up. A redesign with SEO migration, CRM integration, ecommerce, or multiple stakeholder groups usually needs several sessions because requirements affect scope, cost, and launch risk.

Who should answer the questionnaire?

At minimum, include the business owner or executive sponsor, the person responsible for sales or lead handling, the person who will approve content, and the person who will maintain the site after launch. If SEO, paid ads, IT, legal, or operations will be affected, bring them in before scope is finalized.

Should agencies send this to clients before a proposal?

Yes, but do not make the client do all the thinking alone. Send a shorter version before the first call, then use the full questionnaire to guide the conversation. The best answers usually come from follow-up questions, not form fields.

What should a business owner do if they cannot answer these questions?

That is useful information. If you cannot define your best customer, main offers, proof points, content ownership, or success metrics, the website project needs planning before production. A good web partner can help you make those decisions, but they should not pretend the missing answers do not matter.

Want a website project scoped before it gets expensive?

If you’re planning a redesign, rebuild, or new small business website, Your Web Team can help turn messy goals into a clear website plan, build scope, SEO plan, and launch path.

Start here and tell us what you’re working on. We’ll help you figure out what the site actually needs before you spend money building the wrong thing.