Squarespace SEO for Wedding Photographers

The query-shape shift is the most underdiscussed of the four. Search Engine Land's 2026 GEO research⁸ shows the queries AI engines absorb first are long-tail, intent-rich, and structured around a real-world constraint. For weddings that constraint is almost always one of three things: the venue, the season, or the aesthetic. "Wedding photographer Saltwater Farm Vineyard" is a query with one answer set; "Hudson Valley fall wedding photographer film" is a query with another; "Calamigos Ranch wedding photographer documentary" is a query with a third. Each is a 200-search-per-month head with a deep tail of variants, and each is precisely the shape a 1,200-word real-couples blog post on a photographer's Squarespace site can answer directly while a templated directory profile cannot.

The directory consolidation is the second shift. The Knot Worldwide reports 43 to 45 million monthly visitors and 9 million leads delivered to vendors in 2024 across its platforms¹, and The Knot and WeddingWire are the same company after a 2018 merger backed by Permira Funds and Spectrum Equity². The practical effect for a photographer is that two of the three top non-branded results for almost any "wedding photographer [city]" query are owned by one corporate entity, charging vendors for placement, with the same lead broadcast to multiple competing vendors. The owned-site alternative has higher leverage per visit, but it requires content the directory cannot replicate.

The category failure is the most common and the costliest. Google Business Profile⁶ exposes "Wedding Photographer" as a distinct primary category and "Photographer", "Portrait Photographer", and "Photography Studio" as adjacent ones. A wedding photographer choosing "Photographer" competes against newborn studios, real-estate photographers, and corporate headshot shooters for a generic category bucket; the same shooter choosing "Wedding Photographer" competes only against direct peers and ranks for the queries that produce booking inquiries. The same listing should run as a service-area business — addressing hidden, travel radius defined — when the photographer works at venues rather than a public studio, which is true of most wedding shooters.

The schema failure is mechanical. Squarespace auto-emits some structured data on contact pages, but the auto-emitted type is generic LocalBusiness without a serviceType value. The fix is a Code Injection block (Business plan or above) that overrides the auto-emitted markup with LocalBusiness carrying serviceType: "Wedding Photography"³, a connected Person schema for the photographer with a knowsAbout array carrying real aesthetic terms ("documentary wedding photography", "film wedding photography", "editorial wedding photography"), an areaServed array if the photographer travels, and Photograph or ImageObject markup on the portfolio gallery itself for image-rich citation surfaces. The local SEO leaf ships the full block.

The blog failure is strategic. A wedding photographer who writes one blog post per real wedding, with the venue name in the post title, the season in the H1, and a 1,200-word narrative on the day, builds the exact corpus that ranks for "[venue] wedding photographer" and "[city] [season] wedding photography" queries — the highest-converting query shapes in the vertical. A wedding photographer who treats the blog as an afterthought ships templated galleries with no text, and Google reads the result as a thin page set. The blog SEO leaf works through the post template, the venue-paragraph rule, and the gallery-schema pattern.

The AI-toggle failure is the most recent. A wave of 2024-2025 posts told photographers to "protect their work from AI training" by toggling Squarespace's AI exclusion box on. The toggle blocks 26 named training bots from crawling site text⁷; it does not stop image scraping at the network layer (image copyright is a different legal layer entirely), and it does prevent ChatGPT, Perplexity, Claude, and Gemini from citing the photographer when a couple asks the AI for a recommendation. The honest tradeoff is documented in the AI crawlers cluster; the leaf-level photographer answer is in the AI search leaf.

The serviceType value matters because Google's local-pack extraction reads it as a confidence signal for industry-specific queries³. A wedding photographer shipping LocalBusiness with serviceType: "Wedding Photography" plus a connected Person schema is materially easier for Google to slot into the local citation card than a site shipping bare LocalBusiness, and the same pattern appears in Perplexity and ChatGPT citations for wedding-photographer queries we have audited across installs. The Photograph type⁴ sits one layer down and is useful where individual works are presented (a gallery page, a featured-wedding post) and would benefit from creator attribution, contentLocation, and license information.

 <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": "State", "name": "North Carolina" } ] }, { "@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> 

The Photograph type⁴ and ImageObject⁵ are the layer below. Where the LocalBusiness graph identifies the studio, Photograph identifies the individual image on a portfolio page or a featured-wedding gallery, carrying creator, contentLocation, dateCreated, and license. ImageObject is the more general type Google reads for visual-search and image-rich AI Overviews surfaces — caption, creditText, copyrightHolder, and exifData are the properties worth populating. The full gallery-schema pattern lives in the blog SEO leaf.

The audit half of the install starts with four checks. First, the Squarespace AI exclusion box⁷ — a meaningful share of photography sites toggled this on after 2024-2025 "protect my work from AI" posts, and the toggle does not protect image rights at all (it prevents the listed training bots from crawling page text, which is a separate question from image copyright). Second, the Google Business Profile category and service-area mode — most wedding photographers either ran the default "Photographer" category or kept a visible home address when service-area mode was correct. Third, the current schema state — what Squarespace auto-emits, what overrides exist, what serviceType claims are made. Fourth, the current rank set for venue + season queries: where does the site appear for the venues the photographer has actually shot at.

The build half ships the schema graph (LocalBusiness with serviceType + areaServed + connected Person + Photograph or ImageObject on the portfolio), the blog restructure on the most-trafficked posts (venue name in the title, season in the H1, 1,200-word narrative with named venue facts and named vendors in the post body), the GBP category change to Wedding Photographer with service-area travel coverage defined, and the citation-hygiene restructure on the top five pages so AI engines can extract a clean passage. The wedding-specific addition is the venue and season tagging across the blog archive — most photographers have 50 to 200 existing real-wedding posts, and a one-pass retagging recovers ranking on the long tail without rewriting content.

The merger history matters because it explains the lead-broadcast model². XO Group (The Knot's parent) and WeddingWire merged in December 2018 under common ownership by Permira and Spectrum Equity, which is why a couple inquiring through either site can produce the same inquiry routed to multiple vendors at once. The Knot Worldwide reports 9 million vendor leads delivered in 2024¹ across its platforms, broadcast to vendors who pay for placement. The vendor-side experience is consistent across the industry: the lead is real, the lead quality is mixed, and the response-speed-wins dynamic favours full-time studios over solo shooters who shoot 12-20 weddings a year.

The four leaves are written to stand alone — each carries its own sources, its own answer-first passages, and its own internal links back to this hub, the niche pillar, the AI-search pillar, and the schema pillar. Reading order does not matter, but the recommended starting point depends on the failure mode currently costing you the most: venue + city ranking (local SEO leaf), AI-citation absence (AI search leaf), blog archive underperformance (blog SEO leaf), or platform decision (Showit-vs-Squarespace leaf).

The shared foundation for all four is the AI Visibility Framework on the Squarespace × AI Search pillar and the schema patterns on Pillar 3. Generic mechanics live in Pillar 2 (Squarespace SEO mechanics, shipping next). The wedding-photographer-specific layer adds the venue-anchored content strategy, the LocalBusiness with serviceType, the Photograph or ImageObject markup, and the directory benchmark — not the underlying SEO, which is the same for every Squarespace site on the planet.