SEO for Photographers: The Local Keywords, the Image Weight Problem, and the Technical Half Nobody Covers

SEO for a photographer comes down to three things: target the search a client actually types, which is a service plus a place, such as wedding photographer in a named town; make every gallery page fast enough that search engines and phones tolerate it, which is the hard part on an image-heavy site; and publish work regularly in a form that search can read, which means real pages with real words about each shoot, not a slideshow. The keyword research is a morning’s work. The speed problem is where most photography sites fail, and it is the half this guide spends its time on.

The guides that rank for this term are long and mostly right about keywords, blogging and backlinks. They are almost silent on the thing that makes a photographer’s site different from every other small business site: it is made of images, images are heavy, and speed is a ranking factor and a conversion factor at once. This post covers the standard advice briefly, then gets specific about image formats, lazy loading, gallery structure and hosting, which is where the ranking actually happens.

Target the search a client types
The image weight problem
Gallery pages that search can read
The technical half, in order
Backlinks and reviews, briefly
Where the site should live
How this fits the rest of the stack
FAQ

Target the search a client types

Nobody searches for photographer. They search for a kind of photographer in a place: newborn photographer plus a town, headshots plus a city, elopement photographer plus a region. Those are the keywords, and the structure of the site should mirror them: one page per service, each naming the place, each with enough words to tell search engines and clients what it is.

Make the H1 plain and literal: the service and the location. Write the emotional copy in the H2s and the paragraphs, where it persuades clients without confusing the crawler.
Give each service its own page. A single portfolio page cannot rank for five different searches.
Name the places you actually travel to, on the pages where it is true. A destination wedding photographer can have a page per destination.
Put the location in page titles and meta descriptions, and in the alt text of the images that were genuinely taken there.

The real estate SEO post covers the local signals that apply to any location-based service, including the map listing, which for a photographer is worth as much as the site: claim it, fill it, and ask every client for a review on it.

The image weight problem

A photography site fails at speed for a simple reason. Each gallery page loads thirty images, each image is a full-resolution export, and the page weighs sixty megabytes. On a phone on a mobile connection that is a twenty-second load, and both the visitor and the crawler have gone. Search engines measure this, through the loading metrics that make up the page experience signals, and a slow gallery is a gallery that does not rank however good the keywords are.

The fix is not to show fewer images. It is to serve each image at the size the screen needs, in a modern format, and only when it is about to be seen.

Resize for the web. The largest image on the page needs to be about as wide as the widest screen it will be shown on, which is around 2,000 pixels for a full-bleed hero and far less for a grid thumbnail. Exporting the client delivery file is what makes pages weigh sixty megabytes.
Use modern formats. WebP or AVIF at quality 75 to 85 is visually identical to a JPEG at a fraction of the weight. Keep a JPEG fallback if the gallery software needs one.
Serve responsive sizes. The srcset attribute lets the browser pick the right size for the screen, so a phone downloads the 600-pixel version and the desktop gets the 1,600-pixel one.
Lazy-load everything below the fold. loading equals lazy on the img tag is enough; the first two or three images above the fold should load eagerly.
Set width and height on every image so the page does not jump as they arrive. Layout shift is one of the measured metrics.

Most gallery plugins and site builders do some of this and skip the rest. Check by loading a gallery page with the browser’s network panel open and reading the total transferred: a gallery should come in under a few megabytes on first load, not sixty.

Gallery pages that search can read

A slideshow with a title is invisible to search. A gallery page needs words: what the shoot was, where, the venue, the season, the kind of client, a paragraph or two that a person would enjoy reading and a crawler can index. Each real shoot is a page that can rank for a venue name or a location, and venue searches are how a surprising number of wedding clients find their photographer.

One page per shoot, with a descriptive title and URL.
A written introduction, then the images, then a closing paragraph.
Alt text that describes the image and, where true, the place. Not a keyword list.
Image structured data or at least a proper sitemap that includes the images, so they can appear in image search.
Pagination or a load-more that produces real URLs, not an infinite scroll the crawler cannot follow.

This is the blogging advice from the other guides, reframed: you do not need a blog with articles, you need the shoots you already do to become pages. One a week is a page a week.

The technical half, in order

Beyond images, the checklist that applies to any site applies here, and a photography site usually needs all of it because it was built by a designer or a builder rather than a developer.

HTTPS with a valid certificate and a redirect from HTTP. A browser warning on a portfolio ends the enquiry.
One canonical domain. www or not, with the other redirecting. Builders sometimes serve both.
A fast host and a CDN so that images are served from near the visitor. The photography hosting post goes into what image-heavy sites need from a host.
Cache headers that let the browser keep images for a long time. Once a visitor has loaded a gallery, the second visit should be instant.
A mobile layout that works. Not a desktop layout that shrinks. Check on a real phone.
A sitemap submitted to the search consoles, and the map listing linked to the site.

Run a page-speed audit on a gallery page, not the homepage, and fix what it lists in order. The image items will dominate the list; the previous section is the fix for them.

Backlinks and reviews, briefly

The off-site work is the same as for any local business: get listed by the venues you shoot at, the planners you work with and the local directories, ask for reviews on the map listing, and let the client galleries you publish attract the links naturally when clients share them. Guest posts and link schemes are not worth the time; a venue’s recommended-suppliers page is worth a great deal, and it comes from doing good work and asking.

Where the site should live

Everything in the image section is easier on a host that does the serving well. A photographer’s site is mostly static, images and pages, with perhaps a contact form and a client gallery login. That shape is cheapest and fastest as a static site: build from a repository, custom domain, an automatically issued certificate, and on RunxBuild 120GB of monthly bandwidth included before the $0.10 per GB rate, which at a few megabytes per gallery page is a great deal of traffic. Cache headers for the images are a headers file, not server configuration. If the portfolio lives on WordPress because the gallery plugins are there, managed WordPress from $3 a month with a file manager in the dashboard is the other reasonable shape. The starting a photography business post makes the case that the portfolio is the storefront; this post is about making sure the storefront loads.

How this fits the rest of the stack

The keywords take a morning, the gallery pages take a discipline, and the speed takes a host that serves images well. If you are deciding where the portfolio should live, the RunxBuild hosting calculator shows static hosting or a WordPress plan beside the bandwidth a gallery-heavy site uses, so the monthly cost is a number rather than a guess. Resize the images, write the pages, and let the shoots you already do become the SEO.

Useful related references:

FAQ

Why is SEO important for photographers?

Because clients find photographers by searching for a service in a place, and the photographers who rank for those searches get the enquiries. Word of mouth still works, but a first-page result for wedding photographer plus your town is a steady source of bookings that costs nothing per lead once the site ranks.

What keywords should photographers target?

Service plus location: the kind of photography you do and the towns or regions you serve, one page per combination that is genuinely true. Add venue names on the gallery pages for shoots at those venues, since venue searches are a common way clients find a photographer.

Does image file size affect a photography website’s SEO?

Yes, strongly. Page speed is a ranking factor and a gallery of full-resolution exports can weigh tens of megabytes, which fails the loading metrics search engines measure. Resize images for the web, serve WebP or AVIF, use responsive sizes, lazy-load below the fold and set width and height on every image.

Should photographers blog for SEO?

Not with articles. Publish each shoot as its own page with a written introduction, the images with descriptive alt text, and a closing paragraph. That produces a page a week that can rank for the venue and the location, without writing anything you would not write for a client anyway.

How do photographers get backlinks?

From venues, planners and suppliers you work with, who often keep recommended-supplier pages; from local directories; from the map listing; and from clients sharing their galleries. Ask after every shoot. Link schemes and guest posts are not worth the time for a local service.