Start With Ownership: Who Actually Controls the Site When It's Done?
This is the question most contractors skip, and it's the one that costs the most later. Ask directly: when the project is finished, do you own the domain, the hosting account, and the code, or does the designer? A shocking number of contractor sites are built inside a designer's agency account, on a platform license the designer controls, with login credentials the designer never hands over. That's not a website. That's a rental.
Get specific answers to three things before you sign anything:
- Domain registrar. Whose account is the domain purchased under? It should be yours, full stop, even if the designer manages it day to day.
- Hosting account. Ask what happens if you stop paying the designer's monthly fee. If the answer is "the site goes dark," you don't own a website, you're leasing one.
- The code itself. Can you get a full export or a copy of the files? On a hand-coded static site there's no proprietary lock-in: it's HTML, CSS, and JavaScript files that run anywhere. On a page-builder platform (Wix, Squarespace, some WordPress builder plugins), the design often can't leave that platform at all.
A contractor who's run a crew for fifteen years understands this instinctively on a jobsite: you don't sign a contract where the other guy holds the only key to your own building. A website should work the same way. Ask the ownership question in the first call, not the last one, and get the answer in writing before deposit money changes hands.
What Platform Is It Built On, and Why Does That Matter?
"What platform will my site run on?" is a fair question to ask any designer, and the answer tells you a lot about what you're buying. Most contractor sites on the market today are built one of three ways: a drag-and-drop builder (Wix, Squarespace, GoDaddy Website Builder), WordPress with a page-builder plugin (Elementor, Divi, and similar), or hand-coded static HTML/CSS/JS with no CMS at all.
Each has real tradeoffs. Drag-and-drop builders are fast to spin up but slow to load, because the platform ships a huge amount of generic code your visitor's browser has to download before your actual content shows up. WordPress with a page-builder is flexible and familiar to a lot of designers, but it carries plugin bloat, needs constant security patching, and is the single most common target for the kind of hack-and-redirect spam that silently tanks a contractor's rankings for months before anyone notices.
Hand-coded static sites (no WordPress, no page-builder, no database) load faster because there's nothing extra to load: just the page. That's the build we run, and it's why we can commit to a load time under 2 seconds instead of hedging with "it depends." There isn't a plugin between your homepage and your visitor's phone.
None of that means a WordPress site or a builder site is automatically a bad hire. It means you should know which one you're getting, and ask why. A designer who can explain the tradeoff plainly, and who has a real technical reason for their platform choice beyond "it's what I know," is worth more than one who dodges the question.
| Platform type | Typical load speed | Ongoing plugin/security risk |
|---|---|---|
| Drag-and-drop builder | Slow (heavy generic code) | Low, but locked to the platform |
| WordPress + page-builder | Moderate, varies by plugin count | Higher (constant patching) |
| Hand-coded static site | Under 2 seconds | None (no plugins to exploit) |
None of these platforms are inherently disqualifying on their own, but the load-speed gap compounds fast in the field. A homeowner searching for emergency service on a cracked phone screen at a jobsite will bounce off a slow-loading page before they ever see your reviews or your phone number. Ask for the load-speed figure as a specific number tested on mobile data, not a general assurance that the site will "load fine."
Ask to See Real Contractor Sites, Not a General Portfolio
If a designer can't produce real contractor examples, or the examples they show you are slow, generic, or clearly built off the same template with a new logo pasted on, that's your answer. This silo (contractor websites) is specifically about what gets built and handed over: the design, the code, the structure, and the trade-specific money pages. If a designer's contractor portfolio is thin, the build itself is probably thin too.It is fair to ask a designer to walk you through why they built a service-area page the way they did. A strong answer references the specific trade and specific geography: why a roofer's page for one county reads differently than the page for a neighboring one, or why an HVAC company's emergency page leads with response time instead of a photo gallery. A weak answer is a shrug, or a claim that "every trade is basically the same." They are not. A dock builder's buyer and a plumber's buyer are looking for different proof, on different timelines, with different urgency, and a site that treats them identically usually converts poorly for both.
Ask, too, whether the designer has ever turned down a project because the fit was wrong. A designer who takes on every lead regardless of trade or budget is running volume, not craft. One who can describe walking away from a mismatched job, a client who wanted a $99 template dressed up as a custom build, or a scope that didn't make sense for the business, is telling you something real about how they operate. That kind of judgment tends to show up in the finished site.
Get a Straight Answer on Timeline and What Happens After Launch
Ask two blunt questions before you sign: how long will this take, and what happens the day after it goes live? A vague answer to either one is a warning sign.
On timeline, a hand-coded contractor site with trade pages, service-area pages, and a working quote form is a build measured in weeks, not months, once content and photos are in hand. If a designer quotes six months for a standard contractor site with no unusual complexity, ask what's filling that time. Long timelines are sometimes legitimate (a large multi-location company with a lot of custom functionality), but for a typical single-location or regional contractor, a drawn-out schedule usually means the designer is juggling too many clients, working through a slow revision-heavy process, or padding the estimate.
On what happens after launch, get specific about who owns which piece going forward:
- Hosting and uptime. Who's responsible if the site goes down, and how fast do they respond?
- Content updates. If you need to add a new service area or swap a phone number, can you do it yourself, or does every change require a ticket and an invoice?
- Security and technical maintenance. On a static hand-coded site there's very little ongoing maintenance risk because there's no plugin ecosystem to patch. On a WordPress build, someone has to own plugin updates, or the site becomes a liability.
This guide covers the build itself: design, code, speed, and structure. What happens with ongoing search rankings after launch (keyword growth, backlinks, organic traffic) is a separate, ongoing discipline that a website vendor and an SEO vendor sometimes are, and sometimes aren't, the same company. Ask which one you're hiring, because the scope of work is genuinely different.
It helps to get the handoff plan in writing too: what training or documentation you get on launch day, how long the designer stays reachable for bug fixes after go-live, and whether "support" means a phone call or a ticket queue with a multi-day wait. A contractor who runs a crew knows the value of a clean punch list at the end of a job. Ask for the same thing here: a written list of what's done, what's pending, and who's responsible for each item once the site goes live.
Ask How the Site Is Structured for AI Search, Not Just Google
This is the newest question on the list, and most designers still don't have a good answer to it. Homeowners increasingly ask ChatGPT, Perplexity, or Google's AI Overview "who's a good roofer near me" or "how much does a bathroom remodel cost in [city]" instead of typing a search and scrolling through blue links. Those AI tools don't crawl a site the way Google's classic search index does. They favor pages with clear, direct answers: real service descriptions, real pricing ranges where possible, clean structured data, and content that's specific to the actual trade and the actual service area, not generic filler.
Ask your designer these two questions directly:
- "Does the site include structured data (schema markup) that tells search engines and AI tools exactly what services I offer, where I operate, and how to reach me?"
- "Are the trade and service pages written specifically for my business, or are they templated boilerplate with the city name swapped in?"
A site built to be AI-search-readable isn't a separate product bolted on top of a normal website. It's a structural decision made at build time: clean HTML, clear headings that actually answer questions, an FAQ section that mirrors what a homeowner would type into a chat window, and schema that spells out your service area and trade in a machine-readable format. A designer who's never heard the term "AI Overview" or can't explain how their page structure supports it is building you a 2020 website in 2026.
One important boundary here: building the site so it's AI-readable is a one-time structural decision that happens at build time. Running an ongoing campaign to actively win AI citations, monitor how often you show up in ChatGPT answers, and keep optimizing for it month over month is a separate, recurring service. Ask which one you're being quoted, because "AI-ready" and "an active AI visibility program" are two different scopes of work.
Compare Quotes Apples-to-Apples: What's Actually Included
Two quotes that look close in price can represent wildly different scopes of work. Before you compare numbers, make sure you're comparing the same list of deliverables. Ask every designer you're considering to answer these in writing:
| Question | Why it matters |
|---|---|
| How many pages are included, and which ones? | A homepage-only quote and a homepage-plus-20-trade-page quote aren't the same project. |
| Is the quote form connected to a real lead notification? | A form that just sits there with no email alert wired up is worse than no form. |
| Are service-area pages included, and how many? | One page for a whole county reaches fewer local searches than pages built per city or ZIP cluster. |
| Who writes the copy? | Boilerplate copy with the city name swapped in reads as generic to both humans and AI search tools. |
| What's the load-time target? | Under 2 seconds is achievable on a hand-coded static build; ask for a number, not a vibe. |
| What's excluded? | Photography, logo design, and copywriting revisions beyond a set number are common exclusions. Get the list. |
A lower quote that excludes service-area pages, real copywriting, and lead-form wiring isn't actually cheaper: it's a smaller project wearing a bigger project's price tag. Get the full scope in writing, page by page, before you compare the bottom line.
One more thing worth asking: what happens if the first draft misses the mark? Some designers include a set number of revision rounds in the base price; others bill every change as a separate line item. Get that number in writing too, because a site that needs three or four rounds of "make the hero section actually explain what we do" is normal, not a sign you chose wrong, but it should be priced in up front rather than surprise you on the final invoice.
Red Flags That Mean Walk Away
Some warning signs are worth naming plainly, because contractors keep running into the same handful of bad setups.
- No real portfolio you can visit on your own phone. Screenshots in a PDF proposal are not the same as a live, working site.
- Vague or dodged answers on hosting and ownership. If you can't get a straight answer to "who owns the domain when this is done," assume the answer is "not you."
- A price that seems too low for the described scope. A $99/month DIY builder or a $500 total-price WordPress theme swap is rarely a real contractor website; it's usually a template with your logo pasted on, and it usually doesn't rank or convert.
- No mention of load speed, mobile testing, or AI search at all. If the pitch is entirely about how the site looks, with nothing about how it performs or gets found, that's a designer selling looks, not results.
- A relative, friend, or side-hustle designer with no other contractor clients. This is often how the first bad website happens. It's not a knock on the person, it's a scope mismatch: contractor sites have specific mechanics (service areas, trade-specific proof, lead forms wired correctly) that a generalist may not have built before.
- Contracts that lock you into their hosting with no export path. If leaving means losing the whole site, you don't have a website, you have a lease.
None of these are dealbreakers in isolation, necessarily, but two or three together is a pattern worth taking seriously before you sign a deposit check.