Technical & local SEO

A placeholder string was blocking a real review rating from Google

Schema repair, redirect mapping, and thin-page cleanup shipped to two live sites, a Scottish estate agency and a conveyancing firm, each measured against a baseline captured before the first fix went out.

Client
Scottish estate agency and conveyancing firm
Build time
Baseline dated; fixes shipped in phases
Headline outcome
Baseline captured, re-test scheduled
The problem

Both sites carried technical debt that doesn't show up until someone goes looking. A literal placeholder string sat inside the estate agency's review schema, which meant Google had no real rating to display even though the reviews existed. Redirects had accumulated into a malformed double-hop chain through www, sending crawlers and visitors through two jumps instead of one. And hundreds of thin, auto-generated tag and archive pages sat indexed, spreading crawl budget across pages with nothing on them.

The system

Each issue got a direct fix rather than a patch. The placeholder string in the review schema was replaced with the real markup so the actual rating could surface. The double-hop redirect chain was mapped and collapsed to a single hop. Hundreds of thin tag and archive pages were identified and cleaned up, and new location pages were built to replace the gap. A dated baseline was captured before the first fix shipped, so every change since has something real to measure against.

How it runs

The workflow, end to end.

01

Baseline capture

Before any fix shipped, the site's technical and local state was recorded and dated, so later changes have a fixed starting point to measure against.

02

Schema repair

Structured data was audited page by page. A placeholder string inside the review schema, left over from a template, was replaced with the real markup so Google could read the actual rating.

03

Redirect mapping

The redirect chain was traced end to end, including a malformed double-hop through www, and rebuilt so every old URL resolves in a single hop.

04

Thin-page cleanup

Hundreds of thin, auto-generated tag and archive pages were identified and removed or consolidated, cutting the amount of near-empty content sitting in the index.

05

Location pages built

New location pages replaced the gap left by the thin pages removed, built around the areas each business actually serves.

Outcomes

What it moves.

Captured and dated before the first fix
Baseline
Double-hop www chain, mapped and collapsed
Redirect chain
Hundreds of archive/tag pages
Thin pages found
Scheduled, results not yet in
Re-test
Stack

What it's built on.

  • Schema / structured data audit
  • Redirect mapping and rebuild
  • Site crawl for thin-page identification
  • Location page templates
Technical SEOLocal SEOSchema

Got a site with technical debt nobody's mapped? Let's capture a baseline first.

20 minutes. No slides. One process, one prototype.

Book a 20-min intro