Local SEO case study · Lockyer Valley, Queensland
Lou’s Gardening: Building a Search-Ready Website
Lou already had the qualifications, award and customer proof. The website was not giving search engines a clear way to connect any of it.
priority service pages
Built around the service names local customers actually use when searching.
See the source ↗named service suburbs
Mapped from Lou’s approved service-area list instead of claiming every nearby location.
technical issues fixed
Found during the wider audit and repaired as part of the August 2026 launch.
Pro dependencies
The affected Elementor sections were rebuilt without an ongoing Pro licence.
The business already had the proof.
Lou’s Gardening and Landscaping Services was not starting from zero. Yuan Lu had formal agricultural training, a 4.9 rating across 65 Google reviews and a 2026 Quality Business Award for landscaping in the Lockyer Valley.
The problem was translation. The website did not give customers or search engines a clear way to connect that reputation with the individual services Lou wanted to be found for.
- Clarify the priority services.
- Repair the technical foundation.
- Connect the business, services, locations and proof.
The brief was only half the job.
The initial request was structured data: business details, service areas, opening hours, reviews, social profiles, services and frequently asked questions.
Adding code alone would have described a weak structure more precisely. Before writing the schema, BWB audited the pages, plugins, headings, links, language settings and the way eight different services were competing inside one general page.
What the audit uncovered.
- Eight services shared one general services page, with no focused destination for priority searches.
- A placeholder testimonial naming “John Doe, CEO” was still live.
- The homepage title tag was duplicated.
- The site language was set to US English.
- The homepage contained two H1 headings.
- A footer link was broken.
- The copyright year was frozen at 2024.
- The page builder was two years out of date.
- A personal Gmail address weakened the otherwise established presentation.
Use the words customers use.
The services did not need to change. Their page names did. Keyword Planner comparisons supplied for the project showed that customers were using broader, more familiar wording.
| Original wording | Page direction | Monthly search comparison |
|---|---|---|
| Garden Makeovers | Garden Design & Makeovers | 5,000 vs 500 |
| Turfing | Turf Laying & Instant Lawn | 5,000 vs 500 |
| Pruning & Hedge Trimming | Hedge Trimming & Tree Pruning | 50,000 vs 5,000 |
Each priority service received its own page, with the original business knowledge kept intact and translated into the language customers were more likely to search.
Remove the cost that was not helping.
An expired Elementor Pro licence and an updated free plugin had left the testimonial carousel broken. Renewing the licence would have restored the old dependency, but it was not required to solve the communication problem.
BWB rebuilt the affected sections with standard Elementor components, removed the Pro dependency and placed a relevant customer testimonial on each priority service page.
Say what will not work.
Good technical work also means declining tactics that create the wrong expectation. Self-serving review markup on a business’s own website is not eligible for Google’s LocalBusiness or Organization review stars. FAQ content can still clarify a service and help machines understand the page, but Google no longer presents the old FAQ rich result.
Both were explained before launch. The site kept the useful information, without selling Lou a visibility promise the markup could not honestly deliver.
What BWB built.
- An extended Yoast schema graph that upgraded the existing Organization entity instead of adding a competing block.
- A small must-use plugin so the structured data survives theme, plugin and page-builder changes.
- Four focused service pages and a dedicated case studies page.
- Structured service-area data covering 31 approved suburbs across the Lockyer Valley.
- A deliberate exclusion for locations where Lou only wanted substantial work, because structured data cannot express a minimum job value.
- Three real customer projects published with permission.
- A nine-point technical repair pack covering headings, links, language, metadata, plugins and trust details.
Measure the result properly.
The rebuilt structure went live in August 2026. Search Console baselines were recorded before deployment, and the first meaningful comparison is scheduled for February 2027 after the pages have had time to be crawled, indexed and tested in the market.
We would rather publish real numbers late than vague claims early. This page will be updated when the evidence has matured.
The lesson.
Structured data describes what a website already contains. When one page is carrying eight services, there is a ceiling on how much clearer markup can make it.
Fix the structure first. Then the schema has something worth describing.
Related work and reading.
The services, guides and source material connected to this project.