Most website disasters were predictable. Not in hindsight, in the sales meeting. The owner just didn't know which questions to ask, the designer wasn't volunteering, and the demo looked great, so everyone signed.
We've rebuilt enough sites after those deals went sideways to know exactly which questions would have surfaced the problems early. Here are the fifteen we'd ask before hiring anyone, including us. For each one, you'll get why it matters and, more importantly, what a good answer sounds like, because the difference between a pro and a problem is rarely the price. It's the clarity of the answers.
Ask all fifteen. The good designers will respect you more for it. The bad ones will get vague, and vague is your answer.
Ownership questions (ask these first)
1. Who will the domain be registered to?
The single most important question on this list. Your domain is the address printed on your trucks and tied to your Google listing, and whoever controls the registrar account controls it.
A good answer sounds like: "You. It goes in a registrar account under your business email, with your card on the renewal. If we register it for you as a setup convenience, it's documented as yours and we transfer it on request, no fee." Anything involving "we keep client domains in our account for easier management" is a future hostage situation introducing itself politely. You can verify any domain's registration through the public lookup at ICANN, and you should, after launch.
2. If we part ways in two years, what exactly do I walk away with, and in what format?
This question collapses a dozen contract clauses into one sentence, and you'll learn more from the body language than the words.
A good answer sounds like: specific and immediate. "You'd have the domain, all your content, and exportable site files, handed over within X days." Some platforms genuinely can't be exported, and that's not automatically disqualifying, but it must be disclosed now, not discovered later.
3. Will I have admin access to everything from day one?
Hosting, the site itself, analytics, and your Google Business Profile if they're touching it.
A good answer sounds like: "Yes, you get owner-level credentials at launch, and anything we set up is created under accounts you control." Access offered "whenever you need it, just ask" is not access. It's permission.
4. Who owns the content, the photos, and the design?
A good answer sounds like: "Your content and photos are yours, full stop, and that's in the contract. The design and code, here's exactly how that works on our platform." The murky zone is code and templates, where licensing arrangements are common and legitimate. Murky is acceptable. Undisclosed is not.
Timeline questions
5. How long until my site is live, and what does that depend on?
A good answer sounds like: a number with conditions attached. "Three weeks, assuming you get us photos and approvals within two days of each request." Beware the open-ended "it depends on revisions" with no outer bound; that's how four-week projects become four-month projects. The dependency clause matters too, because the most common cause of delay is the client, and an honest designer will say so to your face.
6. What happens if you miss the deadline?
A good answer sounds like: anything, honestly. Most designers have no answer because there's no consequence in their contract. The rare shop that backs a timeline with a guarantee is telling you they've built a process they trust. (We're one of them, more on that below, but ask everyone this and enjoy the pause.)
Copy and content questions
7. Who actually writes the words on my website?
This one ends more projects than any technical issue. Many designers design, then wait for you to send copy, and "waiting on content from client" is where website projects go to die.
A good answer sounds like: a clear owner for the job. "We write the first draft from an interview with you, you edit." Or, "you write it, and here's exactly what we need and when." Either model works. What doesn't work is discovering at week three that a blank Word document is your job.
8. What do you need from me, and when?
A good answer sounds like: a list. Photos, logo files, service details, login access, approval turnarounds, with dates. A designer who can't tell you what they'll need hasn't done this often enough, or runs projects by improvisation, and you'll be funding the improvisation.
SEO questions (where the vague answers live)
9. What specifically will you do for SEO?
"It's SEO-friendly" is not an answer; it's a sticker. You're looking for concrete practices, the kind Google itself describes in its documentation for site owners at Google Search Central.
A good answer sounds like: specifics. "Every page gets unique titles and descriptions, proper heading structure, fast load times, mobile-first layout, local business schema markup, and we write service pages around the actual searches your customers make." If you hear "we submit your site to Google" as a selling point, smile politely and keep interviewing.
10. Will you set up Search Console and analytics under my accounts?
Search Console is Google's free tool showing how your site performs in search, and it should be verified under a Google account your business owns.
A good answer sounds like: "Yes, set up under your account, and we'll walk you through reading it." Data trapped in a vendor's account leaves with the vendor.
11. What results should I realistically expect, and when?
A trap question, on purpose.
A good answer sounds like: honest hedging. New sites take months to build search momentum, local rankings depend on competition and reviews, and nobody can promise a specific position. The designer who guarantees "first page in 30 days" is either using techniques that can backfire or simply lying. Conservative answers here are a green flag, not a weak one. We've written more about realistic SEO timelines on our blog.
Hosting and money questions
12. Where will the site be hosted, and what does it cost ongoing?
A good answer sounds like: a named platform and an itemized number. Hosting, maintenance, and the domain renewal, separated. Bundled "all-in" monthly fees aren't evil, but you should know what's inside, partly so you know what you'd actually need to replace if you ever moved on.
13. What's included in maintenance, and what costs extra?
A good answer sounds like: a boundary. "Maintenance covers updates, backups, security, and small text changes; new pages and redesigns are quoted separately." Every shop draws the line somewhere. The problem is shops that won't draw it until the invoice arrives.
Exit questions (ask these even though it feels awkward)
14. Walk me through what off-boarding looks like if I leave.
The litmus test. Fair providers make leaving boring, because they keep clients with results, not locks.
A good answer sounds like: a process. "You give notice, we transfer the domain if we're holding anything, hand over files and credentials within X days, and point you to your exports." Squirming, scoffing, or "nobody ever asks that" are all the same answer, and it's a no.
15. Are there any cancellation fees, contract minimums, or auto-renewals I should know about?
A good answer sounds like: everything named out loud, before you ask twice. Term lengths and renewals are normal in this business; surprise renewals are not. As a general rule, terms a vendor volunteers are terms they'll honor; terms you discover are terms you'll fight about. If you ever feel a deal crossed from aggressive into deceptive, the FTC takes complaints about deceptive business practices, but the better plan is asking question 15 before signing anything.
How to use this list
Don't turn the meeting into an interrogation. Email the questions ahead, or weave them into conversation, and pay attention to the pattern of answers more than any single one. One fuzzy answer is human. Three fuzzy answers in the ownership and exit sections is a forecast.
And since fair is fair, here's how we answer them.
Our answers, on the record
We're Omnyra, a veteran-owned shop in Wilmington, NC, and we'll happily take all fifteen questions on a live call. The short version: we build done-with-you websites live on a call with you, so you watch your site come together in real time and the copy gets written with you, not awaited from you. First draft in 24 hours. Live in 7 days, guaranteed, which is our answer to question 6. You own your domain and your site, period, which is our answer to questions 1 through 4 and 14.
We've built 1,500+ small business sites in the last 90 days, including portfolio clients like airsupporthvac.com, sanosteam.com, and ramartrans.com, and our website and SEO service covers the ongoing work with your accounts in your name. Tiers start at $500, with pay-in-4 or Klarna if that's easier on cash flow; the full breakdown is on our pricing page.
Bring the list. Ask us all fifteen. Book a call and grade our answers yourself.