A productive consultation is not a quiz about design vocabulary. It is a chance to learn how the designer turns an unclear business problem into a controlled project. Send a short brief beforehand, bring the same questions to every finalist, and take notes in the same format. You will be able to compare the substance of the answers instead of choosing the person who gave the smoothest presentation. For more preparation tools, start with the hiring and project-planning guides, then compare the provider's answers with the scope described on our website design service.

Questions 1–4: goals and audience

Start with the business problem

01

1. How will you learn about our customers and offers?

A strong answer names inputs such as stakeholder interviews, sales-call themes, customer questions, analytics, search behavior, reviews, and competitor research. Be cautious if the plan begins with a visual style before the audience and offer are understood.

02

2. How will you turn our business goal into website decisions?

Listen for a path from goal to visitor action, page structure, content, interface, and measurement. For example, a goal of more qualified consultations may require clearer qualification copy and a better form—not simply more traffic.

03

3. What do you need from our team before work begins?

The designer should name decision-makers, subject experts, brand assets, system access, content inputs, legal or compliance reviews, and approval time. This exposes the client workload that a proposal price alone can hide.

04

4. What would you recommend we leave out of the first release?

A thoughtful answer distinguishes essential outcomes from attractive extras. It may propose a later phase for uncertain features rather than making the first launch carry every idea.

Questions 5–8: scope, people, and decisions

What to ask and what a useful answer should reveal

QuestionStrong answer signal
5. Exactly what pages, templates, and features are included?A written inventory separates unique layouts from pages that reuse a template and names forms, search, booking, payment, or integrations.
6. Who will perform strategy, writing, design, development, SEO, and testing?You learn the actual team, any subcontracted roles, the main contact, and who has final responsibility for quality.
7. What are the review points, and who approves each one?Milestones have defined outputs, review windows, decision owners, and a way to record approval before the next stage begins.
8. How do revisions and scope changes work?The answer separates corrections from new requests and explains estimates, written authorization, schedule impact, and revision limits.

Do not assume a page count tells you the amount of work. One location page based on an approved template is different from a custom service page that needs interviews, original copy, illustration, and a lead-routing form. The proposal should translate nouns such as “SEO” and “content” into tasks and outputs. You can compare this conversation against the practical criteria in how to choose a web design company.

Questions 9–12: content and search

  1. 9. Who plans the information architecture? Look for a process that groups content around what visitors need, gives important pages clear paths, and avoids burying services inside internal company language.
  2. 10. Who writes, edits, and approves the copy? A complete answer identifies source material, interviews, drafts, revision rounds, fact checking, brand voice, final approval, and what happens when client content is late.
  3. 11. What does SEO work include? Ask separately about search research, page mapping, titles and descriptions, headings, internal links, crawlability, structured data, redirects, sitemap work, and measurement. No designer can promise a ranking.
  4. 12. How will you preserve important URLs and content during a redesign? The designer should inventory current pages, identify valuable destinations, map changed URLs, implement appropriate redirects, update internal links, and monitor after launch.

Google's SEO Starter Guide says useful, compelling content often influences a site's search presence more than the other suggestions in the guide, while its site-move documentation explains how URL changes can affect search and recommends careful redirects and monitoring. That makes content ownership and migration planning core project questions, not optional marketing add-ons. If the designer uses the phrase “SEO-friendly,” ask for the written deliverable list behind it.

VISUAL CHECKPOINT · PlanningFollow control from asset to owner

For each layer, identify who owns the account, who pays, who has administrative access, and what can be moved later.

Questions 13–16: accessibility, devices, and performance

Evidence-based answerAnswer that needs follow-up
13. How do you address accessibility?Names a target, responsibilities, design and code practices, content duties, and manual plus automated checksSays a plugin or automated score makes the site compliant
14. Which devices and browsers do you test?Provides an agreed test matrix based on audience and current browser supportPromises the site works everywhere without defining what was tested
15. How do you control page weight and speed?Discusses image formats, fonts, scripts, third-party tools, caching, and measurable checksNames one score but cannot explain the test conditions or tradeoffs
16. How are forms and key journeys tested?Covers validation, error states, notifications, routing, spam controls, confirmation, keyboard use, and real submissionsChecks only that the button can be clicked

The W3C organizes WCAG around four principles: content should be perceivable, operable, understandable, and robust. Its guidance also makes clear that accessibility involves multiple components, including content, authoring tools, browsers, and assistive technologies. Ask the designer which parts are included in the project and which remain your team's ongoing responsibility. A responsible answer should not turn a broad, continuing practice into a blanket legal guarantee.

Questions 17–20: ownership, platform, and accounts

Follow control from asset to ownerFor each layer, identify who owns the account, who pays, who has administrative access, and what can be moved later.
0117. DomainWhich registrar account holds it, and is our business the registrant?
0218. Platform and hostingWhat are the recurring fees, limits, backups, security duties, and exit options?
0319. Creative and codeWhat do we own, what is licensed, and what source or editable files are delivered?
0420. Data and measurementWill analytics, tag management, search tools, form data, and consent tools live in client-controlled accounts?

ICANN's registrant information explains that domain holders have access to information about registration, management, transfer, renewal, and restoration processes. The practical lesson is simple: your company should not discover after a disagreement that a former vendor's private account controls the domain. Require an account register that lists the owner, administrator, billing contact, renewal method, recovery method, and handoff status for every critical service. For the full ownership issue, read who owns your website after launch.

Questions 21–25: launch, care, and cost

01

21. What must be true before the site launches?

Ask for acceptance criteria and a checklist covering approved content, tested forms, redirects, analytics, accessibility review, backups, security, DNS responsibility, legal pages supplied by the client, and final sign-off.

02

22. What happens if launch has a serious problem?

A useful answer identifies the decision-maker, monitoring window, escalation path, backup or rollback plan, and the boundary between a defect and a new request.

03

23. What training and documentation will we receive?

Request role-specific instruction using the finished site, plus notes for common tasks such as editing pages, replacing images, reviewing form leads, adding users, and requesting help.

04

24. What support is included after launch?

Clarify the defect-fix period, response channels, support hours, expected response—not resolution—times, emergency handling, maintenance tasks, and the price of work outside a plan.

05

25. What will we pay now and over the next three years?

Separate project fees from hosting, platform subscriptions, premium plugins, licenses, maintenance, support, transaction fees, usage charges, content updates, and likely renewals. Ask which costs are paid directly to third parties.

Should I ask all 25 questions in the first call?

Not necessarily. Use the first call to confirm fit, goals, process, and the broad scope. Send detailed technical, ownership, testing, and support questions before the proposal or finalist meeting. Every material answer should be clear before you sign.

What if I do not understand a designer's technical answer?

Ask for the decision, risk, and example in plain language. You do not need to become a developer, but you should understand what the choice means for cost, control, customers, and future changes. A good partner can explain those consequences without hiding behind jargon.

Is it rude to ask who will actually do the work?

No. Team structure, subcontracting, responsibility, and communication affect delivery. Ask respectfully who fills each role, whether that person will attend key meetings, and who remains accountable if the team changes.

Can I use these questions for a freelancer and an agency?

Yes. The required clarity is the same even when the delivery model differs. A solo designer may use specialists; an agency may assign several roles. Judge whether responsibilities, coverage, communication, and handoff fit your project.

Which answer should stop the hiring process?

Pause when a provider will not identify your deliverables, total recurring costs, ownership, or change process in writing. Those gaps can alter the deal. Resolve them before paying a deposit or granting access to business systems.