Questions to Ask a Web Development Contractor Before Hiring

Most website projects don't fail at launch. They fail in the first sales call, when nobody asks the right questions. The contractor promised "a modern, fast, SEO-friendly site"; you nodded, and three months later you own a pretty site that nobody can find, that only they can edit, and that costs extra every time you want a change.

The fix is simple: interview contractors properly. Below are the questions to ask a web development contractor before hiring, grouped by what they actually reveal — skill, process, technical quality, cost, ownership, and long-term support. For each one, you'll see what a good answer sounds like and what should make you walk away.

Quick answer: the most important questions to ask a web development contractor

If you only have time for a short call, ask these ten:

1. Can you show me live sites you built that are similar to my project?
2. Who will actually do the work — you, your team, or subcontractors?
3. What is your process from discovery to launch, and where do I give approval?
4. Which platform or tech stack do you recommend for me, and why?
5. How do you handle SEO, page speed, and mobile performance during the build?
6. What exactly is included in the quote, and what costs extra?
7. How do you handle scope changes and extra revisions?
8. Will I own the domain, hosting, code, design files, and all logins?
9. What happens after launch — support, maintenance, security updates?
10. Can I speak to two or three past clients?

A contractor who answers all ten clearly and without getting defensive is worth a serious look. The sections below explain why each question matters and how to judge the answer.

Questions about experience and portfolio

These questions tell you whether the contractor has solved your kind of problem before, or will be learning on your budget.

1. Can you show me live websites you built that are similar to mine?

Ask for live URLs, not screenshots or Dribbble mockups. A live site shows you what a design file can't: how fast it loads on your phone, whether the forms work and whether the menu makes sense.

"Similar" matters. A contractor who builds beautiful portfolio sites for photographers may struggle with a 40-product WooCommerce store or a booking system with payment logic.

Good answer: Two or three live projects close to yours, plus a short explanation of the problem each one solved.

Red flag: Only mockups, or "most of our work is under NDA" with nothing to show at all.

2. What was your exact role on those projects?

Portfolios often blur who did what. The contractor may have written the front-end code while another agency handled design, hosting, and SEO. That's fine — but you need to know which parts they can deliver on your project.

3. Who will actually work on my website?

With a freelancer, you want to know if they subcontract. With an agency, you want to know if the senior person on the sales call ever touches your project.

Ask for names and roles: who designs, who develops, who tests, and who is your day-to-day contact. Outsourcing isn't automatically bad. Hidden outsourcing is.

4. Have you worked in my industry?

Industry experience isn't mandatory, but it shortens the learning curve. A developer who has built clinic websites already knows about appointment booking and privacy expectations. One who has built B2B sites knows that quote forms and spec sheets matter more than flashy animations.

5. Can I speak with two or three past clients?

This is the question weak contractors dread. When you speak to references, skip "Were you happy?" and ask something specific:

• Did the project finish on time and on budget?
• How did they handle problems or disagreements?
• Do you still work with them after launch?
• Did you get full access to your site when the project ended?

Questions about process, communication and timeline

A skilled developer with a messy process will still miss deadlines. These questions show you how the project will feel week to week.

6. What is your process from start to launch?

A professional contractor can explain their process in two minutes without notes. It usually looks something like: discovery and requirements, sitemap and wireframes, visual design, development, content entry, testing, launch and handover.

Listen for where you approve things. If design sign-off happens before development starts, late surprises get much rarer.

7. What do you need from me, and when?

Many projects stall because the client is late with content, photos or feedback — not because the developer is slow. A good contractor tells you upfront what they need from you and by when. Ask who writes the page copy. If the answer is "you do," budget time for it now.

8. How will we communicate, and how quickly do you respond?

Agree on the channel (email, Slack, WhatsApp, a project board), how often you'll get updates, and a normal response time. If you're in different time zones, ask about overlapping working hours.

9. What is a realistic timeline, and what could delay it?

Be wary of anyone who promises a complex custom site in a week. A better answer breaks the timeline into milestones and names the usual risks: late content, extra revision rounds, third-party integrations and hosting or domain access issues.

10. How many revision rounds are included?

"Unlimited revisions" sounds generous but often means nobody defined the scope. A clear number of rounds per phase protects both of you and keeps the project moving.

Technical questions: platform, SEO, speed and security

