Targeting broad searches without proving local service relevance
Observable evidence: Important service pages use generic landscaping language, location references are vague or copied, and Search Console shows impressions from broad queries without meaningful visibility for the places the company actually serves. A multi-location operator may also route every branch to the same generic page even when customers need branch-specific service, contact, and project information.
Consequence: Searchers may not understand whether the company serves their property, and search engines receive weak evidence connecting a specific service with a specific genuine market. The result can be irrelevant impressions, poor landing-page fit, and weak local visibility.
Correction: Build location relevance from real operating facts. Keep core service pages focused on the service, then add dedicated location pages only where the company has a genuine location or enough useful local information to justify a distinct page. Explain service availability, local constraints, representative projects, contact details, and branch information without cloning copy across markets.
Owner: SEO lead with branch or operations input.
Verification: Confirm that local landing pages are materially distinct, internally linked, indexable where appropriate, and earning impressions from queries that match the actual service area.
Severity: critical
Letting project images create avoidable mobile performance problems
Observable evidence: Galleries contain large original files, mobile pages load slowly, layout shifts occur while images render, and project photographs lack useful surrounding descriptions or accessible text. A visual portfolio can still be valuable even when the technical delivery is inefficient.
Consequence: Potential customers may abandon a project page before seeing the work, while crawlers and users receive less usable context about what the images represent. Mobile-first indexing does not mean that a specific load-time threshold guarantees a ranking loss, so performance should be measured rather than described as an automatic penalty.
Correction: Resize and compress project media, use appropriate modern formats where supported, set dimensions, use sensible lazy loading, and write descriptive alt text for images that convey meaningful content. Keep captions or project copy focused on the actual work shown rather than stuffing keywords.
Owner: Developer or web manager with content review from the landscaping team.
Verification: Compare real mobile performance before and after the change and confirm that project pages remain visually strong and accessible. A source example described a 5MB file on a 4G connection and a 10MB gallery reduced to 500KB; treat those values as examples from the original copy, not universal limits.
Severity: high
Using a Google Business Profile category that does not match the real business
Observable evidence: The primary category emphasizes a secondary service, branch profiles use inconsistent categories, or the profile description and services do not match what customers see on the website. A company focused on landscape construction may be represented primarily as lawn care, or the reverse.
Consequence: The listing can attract the wrong expectations and make local performance harder to interpret because the profile, website, and business model describe different priorities. The source used a contrast between $50 maintenance work and $50,000 renovation work to illustrate this mismatch, but those amounts are examples rather than market benchmarks.
Correction: Review available Google Business Profile categories and choose the category that most accurately represents the primary real-world business. Add relevant secondary categories only when they reflect services actually offered. Do not create profile categories or service claims merely to chase keywords.
Owner: Business owner or local marketing lead.
Verification: Compare the profile category, website service hierarchy, incoming calls, and local query data after the correction. Category accuracy can affect relevance, but it should not be described as a guaranteed map-pack position.
Severity: critical
Bundling every landscaping service into one thin page
Observable evidence: A single services page lists mowing, planting, drainage, irrigation, hardscaping, lighting, and patios with little explanation of scope, process, materials, project fit, or customer questions. Search Console may show that the page appears weakly across many unrelated service intents.
Consequence: The page gives searchers little reason to believe it fully answers a specific need and gives the site limited room to demonstrate real expertise in distinct services. The problem is thin decision support, not failure to hit a specific word count.
Correction: Create dedicated pages for core services that the company actually sells and can explain accurately. The source suggested 600-800 words per service, but length should follow the information needed to describe scope, process, materials, constraints, service area, project examples, and next steps rather than a fixed SEO quota.
Owner: Content owner with subject-matter input from estimators, designers, or field leadership.
Verification: Confirm each page targets a distinct customer decision, avoids duplicated boilerplate, is internally linked from relevant projects and hubs, and begins earning service-specific impressions and qualified visits.
Severity: high
Reacting to seasonal demand after customers have already started searching
Observable evidence: Seasonal service pages are updated only when crews are already busy, historical query data shows demand rising before the marketing calendar changes, or old seasonal pages remain inaccurate from one season to the next.
Consequence: The company can miss the period when customers are researching and comparing providers, then mistake lower off-season demand for an SEO failure.
Correction: Use the company's historical Search Console, analytics, CRM, and booking data to identify when interest starts rising for each seasonal service. The source described demand beginning 4-6 weeks before a season, but local weather and service mix can shift that pattern, so schedule updates from observed data rather than a universal calendar.
Owner: Marketing lead with operations input.
Verification: Compare seasonal impressions, clicks, qualified inquiries, and page freshness across equivalent periods. Keep service dates and availability accurate instead of publishing generic seasonal posts for activity alone.
Severity: medium
Ignoring local citations and legitimate community references
Observable evidence: Important directory listings use conflicting business details, branch information differs across sources, or the company has genuine supplier, association, event, community, or project relationships that are not reflected online. At the same time, the backlink profile may contain generic directories with little relevance.
Consequence: Customers can encounter conflicting contact or location information, and the site may lack useful references from organizations that actually know or work with the business.
Correction: Reconcile important citations against the real business record and pursue links only where there is a legitimate editorial or business reason for another site to reference the company. Local nurseries, trade groups, community organizations, suppliers, project partners, and events can be relevant when the relationship is genuine.
Owner: Local SEO or marketing owner, with branch managers validating business details.
Verification: Check whether priority citations agree on the business identity and whether newly earned links come from relevant pages with a defensible reason to mention the landscaper.
Severity: medium
Treating reviews, snippets, and structured data as shortcuts to local rankings
Observable evidence: The marketing plan focuses on review counts without a consistent customer-feedback process, promises star displays from markup, or assumes that replying to every review directly moves rankings. The source contrasted a profile with 5 reviews against one with 150, but that comparison does not prove a fixed ranking outcome.
Consequence: Even when a profile appears in the top 3, the company can underperform if the information is weak, the service fit is unclear, or the review process does not reflect real customer experience. Chasing a visible metric can also distract from profile accuracy, page quality, and project evidence.
Correction: Ask eligible customers consistently for honest feedback without incentives, review gating, or discouraging negative responses. Respond when useful for customers and reputation, not because a response rate is treated as an official ranking factor. Do not promise that markup will produce a 5-star search display.
Owner: Customer-success or operations lead for review requests, with the web team responsible for valid markup.
Verification: Audit the request process, confirm it is applied consistently, validate any structured data, and track local visibility and profile actions separately from review volume so correlation is not mistaken for causation.
Severity: high
