A beautiful portfolio that Google can’t read is a gallery with no front door.

Photography demand always arrives qualified. The couple searches their venue’s region; the marketing manager searches the deliverable (“e-commerce product photography”); the new parent searches their town. The generic homepage targeting “photographer + city” competes against directories and studios for a query with weaker intent than any of the genre terms it is neglecting.

The queries that pay

• “Wedding photographer [region / venue area]”, plus the venue names themselves.
• “Newborn photographer [town]”, “family photoshoot [area]”.
• “Corporate headshots [city]”, “LinkedIn headshot photographer”.
• “Product photographer for [platform]”: Amazon, Shopify, Etsy sellers.
• “[Event type] photographer”: conference, awards dinner, graduation.

Each cluster deserves a dedicated page with its own gallery, copy, pricing signal and FAQs. That is the single highest-leverage change on most photography sites.

For visual services, image search is a buying surface: people shortlist photographers from the images themselves. Winning it is mechanical and almost nobody in the vertical bothers.

The image pipeline we implement

• Descriptive filenames before upload: thornton-manor-wedding-first-dance.jpg, not DSC_4021.jpg.
• Alt text describing the actual frame, written for a person who cannot see it.
• Captions and surrounding text: Google reads context around the image as hard as the file itself.
• An image sitemap covering galleries the crawler cannot navigate.
• WebP/AVIF derivatives with responsive srcset, full-resolution originals behind click-through, so Core Web Vitals stop bleeding.
• IPTC creator and licence metadata, which also feeds the Licensable badge.

The performance dividend

Portfolio sites routinely ship 15-40MB pages. Getting LCP under 2.5 seconds on an image-led page is entirely achievable with a proper derivative pipeline, and the ranking and enquiry-rate gains stack.

Wedding photography SEO has a weapon no other genre gets: the venue. Couples search venues by name for months, “[venue] wedding photos”, “photographer for [venue]”, and a real-wedding post shot at that venue answers the query with proof no competitor can fake.

The venue playbook

• One real-wedding write-up per venue you have shot: the story, 30-50 curated frames, named suppliers, practical notes on light and logistics at that venue.
• A venues-served hub linking every write-up, structured by region.
• Supplier link earning: the florist, venue coordinator and band you credited all have websites and blogs that link back to real-wedding features.
• Destination positioning where relevant: “Lake District elopement photographer” is a different, winnable market with travel-inclusive pricing made explicit.

Twelve venue posts outrank five years of generic blogging, and they convert because the couple literally sees their venue through your eyes.

Portrait, newborn and family demand is radius-bound: parents book close to home. That is Google Business Profile territory: category set to the right photography type, genre-organised photo uploads (your GBP gallery is a portfolio surface), service list with prices, and review velocity with genre keywords appearing naturally in review text.

Studio vs on-location nuance

A studio address anchors Map Pack eligibility cleanly. On-location photographers work a service-area profile, which ranks less prominently, so the organic genre pages plus venue and location content carry more of the load. Both models work; the architecture differs, and getting it wrong wastes a year.

Photographers arrive convinced they need a rebuild. Usually they need configuration: deliberate page titles and descriptions instead of platform defaults, alt text applied at upload, genre pages created as real pages rather than gallery links, heading structure that says what the page is, and the blog used for venue write-ups rather than nothing.

When a rebuild is honest advice

• The template renders galleries client-side with no crawlable fallback, and the platform offers no fix.
• Core Web Vitals stay red after every optimisation lever is pulled.
• You need genre + city scale (studio with associates) that platform routing cannot express.

Then we build hand-coded, schema-complete and gallery-fast, and migrate with redirects that preserve every ranking you already own. Otherwise, keep the platform and spend the difference on venue content.