Gallery&ProjectPages:GeotagMyths&WhatReallyMatters(Cochrane)

01Who This Is For — And What You'll Walk Away With

You run a plumbing, HVAC, electrical, roofing, or landscaping & snow company in Cochrane, AB. Somewhere along the way, you heard that "geotagging" your images (embedding GPS coordinates into your photo files) helps you rank locally.

Here's the truth: geotags don't move the needle. What does? Neighbourhood context, clean captions, real proof, and a fast first screen that nudges visitors to call or request a quote.

This page gives you owner-friendly templates you can use right away. You'll get file-naming patterns, alt text examples, caption formulas, a project-page layout, and speed basics. There's also a one-page checklist you can print and hand your team.

02TL;DR

Skip geotagging your photo files. Instead, win with context and speed:

• Mention the neighbourhood in every caption.
• Use descriptive alt text and file names.
• Show 2–4 decisive images per job — not 20 tiny thumbnails.
• Put the best "after" photo in the hero image (the big main photo at the top of the page).
• Keep sliders below the fold (the part of the page you see before scrolling).
• Serve responsive AVIF/WebP images (newer formats that load faster than JPEG or PNG without losing quality) with sizes set.
• Add a visible Start My Project button.

If you'd like us to wire this into your site and keep it loaded fast on phones, start here: Start My Project. Want inspiration? See Our Work.

03Myth vs. Reality: "Geotagging Boosts Local SEO"

"

The myth: Embedding GPS coordinates — called EXIF data (the hidden data your camera saves inside a photo file, like date, location, and camera settings) — into your photos helps you rank higher locally.

"

The reality: Search engines care about what's on the page — your headings, the text near each image, and your captions. They also care about how fast the key image loads on mobile. EXIF data is often ignored or stripped the moment you upload.

Here's what to do instead:

• Write a neighbourhood-named caption under each photo (e.g., "Panel upgrade in Riversong — labeled and inspected.")
• Use clean file names and helpful alt text (see the copy-paste templates below).
• Let the hero image load immediately — no slider, no lazy-load (a setting that delays loading images until the visitor scrolls down to them).
• Place a Start My Project button near every proof block so visitors can act.

04The Project Page Recipe (Works for Any Trade)

The goal is simple: a short, scannable story plus proof that leads to a tap-to-call or quote request.

Here's the structure that works:

1. H1: Job & location in natural language — "Electrical panel upgrade — Riversong, Cochrane"
2. Intro (60–80 words): What was wrong, what you did, the outcome, and the neighbourhood.
3. Proof block (2–4 photos): Best "after" shot as the hero image; 1–3 supporting images below with captions.
4. Micro-FAQ (3 bullets): "How long did it take?" "Any permits?" "What changed the price?"
5. CTA row: Start My Project (primary) + a review chip or short quote from the customer.
6. Related links: Service page, Proof hub, Areas We Serve.

The result: Visitors see what you did, where you did it, and how to contact you — without wading through a slow, endless gallery.

05File Names, Alt Text & Captions (Copy These Templates)

File Name Pattern

Use this format: service-neighbourhood-year.avif

Examples:

• furnace-repair-fireside-2025.avif
• panel-upgrade-riversong-2025.avif
• roof-leak-west-terrace-2025.avif