You don't need to be technical to ask these. You only need to notice whether the answers are clear and specific, or vague and full of buzzwords.

11. Which platform do you recommend for my site, and why?

WordPress, Shopify, Webflow, a custom Next.js or React build — each suits different needs. The right answer depends on your goals, budget, and who will update the site after launch.

Good answer: A recommendation tied to your situation, such as "You'll publish blogs weekly and your team isn't technical, so WordPress with a lightweight theme makes sense."

Red flag: Every client gets the same stack, whatever they need.

12. Will I be able to update content myself?

Ask for a short demo of the editing experience. If changing a phone number or adding a blog post requires a developer, you'll be paying for small edits for years.

13. How do you handle SEO during the build?

This is the question most business owners skip, and it's often the most expensive one to get wrong. Many sites launch looking great but with technical problems baked into the build: slow load times, messy URLs, missing meta tags, no XML sitemap, poor heading structure or content hidden from search engines.

Fixing those after launch usually means paying a second team to undo the first team's work. That's why some agencies now offer web development and SEO services in one build — so the site's structure, URLs, and technical foundations are planned for search from day one.

Ask the contractor specifically about:

• Clean URL structure and a logical site architecture
• Editable title tags and meta descriptions on every page
• Proper heading hierarchy (one H1 per page)
• XML sitemap and robots.txt setup
• Schema markup where it fits (business details, products, FAQs)
• 301 redirects if you're replacing an existing site
• Google Search Console and analytics setup at launch

Red flag: "Our sites are SEO-friendly" with no detail behind it, or "Just install a plugin."

14. How fast will the site be, and how do you measure it?

Google uses Core Web Vitals as part of how it evaluates page experience. A serious contractor will mention them, test on real mobile devices, and optimize images, fonts, and scripts. Ask what speed score or load-time target they aim for, and whether they'll show you the results before launch.

15. Will the site be mobile-friendly and accessible?

"Responsive" is the bare minimum. Also ask about accessibility basics: readable colour contrast, alt text on images, keyboard navigation, and properly labelled forms. These help real users and reduce legal risk in some markets.

16. How do you handle security?

Listen for SSL certificates, regular updates of the CMS and plugins, secure hosting, strong admin access controls and automatic backups. If the site handles payments or personal data, ask how that data is protected and stored.

Questions about cost, contracts and ownership

This is where most disputes start. Get every answer here in writing.

17. What exactly is included in your quote?

Two quotes with the same price can cover very different work. Ask for a line-by-line breakdown: number of pages, design, development, content entry, copywriting, stock images, integrations, SEO setup, training, and post-launch support.

Then ask the reverse question: what is not included? Common extras include premium plugins or themes, hosting, domain renewal, stock photos, copywriting, and ongoing maintenance.

18. What is your payment structure?

A common, fair setup is a deposit upfront with the rest tied to milestones — for example, design approval and launch. Be cautious if a contractor wants 100% upfront, especially on a first project together.

19. How do you handle changes to the scope?

New ideas always come up mid-project. A good contractor has a simple change-request process: they estimate the extra work, you approve it in writing, then they build it. Without this, you either get surprise invoices or a contractor who quietly cuts corners elsewhere.

20. Will I own everything when the project is finished?

This is one of the most important questions to ask a web development contractor before hiring. You should own, and have admin access to:

