Hiring Guides

12 Questions to Ask a Web Designer Before You Hire Them

A website is usually the most expensive marketing decision a small business makes — and it's the one people research the least. Most owners compare three portfolios, pick the one that looks nicest, and sign. Months later, they're stuck with a site they can't update, a designer who won't answer emails, and a second bill for everything the first quote left out. None of that is bad luck. It's what happens when you hire without asking the right questions first. Here are the twelve questions that separate people who build websites for a living from people who build websites that actually work — plus the red flags that tell you to walk away.

1. Can You Show Me Live Websites You've Launched Recently?

Not screenshots. Not mockups. Live websites you can open on your phone right now.

This matters more than almost anything else. A portfolio of polished mockups tells you nothing about load speed, mobile layout, or how the site feels to click through. Open their recent work on your phone. Can you tell what each business does within a few seconds? Does the menu work? Does the page load fast enough that you don't notice it loading? One hiring guide we read puts it bluntly: review live sites launched in the last 12 to 18 months, not just portfolio samples. Sites from three years ago don't prove someone still knows what they're doing.

Then ask a follow-up most people never think of: what did you actually handle on each project? Some designers show work where they only made it pretty — someone else wrote the copy, built the pages, handled SEO, and set up analytics. That's not dishonest, but you deserve to know which parts are theirs. And here's the sharpest question of all: are you still working with that client? A designer whose clients keep them around is worth more than one with a prettier gallery.

2. What Questions Do YOU Have for Me?

Yes — turn it around. The best answer to "how do I judge a web designer" is watching what they ask before they start designing.

A serious designer should be trying to understand your customers before they talk about your color palette. Who are your best customers? What usually makes someone pick up the phone or place an order? What questions do people ask before they buy? What makes you different from the competitor down the street? If the first conversation is all fonts, colors, and page counts, that's a warning: you're talking to someone who builds brochures, not someone who builds a tool that brings in business.

In our experience, this is also where the freelancer-versus-agency question starts answering itself. Whoever you hire, they need to think like a partner in your business, not a vendor fulfilling a brief. If you're weighing the two, our freelancer vs. agency comparison walks through the trade-offs honestly.

3. What Exactly Is Included — and What Isn't?

This is where most projects go sideways, and it almost never feels like anyone's fault. The quote said $1,500. Three months later the real cost is double, because the original price didn't include things everyone assumed were in there.

Ask straight out: what's included, and what's not? How many pages? Who writes the copy — you or them? Who provides the photos? Are contact forms, analytics, and basic SEO setup included, or extras? What usually causes the price to go up mid-project? How many rounds of revisions come with the price, and what does an extra round cost?

The copy question deserves special attention. Most small business owners don't realize they're expected to write all their own website text — and discover it the week they're supposed to deliver twenty pages of copy while running their business. If the designer doesn't write or edit copy, budget your own time for it, or expect to pay someone who will. Vague proposals are how the hidden costs of cheap websites sneak in, so get specifics in writing before anything starts. And if you want to skip the guessing game entirely, see our fixed-price packages — everything's listed, nothing's a surprise later.

4. Who Owns the Website When It's Done?

This one surprises a lot of first-time clients, and it's the question that saves people from the worst outcomes. You need to know: who owns the domain name, the hosting account, the website files, the CMS login, and your analytics accounts?

The honest answer should be: you do, all of it, registered in your name or transferred to you on final payment. Some designers hold everything under their own accounts. They'll tell you it makes support easier — and in the short term, it can. But it also means leaving them later requires their cooperation, and if the relationship sours, you can end up effectively renting your own website. Multiple hiring guides call refusal to hand over admin access and files a deal-breaker. They have a word for the alternative: hostage situations, where you can't update or move your site without their approval or extra fees.

Ask specifically about the pieces people forget: will your Google Analytics and Search Console be set up in your business name? What happens to form submissions and email integrations if you part ways? Our guide on who owns your website breaks down exactly what should be in your name and why.

5. How Do You Handle Speed, SEO, and Redirects?

