12 Questions to Ask Before You Hire a Web Designer

Questions to Ask a Web Designer Before You Sign

Most businesses hire a web designer the same way they buy a car: they ask about price and pick the one they like the look of. That's not a terrible strategy, but it misses the things that actually determine whether you end up with a site that serves your business — or an expensive headache three years later.

These are the questions to ask a web designer before you sign anything. Specifically, the ones that expose what's really going on.

---

The 12 Questions

1. Will I own my domain, hosting, and code?

This is the most important question on the list. Some designers register your domain in their own account, host your site on their server, and retain the code as their intellectual property. When you want to leave — or they raise prices, or they go out of business — you're stuck. You should be the owner of record on everything.

2. What platform will my site be built on?

WordPress, Wix, Squarespace, Webflow, hand-coded HTML/CSS/JS — these are not equivalent options. Each has different implications for speed, security, ongoing costs, and what it costs to leave. Ask which one, and why.

3. Who actually builds it?

At an agency, the person who pitches you may not be the person who builds your site. Ask whether the work is done in-house or subcontracted, and whether you'll have a direct line to the person doing the actual work.

4. What's the turnaround time, and what happens if it slips?

A realistic answer includes some acknowledgment of what depends on you (content, feedback, approvals) and what depends on them. Vague promises about "3–4 weeks" with no follow-up process are a yellow flag.

5. What does post-launch support look like?

Does support cost extra? Is there a retainer? Who do you call when something breaks at 10pm? This is often where the real ongoing cost lives, and it's rarely front-and-center in the initial quote.

6. Is SEO included?

"SEO" can mean anything from a plugin installed to a full technical setup with structured data, proper heading hierarchy, metadata, and local optimization. Ask what's specifically included — and what isn't.

7. What does the revision process look like?

Some designers give you unlimited rounds until you're happy. Others count revisions and charge for extras. Know upfront what "two rounds of revisions" means in practice.

8. Is it custom-designed or a template?

There's nothing wrong with a well-adapted template, but you should know what you're getting. Ask to see examples and ask whether your design starts from scratch or from an existing theme.

9. Will the site be fast and mobile-optimized?

Ask for Google PageSpeed scores on their past work. A score in the 90s on mobile is achievable with a hand-built site. Many page-builder sites can't get there.

10. Is the site accessible and legally compliant?

ADA / WCAG 2.1 AA accessibility isn't optional — it's a legal baseline for sites that serve the public. Required legal pages (Privacy Policy, Terms of Service, Cookie notice) matter too. Ask whether these are included or upcharged.

11. Who owns the content?

Photos, copy, graphics — who holds the rights? If a designer uses licensed stock photography through their account, you may not actually be able to use those images after you part ways.

12. What happens if I want to leave?

What does "moving on" actually look like? Can you take the code? Can you move hosting yourself? Will they help with the transition? The answer tells you a lot about whether they're building something for you or for themselves.

---

How I Answer Them

Here's exactly where CATESWEB lands on each:

Ownership (Q1): Yes — domain, hosting, analytics, and code are all in your name. If you ever leave, you take everything. I have no leverage over your site. Read more in Do You Actually Own Your Website?

Platform (Q2): Hand-written code, not a page builder. Faster load times, no platform fees, and nothing proprietary that traps you.

Who builds it (Q3): Me. I'm a solo operator. When you email CATESWEB, you get Christian. That's the whole team.

Timeline (Q4): I give realistic timelines in the proposal and flag what depends on client content and feedback. Most straightforward sites go live in 4–6 weeks.

Post-launch support (Q5): Covered in the project. Urgent fixes don't wait for a ticket. Ongoing changes are discussed at the start so there are no surprise invoices.

SEO (Q6): Yes — every build ships with proper page structure, metadata, structured data, and local SEO. The right customers can find you from day one.

Revisions (Q7): Two formal rounds are standard; most clients don't need more than one.

Custom or template (Q8): Custom-designed. Every site starts from the brief, not a theme marketplace.

Performance (Q9): Hand-coded sites routinely hit 90+ on Google PageSpeed, including mobile.

Accessibility and compliance (Q10): Every site ships ADA / WCAG 2.1 AA accessible with the required legal pages built in. Not billed as an extra.

Content ownership (Q11): Your content is yours. If I source photos, they're licensed for you to keep.

Leaving (Q12): Clean handoff. Code, hosting credentials, domain access — everything transfers. No friction.

---

If you're comparing options, a web design in Wyoming or anywhere else in Kent County — run these questions by every vendor. The answers will do more than any portfolio to tell you who you're actually dealing with.