Journal·SEO·April 13, 2026

Before/After Galleries as SEO Engines: Image, Caption, Crawl

How to build a before/after gallery that drives long-tail SEO for an interior design studio — naming, structure, schema, and crawl optimization.

10 min read · By decorator.tv editorial

Side-by-side before-and-after photos of a renovated living room in a web gallery layout, demonstrating SEO-friendly project galleries for decorators.

A decorating studio's gallery is the single most under-leveraged SEO asset on most studio sites. Every project produces fifteen to fifty unique images that no other site has. Every image, properly handled, ranks for a long-tail query somewhere. Most studios capture none of that potential. This post is the rebuild guide.

Why galleries underperform by default

The default modern gallery is a JavaScript carousel with thumbnails and a lightbox. It looks great. It is also nearly invisible to search engines. The image filenames are auto-generated, the alt text is empty, the captions are hidden behind hover states or click events, and the surrounding text on the page is "Our Recent Work." From a crawler's perspective, you have a page with one heading, no body content, and a blob of JS.

The fix is structural, not cosmetic. The gallery needs to live as crawlable HTML, with each image-pair on a real, indexable URL, with body content around it, with structured metadata. The studios that have done this rank for long-tail queries like "white shaker kitchen cabinet repaint langley" or "1990s split-level exterior color makeover abbotsford" — queries that competitors cannot manufacture and cannot copy.

The image hygiene checklist

Before a single image goes live, six things happen.

One: descriptive filename. "white-shaker-kitchen-cabinet-repaint-langley-bc-2026.jpg" — not IMG_4823.jpg. Hyphens between words, lowercase, includes service, city, year. The filename is read by every image search engine and contributes to long-tail ranking.

Two: descriptive alt text. The alt attribute is what screen readers read to visually impaired users and what search engines parse for image relevance. "Before and after photo of a 1990s oak kitchen cabinet refinish to white shaker style in Langley, BC, completed by Decorator.tv in April 2026." Long, specific, accurate. Not "kitchen cabinets."

Three: WebP format, resized. Photos shipped from a phone are 4MB and 4032×3024. The web version should be WebP, 1600px on the long edge, under 200KB. There are zero exceptions. Page weight is a ranking factor and a conversion factor.

Four: EXIF preserved (camera and date metadata). Location EXIF data is optional — strip it if the site shows specific home addresses, keep it if you've handled privacy at the photo selection stage.

Five: lazy loading attributes set correctly. The first three images on a page get `loading="eager"` and `fetchpriority="high"`; everything below the fold gets `loading="lazy"`. Misuse hurts Largest Contentful Paint, which hurts Core Web Vitals, which hurts ranking.

Six: width and height attributes set explicitly. This prevents Cumulative Layout Shift, another Core Web Vitals signal.

The page structure for each project

Each project gets its own URL: /gallery/[city]-[service]-[descriptor]. So /gallery/langley-kitchen-cabinet-refinish-white-shaker. On that page:

H1: A descriptive sentence-style heading. "1990s Oak Kitchen Cabinet Refinish to White Shaker, Langley BC." Not "Project 47."

First paragraph: 60-80 word answer paragraph. What was the project, in what city, what materials, how long it took, what the result was.

Image gallery: 4-12 image pairs, each a before/after sequence, each with a caption beneath naming the surface, the material applied, and any notable details.

Project details list: bullet list of materials used (paint product and color, primer, hardware), duration, scope.

Customer context paragraph: 100-150 words about the homeowner's brief and the studio's response. This is the long-form content that rounds out the page for SEO.

Schema: a custom Project type using the schema.org/CreativeWork superclass, plus ImageObject schema for each image with caption and contentUrl.

Internal links: link back to the parent service page and the parent city page using descriptive anchor text.

The index page that aggregates them

A single /gallery URL with a filterable grid of all project URLs. Filters by city, by service, by year. Each grid card has an image, a title, and a snippet. The grid is server-rendered HTML — the filters can be client-side JavaScript that hides cards, but the cards themselves must be in the DOM at first paint.

This page is what most users arrive at. It is also what Google uses to discover the individual project pages. Without a real, crawlable index page, the project pages are orphaned and never get indexed even if they exist.

Captions that earn long-tail queries

The hidden lever is the captions on individual images within each project page. A typical project produces eight to fifteen images; with a 30-50 word caption per image, you are publishing an additional 250-700 words of unique, image-specific content per project page.

Caption template: "[Surface or area shown]. [Material applied with product name and color]. [Notable detail or technique]." For example: "Upper cabinet face frames after spray application. Benjamin Moore Advance in Decorator's White, two coats over factory-stripped maple. Hand-cut shaker rails added on-site to convert flat-panel doors."

Each caption is a small SEO opportunity. Across a 20-image project, the page accumulates significant long-tail relevance for paint product names, color codes, technique terms, and surface vocabulary that no automated content tool can fake.

What this produces

A studio that ships 40 project pages built this way will accumulate, in our experience, between 800 and 2,000 monthly long-tail visits within nine months. The conversion rate on this traffic is unusually high because the queries are extremely specific — a homeowner searching "white dove kitchen cabinet repaint" is far closer to hiring than a homeowner searching "kitchen design ideas."

Better, the gallery becomes an ongoing referral source. Real estate agents, interior photographers, and adjacent trades begin linking to specific project pages because they're useful references. Each external link is an SEO compounding asset.

Implementation cadence

Studios trying to retrofit a 200-photo legacy gallery into this structure get overwhelmed. Don't. The sustainable cadence is one new project page per week, drawn from current work. After a year you have 50 project pages — more than enough to dominate long-tail in any market.

Existing gallery: leave as-is. Build the new structure parallel. Migrate the best ten old projects in the first month. Let the rest age out.

Common mistakes

Watermarking images aggressively. Search engines and human visitors both find heavy watermarks distracting; they reduce engagement signals, which hurt rankings. A small corner mark is fine; a 30%-opacity diagonal "DECORATOR.TV" across the entire image is sabotage.

Using stock-photo-style "model homes" or staged listings instead of real client work. The whole point of the gallery is uniqueness. Stock-style content is duplicate content.

Geotagging photos with full client addresses. Privacy violation and a legal risk. Use neighborhood or street-only references in copy.

Hiding captions in modal popups. Captions inside modals are typically not indexed because they require JS interaction to render. Captions live below the image, in the page source, always.

This is one weekend of structural work plus an ongoing one-page-per-week cadence. The compound returns are larger than any other on-site SEO work a decorator can do.

#image SEO#gallery#long-tail

Two ways to start

A fast, written quote — or a call to join the trade network.