Publishing Seasonal Content After Customers Start Searching
Observable evidence: Compare the pages that receive impressions across the year with the services promoted on the site. A common pattern is a static service mix while real customer needs shift between pruning, planting, lawn recovery, garden clearance, hedge work, and winter preparation. Industry estimates put the loss from a static service mix at 30-50% of potential organic traffic during the shoulder seasons, when homeowners are looking for specialized care; where historical analytics are available, compare your own seasonal dips with that range.
Consequence: Relevant searches can land on pages that do not answer the seasonal need, which can reduce qualified visits and make the site less useful at the moment customers are deciding whom to contact.
Correction: Build a 12-month editorial plan around services the business truly offers, refresh important service pages before each seasonal demand window, and keep evergreen URLs when the underlying service returns each year.
Owner: The marketing owner should coordinate timing with the person responsible for service availability so published information matches operational reality.
Verification: Confirm that seasonal pages are crawlable, internally linked, accurate, and receiving impressions for the intended queries before judging performance.
Creating Location Pages Without Enough Local Substance
Observable evidence: Review every area page for unique service details, proof of work, access or coverage information, and genuinely useful local context. A thin page that only changes a place name is weak evidence of local relevance. Develop 5-10 localized service area pages that highlight specific projects completed in those zones, limited to genuine locations or service areas for which the business can provide useful differentiated information.
Consequence: Near-duplicate pages can create a poor user experience and make it harder to understand which areas are meaningfully served.
Correction: Keep a dedicated page only where the business genuinely serves the area and can explain relevant services, typical project constraints, examples of completed work, or other location-specific information.
Owner: The local SEO owner and operations lead should jointly confirm service coverage and provide evidence for each retained page.
Verification: Compare page content side by side, check indexing and internal links, and confirm that enquiries from each page map to an area the business actually serves.
Making Expertise Claims Without Verifiable Support
Observable evidence: Audit biographies, service pages, footer badges, insurance statements, association references, and project claims. Google uses many signals to evaluate relevance and quality, but there is no special 'EEAT score' that can be raised by adding badges. The practical issue is whether the site accurately identifies who provides the work and what experience or qualifications can be substantiated. Building authority in gardening search requires proving you are a qualified professional, not just a hobbyist with a mower; the broader SEO for gardeners resource sets out the wider strategy.
Consequence: Unsupported or vague authority claims can weaken user trust and create inconsistency between marketing copy and the business information a customer can verify.
Correction: Publish only credentials, memberships, insurance details, and professional experience the business can document. Explain relevant horticultural or landscaping experience in plain language and connect expert information to the services it supports.
Owner: The business owner should approve factual claims, while the content owner ensures they are presented consistently across relevant pages.
Verification: Review the site against supporting documents and current team information, and remove any claim that cannot be substantiated.
Letting Project Images Damage Mobile Usability
Observable evidence: Test key portfolio and service pages on mobile, inspect image file size and dimensions, and check whether images are appropriately compressed and responsive. It is tempting to upload 10MB raw photos of the latest garden transformation. Picture a stunning portfolio page that takes 8 seconds to load on a 4G connection, causing 60% of visitors to leave before seeing any of the work.
Consequence: Heavy pages can delay access to service information and calls to action, especially for visitors on slower mobile connections.
Correction: Resize images to the display need, use efficient formats such as WebP where appropriate, serve responsive variants, defer off-screen media, and write descriptive alt text for meaningful images without stuffing locations or keywords.
Owner: The web developer should own delivery performance, while the content or design owner controls image selection and descriptive text.
Verification: Re-test the same pages after changes and confirm that images remain sharp, usable, and correctly described while page performance improves.
Treating Structured Data as a Shortcut to Local Rankings
Observable evidence: Check whether the markup matches visible page content and business facts. A common error is assuming that changing a schema type alone will produce map visibility, star ratings, or other search features. Structured data can help search systems interpret eligible information, but display and ranking outcomes are not guaranteed. Consider a competitor appearing in the Map Pack with a 5-star rating and 'Open Now' status: that display is an example of a search presentation, not a result that markup alone can deliver.
Consequence: Teams can spend time on markup while more important problems, such as inaccurate business details, weak service pages, inaccessible content, or incomplete local profile information, remain unresolved.
Correction: Use valid structured data that accurately reflects the business and page content, keep core business details consistent, and follow current Google documentation for any search feature you intend to support.
Owner: The technical SEO or developer should implement markup, with the business owner responsible for the underlying factual data.
Verification: Validate the markup, compare it with visible content, and check Search Console for parsing issues without treating successful validation as evidence of a ranking gain.
Allowing Business Details to Drift Across Citations
Observable evidence: Compare the business name, address where applicable, phone details, website URL, and core service information across the website, Google Business Profile, social profiles, and relevant directories. Exact stylistic uniformity is less important than factual consistency, but outdated addresses or phone numbers can create real confusion.
Consequence: Customers may contact the wrong number, visit an outdated location, or encounter conflicting business information, while search systems receive weaker entity signals.
Correction: Maintain one approved source of truth for current business details and update high-value listings first. Keep your business name, address, and phone number (NAP) 100% consistent across every directory, social media profile, and your own website; treat that as an operational completeness goal rather than a documented ranking threshold.
Owner: The local marketing owner should manage the master record and coordinate corrections with directory or profile owners.
Verification: Re-check the highest-visibility listings after edits and log any remaining discrepancies that require manual resolution.
Ignoring Specific Questions That Reveal Service Intent
Observable evidence: Review Search Console queries, enquiry messages, sales conversations, and customer questions for recurring topics the site does not answer. Broad service pages may cover the category while missing specific concerns about pruning timing, lawn renovation, planting conditions, hedge maintenance, or disease symptoms.
Consequence: The site may fail to demonstrate useful expertise early in the customer's research process and can leave high-intent questions unanswered until a competitor supplies the information.
Correction: Create concise advice content tied to real services and local conditions, then link it to the relevant service page. One example: a gardener who writes a guide on 'Dealing with Box Blight in local gardens' and captures 50 new leads from worried homeowners who eventually hire them for a full garden replant.
Owner: A horticulturally knowledgeable team member should supply or review the subject matter, while the content owner handles structure, search intent, and internal linking.
Verification: Check whether the new content earns relevant impressions, answers the target question accurately, and sends qualified visitors toward the appropriate service page without making unsupported promises.