A website can look polished and still be badly built. You'll feel it after launch: pages drag on phones, forms are clunky, and Google quietly ranks you below competitors with uglier sites that load faster.

Ask what SEO basics come with the build. Good answers mention real specifics: clean heading structure, optimized page titles and meta descriptions, image compression and alt text, mobile-first layouts, and fast load times. If they say "SEO is a separate service," that's not automatically bad — but basic on-page SEO should be baked into any professional build, not sold back to you later.

One question that separates pros from amateurs: how do you handle redirects if this is a redesign? When page URLs change without redirects, search rankings can drop overnight — one of the most common and most avoidable disasters in web projects. If your designer looks confused by the question, that's your answer about hiring them.

6. What Happens After the Website Launches?

This is the question most people forget to ask, and it's often the most important one. Websites aren't appliances you buy and forget — they need ongoing attention. Security updates, plugin updates, backups, uptime monitoring, and fixing things when they inevitably break.

Ask: do you offer maintenance support, what's included, and what does it cost? If something breaks, who's responsible — and how fast will they respond? You should also know whether you'll be able to make simple updates yourself. You shouldn't have to call your designer every time you need to change a price or add a photo. Ask whether you'll get training or simple documentation after handover.

Here's the uncomfortable truth: some designers hand you the site and disappear. For most small businesses, having one person who knows your site and answers when it breaks is worth more than a slightly prettier design. Our monthly maintenance cost guide shows what reasonable ongoing support looks like, so you can tell a fair plan from a cash grab.

7. Red Flags That Should Make You Walk Away

Beyond the questions, watch for the warning signs. No portfolio — only mockups, or "we can't show client work" without a good reason. A portfolio where every site looks like the same template with different logos. No written proposal or contract — just emails and "don't worry, we'll sort it out." That's how misunderstandings (and lawsuits) start.

Be skeptical of guarantees no honest person can make: "we'll rank you #1 on Google fast." Nobody can promise that, and anyone who does is either lying or planning to use tricks that'll get your site penalized. Same with absurd timelines — a quality custom site takes weeks, not days. And pay attention to how they communicate during the sales process. If it takes them three days to answer an email before they have your money, imagine how responsive they'll be after.

Finally, notice whether they're curious about your business. If they never ask about your customers, your goals, or your competition, they're not planning to build a site that fits your business — they're planning to ship another template. If you'd rather skip the interview gauntlet and work with a team that starts every project with your customers, not your color scheme, take a look at our services or just get a free quote — no obligation, no jargon.

The Short Version

Hiring a web designer is a business decision, not a taste decision. The prettiest portfolio in the world means nothing if you don't own the site, can't update it, and can't get hold of the person who built it. Ask about live work, ownership, what's included, and what happens after launch — and trust your gut when answers feel vague. The right designer will welcome every one of these questions. The wrong one will rush you past them.

Frequently Asked Questions

How much should I expect to pay a web designer?

There's no single honest answer — it depends on scope, who writes the copy, and what's included in the quote. A simple small-business site costs far less than a custom build with integrations, but anyone who quotes you an exact figure before understanding your project is guessing. What matters more than the headline price is clarity: get a detailed proposal that spells out deliverables, timelines, ownership, and what's extra.

Should I hire a freelancer or an agency for my website?

It depends on your project. Freelancers are usually more affordable and flexible — good for straightforward sites. Agencies bring structured processes and multiple specialists, which helps for complex projects, but at a higher cost. Either way, vet the actual person doing the work using the questions in this guide. Our full comparison breaks down the trade-offs in detail.

What should a web design contract include?

At minimum: exactly what's being delivered (pages, features, content responsibilities), the timeline with milestones, the total price and payment schedule, how many revision rounds are included and what extras cost, who owns the domain/hosting/files when it's done, and what post-launch support you get. If any of these are vague, ask for them in writing before you sign.

Who should own my domain and hosting accounts?

You should. The domain, hosting account, CMS admin access, and analytics accounts should be registered in your name or fully transferred to you on final payment. If a designer insists on keeping everything under their accounts, you're renting your own website — and leaving them later will cost you. Get ownership terms in the contract, not in a handshake.

Keep Reading