12 questions to ask before you hire a website developer
The questions a business owner should ask any freelancer or agency before paying for a website: who owns the domain, hosting and code, who writes the content, how changes are charged, what happens after launch, and the red flags to walk away from.
Vishal Solanki · Full-stack developer, Noida
A website project can go wrong even when the developer codes well. It goes wrong when nobody agreed, at the start, on who owns what, who does what and what happens after the site goes live.
I'm a freelance developer, so these are the questions I think you should ask me, or anyone else you are considering. A good developer will have answers ready.
Short version: before you pay anything, get clear answers in writing on five things: you own the domain, the hosting account and the code; what is included and what is not; who supplies the text and photos; how changes and support are charged after launch; and which live sites you can look at that this person built.
1. Who will own the domain name?
The domain is your address on the internet. It should be registered in your name, in an account you can log in to, with your email address on it. A developer can manage it for you, but they should not own it.
If the domain is in someone else's account and you fall out, they hold your address, and with it your email and your search rankings.
2. Who owns the hosting account, and can I move?
Hosting is where the site's files live. Ask whether the hosting account will be yours or the developer's, and what it would take to move the site to another host or another developer.
Hosting through your developer is not wrong, but you should know that you can leave, and how.
3. Do I get the code and the design files?
When the project is paid for, you should receive the source code, the design files and the logins for everything connected to the site. Ask if anything is licensed, not owned: a paid theme, a plugin with a yearly fee, stock images or fonts.
If the site is built on a platform you rent, such as a website builder, there may be no code to hand over. That is fine as long as you know it before you start. I compare the options in website builder, template or custom build.
4. What exactly is included?
Ask for a written list: how many pages, which features, how many rounds of design changes, and what counts as finished. "A website" is not a scope.
Ask the opposite question too: what is not included? Common gaps are the logo, the text, photography, the business email setup and entering all your products.
5. Who writes the text and supplies the photos?
Waiting for content is a common reason a website launches late. Some developers write it, some expect it from you, and some will tidy up what you send. Any of these can work, but agree which it is, and by what date.
6. How long will it take, and what does that depend on?
A realistic timeline has stages: plan, design, build, review, launch. Ask what happens at each stage and what the developer needs from you to keep it moving.
Be wary of a date with no conditions attached. Every timeline depends on how quickly content and feedback arrive.
7. How will I make changes myself?
Ask which parts of the site you will be able to edit without help: text, prices, photos, blog posts, opening hours. Then ask to see what the editing screen looks like.
8. How are changes charged after launch?
You will want changes. Ask how they are priced: by the hour, per request or under a monthly plan. Ask how quickly small changes are normally done, and whether there is a period after launch when fixes are free.
Make sure you understand the difference between a bug (something that does not work as agreed, which should be fixed without charge) and a change (something new you have decided you want).
9. What happens after launch?
A website needs looking after: software updates, backups, security fixes and renewals for the domain and hosting. Ask who does each of these, how often, and what it costs.
10. Will it be fast on a phone?
Ask how the developer checks speed, and ask them to run one of their live sites through Google's PageSpeed Insights tool in front of you, on the mobile setting. You are checking that they measure it at all. What the numbers mean is in Core Web Vitals in 2026.
11. What SEO basics are included?
Nobody can promise you the top spot on Google, and you should not trust anyone who does. What a developer can and should do is the groundwork: a unique title and description on every page, a clear heading structure, a sitemap, sensible page addresses, and Google Search Console set up in your name.
Ask which of those are included. Ongoing SEO, such as writing articles and earning links, is separate work. The groundwork is listed in my SEO checklist, which you can hand to whoever you hire.
12. Which live sites can I look at?
Ask for links to sites the developer built that are online now. Open them on your phone. Are they quick? Is it clear what each business does? Do the forms and buttons work?
Then ask what the developer's part was. If you can speak to a past client, do. Ask them how the project went after the first payment, not only how the site looks.
Red flags
Any one of these is a reason to slow down. Several together are a reason to walk away.
| Red flag | Why it matters |
|---|---|
| The domain or hosting will be in their name only | You can't leave without their cooperation |
| A guaranteed first-place ranking on Google | Nobody controls Google's results |
| No written scope | Every disagreement later becomes your word against theirs |
| Full payment asked for before any work is shown | You have nothing to hold them to |
| No live sites to show, or only screenshots | You can't check speed or quality from a picture |
| A price given before any questions about your business | The quote is for a generic site, not for what you need |
| They won't say what the site will be built with | You can't judge whether someone else could maintain it |
FAQ
Should I hire a freelancer or an agency?
It depends on the size of the job and how you like to work. With a freelancer you talk directly to the person building the site, but one person has limited hours. An agency has more people and more process. Either can do a good job on a small business website. The questions above matter more than the label.
Do I need a written contract for a small website?
Yes, though it does not need to be long. One or two pages covering the scope, the price, the payment stages, the timeline, who owns what and what happens after launch is enough. A clear email that both sides confirm is better than nothing.
What should I prepare before I contact a developer?
Three things help most: a sentence on what you want the website to achieve, two or three websites you like and why, and a rough idea of the pages you need. If you already have a site, run it through my 12-point checklist first so you know what you want fixed.
You are welcome to ask me all twelve. I'm a full-stack developer based in Noida, I take freelance and contract work, and I'm happy to answer these before you commit to anything. Get in touch, or read about hiring me as a website developer in Noida.