How do clients ask AI for a photographer?

Photography queries are style-plus-budget queries with heavy visual research behind them. Style: documentary wedding photographer in a city, moody newborn photography, natural-light family photographer — the engine matches stated style language, so photographers who articulate their style in words (not only images) get matched. Budget: what wedding photography costs in a metro, headshot pricing, what a family session includes — quoted from whoever publishes at least the shape of pricing. Logistics: how far ahead to book, what happens if it rains, how long until gallery delivery — answered from whoever publishes process content. With the Gemini app past 750 million monthly users and local answers built on GBP and reviews, photographers who translate visual work into crawlable language enter the answer set; image-only portfolios do not.

Making the portfolio crawlable

The core problem in this vertical is that the product is images and engines read text. The fix is structured translation. Every portfolio gallery gets a text companion: location, season, venue type, style notes, what the client asked for. Image alt text written as honest description, not keyword stuffing. Project pages per shoot type — weddings at specific venues, studio headshots, outdoor family sessions — with real photos and written context. Venue-specific pages (weddings at a named local venue, where permitted) capture high-intent long-tail queries. This is the same mirror principle as any visual trade: the work exists on visual platforms, but the citations come from crawlable text on your own domain.

Google Business Profile, reviews and pricing shape

GBP category: Photographer or Wedding Photographer — precise categories matter because the vertical fragments by shoot type. Photos: current portfolio selections, refreshed seasonally. Review texture that moves answers: made us comfortable in front of the camera, delivered the gallery early, calm when the timeline slipped, the photos look like us. Working-experience texture is what vetting answers quote, because clients cannot judge image quality differences as well as they fear a difficult experience. Pricing: publish the shape — collections starting at X, what each tier includes, what drives cost (hours, second shooter, albums). Full secrecy forfeits every budget query to competitors and aggregators; honest ranges with drivers are quotable and filter for fit.

Schema and entity work

Use LocalBusiness with areaServed, priceRange and sameAs to GBP, Instagram-class portfolios and any directory listings; ImageObject markup on portfolio images with descriptive captions. Service markup per shoot type: weddings, portraits, headshots, events, commercial. FAQPage on the real questions: what do your collections cost, how far ahead should we book, how many photos do we get, what is the turnaround. NAP consistency is simpler here than in trade verticals but still breaks across studio names, personal brands and DBA drift — one canonical name everywhere. Method: the entity guide.

Source graph: vendor networks and community proof

Photography referrals run through vendor networks — planners, venues, florists — and community threads asking who shot your wedding. The source-graph work: real relationships with venues and planners (cross-referral mentions are citable), features on wedding-publication-class platforms where legitimately earned, and consistent presence in local creative directories. Community participation works when it is generous: answering what-should-we-budget threads honestly, including the ranges where you are not the fit. Earned features and venue partnerships corroborate the entity in exactly the places engines cross-check; method in digital PR for GEO.

Pitfalls

  • Image-only portfolios. Beautiful, uncrawlable, unanswerable — the engine cannot match what it cannot read.
  • Full pricing secrecy. Budget questions dominate the funnel; contact-for-pricing hands the answer to whoever publishes ranges.
  • Style vagueness. Timeless and romantic describes everyone; specific style language is what style queries match.
  • Stale portfolios. Galleries showing work from years ago suppress recommendations; recency is a quality proxy.

First-month checklist

  1. Text companions added to every portfolio gallery.
  2. Pricing shape published: collections, ranges, drivers.
  3. LocalBusiness + Service + FAQPage schema live.
  4. Three shoot-type pages and two venue pages published.
  5. GBP photos refreshed; review cadence tied to gallery delivery.
  6. Baseline four-dimension run archived.

Frequently asked questions

Do photographers really need text if the images are strong?
Yes — engines match queries to text. Style, budget, logistics and venue queries are answered from words, and images are corroboration. The strongest image portfolio without text companions is invisible to the answer layer where bookings increasingly start.
Should photographers publish exact package prices?
Starting prices and tier shapes, yes: collections from X, what each includes, what drives the final number. Exact bespoke quotes stay bespoke, but publishing the shape captures budget queries and filters for fit before the inquiry.