How to Hire a Web Developer: 20+ Questions to Ask Before You Sign Anything

Most business owners who got burned by a web developer say the same thing: "I didn't know what I was getting into." This guide fixes that. Read it before your next conversation with any web developer or agency.

Hiring a web developer is one of the most consequential decisions a small business owner makes. A bad hire can cost you months, thousands of dollars, and leave you with a site you don't own. A good one can become the foundation of how you generate leads for the next decade.

The difference between the two usually comes down to the questions you ask and whether you knew what the answers should sound like before you asked them.

Section 1: Portfolio and Experience Questions

Before you talk about your project at all, you need to understand who you're talking to.

• Can I see 3–5 websites you've built that are similar to what I'm asking for? A developer who only shows you their best work from 2019 is not the same as one who can show you live, recent sites in your industry.
• Did you build these yourself, or did you manage the project? Agencies often show portfolio work that was built by subcontractors. Know who's actually doing the work.
• Can I contact any of these clients? Any developer worth hiring will give you references without hesitation.
• Have you built sites for businesses in my industry or my local market? Local market knowledge matters. A developer who understands Port St. Lucie or the Treasure Coast builds differently than one who has never set up a local SEO page.

Section 2: Ownership and Control Questions

This is the area that causes the most disputes. Get it in writing before you pay anything.

• Who owns the domain name when the project is complete? You should. Full stop. If the developer registers your domain, it should be in your name and transferred to your account control.
• Who owns the code? On most projects, you should own the final deliverable outright. Watch for contracts that license the code to you rather than transferring ownership this can create dependency on the developer forever.
• Where will the site be hosted, and can I move it if I want? Your hosting should be in your name or clearly transferable. Developers who lock you into their hosting as a way to guarantee recurring revenue are not always acting in your best interest.
• Will I have admin access to my own website's backend? Yes, always. If the answer is "we manage that for you," ask why and get specifics.

Section 3: Scope, Timeline, and Revisions

• What exactly is included in the quoted price? "5-page website" is not a scope. Ask for a detailed list: home, about, services, contact, blog and what each page includes (copywriting? stock photos? contact form? analytics setup?).
• What's not included? Just as important. Logo design, copywriting, SEO setup, photography, and hosting are frequently excluded from base quotes and added as surprises.
• How many rounds of revisions are included? Get a number. Unlimited revisions = a nightmare for everyone. Two to three rounds with a clear definition of what constitutes a "revision" is reasonable.
• What's the realistic timeline from signed contract to live site? Add 20% to whatever they say. Projects always take longer. Ask what can delay the timeline and what your responsibilities are (supplying content, providing feedback within X days, etc.).
• What happens if the project goes over timeline? Who is responsible and what's the recourse?

Section 4: SEO and Performance Questions

A site that looks great but doesn't rank or load fast is a very expensive business card. Ask these before agreeing to anything.

• Is on-page SEO setup included? This means: title tags, meta descriptions, header structure, image alt text, and Google Search Console submission. These are not optional they're the bare minimum.
• What will the site score on Google PageSpeed Insights? Ask them to show you recent scores for the sites they've built. Anything below 80 on mobile is a problem.
• Will the site be mobile-first? In 2026, over 70% of local searches happen on mobile. This is not negotiable.
• Do you set up Google Analytics and Search Console? These should be standard. If they're going to charge extra, understand why.
• Will you add schema markup for local business? If they don't know what this is, that's informative.

Section 5: After Launch Questions

• What does ongoing support look like after launch? Is there a support period? An hourly rate? A maintenance plan? What's included in each?
• How do I request changes or updates after launch? Email? Ticket system? Is there a turnaround time commitment?
• What happens to my site if you go out of business or stop working? Especially important with freelancers. If all your credentials are with them and they disappear, what happens to your business?
• Do you provide training so my team can update content ourselves? If you're on WordPress, you should be able to update blog posts and basic content without calling a developer for every change.

Section 6: Contract and Payment Questions

• Do you provide a written contract? Non-negotiable. Anyone operating without one is a red flag, full stop.
• What's the payment structure? Standard is 50% upfront, 50% on delivery. Be wary of developers who require 100% upfront, or who ask for full payment before you've seen anything.
• What are the terms if I want to cancel the project midway? Understand the refund and deliverables policy before you sign.

The 5 Biggest Red Flags

1. No written contract verbal agreements protect nobody.
2. They own your domain this is leverage over you forever.
3. Vague scope with "unlimited revisions" this ends in conflict every time.
4. No portfolio of recent, live work showing Dribbble mockups is not the same as showing real sites that real businesses are using.
5. No mention of SEO or mobile performance if they're not talking about these, they're building you something Google will ignore.

What a Good Answer Sounds Like

When you ask "who owns the code," a great developer says "you do, completely" without hesitation. When you ask about SEO, they talk about schema markup and Core Web Vitals. When you ask for references, they send you three names within an hour. When you ask about the timeline, they give you a realistic estimate with contingencies, not a promise they'll inevitably miss.

The best web developer relationships are partnerships they should be as interested in understanding your business goals as you are in understanding their process.