Landscaping Website Guide: Photos, Tags, and Pages

Landscaping is one of the trades where the website does some of the hardest work in the sales process. A homeowner is making a multi-thousand-dollar decision about a part of their property they live with every day. They want to see what you have built, in their kind of yard, in their climate, before they ever pick up a phone. The website is where that conviction gets built.

It is also a brutally competitive local search market. Every metro has dozens of landscapers. Most of their websites look the same: stock photos, "transforming outdoor spaces since [year]" headlines, a contact form, a Facebook icon. The websites that actually win, the ones that book consultations with serious design clients month after month, do specific things the average site does not.

This is what those things are.

Photography is the foundation. Treat it that way.

Landscaping is a visual trade. Customers buy with their eyes. The biggest single thing separating great landscaping sites from forgettable ones is the photo library. Specifically:

• Real, recent project photography. Stock photos read as inauthentic in this trade more than any other. A homeowner browsing for a designer can tell the difference between a stock photo and a photo of an actual finished install in twenty seconds. Stock photos signal "this person has not built enough work to fill a portfolio yet."
• Before / after pairs. The single most powerful piece of content a landscaping site can publish. Show the bare yard, the half-finished install, and the finished space. Pair them with one or two sentences about the constraint that drove the design (south-facing slope, drainage problem, kids and a dog, shade-tolerant only). The pairs do more selling than any copy.
• Seasonal coverage. A garden in May does not look like a garden in November. If every photo on your site is shot in peak summer, your work looks one-dimensional. Photograph a few signature projects in spring, summer, and fall, the maturity arc tells the customer what their yard will actually look like over time.
• Real photo optimization. A 4MB phone photo on every page is what kills landscaping site speed. Modern image formats (AVIF and WebP) compress those photos to 200–400KB at the same visual quality. A custom-coded site does this automatically; most builder platforms will only do part of it.

If you do nothing else from this guide, fix the photography. It is the single biggest lever available.

Structure the work the way customers think about it

Most landscaping websites organize their portfolio chronologically ("our 2025 projects") or by service category ("hardscape / softscape / irrigation"). Customers think differently. They think:

• "What does a yard like mine look like when this person finishes with it?"
• "What did they do for someone with my problem?" (slope, shade, no time, kids, drought, HOA constraints)
• "What does their work cost in my range?"

The portfolio that wins is organized around those questions. Tag projects by yard size, sun exposure, dominant feature (front-yard curb-appeal redesign, full backyard build, drystone wall, native pollinator garden, kid-and-dog-proof play space), and rough budget tier. Filter the gallery on those tags. A homeowner with a small shaded urban backyard wants to see your small shaded urban backyard work, not scroll past five acres of country property to find one example that fits.

Local SEO depth that the competition does not bother with

"Landscaper [city]" is the search every potential client will eventually run. The local pack is brutally competitive: typically dominated by Google Business Profiles with the most reviews, but the website behind the profile decides whether the click converts.

The on-page work that moves the needle:

• Real city pages, not doorway pages. If you serve five towns, build five real pages, each one with photos of work in that town, references to local conditions (clay soil in this neighborhood, drought-zone restrictions in that one, HOA aesthetics in another), and at least one local landmark in the copy. Doorway pages where every paragraph is the same with the city name swapped in are the doorway pattern Google's local algorithm specifically penalizes.
• Service-specific pages with custom-coded schema. Page for "drystone walls", "native plant design", "irrigation install", "outdoor lighting", "patio build", each with its own page, its own photos, its own LocalBusiness + Service schema. A custom-coded site does this; most templates will not.
• Connection to your Google Business Profile. NAP (name, address, phone) on every page must match the GBP exactly. Phone numbers in a different format break this. Address truncated differently breaks this. The whole local-pack ranking signal pivots on consistency, sloppy NAP costs visibility.
• Reviews surface on the site. The Google Business Profile collects reviews. The website needs to surface the strongest of them on the relevant service pages and on the homepage. New visitors do not click out to Google Maps to find reviews; they leave.

Seasonal pages and seasonal calls-to-action

Landscaping demand is seasonal. Spring is when consultations are booked for summer installs. Late summer is when homeowners are scoping fall renovations. Late fall is when the firewood-leaf-cleanup-snow trio carries the off-season.

The website should reflect that calendar:

