Guide

What to ask before you hire a web designer.

Ask who owns the domain, who owns the site if you stop paying, and what happens if the designer disappears. Those three answers tell you more than any portfolio.

Most of what goes wrong between a small business and a web designer isn't about design. It's about ownership, access, and what happens when the relationship ends.

These questions are worth asking before signing anything. A good answer to all nine is a genuinely reassuring sign, and none of them are unfair to ask.

1. Whose name is the domain registered in?

It should be yours, in an account you control, with your card on file. Not the designer's account, not their agency's, not 'we'll handle it'.

This is the single most important question on the list. Everything else can be rebuilt if it has to be. A domain you don't control can be held, lost when someone stops paying, or simply become unreachable when the person who registered it stops answering email — and it's the address every customer, every link and every listing points at.

2. What happens if I stop paying you?

There are two honest models and you should know which you're buying. Either you own the site and can take it elsewhere, or you're renting it on a platform and it goes away when you stop.

Renting isn't inherently wrong — it can be reasonable value. But it should be stated plainly, not discovered two years later when you want to move and find there's nothing to move.

3. Can I get the files?

Ask specifically: will I get the repository, or an export, or nothing? A site you can't take a copy of is a site you don't own regardless of what the invoice says.

It's also worth asking where it's hosted and whether you'll have an account there. 'It's on our hosting' is a dependency to go in with your eyes open about.

4. Will each service have its own page?

If everything you offer lives on one page, that page has to compete for every search at once, and it will lose most of them. One page per service is the difference between ranking for four things and ranking for none.

This is also a decent test of whether the person thinks about search at all, or only about layout.

5. How will you handle titles and descriptions?

The answer you want is that they're written per page. The answer that should worry you is that they're generated from the business name, or not mentioned as something anyone decides.

It's a small thing that reveals a large thing: whether the site is being built to be found, or just to exist.

6. Will the content be in the HTML?

Phrase it however you like — 'will the text be in the page source, or added by JavaScript?' Static HTML is faster, and it's readable by the AI assistants that increasingly answer questions before anyone reaches a search results page. Most of those crawlers don't run JavaScript.

It's a technical question but the consequence is commercial: a site built the wrong way here can be invisible to a whole category of search.

7. What's included in SEO, specifically?

'SEO included' means nothing on its own. Ask what specifically — page titles, structured data, sitemap, Google Business Profile, content, links? Which of those, and how will you know it happened?

Be wary of anyone guaranteeing a position. Nobody controls the ranking, so nobody can guarantee it. That claim is either about a phrase nobody searches, or a sign of tactics that cost you later.

8. Who updates it, and how fast?

Changing a phone number, adding a service, swapping a photo. Can you do it yourself, and if not, what's the turnaround and the cost?

Businesses that can't update their own site stop updating it, and a site that's two years stale reads as a business that might have closed.

9. Can I see a site you built that's been live for two years?

A portfolio full of launch screenshots tells you someone can produce a nice-looking page. A site still working and still current two years later tells you they built something maintainable.

Ask whether that client is still with them, and why or why not. The answer is usually informative.

Common questions

Is it rude to ask all of this?

No, and anyone who reacts badly has answered a different question for you. These are ordinary questions about a significant purchase, and someone doing this properly will have ready answers.

How do I check who really owns my domain?

Look up your domain in a public WHOIS lookup to see the registrar, then confirm you can log into that registrar yourself. Being able to see the site is not the same as controlling the domain.

What's a reasonable amount to spend?

It varies enormously by scope and there's no honest single number. What's more useful is knowing what you're buying: a rented template, a custom build you own, or ongoing work. Compare quotes on that basis rather than on price alone — the cheapest option is sometimes a subscription you can never leave.

If you're comparing quotes right now and want a second opinion on what you've been sent, that's a reasonable thing to ask for and it doesn't obligate you to anything.

Is my website actually findable?

Search Google for site:yourdomain.com. If it returns one result, or none, search engines cannot see most of your website — and no amount of design work will fix that.

Why your Google Business Profile beats your website

Google Business Profile signals account for roughly a third of local pack ranking — more than the website contributes. A complete profile with steady reviews will outrank a better website attached to a neglected one.

Why city pages usually backfire

Near-identical pages get clustered by Google, which picks one and ignores the rest — so fifty city pages earn roughly the ranking value of one, while the site-wide quality signal drags down the pages that were genuinely good.

Want to know where you actually stand?

Send over your domain and you'll get back a specific list of what's working and what isn't — including when the honest answer is that nothing needs replacing.