• Your domain name (registered in your name or your company's)
• Your hosting account
• The website code, theme and design files
• All CMS admin logins
• Google Analytics, Search Console and Google Business Profile
• Licences for any paid plugins or fonts

If a contractor registers your domain in their own name or holds your logins hostage, leaving them later becomes painful and expensive.

21. Is there a written contract?

Always. The contract should cover scope, timeline, payment milestones, revision limits, ownership of work, confidentiality and what happens if either side ends the project early. This isn't legal advice, so for larger projects it's worth having a lawyer review the terms.

Questions about launch, maintenance and support

Launch day is the start of your website's life, not the end of the project. Ask these before you sign, not after something breaks.

22. How do you test the site before launch?

Look for testing across browsers and devices, form and checkout testing, broken-link checks, speed tests and a staging site where you can review everything before it goes live.

23. If you're replacing my current site, how will you protect my rankings?

A redesign can wipe out years of search traffic if old URLs disappear without redirects. Ask how they'll map old pages to new ones, keep valuable content and monitor traffic after the switch. If they look confused by the question, that's your answer.

24. What support do you offer after launch?

Ask how long free bug fixes last after launch, and what ongoing maintenance costs. A monthly plan might cover updates, backups, uptime monitoring, security patches, and a set number of small content changes.

25. Will you train my team and provide documentation?

A short recorded walkthrough of the admin area saves you dozens of support emails later. Documentation also matters if you ever switch developers.

26. How will we measure whether the website is working?

A website is a business tool, so success should mean more than "it launched." Ask which results the contractor will help you track: enquiries, calls, form submissions, sales, or organic traffic. Contractors who think this way tend to build sites that earn their cost back. KodRank's guide to SEO performance marketing explains how to connect rankings to leads and revenue rather than vanity numbers.

Red flags to watch for when hiring a web developer

Sometimes how a contractor answers tells you more than what they say. Walk away, or at least slow down, if you notice any of these:

• A price before any questions. A quote sent before they understand your goals, pages and features is a template, not a plan.
• Vague answers about SEO or speed. "Don't worry, it'll be optimized" isn't a process.
• No written scope or contract. Handshake deals are how "small extras" turn into big invoices.
• They keep ownership of your domain, hosting or code. This locks you in.
• No live work or no references. Everyone starts somewhere, but you shouldn't be the experiment on a business-critical project.
• Guaranteed #1 Google rankings. Nobody controls Google's results. A promise like this is a sales line.
• Pressure to sign quickly. Limited-time discounts on a website contract are a warning sign, not a bonus.

Many of these apply when you hire an SEO agency too. KodRank's checklist on how to evaluate an SEO company covers the same warning signs, from vague reporting to agencies that hold your accounts.

How to compare contractors side by side

Once you've interviewed two or three contractors, put their answers next to each other. A simple comparison table like this keeps you from choosing on price alone:

The cheapest quote often becomes the most expensive project once you add the extras, the delays and the cleanup work. Weigh clarity and ownership as heavily as price.

Frequently asked questions

What should I ask a web developer before hiring them?

Ask to see similar live work, who will do the work, their process and timeline, which platform they recommend and why, how they handle SEO and speed, what the quote includes and excludes, who owns the finished site and what support you get after launch. Also ask for two or three client references.

Should I hire a freelancer or an agency for web development?

A freelancer usually costs less and gives you direct contact with the person building your site. An agency gives you a wider team — design, development, SEO and support — and more backup if someone is unavailable. For a simple brochure site, a strong freelancer is often enough. For e-commerce, custom features or SEO-driven growth, an agency is usually the safer choice.

How do I know if a web development quote is fair?

Compare at least three detailed quotes for the same scope. A fair quote lists deliverables clearly, separates one-time and recurring costs, and explains what's excluded. Very low quotes often leave out content, SEO setup, testing, or support, which you then pay for later.

Who should own my website after it's built?

You should. Your domain, hosting account, code, design files, and all admin logins should be in your name or your company's. Put this in the contract before any work starts.

Is SEO included in web development?

Not always. Some developers build the site and leave SEO entirely to you or a separate agency. Others build technical SEO foundations — clean URLs, editable meta tags, sitemaps, schema and fast load times — into the project. Ask exactly which SEO tasks are included in the quote.

What documents should I get when the project ends?

At minimum: a list of all logins and accounts, licence details for paid plugins and fonts, a copy of the code and design files, basic documentation or a training video, and your signed contract with the final scope.

Final thoughts: ask more questions now, pay less later

Hiring a web development contractor is a bigger decision than it looks. The site you launch will shape how customers find you, trust you, and contact you for years.

The questions in this guide aren't meant to trap anyone. Good contractors welcome them, because clear answers make projects smoother for both sides. Pay close attention to three areas: SEO and performance, what the price really includes and who owns the site at the end. Those are where most expensive mistakes happen.

If you'd rather not manage one team for the build and another to fix its SEO later, KodRank builds websites with SEO engineered in from the first line of code — one team, one build, ready to rank from launch day. Bring these questions to your first call; we'll happily answer every one.

— Written by

Fahad Bin Khalid

Co-founder, KodRank

Fahad is a co-founder of KodRank, building fast WordPress and custom web platforms with clean architecture, Core Web Vitals performance, and SEO-ready foundations from day one.