• Spring landing page for the design-consult booking surge. "Get on the spring install list" with a real, simple intake form. Time-boxed urgency that is true (capacity actually does fill up).
• Fall landing page for fall renovation, bulb planting, irrigation winterization. Different audience, the customer who missed spring and is salvaging the season.
• Off-season offer. Winter is when serious design clients have time to plan. Many landscapers under-use the off-season. A "design contracts signed in winter, installed in spring" page captures that audience.

None of these need to be full pages of copy. Each is a small landing page tied to a specific intake form, surfaced from the homepage during the relevant window, and removed (or quietly de-prioritized) when out of season. A custom-coded site with a date-driven banner system does this without the owner remembering to swap content.

The intake form does the qualification work

A generic "Name / Email / Message" form on a landscaping site is a missed opportunity. The form is the first piece of project-fit qualification you will do. The right four or five questions on a landing-page form save hours on the phone:

• What kind of project? One-time install, maintenance, design-build, ongoing seasonal. Pre-segments the intake immediately.
• Approximate yard size and feature. Front yard, backyard, full property; small / medium / large. Tells you whether to scope a $5K touch-up or a $50K full design.
• Budget tier. A simple range ("under $5K", "$5K–$15K", "$15K–$50K", "$50K+", "not sure yet"). Filters out the wrong fit before a phone call. This is the single highest-leverage form question for any service business with a wide pricing range.
• Timing. "I want this done in spring", "this fall", "next year", "still figuring out". Determines which queue the lead goes into.
• How they found you. One question, one click. Tells you which marketing channel is actually working.

The form should also offer the option of attaching photos of the existing space, a custom-coded site can do this cleanly with a third-party intake provider that handles file uploads.

Speed matters more in this trade than most

The customer browsing landscaping sites is almost always doing it from their phone, often outside, often standing in their yard. They are scrolling through ten or fifteen sites in one sitting. The site that paints first wins; the site that takes four seconds to render its hero image is closed before it even shows up.

This is not a small-margin effect. Google's own data shows roughly 7–10% of mobile visitors bounce per additional second of load time. A landscaper site at 60 PageSpeed mobile is losing roughly half of its mobile traffic before the visitor reads a word. A landscaper site at 95+ keeps that traffic and gives the visitor a chance to actually see the portfolio.

Page speed is structural. It cannot be fixed with a plugin. It comes from the way the site is built, AVIF / WebP images served at the right size, minimal JavaScript, no heavy template runtime, custom CSS. A custom-coded site achieves it natively; most templated platforms do not.

Trust signals that mean something to landscape buyers

Landscaping is a high-trust trade. The customer is letting strangers tear up their property. The site has to earn that trust quickly:

• License and insurance, prominently. Specific license number, specific insurance carrier, specific liability limit. "Licensed and insured" alone is not specific enough.
• The team, with faces. Even if it is just you and one helper, photos of the people doing the work and a short note about each one. Especially in this trade, customers want to know who is going to be in their yard for two weeks.
• Equipment and process. What machines come on a job, how the property is protected, how cleanup works at the end of each day. Customers fear bad neighbors complaining about a torn-up street more than they fear the cost.
• Real testimonials with project specifics. "Great work, recommended!" tells the next customer nothing. "They handled the drainage problem on our south slope and the front yard is the only one on the block that drains correctly after the spring snowmelt now" sells the next job.

Blog content that ranks for the searches landscape buyers actually run

Landscaping has a clear set of searches that drive consideration-stage buyers. The website that has long-form, useful content on those topics earns the long tail of organic traffic that the local-pack alone does not:

• "What landscaping increases home value the most"
• "Drought-tolerant front yard ideas [region]"
• "How much does a backyard redesign cost"
• "Best plants for [hardiness zone] [sun condition]"
• "Do I need a landscape designer or just a maintenance company"

None of these need to be 5,000-word pillar posts. A 1,000–1,500 word post that answers the question honestly, with photos of relevant work and a clear next step, ranks for years. Five or ten of them, written one per month, become the backbone of an organic traffic funnel that the GBP alone cannot match.

The bottom line

Landscaping is a trade where the website earns its keep. Done well, it is the first qualifier, the portfolio, the seasonal demand-shaper, and the local-pack engine all at once. Done poorly, it is a Facebook-tier brochure that loses every search to the competitor who took the website seriously.

If you want to see what a real landscaping site looks like end-to-end, Meadow & Stone is a working sample, full-portfolio gallery, real schema, seasonal landing pattern, real intake form. It is built on the same stack and pricing as the rest of the trades I serve.