What to Ask a Web Designer Before You Hire Them

You have two or three proposals open in different tabs. They are priced differently, worded differently, and impossible to line up beside each other. One is built on a template, one promises something custom, and none of them says clearly what happens after the invoice clears. Searching for what to ask a web designer before hiring returns a pile of numbered lists, and reading four of them leaves you with forty questions and no more confidence than you started with. The problem was never a shortage of questions. It is that a question you cannot judge the answer to gets you nowhere, and most people nod along rather than risk sounding uninformed. So, this is the other half: for the three things that actually decide how this goes, here is what a good answer sounds like, what a weak one sounds like, and what each tells you about the months after signing.

Because the price line is the only part written in a shared language.

Everything above it uses labels that each provider defines privately: pages, design, development, content, SEO, hosting, maintenance, custom, template, launch, support. Two proposals can use all the same words and describe substantially different work.

Everything below the price line, meaning the rights, the accounts, the recurring charges and the exclusions, is usually either buried or absent. That is the part that decides whether you can change a sentence next year, move to somebody else, or see your own search data.

So, the fear underneath is not really about ending up with an ugly website. It is about discovering the actual deal after the deposit has cleared, when switching is expensive and awkward. That is a reasonable thing to be worried about, and it is checkable in advance.

Ask three plain questions, then listen for specificity rather than reassurance.

Who will be named as the registrant on the domain? Which email address receives the renewal notices? Will I be a verified owner in Search Console, or a user?

A good answer sounds like this. "The domain goes in your business name at the registrar, with your email as the recovery address and two-factor enabled on your account. I will be added as a technical contact. In Search Console you will be the verified owner and I will be a user, so if we part company you remove my access rather than the other way round."

A weak answer sounds like this. "Don't worry, we handle all of that for you." Or: "It's under our agency account, which makes it easier to manage."

Neither of those weak answers is necessarily dishonest, and the second one is even partly true, since it is easier to manage. What they have in common is that they answer a question about control with a statement about convenience, and that substitution is the thing to notice. It predicts how the next awkward question will go too.

Google's own documentation is worth knowing here because it settles the stakes: verification is what establishes the owners and operators of a Search Console property, and Search Console exposes confidential site data only to verified users. If you are not verified, you cannot see how your own site performs without asking somebody.

This is the one where a confident-sounding phrase does the most damage.

If a provider says "it's work made for hire, so you own it," that is a label rather than an answer. The Copyright Office's website circular is direct: an independent contractor who develops a website or its content is generally the author and copyright owner unless the hiring party acquires the rights through a signed written agreement. Its general guidance adds that commissioned work qualifies as work made for hire only in specified circumstances and with a signed written instrument.

A good answer sounds like this. "The agreement assigns you the copyright in the original design and copy we produce. The theme licence, the fonts, the stock photographs and the plugins stay licensed rather than assigned, and they are listed in the schedule. Here is that clause."

A weak answer sounds like this. "You own it, obviously, you're paying for it."

The tell is not whether the answer is assignment or licence. A durable licence is genuinely fine for most businesses, and being able to use, edit, host and move your site indefinitely covers what most owners actually need. The tell is whether they can point at the words in the contract. Somebody who can has thought about this before; somebody who cannot is telling you what they assume.

You do not have to invent these, because the FTC has already written them for small business buyers.

Its guidance tells a business to clarify from the beginning who will be able to make changes after the site is built, whether you have to go through the provider, and whether you can log in and change things yourself. It also says to ask where visitor data is stored, whether it is encrypted, and who can access it.

A good answer sounds like this. "You'll have an administrator login and can edit text and images yourself. Structural changes come to us. The site runs on this host, on this plan, at this price, in your account. Form submissions go to this mailbox and are stored here. The certificate renews automatically. Updates are covered under the support arrangement, monthly, and here is what that includes."

A weak answer sounds like this. "It's all managed, you won't need to worry about updates."

Managed by whom, at what price, and for how long. A monthly fee for real maintenance work is a perfectly good arrangement. A monthly fee that nobody will itemise is a different thing, and the difference is visible in whether the answer contains nouns.

One specific item worth raising because almost nobody does: what happens to old access at handover. Google explicitly tells site owners to review and remove stale verification tokens when access changes, and that kind of tidying up does not happen automatically. A provider who has an answer for that has run a handover before.

The exclusions are where the surprises live, so ask for them explicitly rather than reading around them.

Ask what is not included. Ask what counts as a change request once the build is under way, and what one costs. Ask who writes the copy and who supplies the photography, because that single question separates more quotes than any other. Ask what happens if your content arrives late.

A good answer sounds like this. "Five pages, these five. Copy supplied by you against a brief we provide; if you'd rather we wrote it, that's a separate line at this price. Two rounds of revisions on design, then further rounds are billed hourly at this rate. Photography is not included. Late content moves the launch date rather than the price."

A weak answer sounds like this. "We'll take care of the content." Followed, months later, by either a bill you did not expect or three paragraphs written from your competitor's site.

