Websites built for tree companies, not for awards

    A tree service website has one job: turn a worried homeowner into a phone call. Most of them fail at it slowly, by loading late on a phone, by hiding the number, or by saying nothing a search engine can read.

    The failure we see most often is invisible

    A great many small business sites are built so that the page assembles itself in the visitor's browser. It looks perfect to you. To anything that does not run JavaScript, the page arrives as an empty shell.

    Google will usually work it out eventually. The AI answer engines people increasingly ask for recommendations mostly will not, because they read what the server sends and move on. A site can look finished and be effectively invisible to the fastest-growing way people find contractors.

    We rebuilt a client site with exactly this problem in September 2026. Before: every address returned the same document with no page content and no canonical tag. After: 23 pages a search engine can tell apart, carrying 29,657 words of that company's own copy in the HTML where a crawler can read it.

    Speed is not a vanity metric on a phone

    Your customer is standing in their driveway looking at a damaged tree on a mobile connection. A site that takes four seconds to show anything has already lost a share of them, and you never see the ones who left.

    Prerendering the page rather than assembling it live is most of that fight. On the rebuild above it took the largest contentful paint from 3.5 seconds to 2.4.

    Written to be believed, which means claims you can defend

    Before that site launched we removed or rewrote 69 sentences, because they claimed things about the business that only the owner could confirm. Response times. Which town they get called to most. Equipment nobody had verified.

    It all read well. None of it was ours to assert. What shipped instead was checked with the owner line by line, and the stances now on that site are there because he said them.

    A tree company's website is a promise about how carefully you work. Filling it with claims that fall apart under one phone call is a strange way to make that promise.

    What you get

    A site that loads fast on a phone, puts the number where a panicking homeowner can hit it, says enough about the actual work to be found for it, and is written so you would be comfortable being asked about any sentence on it.

    You can see a sample build at nightingaletreeservice.lovable.app.

    What every tree service page needs

    A tappable phone number at the top of every page. A plain list of the services you actually offer. The towns you serve. Photos of your own crew, equipment and finished jobs. Recent reviews. Proof of insurance and any certifications you hold, such as ISA certified arborists on staff, where you can show them.

    And one short quote form that asks only what you need to call back: name, phone, address, what needs doing, and optionally a photo. Every extra question costs enquiries.

    Record where every enquiry came from

    A website is also a measuring instrument. On Big Green Tree Care's site, every quote form records the channel the visitor first arrived from, so a lead that came from organic search is credited to organic search rather than guessed at. Without that, the website's contribution is invisible and every decision about where to spend next is a guess.

    Built to be changed

    A tree company's services, prices and service area change. The site should be easy to update without a developer, and every page should be something you would be comfortable being asked about by a customer on the phone.

    Questions

    How long does a site take?

    Days rather than months for the build itself. The part that takes real time is getting the words right, because the pages that earn calls describe the actual work in the actual towns, and that detail has to come from you.

    Do I own the website?

    Yes. The code lives in a repository you own, and it can be hosted anywhere. Nothing here holds your site hostage.

    Can you fix my existing site instead of replacing it?

    Often, yes, and it is worth checking before rebuilding. The invisible-to-crawlers problem described above is fixable without touching how the site looks to visitors. We would rather do that than sell you a rebuild you do not need.

    Will it work with the ads?

    That is the point of building both. An ad that sends traffic to a page that loads slowly or buries the phone number is paying full price for a fraction of the result.