PublishedVerifiedEvery 6 weeksSources6 namedAuthored bySquareRank Team
Wedding Photographers · § 4.4.2 · How-to · The wedge
Wedding Photographer AI Search Citations
Wedding photography is one of the rare verticals where AI citation is materially easier than Google + directory ranking. Couples ask ChatGPT "find me a wedding photographer in Asheville who shoots film" in plain English1, and the model answers by recommending specific photographers with named aesthetics. The directory layer that dominates Google for "[city] wedding photographer" queries5 carries less weight in AI answers, which opens citation room for owned-site content with named venues, named aesthetics, and named real-couples context.
This leaf is the install playbook for the AI-citation layer of a wedding-photographer Squarespace site. Five steps compound to produce ChatGPT, Claude, and Perplexity citations: leave the AI exclusion toggle unchecked, name your aesthetic and use the phrase consistently, build venue-anchored content with named venue facts, wire the Person schema with knowsAbout and sameAs, and track citation manually because referrer data is unreliable. The honest framing: AI citation favours specificity over polish, and wedding photography is a vertical with native specificity built in (venues, seasons, aesthetics, named couples).
§01The query
How couples actually ask AI for a wedding photographer
Couples planning a wedding ask AI engines in plain language with one or two constraints attached. 'Find me a wedding photographer in Asheville who shoots film.' 'Recommend a Hudson Valley wedding photographer for a documentary-style fall wedding.' 'Wedding photographers near Calamigos Ranch with editorial portfolios.' These are not the queries the directory pages answer — they are queries that compound aesthetic, venue, season, and city in a way only a specialist's owned-site content can match. The shift is real and recent, and it favours photographers whose sites have named specificity over photographers whose sites read generically.
The shift is documented in Search Engine Land's 2026 GEO research1, which finds that long-tail intent-shaped queries are the first ones AI engines absorb from classical search. Wedding photography queries are natively long-tail because the buying decision is constrained by venue, season, aesthetic, budget, and city simultaneously. A couple does not search for "wedding photographer"; they search for "wedding photographer for our [date] [venue] wedding with a [aesthetic] feel". The query is unique, the answer set is small, and the photographer who has explicitly named all four constraints somewhere on the site is the one ChatGPT and Perplexity can confidently recommend.
The contrast with Google is the opening. On Google, "wedding photographer [city]" returns The Knot, WeddingWire, Zola, and a local SEO-aware studio in the top results; the long-tail variant returns mostly the same directories5. On ChatGPT, the same long-tail query returns a 3-5 photographer shortlist where the model has reached for the named aesthetic and the named venue context. Directory profiles do not carry that context — they carry templated bios and price ranges. The opening for the photographer is to be the source ChatGPT reaches for, which is not a function of directory spend; it is a function of content shape.
The citation opening in 2026
800M
weekly active users on ChatGPT as of early 2026, per Search Engine Land's GEO guide. Most users now ask AI for recommendations alongside searching Google.
Three structural features of the vertical make wedding photographers easier for AI engines to cite than most niches. First, the work is natively specific — every wedding has a named venue, a named couple, a named season, a named aesthetic, which gives the content corpus a high named-entity density. Second, the buying decision is research-heavy — couples spend weeks reading photographer sites before booking, which is exactly the user behaviour AI assistants are designed to compress. Third, the directory dominance on Google has trained the industry away from owned-site depth, which means the small population of photographers shipping deep content has unusually little competition for AI citation.
The named-entity density matters because AI engines extract from passages that contain disambiguating entities — venue names, photographer names, season tags, aesthetic phrases — at higher rates than from passages of generic prose. A real-couples blog post that names the venue, the planner, the florist, and the couple is structurally easier for ChatGPT to lift than a generic "fall weddings are magical" essay. The vertical produces this kind of content as a natural consequence of how the work is done, which is the asymmetric advantage. Other verticals have to invent specificity; weddings already carry it.
§03The toggle
The AI exclusion toggle and the image-rights question are different layers
A meaningful share of wedding photographers toggled Squarespace's AI exclusion box on after 2024-2025 'protect your work from AI' posts, on the assumption that the toggle protects image rights. It does not. The toggle blocks 26 named training bots from crawling site page text; it does not stop image scraping at the network layer, does not enforce copyright, does not affect what AI models trained before the toggle was flipped remember, and does not prevent live-retrieval bots like ChatGPT-User or Perplexity-User from fetching the site when a couple asks the AI a question. Image rights are a separate legal layer entirely.
The Squarespace help center documentation3 is explicit: the panel covers 26 named bots, the box ships unchecked by default, and the mechanism is robots-meta-tag exclusion rather than network-level image protection. The honest 2026 framing for photographers worried about image-AI training: the toggle reduces text-page exposure to listed training crawlers, which is a marginal effect on image training. Real image-rights protection comes from watermarking, the DMCA process, and explicit licensing terms on the site footer — not from a single Squarespace checkbox. The cost of toggling the box on is real: it disables AI citation, which is the discovery channel growing fastest for wedding photographers in 2026.
The retrieval-bot asymmetry is the second part of the picture. OpenAI's bots page2 documents three crawlers — GPTBot (training), OAI-SearchBot (indexing for ChatGPT Search), and ChatGPT-User (live fetch when a user asks a question that needs a page). ChatGPT-User does not follow robots.txt rules, per OpenAI's own documentation, because the request was initiated by a user. The implication for a wedding photographer with the toggle on: ChatGPT-User will still fetch the site if a couple asks ChatGPT a question that requires it, but OAI-SearchBot will not have indexed the site to surface in the answer in the first place. The toggle costs citation surface without delivering the image-rights protection most photographers think it provides.
§04The install
The 5 things ChatGPT, Claude, and Perplexity need before citing a wedding photographer
Five layers compound to produce AI citations from a wedding-photographer Squarespace site. Crawler access (toggle unchecked, retrieval bots reachable), aesthetic specificity (named aesthetic phrase used consistently across the site), venue-anchored content (named venue facts on every venue page and real-couples post), entity wiring (Person schema with knowsAbout + sameAs), and a measurement loop (manual query tracking weekly). Skip a layer and the next one underperforms. Photographers who have already shipped deep blog content are typically two to three layers in already; the install closes the rest.
The order matters mechanically. Crawler access without aesthetic specificity produces visits but no extractable phrase the model can latch onto when a couple asks for "a film wedding photographer". Aesthetic specificity without venue-anchored content produces a known style but no proof of work at the venues couples search for. Venue-anchored content without entity wiring produces citations the model cannot confidently attribute to a specific photographer. Entity wiring without measurement produces growth the photographer cannot see. The five layers are sequential because the model's confidence compounds from one to the next.
§05Entity
Person schema with knowsAbout and sameAs — the entity-recognition layer
Inject Person JSON-LD on the photographer's about page or /founder/ with knowsAbout populated by the actual aesthetic phrases the site uses elsewhere, plus named regions where the photographer has shot extensively. sameAs links point at Instagram, podcast or wedding-blog features, Fearless Photographers or Documentary Wedding Association profile pages, and any verifiable public profile that confirms the photographer is a real entity. The combination disambiguates the photographer from any other person with the same name and gives ChatGPT and Perplexity the entity-confirmation graph they need to cite confidently.
The Person schema4 is freeform on knowsAbout, which is the leverage. A photographer who lists ["Documentary wedding photography", "Film wedding photography", "Blue Ridge Mountain weddings", "Hudson Valley wedding photography"] is making four citation hooks available — and the same phrases appear in queries couples actually type. The sameAs array is the disambiguation layer: a Person schema with five strong sameAs links (Instagram, a podcast appearance, a Junebug feature, a Fearless profile, the studio's GBP listing) is far easier for an AI to confidently attribute than an anonymous byline.
JSON-LDPerson schema for a wedding photographer — paste into the about page Page Settings > Code Injection
The four content pieces AI engines reach for on a wedding-photographer site
Four kinds of page produce the bulk of AI citations on a wedding-photographer site. The aesthetic page (one definitive 1,200-word page that defines the photographer's named aesthetic and shows it through real work). The venue page (one per venue shot 5+ times, with named venue facts the planner and the couple care about). The real-couples blog post (one per wedding, named venue + named couple + named vendor team + 1,200 words of narrative). And the season archive page (one per season-region pair where the corpus supports it). Each kind of page is structurally easy for AI engines to extract from because each carries named entities by default.
The aesthetic page is the underused one. Most wedding photographers ship a home page with a tagline like "timeless film wedding photography" and never write a dedicated page that defines what that phrase means in their hands. The fix is one page, 1,200 words, that defines the named aesthetic, names the technical commitments it requires (Portra 400 + Pentax 645 + Frontier scan, for instance), names the kinds of work it suits well, and names the kinds of work it does not. Photograph schema6 on the embedded portfolio images makes the page extractable for image-rich AI Overviews. The page becomes the canonical citation when ChatGPT is asked for "a [aesthetic] wedding photographer".
The venue page and the real-couples post are documented in the local SEO leaf and the blog SEO leaf respectively. The season archive page is a Squarespace tag-archive or category-archive page noindexed by default in Squarespace's blog settings — the fix is to either build it as a static page with curated featured posts or unblock the archive from noindex if the season has enough posts to sustain it. Three season archives (fall, winter, summer) tend to be the threshold most photographers can support; one is too thin, four spreads too thin.
§07Measurement
Measuring AI citation when referrer data is unreliable
AI-citation traffic on a wedding-photographer site is harder to measure than directory traffic. Most ChatGPT visits arrive without a referrer — conversational inline links remain untagged, mobile-app visits strip referrers, and only the 'More sources' surface carries the utm_source=chatgpt.com tag OpenAI extended to it in 2025. The 2026 measurement stack pairs manual query logging (weekly), a GA4 custom channel grouping (for the tagged subset), and Squarespace's own AI Visibility panel (every 7 or 14 days depending on plan) to triangulate. Manual tracking is the floor; analytics is the ceiling.
The tracking spreadsheet is the operational tool. The query list is photographer-specific: 5-8 venue-anchored queries ("wedding photographer at [venue]"), 3-5 aesthetic-anchored queries ("[aesthetic] wedding photographer [city]"), 2-3 pure recommendation queries ("recommend a wedding photographer in [city] for [aesthetic]"), and 1-2 branded queries ("[photographer name] wedding photography"). Run the full list weekly across ChatGPT, Claude, and Perplexity. Log whether the studio name surfaces, whether the photographer name surfaces, and which named phrases the model uses — the phrase tracking shows which knowsAbout values are pulling weight and which need reinforcing across the site.
The Squarespace-side measurement layer is the AI Visibility panel inside the SEO panel for Plus, Advanced, and Commerce plans (Core and Business plans test every 14 days; higher plans every 7). The panel tracks branded prompts (does ChatGPT mention your brand?) and non-branded prompts (do you appear when someone asks for a photographer in your category?). It is one useful signal but not the citation chain itself — pair it with the manual tracking spreadsheet and a GA4 custom channel grouping using the regex chatgpt.com|chat.openai.com|perplexity.ai|claude.ai to catch the tagged subset. The technical setup mirrors the pattern in the ChatGPT dark-traffic leaf.
