The SEOFlow Agency

000

// Build

Launching a trade company website in Webflow without losing a month

A page-by-page structure for solar, roofing and HVAC businesses that need to be live before the next campaign starts — and the parts you can safely leave until later.

Most trade company websites take too long for a reason that has nothing to do with design. They take too long because nobody decided, in advance, what the site was for. Without that decision every page becomes negotiable, every review round reopens settled questions, and a four-week build turns into three months of drifting.

This is the structure I use when a solar installer, roofer or HVAC company needs to be live quickly and the site has one job: turn people who are already searching into people who ring the phone.

Decide the one action first

Before a single page is designed, name the single action the site exists to produce. For most trade businesses it is a phone call, occasionally a form for a free assessment, very occasionally a booked slot in a calendar.

Pick one. Not three. Every additional call to action divides attention and each one needs its own follow-up process that somebody has to actually run. A site with one obvious action and a well-drilled response beats a site with a chat widget, a quote calculator and a newsletter box where two of the three are quietly ignored.

The five pages that matter

A trade company needs five pages at launch. Everything else can come later, and most of it never needs to come at all.

Home. Above the fold: what you do, where you do it, and the action. “Solar installation across greater Phoenix. Free roof assessment, usually within 48 hours.” That sentence does more work than any hero image. Below it: proof — real installation photographs, not stock; a review count with the platform named; any licence or certification numbers, because in trades those are trust signals that convert.

Services. One page listing what you do, with enough detail that someone can tell whether their job fits. If you do residential but not commercial, say so here. Being explicit about what you decline saves you a dozen wasted calls a month, which is worth more than the two you might have converted.

Work. Six to ten real jobs with photographs, the suburb, and one line about what made the job interesting or difficult. Suburb names matter more than most owners expect: they are how people search, and they are how a prospect decides whether you work near them.

About. Who runs the business, how long it has existed, and a photograph of actual people. Trades are bought on trust, and a stock photo of a smiling model in a hard hat destroys trust faster than having no photograph at all.

Contact. Phone number as tappable text, service area, hours, and a short form. Three fields at most: name, phone, and what you need. Every extra field costs completions and none of the information is worth that.

What to leave out at launch

  • A blog. If you are not going to write consistently, an empty journal with three posts from launch week actively damages credibility.
  • A quote calculator. Trade pricing depends on site conditions. A calculator either lies or hedges so heavily it is useless, and both outcomes cost you the call.
  • Live chat, unless somebody is genuinely watching it. An unanswered chat widget is worse than none.
  • A gallery of a hundred photographs. Ten good ones beat a hundred mediocre ones, and the hundred take three weeks to caption.

Why Webflow, and when not to

Webflow suits this well: hosting and SSL are handled, the CMS is comfortable enough for a non-technical owner to add a project without breaking layouts, page speed is good by default, and the structure is clean enough that search engines have no trouble with it.

It is the wrong choice in three situations. If you need real e-commerce with inventory, look elsewhere. If your team is genuinely non-technical and nobody will ever log in, a simpler platform may serve better. And if you are publishing several times a week and need editorial workflow, WordPress still does that better.

A realistic three-week schedule

Week one is content. Not design — content. Photographs, service descriptions, service area, the exact phone number, licence numbers, review links. This is where projects die. Booking a photographer for a half day on a live job produces better material than any amount of chasing the owner for pictures on their phone, and it costs less than a week of delay.

Week two is design and build. With content in hand, the home page and one interior template take a couple of days. The rest is assembly. Build mobile first, genuinely — the majority of trade traffic is a phone, often outdoors, often on a poor connection.

Week three is testing and launch. Every phone link tapped on a real device. Form submissions arriving where someone will see them, which usually means a phone notification rather than an inbox nobody opens. Page speed checked on a throttled mobile connection. Redirects mapped from every old URL, because losing existing rankings on launch day is the most common and most expensive mistake in this entire process.

The parts people skip that actually matter

Redirects. If a site exists today, every URL that ranks needs a 301 to its new equivalent. Skipping this can cost months of accumulated search visibility overnight.

The Google Business Profile. For most local trades this drives more calls than the website. The site should match it exactly — same name, same address format, same phone number, same hours.

Where the leads land. Decide who receives form submissions and how fast they respond. Studies of lead response time all point the same direction and the effect is dramatic: the business that calls back within five minutes wins most of the time, almost regardless of anything else. A beautiful site feeding an inbox checked twice a week is a beautiful waste.

After launch

Give it a month, then look at three things: how many people call from the site, which pages they were on when they called, and which search terms brought them. That is enough to decide what to build next, and it is a far better basis than anyone's opinion, including mine.

What to hand over

A launch is not finished when the site goes live. It is finished when the owner can operate it without you, and the gap between those two moments is where most projects quietly sour.

The handover pack that prevents this is short. A one-page document listing where the domain is registered, where the site is hosted, who has admin access, and what the renewal dates are. A ten-minute screen recording showing how to add a project and change a phone number — the two things they will actually need. And confirmation of where form submissions go and who is responsible for answering them.

Also hand over the accounts properly. The site should be in the client's Webflow account with you invited, not in yours with them dependent on you. Owners are rarely told this matters until the day it does, and it is one of the clearest signals that you are working in their interest rather than building a dependency.

The instinct after launch is to add pages. Usually the right move is to improve the five you have. A home page that converts eight per cent instead of four is worth more than nine new service pages, and it takes a fraction of the effort.

// Start here

Tell me what's not working

Thirty minutes, no deck. If I'm not the right person for it, I'll say so and point you at someone who is.

Book a call