W-02 · Two-branch repair business case study

Two shops.One site.Zero signals.

Two strong shops with loyal customers, and a website that told Google almost nothing about either of them.

Ongoing engagementDevice repair · two shopsCentral LondonSince June 2026
Client confidential
Two-branch repair business: website preview with client identity blurred
Local SEOSchemaTrust & reviewsAnalyticsContent
Platforms
01

At a glance

Since June 2026
89Google reviews at 5.0 ★ across both shops13 Sep 2026
0 → 13Core pages with written meta descriptionsSep 2026
221 / 221URLs with clean canonicalsSep 2026
3New ranking pages shippedSep 2026

The short answer

The client runs two repair counters in central London, but its site had no meta descriptions, conflicting shop data and no page for either branch. AiS LABZ built a locations hub and two branch pages with Store schema, rewrote every core page's metadata, and tied every testimonial to a verified Google review.

02

Where things stood

the starting point
  • Both shops declared twice under one identity, with conflicting details.
  • 0 meta descriptions and no SEO plugin.
  • Opening hours under-reported by 2–3 hours a day on six pages.
  • No branch pages and no breadcrumb markup anywhere.
  • 18 duplicate product pages and invalid article markup on every blog post.
03

What changed

results

89 Google reviews at 5.0 ★ across both shops

13 Sep 2026

  • 89 Google reviews at 5.0 ★ across both shops by 13 September.
  • 13 of 13 core pages carry hand-written meta descriptions (from none).
  • 0 pages with duplicate H1s, 6 of 6 service pages with schema.
  • Two branch pages and a screen-repair page live and linked site-wide.
  • 16 verified Google reviews now power every testimonial on the site.
04

In numbers

hover or tap for exact values

Technical coverage after the fix

Share of pages meeting the standard, Sep 2026

13 / 13
Core pages with written meta descriptions
221 / 221
URLs with clean canonicals
6 / 6
Service pages with schema
View as table
MeasureResult
Core pages with written meta descriptions13 / 13
URLs with clean canonicals221 / 221
Service pages with schema6 / 6

Reputation

13 Sep 2026

89Google reviews across both shops
5.0 ★Average rating
16Verified reviews powering site testimonials

Want a result like this for your business?89 Google reviews at 5.0 ★ across both shops. Book a free 15-minute diagnostic and we will tell you what would move your number.

05

How we did it

diagnose, model, build, compound

01Diagnose

Live audit of 221 URLs: 8 critical issues, 11 warnings. A 22-term keyword map built around both branch postcodes.

02Model

Own the two postcodes before chasing London. The map pack is the target, not the head term.

03Build

A /locations/ hub, two branch pages with Store schema, a screen-repair money page with FAQ and breadcrumbs, Service schema on all six service pages, corrected hours and contact data, and GA4 live on 12 September.

04Compound

Every testimonial replaced with a verified Google review, a seasonal homepage calendar through December, and a weekly automated bug audit.

06

How we leveraged the platforms

what each one did in this engagement

Claude

Wrote the 13 hand-crafted meta descriptions, the branch and screen-repair pages, and audited all 221 URLs for canonicals and duplicate H1s.

WordPress

The CMS: branch pages, schema on six service pages and site-wide internal links were built inside WordPress.

WooCommerce

Runs the accessories shop; product categories were structured so shop pages support, not compete with, repair pages.

Google Search Console

Monitored indexing and canonical coverage after the fixes.

Google Analytics 4

Measures bookings and calls per branch.

Google Business Profile

Two branch profiles, each with its own hours, services and reviews, feeding the ratings shown on the site.

Hostinger

Hosting: caching and SSL configured for fast, secure branch pages.

GoDaddy

Domain management and DNS records for the site and email.

Canva

Designed the trade-in and diagnostic campaign graphics used on the homepage slider and socials.

07

Feature spotlights

what each piece does and why
Two branches, two identities: Each shop has its own card, page, hours and rating, backed by its own Store schema and Bus
Branch pages

Two branches, two identities

What it is
Each shop has its own card, page, hours and rating, backed by its own Store schema and Business Profile.
Why it matters
A two-branch business competes in two "near me" markets. Separate branch entities let Google rank each shop where it is.
What it did
Both branches at 5.0 ★ on Google.
Verified reviews as the testimonials: The site testimonials come only from verified Google reviews, with a rating badge summaris
Google reviews

Verified reviews as the testimonials

What it is
The site testimonials come only from verified Google reviews, with a rating badge summarising the total.
Why it matters
Borrowed proof beats written claims. Real reviews carry trust into the page and stay consistent with what searchers see on Maps.
What it did
89 reviews at 5.0 ★ across both shops by 13 September; 16 verified reviews power every testimonial.
Why us, in one table: A side-by-side table against the big chains on rating, latest closing time, free diagnosti
Comparison table

Why us, in one table

What it is
A side-by-side table against the big chains on rating, latest closing time, free diagnostic and walk-ins (competitor names blurred here).
Why it matters
Comparison shoppers and AI assistants both look for a structured answer to "which one should I choose". A table gives them one.
What it did
Built from the shop's own 5.0 ★ rating against the chains' public ratings.
08

What we shipped

client identity blurred
Homepage hero: free diagnostic offer and device-first booking
Branch cards with per-branch rating and hours
Comparison table against the chains (names blurred)
Verified Google reviews used as testimonials

Client names, logos, contact details and locations are blurred for confidentiality.

09

Who we worked with

by level and role
Business ownerBranch managers

What happens nextSearch Console verification, then the review and citation phase: map-pack top three for repair terms in both branch postcodes.

10

Keep exploring

the services, proof and reading behind this result
11

Common questions

Why build separate branch pages?

Google ranks a location page for a location. Two shops on one contact page compete with each other; two branch pages with their own schema rank for their own postcodes.

What happened to the old testimonials?

They were replaced with real reviews from the shops' Google profiles, so every quote on the site can be verified.

Is the work finished?

No. Foundations are done. Reviews, citations and local links are the next phase.

Next step

Want numbers like these? Book a diagnostic. You get the constraint map and a costed roadmap, and you own it either way.