Wedding Photographer Local SEO on Squarespace

The category choice in Google Business Profile¹ is the most under-discussed lever. Wedding Photographer is exposed as a distinct primary category alongside Photographer, Portrait Photographer, and Photography Studio, and the one you pick decides which queries you compete for. A solo wedding shooter choosing Photographer competes against newborn studios, real-estate photographers, and corporate headshot shooters in a generic category bucket; the same shooter choosing Wedding Photographer competes only against direct peers and surfaces for the queries that actually produce booking inquiries. The most specific accurate primary usually wins, and secondary categories (up to nine) pick up the adjacent shoots — Portrait Photographer for engagement sessions, Photography Studio if you maintain a public space.

The service-area-business question is the second shift². Most wedding photographers either work from home or rent a non-public studio space, and showing the home address on a public profile is both a privacy issue and a ranking distortion (Google reads the listing as a brick-and-mortar storefront when it is not). Service-area mode hides the address and lets the listing carry a travel coverage instead, which is the truthful representation of the business and the setting that ranks correctly for "[city] wedding photographer" queries originating from anywhere inside the service area. The address question and the travel-coverage question are answered together, not separately.

The primary-category choice carries more ranking weight than any single other field¹. Most wedding-photographer GBP listings under-specify here — defaulting to "Photographer" because that is what the photographer learned to call themselves before Google added the wedding-specific value. The fix is honest specificity: if 70% or more of revenue comes from weddings, primary is Wedding Photographer; the rest is held in secondary categories where they actually contribute booking inquiries. Adding too many secondaries dilutes the wedding signal; the current best-practice cap most credible field analyses cite is 2-3 closely related secondaries, not the full nine the platform allows.

The service-area-business setting is where photographers most often misconfigure². Three patterns are common: home-based shooter with home address visible (wrong — set service-area, hide address), home-based shooter with no public address but no service area defined either (incomplete — define the cities), and studio-based shooter with the public studio address visible (correct as configured, no change needed). The travel coverage should match the cities listed on the Squarespace site itself; mismatches between GBP service area and on-site coverage statements read as conflicting signals.

The venue-anchored shape is the highest-leverage of the three. A "[venue name] wedding photographer" query has clear booking intent — the couple has already chosen a venue and is now sourcing the photographer — and the page set that ranks for it is the photographer who has actually shot at that venue and has a dedicated venue page with named details. For any venue where you have shot 5+ times, the venue-anchored landing page (with the venue name in the H1, 1,200 words of why the venue is different to shoot at, 8-12 images, and links to the relevant real-couples posts) is the highest-converting page on a wedding-photographer site by booking rate.

The season-anchored shape compounds with the blog archive. "[City] fall wedding photographer" and "[city] winter wedding photographer" queries respond to a corpus of real-wedding blog posts tagged by season; the photographer with 12-20 fall weddings posted over the last three seasons ranks above the photographer with the same number of weddings posted untagged. The aesthetic-anchored shape responds to the knowsAbout array on the Person schema plus consistent on-site language: "documentary wedding photography" used as the same exact phrase across the home page, the about page, and the knowsAbout array reinforces the entity. Search Engine Land's GEO research⁷ finds AI engines lift these long-tail intent-rich queries first, ahead of the saturated head terms.

The serviceType property³ is the lever that turns generic LocalBusiness markup into wedding-industry-recognised markup. The value is a freeform string, but the conventional choice the wedding industry has settled on is "Wedding Photography" exactly — title-case, no abbreviations, no brand-specific variations. Google reads this as an industry confidence signal and the same string surfaces in Perplexity and ChatGPT citations when a couple asks the AI for a recommendation. The areaServed property⁴ is the second lever: for a destination photographer, it accepts an array of City and State entries mirroring the travel coverage, which makes the multi-city ranking story explicit in the schema graph.

 <script type="application/ld+json"> { "@context": "https://schema.org", "@graph": [ { "@type": "LocalBusiness", "@id": "https://yourstudio.com/#studio", "name": "Linden & Vale Photography", "serviceType": "Wedding Photography", "url": "https://yourstudio.com/", "telephone": "+1-828-555-0142", "priceRange": "$$$", "areaServed": [ { "@type": "City", "name": "Asheville, NC" }, { "@type": "City", "name": "Charleston, SC" }, { "@type": "State", "name": "North Carolina" } ], "photo": "https://yourstudio.com/portrait.jpg" }, { "@type": "Person", "@id": "https://yourstudio.com/#photographer", "name": "Avery Linden", "jobTitle": "Wedding Photographer", "worksFor": {"@id": "https://yourstudio.com/#studio"}, "knowsAbout": [ "Documentary wedding photography", "Film wedding photography", "Editorial wedding photography", "Blue Ridge Mountain weddings" ] } ] } </script> 

Google's local-business structured-data guidance⁵ recommends a single LocalBusiness block per location on a page describing that location. For a service-area photographer that is one LocalBusiness block on the home or contact page; for a photographer who also maintains a public studio, the studio page carries a second block with the streetAddress and openingHoursSpecification populated. The Person schema is the entity-recognition layer that turns the byline into a known entity, which is how AI engines disambiguate when the user asks for a recommendation by name or by aesthetic.

The single-market shooter case is the simplest. One LocalBusiness page (home or contact) carrying the LocalBusiness schema, one venue page per venue you have shot at 5+ times, one season-anchored archive page if your blog corpus supports it, and you are done. The expansion happens through the real-couples blog posts, not through generic city pages. A shooter based in Asheville does not need a "Wedding Photography in Charlotte" page unless they have actually shot weddings in Charlotte; the listing instead leans on the areaServed schema and the GBP service area to surface in Charlotte queries.

The destination-photographer case looks different. A genuine destination shooter who has shot weddings in 6-8 cities across the last three seasons benefits from a city-page set: one parent destination-weddings page with the coverage map, one city page per destination market with the city in the H1, named venues you have shot at in that city, and real images from those weddings. The minimum bar for a destination city page to rank is roughly 1,000 words of city-specific content and at least one named venue you have actually worked at — generic "I would love to shoot your wedding in Paris" pages without that depth read as thin and are filtered.

The directory-citation audit is mechanical. List every directory you appear on (most photographers find 10-15 after a 60-minute audit), pick one canonical NAP (full studio name with consistent suffix, phone in (xxx) xxx-xxxx format, service-area cities listed identically), and edit every directory entry to match. Updates can take weeks to propagate, so the cadence is quarterly. The Knot and WeddingWire, as the dominant directory pair under one ownership⁶, are worth standardising first, alongside Google Business Profile. Regional wedding blogs and venue lists are the long tail; annual audits are fine for that layer.

Reviews carry differently than NAP. Google Business Profile reviews compound into the local pack ranking directly; The Knot and WeddingWire reviews carry directory-side credibility but do not feed back into GBP ranking. For most photographers, the right review-ask sequence is GBP first (every couple, six weeks after delivery), then The Knot or WeddingWire if the photographer runs a paid tier there (renewal incentive), and any niche-specific directory (Fearless, DWA) only if the photographer participates in that community. Cross-platform review fatigue is real; asking for three reviews across three platforms produces fewer reviews than asking for one strong GBP review.