Questions to Ask Before Hiring a Web Developer

Before you sign with a web developer or freelancer, a short list of questions tells you who will own your site, who holds the keys, what happens after launch, and whether the quote is real — the things owners usually learn too late.

Common signs of this issue

• You are about to have a new website built, or an old one redesigned, and are comparing quotes.
• You have quotes that differ wildly for what sounds like the same job, and you can't tell why.
• A previous developer disappeared and you found out you didn't own the domain, the hosting, or the admin login.
• You are being offered a monthly plan that bundles hosting, design, and "maintenance" and you are not sure what you are actually buying.
• You don't have the technical background to judge someone's work and want questions that don't require it.
• You are hiring through a marketplace, a referral, or a cold email and have no track record to go on.

Safe checks you can do yourself

None of these require sharing passwords with anyone.

• "Whose name will the domain and hosting be in?" The only good answer is: yours. The domain should be registered in an account you own, with your email address on it. Hosting should be in your account too, or at minimum you should be the named account owner with the developer added as a user. This single question prevents the most painful problem on this site.
• "Will I have my own admin login when the site is done?" You should get a full administrator account on the site itself, plus your own logins to the hosting and domain registrar. The developer can have their own separate account that you can remove later. Shared logins, or "just ask me if you need anything changed", leave you dependent on one person.
• "What platform will you build on, and can someone else take it over?" WordPress, Shopify, Squarespace, Wix, and similar mainstream platforms mean another professional can pick up the work later. A custom-built system or a developer's own private framework may be fine, but ask plainly whether another developer could maintain it without them.
• "What exactly is included in the quote — and what is not?" Ask for a written list: number of pages, who writes the text, who supplies photos, contact forms, online booking or payments, how many rounds of changes, and whether hosting, the domain, premium plugins or themes, and email are included. Two quotes that look far apart often cover very different things.
• "How are backups handled, and where are they stored?" Look for automatic backups on a schedule, stored somewhere other than the website's own server, and that you can get a copy on request. "The host does that" is only a good answer if they know what the host keeps and for how long.
• "What happens after launch?" Ask who applies updates, what a small change costs, how quickly they respond when something breaks, and whether there is a warranty period for bugs. Also ask what happens if you stop paying a monthly plan: do you keep the site and its files, or does it go away?
• "Can I see sites you built that are still live, and talk to one of those owners?" Visit them on your phone. Check that contact forms work and pages load reasonably fast. A short call with a past client tells you more than any portfolio page.
• "How do you want to be paid?" A deposit with the balance on milestones or completion is normal. Full payment upfront for a build that has not started is not.

What this usually means

Most website disputes are not about design at all. They are about ownership and access — who holds the domain, who controls the hosting, who has the admin password — and they surface months or years later, when the developer has moved on and the owner discovers they cannot change a phone number or renew a domain without them. Asking these questions up front costs nothing and is completely normal. A professional will have ready answers; hesitation or vagueness here is the most important signal you will get.

Wide price differences usually come from scope, not greed. One quote may include writing your text, setting up email, and a year of hosting; another may be design only and expect you to supply everything. A "cheap" monthly plan may include the site only as long as you keep paying. That is why the written list of what is included matters more than the headline number. Ask each candidate to quote the same list and the comparison gets much easier.

Red flags worth walking away from: the developer insists on registering the domain in their own name "to make it easier"; they will not give you an administrator login; they build on a private system only they can edit; there is no written scope; they want everything paid upfront; they cannot show you any live sites or put you in touch with a past client; or they promise specific Google rankings or guaranteed traffic. None of these require technical knowledge to spot — they only require asking the question and listening to the answer.

What not to do

• Don't let a developer register your domain in their own name or their own account, even temporarily.
• Don't accept a finished site without your own administrator login and your own logins to hosting and the domain registrar.
• Don't choose on price alone. Compare what each quote actually includes, line by line.
• Don't pay the full amount before work starts. A deposit and milestone payments protect both sides.
• Don't believe guarantees of first-page Google rankings. Nobody can honestly promise that.
• Don't skip a written agreement because the person is a friend or a referral. Friendly and vague is still vague.

When to get help

If you already have a site and cannot answer the ownership questions above — you don't know who holds the domain, you have no hosting login, or the only admin account belongs to a former developer — it is worth sorting that out before hiring anyone new. A helper can usually work out from the outside where your domain is registered and where the site is hosted, then walk you through recovering the accounts in your own name. Doing that first means your next developer starts from a clean position, and you never have to go through the same scramble again.

Frequently asked questions

Related free guides