Alt Text (10–12 words — describe what's in the image, not sales copy)

• "Panel upgrade — Riversong home, labeling complete before inspection."
• "AC condenser replacement — Fireside backyard, new pad and lineset."
• "Asphalt shingle repair — West Terrace ridge cap sealed."

Caption Formula (neighbourhood + outcome + one detail, 1–2 lines)

• Riversong — Panel upgrade with labeling; passed inspection next day.
• Fireside — AC swap; quieter, lower draw, homeowner review below.
• West Terrace — Wind lift fixed; new ridge cap and fasteners.

Neighbourhood chips to sprinkle near proof: Riversong · Fireside · Sunset Ridge · Heartland · GlenEagles · Bow Meadows · West Terrace

06Before/After Without Killing Speed

The key rule: show less, say more.

• Put one decisive "after" image above the fold. Let it load immediately. Never lazy-load it.
• Love sliders? Keep them. But place them below the first screen so they don't slow down the initial view.
• Caption every photo. A captionless image is a missed chance to name the neighbourhood and the work.
• Quick test: Pull up your project page on your phone. If the first screen feels instant, you're winning. If it lags, it's usually a heavy hero image or scripts trying to run before the page is ready.

07Make Galleries Fast on Phones

Here's a plain-English guide to keeping your gallery pages fast on mobile:

• Never lazy-load the hero/LCP image. LCP (Largest Contentful Paint) measures how fast your main image appears — so your hero photo must load right away, not be lazy-loaded. Everything below the fold? Lazy-load it.
• Set width and height on every image. This prevents layout jump — called CLS (Cumulative Layout Shift) in Google's speed report — so text doesn't bounce around while images load.
• Use AVIF/WebP with srcset. Srcset tells the browser to serve a small image on phones and a larger one on desktops — faster loads on every device.
• Keep images under ~200–300 KB for typical shots. Larger is fine for hero images that need the extra detail.
• Delay heavy scripts (chat widgets, map embeds) until after the user interacts with the page.
• Keep buttons visible on mobile — Call Now and Start My Project should never be hidden behind a scroll.

For a deeper owner guide to phone speed: Minimal-bloat build & Core Web Vitals.

08The Case-Quote Wall (Proof That Actually Gets Read)

Instead of a single "Gallery" page that loads slowly, build a Case-Quote Wall:

• 2–3 columns of job cards.
• Each card: 1–2 photos, a two-line customer quote, and a neighbourhood tag.
• A tiny "View details" link to the full project page (150–250 words).

Why it works: People scan. Short cards with real quotes feel trustworthy. They encourage the next tap far more than a giant slideshow ever will.

See examples and patterns: Photos & Proof that Build Trust. Roofing-specific gallery tips: Before/After Galleries Without Killing Speed.

09Google Business Profile Photos: What Actually Matters

Your project pages live on your website — but your Google Business Profile is where many Cochrane homeowners see you first.

Your GBP (Google Business Profile — your free Google listing that shows up in Maps) needs real, recent photos:

• Post photos of real, recent work. Not stock images. Not last year's jobs.
• Keep them upright, bright, and tidy. No cluttered, dim garage shots.
• In GBP posts, link to the exact matching page on your site — the specific project page or service page, not your homepage.
• Skip the EXIF tricks. Consistency and quality beat metadata tinkering every time.

For the full GBP playbook — from setup to your first 25 reviews — see Google Business Profile: Setup to First 25 Reviews.

10Owner Checklist (Print This and Tape It Up)

Here's your quick-reference checklist for every project page and monthly upkeep:

Every New Project Page

• H1 includes the job and neighbourhood
• Intro says problem → fix → outcome (60–80 words)
• 2–4 photos: best "after" on top, supporting images below
• File name / alt text / caption templates applied
• Neighbourhood chip added (e.g., Fireside)
• Start My Project button near proof; Call Now visible on mobile
• Page loads snappy on your phone (first screen feels instant)

Monthly (Batch Updates)

• Add 3–6 new job cards to the Case-Quote Wall
• Post 1 GBP update linking to a relevant page
• Replace any stock-looking photo with a real one
• Run a speed snapshot on one Proof/Project page; fix any regressions

Need hands-off maintenance? No CMS, No Problem covers edits by email, form tests, and monthly speed checks.

11Common Owner Questions

Here are the questions we hear most from Cochrane trade owners:

Do we really need neighbourhood names on every project?

Yes. Cochrane is tight-knit. "Sunset Ridge AC swap" feels local and relevant — and it helps your Areas We Serve page tell a real story instead of a generic one.

How many photos is too many?

If the page starts to feel slow or repetitive, it's too many. Aim for 2–4 decisive images per project page. Put extra shots into the Case-Quote Wall card or a below-the-fold mini-gallery.

Can we keep our before/after slider?

Absolutely — just put it below the fold. Keep a clean, static "after" hero image up top, and let the slider load after the visitor scrolls down.

What about video?

Short, silent clips can be great. Just don't let an auto-play video block the first screen. Use a play button that loads the video on demand instead.

12Related Reading

• Proof: Photos & Proof that Build Trust
• Roofing galleries: Before/After Galleries Without Killing Speed
• Local structure: Service-Area Pages (Doorway-Safe)
• Speed & UX: Minimal-bloat build & Core Web Vitals
• Tracking: Tracking Calls & Forms the Simple Way