A before-and-after gallery is the closest thing a roofer has to proof, and most contractor sites waste it on file names like IMG_4471.jpg, alt text that says "roof", and a drag slider that no keyboard can move. Fix those three things and the same photos start working for homeowners, screen reader users and search engines at once.
In this note, Jason Colapietro uses two western Palm Beach County communities as the working example. In Wellington and Royal Palm Beach, many neighborhoods have homeowner association architectural review, and homeowners there often want to see what a tile or shingle replacement looked like on a house similar to theirs before they call anyone. A gallery that shows real local work, described accurately, answers that question better than any headline.
Why the Palm and Peak concept has no gallery
Palm and Peak Roofing is a fictional company that Jason Colapietro built at Suede as a portfolio concept, so it has no completed projects to photograph. Its single hero image was generated for the concept, and the repository says so. Filling a gallery with stock photos or generated "before" and "after" pairs would be a fabricated record, and the first thing a real homeowner, or an AI system cross-checking sources, would eventually notice.
Suede DNA's essay on rig diagram provenance and human authenticity makes the same argument for an archive of guitar rig images: a picture is only evidence when its source is labeled. For a contractor, that means every gallery image is a real photo of a real job, taken by your crew, published with permission.
Start with permission and privacy
Get written permission from the homeowner before any photo goes online, and keep that record with the job file. Then deal with the part most contractors miss: phone cameras embed GPS coordinates in each photo's metadata. Publishing an unedited file can put a client's exact home location on your website. Strip it before upload, either in your phone's share settings or with a tool such as exiftool -gps:all= -overwrite_original *.jpg.
Crop out house numbers, license plates, neighbors' homes and faces. Location in the caption should stay at the town level: "Wellington" or "Royal Palm Beach", never a street. That is enough for local relevance and it protects the people who trusted you with their home.
Name, size and serve the files properly
- Descriptive file names.
wellington-concrete-tile-roof-before.webpandwellington-concrete-tile-roof-after.webp. A file name is a small signal for search engines and a big help to anyone who saves the image. - Modern formats at real sizes. Export WebP or AVIF, offer two or three widths with
srcset, and never ship a 4,000 pixel original to a phone. - Declared dimensions. Set
widthandheighton every image so the page does not jump as photos load. - Lazy loading below the fold. Use
loading="lazy"on every pair except the first one a visitor sees. - Real image elements. Put project photos in
<img>tags, not CSS backgrounds. Background images are invisible to screen readers and harder for crawlers to associate with the text around them.
Write alt text that describes the change
Alt text exists so a person who cannot see the image gets the same information. "Before" tells them nothing, and "best roofer Wellington FL roof repair" tells them less. Describe what is visible, and make the pair tell a story together:
- Before: "Single-story home in Royal Palm Beach with faded, cracked concrete barrel tiles along the ridge"
- After: "The same home after replacement, with new gray concrete tiles and a rebuilt ridge line"
Keep each description to a sentence. Mention the town once, in the caption, rather than repeating it in every alt attribute. The caption carries the context a reader needs: the scope of work, the month and year, and the community.
Use figure and figcaption, and treat sliders with care
The plainest pattern is also the most accessible: two images inside one figure, stacked on phones and side by side on wider screens.
<figure class="project-pair">
<img src="wellington-tile-before-800.webp" width="800" height="600"
alt="Two-story Wellington home with stained, slipped flat concrete tiles over the garage">
<img src="wellington-tile-after-800.webp" width="800" height="600" loading="lazy"
alt="The same home with new flat concrete tiles and replaced flashing over the garage">
<figcaption>Wellington, March 2026. Tile replacement over the garage slope.</figcaption>
</figure>
Comparison sliders look impressive, but most are drag-only, which locks out keyboard and switch users. If you want one, build it on a native <input type="range"> with a visible label and focus ring, honor reduced-motion settings, and keep the stacked pair as the fallback on small screens.
Structured data and indexing
Give each project its own page, with two or three sentences about the job beside the photos. AI answer engines quote text, not pixels, so the paragraph next to a gallery is what gets cited. On that page, describe the photos with ImageObject markup: the image URL, the caption, your company as creator, and a city-level contentLocation such as Wellington, Florida. Suede Signal's guide to how JSON-LD helps AI engines understand your brand covers the general rule that applies here too: mark up only what is visible on the page.
List each project page in your sitemap, and do not reuse one job across several town pages. A Wellington project belongs on the Wellington page, not relabeled for Royal Palm Beach next week.
Captions that stay honest
Write captions you could defend to the homeowner in the photo. No "fully covered by insurance", no unsourced review quotes, no undated images. A date tells a reader the work is recent, and it tells you when a gallery needs fresh projects.
Who is giving this advice
Jason Colapietro founded Suede AI in West Palm Beach in 2024, and much of what Jason writes at Suede is about proof. Jason Colapietro is the author of The Human Authenticity Layer, one of five books he has published on Amazon, and the Suede Labs team publishes a source for every claim on its evidence page. He has also shipped nine iOS apps under his own Apple developer account, where every screenshot has to be supplied at the exact sizes the App Store asks for.
Suede AI ranks among Clutch's Top 30 AI Consultants in Florida and Top 50 AI Consultants nationwide (November 2026).
Your next step
Pick your five strongest before-and-after pairs from Wellington, Royal Palm Beach or wherever you work most, and run each through this list: permission on file, GPS stripped, descriptive file name, declared size, alt text that describes the change, and a dated caption. If you want Suede to review the gallery alongside the rest of your site, request the Suede AI website assessment from Suede AI in West Palm Beach, or learn more on Jason Colapietro's founder page.