Skip to content
Academy
Marketing Academy · Field Work●SEO
CoreTeardown· 50 minutes

Same Template, Different Store: Teardown of Four Location Pages

Lenskart

Objective: Given four synthetic location page specimens built on the same template, decide which pages differentiate enough to survive Google's duplicate-content detection and which are cannibalization risks, citing the specific defect, not a vague impression.

You're reviewing four Lenskart store page drafts ahead of a 60-store rollout, deciding whether the shared template's variable content slots are actually being filled with location-specific substance.

For each page, identify what's genuinely unique versus what's a city-name swap dressed up as local content, and don't get distracted by cosmetic differences that don't actually help.

Before you start

What you'll need

Free path (everything below is enough to finish)

FreeLog defects per specimen with severity and owner

Simple structured tracking

FreemiumCross-check canonical tags and schema @id values across a real location-page set

Free up to 500 URLs, surfaces exactly these two defects at scale via its Canonicals and Structured Data tabs

The process

Specimens to review

This paragraph mentions the neighborhood five times. Is that real local differentiation?

Sample output
Koramangala store page excerpt: 'Our Koramangala eyewear store brings expert eye tests and the latest frames to Koramangala residents. Visit our Koramangala store today for a free eye checkup and browse premium frames at prices Koramangala shoppers love.'

Specimen: synthetic, realistic

The page has solid metadata otherwise. What's missing that matters specifically because this is one of many near-identical templates?

Sample output
Page <head> for the Indiranagar store: contains a meta description and Open Graph tags, but no `<link rel="canonical">` tag anywhere in the source.

Specimen: synthetic, realistic

Both pages have valid LocalBusiness schema with real addresses filled in correctly. What's still wrong?

Sample output
LocalBusiness schema on both the Whitefield and HSR Layout store pages uses the identical `@id`: `https://lenskart.com/#business`.

Specimen: synthetic, realistic

Compare this to item 1. What makes this one actually pass?

Sample output
Andheri West store page excerpt: 'Our Andheri West optometrist, Priya Deshmukh, has fitted over 4,000 pairs of glasses since the store opened in 2021. We're one of two Lenskart stores in Mumbai offering same-day contact lens fitting, next to the Andheri metro station, parking available at the adjacent D-Mart lot.'

Specimen: synthetic, realistic

Final deliverable

A defect log across all four specimens, each tagged with severity, a fix owner, and, for the one clean specimen, an explicit note on why it passes.

See a reference example
Sample output
Chewy retail-partner locations, page teardown log (excerpt)

Specimen 2, Naperville store
  CRITICAL, developer: no self-referencing canonical tag found in <head>

Specimen 3, Schaumburg store
  CRITICAL, developer: LocalBusiness @id identical to the Naperville store's schema

Specimen 4, Oak Park store
  PASS: named store lead, service note specific to this location, real neighborhood detail

Success criteria

You're done when you can:

  • Correctly identifies all 3 planted critical defects across specimens 1-3
  • Correctly identifies specimen 4 as the clean control and explains why
  • Does not flag any of the 3 distractors as real defects