I Audited a Landscape Company.
Great Work,
Zero Online Visibility.

This landscape company does beautiful work. Patios, retaining walls, garden design, seasonal maintenance. They've been in business for years. Loyal repeat customers. A portfolio of completed projects that sells itself in person. Customer testimonials that read like love letters.

When I audited their website, I found what I find with most local service businesses: the work is excellent, the reputation is real, and the website is structurally invisible. No schema markup of any kind. No blog. No FAQ page. No Google Business Profile optimization. The kind of site that looks fine to a human visitor but tells search engines and AI systems almost nothing.

If you run a landscaping company, contracting business, or any local service company -- these findings probably apply to your site too.

The Scores

A 5 in Schema and a 5 in AI Discoverability. For a local service business, those two numbers mean you are functionally invisible to the systems that increasingly decide which contractor homeowners call first.

Finding #1: No LocalBusiness Schema

For a local service business, LocalBusiness schema is the single most important piece of structured data you can have. It tells Google your business name, address, phone number, service area, hours, and what you do -- all in a format machines can read instantly.

This site has none of it. Zero schema markup of any kind. Google has to guess everything about this business from unstructured HTML, page titles, and whatever it can scrape from the text on the page. That guessing game puts you at a disadvantage against every competitor who has given Google the answers directly.

When a homeowner searches "landscaping company near me" and Google shows a map pack with hours, ratings, and phone numbers for three competitors -- this company isn't in that pack. Not because the work is worse. Because the website hasn't told Google what it is.

Finding #2: No Service Schema for Landscaping Services

The company offers distinct services: patio installation, retaining walls, garden design, lawn maintenance, seasonal cleanup. Each one is a search query homeowners make. "Patio installation near me." "Retaining wall contractors." "Garden design services."

None of these services have dedicated pages with Service schema. The services are mentioned on the homepage and maybe a general services page, but there are no individual pages optimized for each service with structured data telling Google exactly what's offered, where, and at what price range.

Each service page with proper Service schema is a new opportunity to rank for a specific search query. Without them, the site has one page competing for every landscaping search instead of six or eight pages each targeting a specific service.

Finding #3: Customer Testimonials With No Review Schema

The site has real customer testimonials. People praising the quality of work, the professionalism, the attention to detail. These are exactly the kind of signals that build trust with both potential customers and AI systems.

But they're just text on a page. No Review schema. No AggregateRating. Google can't show star ratings in search results for this business. AI systems can't cite the review count or rating when making recommendations. The social proof exists -- it's just locked in unstructured HTML where only human visitors can benefit from it.

Adding Review and AggregateRating schema to existing testimonials is one of the fastest wins in earned visibility. The content is already there. It just needs the structured wrapper.

Finding #4: No Google Business Profile Optimization

Google Business Profile is the front door for local service businesses. It's what shows up in the map pack, in "near me" searches, and increasingly in AI-generated local recommendations. A complete, optimized GBP with photos, services, hours, posts, and reviews is the single highest-impact thing a local business can do for online visibility.

This company's GBP is either incomplete or not actively managed. No regular posts. Limited photos. Service categories not fully populated. In a competitive local market, an inactive GBP is like having a storefront with the lights off -- potential customers drive past without stopping.

Finding #5: No Content Strategy

No blog. No FAQ page. No resource section. No seasonal guides. The website is a static brochure: homepage, about, services, contact. That was fine in 2015. In 2026, it means the site has four or five URLs competing for every landscaping search in the area.

Every service, every season, every common question is a content opportunity:

The company sees these questions from customers every week. Each one is a blog post waiting to be written. Each blog post is a new URL that can rank, drive traffic, and demonstrate expertise to both Google and AI systems.

Finding #6: No AI Discoverability Infrastructure

No AI crawler directives. No structured data for AI consumption. No presence in the places AI systems pull recommendations from -- no "best landscapers in [city]" listicles, no directory listings with structured data, no review platform presence beyond the basics.

When a homeowner asks ChatGPT or Google AI "who's the best landscape company near me," the AI pulls from Google Business Profile data, review platforms, directory listings, and structured website data. If you have none of those signals, you're not in the recommendation pool. Period.

What's Actually Working

Does This Look Like Your Business?

If you run a landscaping company, contracting business, or local service company and you recognize these patterns, you're in the majority. Most local service websites were built by web designers who made them look professional but didn't think about local SEO, earned visibility, or reputation management structure.

The good news: the hardest part is already done. You have the business, the reputation, the customer relationships, and the portfolio. What's missing is the structural layer that translates all of that into machine-readable signals. And that layer is buildable -- usually in weeks, not months.

Frequently Asked Questions