The short answer: a "Gallery" page with sixty photos on it ranks for nothing. Sixty individual project pages, each with its own location, scope, materials, and photographs, can rank for hundreds of long-tail searches that convert far better than the head terms you're currently losing.
Most contractor websites have this exactly backwards. They put enormous effort into a handful of service pages competing for brutally contested keywords, and they dump their best asset — documented completed work — into a single undifferentiated gallery.
Why the gallery page fails
A gallery is a pile of images with no text, no context, and no individual URLs. From a search engine's perspective it is one page about nothing in particular.
Consider what it can't do:
- It can't rank for "modern pool with tanning ledge Frisco" because those words don't appear anywhere
- It can't earn a link, because there's nothing specific to link to
- It can't answer a question, because it doesn't contain any answers
- It can't be shared, because "here's their gallery" isn't a recommendation
Meanwhile it holds the only genuinely unique content on the site. Every competitor can write a services page. Only you built that specific backyard.
What a project page actually is
A project page documents one completed job as its own URL. Not a photo — a page. The photographs still matter — bad photography has a measurable cost in search — but they need a page to live on.
The structure that works:
A descriptive, searchable title. Not "Project 14." Something like "Modern Pool and Outdoor Kitchen — Frisco, TX." That title contains a service, a style, and a location, which is how people search.
The specifics. Square footage, materials, features, timeline, and where it is. A homeowner reading this is calibrating whether you do work like theirs.
The problem and the solution. What the client wanted, what constrained the site, what you did about it. This is the part that separates a portfolio from a catalog, and it's the part that makes the page worth linking to.
Real photography, properly handled. Multiple angles, descriptive filenames and alt text that say what's in the image. Before-and-after where you have it.
A price range, if you can stomach it. Most contractors won't. The ones who do filter out unqualified leads and rank for a class of searches nobody else touches.
Internal links to the relevant service page and the relevant city page.
The math that makes this worth doing
One service page might target "pool builder Dallas" — a term with real volume and every established competitor in the metro fighting for it. You may never win it.
Forty project pages target forty long-tail phrases each. "Small backyard pool Plano." "Pool with baja shelf and spa." "Outdoor kitchen with pizza oven DFW." Individually tiny. Collectively substantial, and dramatically less contested.
More importantly, the intent is different. Someone searching a head term is browsing. Someone searching "pool with tanning ledge and fire bowls" has a picture in their head and is looking for someone who has already built it. If your page is what they find, you're not competing on price anymore.
How this connects to service-area pages
Project pages and service-area pages reinforce each other, and that's the whole architecture.
A service-area page for McKinney that says "we proudly serve McKinney and surrounding areas" is worthless. One that says "here are eleven projects we've completed in McKinney" — each linking to its own page, with addresses in the neighborhoods — is a genuinely strong page that no competitor can fake.
The structure looks like this:
- Service pages — one per service, targeting the head terms, linking down to relevant projects
- Service-area pages — one per city where you have real history, linking to projects completed there
- Project pages — the foundation, feeding both
Every completed job strengthens both the service page and the city page above it. The site gets stronger as you work, which is the opposite of how most contractor sites behave.
The objection everyone raises
"That's a lot of pages to build."
It is. But it's mostly a documentation problem, not a writing problem. If you photograph every completed job properly — which you should be doing anyway — the page is thirty minutes of work while the details are fresh.
The businesses that do this treat it as part of closing out a job, the same as final walkthrough and invoicing. A year later they have forty pages of unique, unfakeable content, and a competitor starting from zero cannot catch up without doing forty more jobs.
Where this goes wrong
Thin pages. Three photos and two sentences is not a project page. If you can't say something substantive about the job, don't publish it yet. Deciding which jobs deserve a page, and in what order, is content strategy work.
Templated pages. Same paragraph with the city and dimensions swapped, forty times. Google's spam policies name this risk: scaled content abuse, meaning many pages made to game rankings rather than help people. Each page must be genuinely about that job.
Bad photography. This is the one that quietly kills it. A page structured perfectly with dim, wide-angle phone photos converts worse than no page. The whole point is showing quality, and the images are the argument.
No internal linking. Orphaned project pages that no navigation reaches are harder for search engines to find. Google's link guidance says every page you care about should be linked from another page on your site. Project pages need to be linked from the service and city pages above them.
Getting started without rebuilding your site
You don't need a redesign. You need a URL pattern and a habit.
- Pick your ten best completed jobs — the ones you'd want a prospect to see.
- Build one page for each, at
/projects/[descriptive-slug]. - Link them from the relevant service pages and from a project index.
- Add each to your sitemap.
- Document every new job as you finish it, going forward.
Ten pages is enough to see whether it works for you. If those pages start appearing in Search Console's Performance report for terms you never targeted, you have your answer.
The underlying point
Most contractor SEO advice treats your website as a brochure to be optimized. For a portfolio business, the website is a record of work, and the record is the ranking asset.
The companies that win this are the ones that recognize their completed jobs aren't marketing material to be summarized. They're the content. For builders, read the builder version of this argument.
Carpenter Growth builds search and visual strategy for high-ticket home service businesses in Dallas-Fort Worth — including the photography and video that makes project pages worth reading. Start a conversation.
This note is part of the broader Contractor SEO: The Complete Guide.
Once those project pages exist, make sure the supporting images are search-ready with Image SEO for Contractors: The Complete Checklist.

