21 Questions to Ask a Web Developer Before Hiring
Hiring a web developer is easy. Hiring the right one is mostly about asking the questions they would rather you did not. Here is the list I would use if I were on your side of the table.
By Muhammad Umer Khan · · 9 min read
I am a freelance web developer, so this list is written from the other side of the call. These are the questions that reveal how someone actually works, not just what their portfolio looks like. For each one you will find what a good answer sounds like and the red flag that should make you pause.
Before you reach out
Write down three things first: what the website must do (bookings, quote requests, sales), your budget range, and your deadline. A good developer will ask about all three. If you already know them, you will get faster, more honest quotes. If you are unsure about budget, the website cost calculator gives a realistic range in a minute.
Portfolio and live sites
- Can I see three live sites you built, not just screenshots? Good: links you can click, on real domains. Red flag: only mockups, or sites that are offline.
- Which of these is closest to my project, and what did you do on it? Good: a specific answer about their part. Red flag: vague "we did everything" when they clearly used a template.
- Can I speak to, or read reviews from, a past client? Good: verified reviews on a platform like Upwork, or a reference. Red flag: no reviews anywhere you can check.
Process and timeline
- What happens in the first week? Good: a discovery call, a sitemap, and a plan with dates. Red flag: "I'll just start building."
- How will I review progress? Good: a private staging link you can open on your phone. Red flag: screenshots only, until the end.
- How long will it take, and what would delay it? Good: a range, plus "waiting for content" named honestly as the usual delay. Red flag: an exact date with no caveats.
- Who will actually do the work? Good: a clear answer. Red flag: you meet one person and the work is quietly passed to someone else.
Pricing and changes
- Is the quote fixed or hourly? Either can work, but you should know which and what is included.
- How are payments split? Good: a deposit and milestone or launch payment. Red flag: 100% upfront from someone you have never worked with.
- What counts as a change, and how is it priced? Good: a written rule, such as "new pages or features are quoted before work starts." Red flag: "we'll figure it out."
- What will this cost me every year after launch? Good: hosting, domain, premium plugins and maintenance listed. Red flag: the build price is the only number you ever hear.
Ownership: domain, hosting and code
- Whose name will the domain be registered in? It should be yours. This is the single most important answer on the list.
- Who owns the hosting account and the code? Good: you do, with the developer added as a user. Red flag: "we host it for you" with no way to move it.
- Will I get all logins and a handover? Good: yes, plus a short walkthrough video. Red flag: hesitation.
SEO, speed and mobile
- How will the site perform on a phone? Mobile is now most web traffic: about 60% worldwide according to StatCounter. Good: they test on real devices and talk about load time.
- Why does speed matter for my business? Good: they can explain it in money. A Deloitte and Google study found a 0.1-second faster mobile site lifted retail conversions by 8.4%.
- What SEO is included? Good: titles, descriptions, headings, schema, sitemap, redirects from old URLs. Red flag: "SEO is a separate monthly package" with nothing on-page included.
- If you are replacing my current site, how do you protect my Google rankings? Good: a URL map and 301 redirects. Red flag: they have not heard of redirects.
Support after launch
- What happens if something breaks a month later? Good: a stated support window and response time.
- Can my team edit text and images without you? Good: yes, and they will show you how. Red flag: every small edit needs a ticket.
- What is the one thing you would change about my current site? This shows whether they looked at it, and how they think.
Red flags worth walking away from
- They want the domain registered in their name.
- They cannot show live work.
- They promise a fixed Google ranking or "page 1 guaranteed".
- No written scope, or a scope that only says "website".
- They go quiet for days during the sales process. It rarely improves after you pay.
Vetting a developer on Upwork
Marketplaces add a useful layer of proof. Check the Job Success Score, read the written reviews rather than just the stars, look for repeat clients, and see whether past jobs resemble yours. Payment protection through the platform also lowers the risk of the deposit.
If you would like to put these questions to me, I am happy to answer every one of them on a call. You can also read freelancer vs agency if you are still deciding which route to take, or book a free 20-minute call.