Notice that the good answer contains things you might not like. That is a feature. A quote with no exclusions listed has not had its exclusions removed; it has had them left unwritten.

Compare five-year cost, not build price, because that is the number you will actually pay.

Write down, for each quote: the build price, the domain renewal, the hosting or platform subscription, any paid plugins or apps, the email service, payment processing if relevant, and any monthly support fee. Then add two questions most comparisons miss. What happens if you stop paying the monthly fee, and what would it cost to leave?

That last question has a concrete answer, and how it is handled is informative. Moving a common domain between registrars requires an authorisation code, which the registrar must provide on request within five calendar days. A provider who explains that calmly is describing a normal process. A provider who becomes vague about it is telling you something.

A good answer sounds like this. "If you stop the monthly, the site keeps running; you'd take over hosting at this cost. If you leave, we send you the source files, transfer the domain and remove our access. There's no exit fee."

A weak answer sounds like this. "Nobody's ever asked that."

There is no sourced industry timeline for a small business website, and any "four to six weeks" figure hides the largest variable, which is how fast you supply and approve things.

So, ask for gates with dates rather than a duration: discovery and account access, scope sign-off, content supplied, first design, your review, build complete, testing complete, launch, handover, and a post-launch correction period. Ask which of those dates depend on you. That turns two incomparable quotes into two schedules you can lay side by side.

One thing to expect afterwards rather than be alarmed by: Google says it does not crawl a page immediately, that in most cases noticing a change takes a few days, and that Search Console can keep showing an error until the corrected page is recrawled. A quiet first week is normal.

More than most owners expect, and knowing it in advance prevents the stall that makes projects run late.

You will supply the truth the site publishes: legal business name, address or service area, contact method, services, prices or your price policy, staff credentials where they matter, photographs or permission to use the ones you provide, and where enquiries should go.

You will decide what a visitor should do on each page, which statements need approval, whether a form collects personal information, who answers messages, and who holds administrator access.

You will also approve trade-offs, and it is worth being honest with yourself about them. A low project price usually means fewer pages, a template, copy you write, simple form handling, limited revisions and no ongoing updates. That can be exactly the right deal. It becomes the wrong one when nobody said it out loud.

Not many, and one worth a moment.

No Texas rule governs how a website is built or what a designer must include. If your business trades under a name other than its legal name, the Texas Secretary of State says an assumed name certificate is required for covered entities, and that the filing is notice only rather than a right to the name. That matters here only because the name on your new site, your invoices and your listings should match, and it is easier to settle before the site is written than after.

Otherwise, treat "local" as a practical question rather than a legal one. Ask whether the provider will be available for a conversation when something breaks, and in which time zone. That is worth more than proximity.

What is the single most important question to ask?

Who will be named as the registrant on the domain. It is the one asset that can take your site and your email offline, and the answer is a fact rather than an opinion.

How do I know if a designer is any good if I cannot judge the technical side?

Judge the specificity of the answers rather than the technology. Somebody who names the registrar, the host, the plan, the contract clause and the handover steps has done this before. Vagueness across several answers is the pattern worth acting on.

Is it rude to ask about ownership and exit before I have even hired someone?

No, and a good provider expects it. These are standard commercial questions. How somebody responds to being asked is itself information.

Do I actually own the website when it is finished?

Only as far as the paperwork says. Copyright in commissioned work generally starts with the person who created it unless a signed agreement transfers it. Ask what is assigned, what is licensed, and what belongs to a third party.

Should I be worried about a monthly fee?

Not by itself. Ask what it covers, what happens to the site if you stop paying it, and whether the price is fixed. A fee for real work is fine; a fee nobody will itemise is the problem.

What if a designer cannot answer these questions on the call?

That is reasonable, and the follow-up matters. "I'll check and confirm in writing" is a good answer. Redirecting to price or portfolio twice in a row is a different signal.

Can anyone promise my new site will rank?

No. Search results move for reasons outside any one website, and no provider controls them. Somebody can define the work and how it gets measured, and should stop there.

The reason the numbered lists do not help much is that they hand you a script without telling you how to hear the reply. Once you know what a specific answer sounds like on ownership, on access and on cost, you can run the conversation yourself, and you can ask a follow-up out loud instead of nodding and hoping.

The pattern to watch for is simple enough to hold in your head. A good answer names things: a registrar, an account, a clause, a price, a date. A weak answer offers reassurance in place of a fact. Neither one tells you somebody is dishonest, and both tell you what the next twelve months will feel like.

That is what turns two incomparable quotes into a decision. Not a longer list of questions, but a way to grade the answers you are already getting.

If you want somebody to sit on your side of that conversation and read the proposals with you, we are glad to. We are Arlington Website Designer, working out of Arlington, Texas and the surrounding Tarrant County towns, and nationally for search and writing work. We build sites our clients own outright, the domain, the content, the analytics and the code, in accounts in their own name and with no monthly platform rent, so the exit questions above have easy answers. Have a look through the sites we have built, and when you are ready, get in touch and tell us what you have been quoted.