Portrait Photographer AI Search Citations on Squarespace

The pattern is mechanical. Search Engine Land's 2026 GEO guide¹ documents the shift: AI engines lift answers from passages that match the user's full constraint stack, not just the head term. A page that addresses "newborn photographer Brooklyn in-home" with a named session type, named neighbourhood, named location modifier, named photographer, and one specific approach detail beats a directory profile that answers the head term alone. The engines reward the specificity because the user's question contained it.

The reason this is a portrait wedge is the unusual stacking depth in parent-shaped queries. A family-photography query commonly stacks five constraints: session type (newborn, family, maternity, milestone, extended family, senior, cake smash, first-birthday), city or neighbourhood ("Brooklyn", not "New York"), location modifier (in-home, studio, outdoor, beach, park, urban), aesthetic or style (lifestyle, posed, candid, documentary, natural light, golden hour), and approximate age range or session detail ("six-month milestone", "fresh 48", "one-year cake smash"). The number of pages that can earn a citation for any specific constraint stack is much smaller than the search-volume tooling suggests, which is the structural opening for a studio's own site.

The first filter is crawler access. Squarespace's AI exclusion checkbox⁷ ships unchecked by default, but a meaningful share of portrait sites toggled it on after 2024-era "protect my portfolio from AI" advice that conflated training crawlers (which scrape content into model training sets) with retrieval crawlers (which fetch a page in real time so the engine can cite it). The exclusion box treats both as one. The first audit step is verifying the box is unchecked and that ChatGPT-User, OAI-SearchBot², and PerplexityBot³ can all reach the session-type and gallery pages the studio wants cited.

The second filter is passage shape. AI engines prefer pages where the first 134-167 words under each H2 directly answer the section's question without requiring a click. A portrait session-type page targeting "newborn photographer Brooklyn in-home" should open with a bolded passage stating the named session type, the neighbourhood and city, the location modifier (in-home), the principal photographer, the typical age window, and one specific approach detail. Below the lead the page expands with the session timeline, fee range, gallery cross-link, and recent featured posts. The lead is what the engine quotes; the expansion is what the engine reads to confirm the page is real.

The contrast with a directory profile is the strategic point. A directory profile is field-driven and front-end-filtered — name, session tags, style tags, a short bio, a few photos. AI engines can read all of it, but they cannot extract a fluent passage from a tag set. A Squarespace session-type page that puts the same information into a 134-167 word answer-first lead reads as a citable passage and the engine quotes it; the same information distributed across a directory's profile fields reads as a database row and the engine cites the directory instead.

Three details inside the example matter for AI citation. Specific named-session vocabulary ("in-home newborn", "fresh-48 hospital sessions") — not "newborn photography" alone. Specific neighbourhood and timing window ("first three weeks after birth", "Cobble Hill", "Park Slope") — not "Brooklyn area, post-newborn period". Named credential (PPA Certified Professional Photographer) — not "professional photographer". The engines reward this specificity because the parent's query asked for it, and the page that supplies it directly is the page the engine has the highest confidence quoting.

The knowsAbout property⁴ on a Person schema accepts a freeform array of subjects the person is knowledgeable about. AI engines read it as the canonical list of session types and styles a photographer is known for. The discipline that makes the array work is honesty: list the session types the studio has actually shipped sessions in, not the session types the studio aspires to. A studio that shoots 60 newborn sessions, 40 family sessions, and 10 maternity sessions per year lists those three — In-Home Newborn Photography, Outdoor Family Photography, Maternity Photography — not the full glossary. The engine reads the array against the session-type pages, finds matching content, and the citation graph closes.

 <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Person", "@id": "https://yourstudio.com/#photographer", "name": "Robin Marsh, CPP", "jobTitle": "Family & Newborn Photographer", "url": "https://yourstudio.com/about/", "worksFor": { "@type": "LocalBusiness", "name": "Marsh Hill Studio" }, "hasCredential": "PPA Certified Professional Photographer", "knowsAbout": [ "In-home newborn photography", "Outdoor family photography", "Milestone child photography", "Fresh 48 hospital sessions", "Maternity photography", "Brooklyn brownstone interiors" ], "sameAs": [ "https://www.instagram.com/marshhillstudio", "https://www.ppa.com/find-a-photographer/marsh-hill-studio" ] } </script> 

The sameAs links matter. AI engines use them to disambiguate one named photographer from another, and a photographer with Instagram plus a PPA Find-a-Photographer profile is significantly easier to confidently attribute than an anonymous name on a single domain. The PPA Find-a-Photographer link is the highest-leverage one because it functions as a verification path confirming the photographer is a real listed professional with a credential, which is the confidence signal AI engines reward most. The Instagram link adds a corroborating visual feed the engines can cross-reference.

The mechanism. The Squarespace Gallery Section⁶ renders each image with a configurable caption (output as <figcaption>) and an alt-text field (output as the image's alt attribute). AI engines and Google's image search both read the alt attribute as the description of the image, and Perplexity in particular weights the caption text heavily when deciding whether to return an image-rich citation card for a session-type query. A gallery with empty alt text is invisible to image search; a gallery with descriptive alt text — naming session type, neighbourhood, and approximate age in each string — surfaces on image-flavoured queries that no text-only page can answer.

The ImageObject schema⁵ is the layer above. Squarespace does not auto-emit ImageObject on Gallery Sections, but a Code Injection block on the gallery page can add one ImageObject node per featured image with contentUrl, caption, creditText, copyrightHolder, and contentLocation. The combination — populated alt text and captions in the Squarespace UI, plus ImageObject JSON-LD on the three or four featured images per gallery — is what graduates a portrait gallery from "visible to Google Images" to "citable by ChatGPT and Perplexity on session-type queries". The full pattern is in the schema pillar; the portrait-specific application is the install layer above.

The query list is the leverage. Generic queries ("family photographer Brooklyn", "newborn photographer near me") are easy to track but unlikely to move; session-type + location queries ("in-home newborn photographer Brooklyn", "outdoor family photographer Asheville fall", "fresh-48 hospital photographer Park Slope") are harder to track because they require specific phrasing — but those are the queries where citation movement actually shows up. The right list mixes one or two broader queries with eight to twelve session-stacked queries the studio genuinely wants to be the answer for. Update the list quarterly as the studio's session mix evolves.