AI Visibility for Wedding Vendors: Getting Prices, Travel Areas and Availability Right

Couples use AI assistants the way they once used a directory search plus a group chat. The questions are specific: a budget, a date, a place, a style. These examples are hypothetical but realistic for photographers, planners and florists:

• "Best documentary-style wedding photographers in Asheville under $4,000"
• "Does [photographer name] travel to destination weddings in Italy, and what do they charge for travel?"
• "Full-service wedding planner in Austin for a 150-guest October 2027 wedding, typical fee?"
• "What's included in [planner name]'s day-of coordination package?"
• "Wedding florists near Napa who do large ceremony arches and are still booking June 2027"
• "Compare [florist A] and [florist B] for a flower budget around $5,000"
• "Which Denver wedding florists use locally grown flowers?"

Each prompt carries a price ceiling, a travel question, a date or a package detail. Those are the facts engines most often get wrong. The engine also doesn't send the couple's words straight to search. OpenAI says ChatGPT search typically rewrites a query into one or more targeted queries. So you can't optimize for one exact phrasing. You can make sure the underlying facts are stated where an engine can fetch them.

Each engine reaches the web through its own crawler or index. Treat each one as a separate check.

Google states there are no additional technical requirements for AI Overviews or AI Mode beyond indexing and snippet eligibility. Health on one engine says nothing about another. In Otterly's 2026 experiment, Google deindexed two AI-generated test sites and its AI features almost never cited them. Bing kept both sites, and Copilot kept citing them. That was one pair of low-stakes sites, but the mechanism is plain: an engine can't cite a page its index doesn't hold. As of October 2026, check each engine on its own.

Wedding facts change every season. AI answers draw on sources of very different ages.

• Training data. When an engine answers without searching, it relies on what the model learned before its cutoff. OpenAI lists an August 31, 2025 knowledge cutoff for the Instant model path ChatGPT uses for some answers. Last year's collection prices can live on there, and nothing you publish today reaches that answer.
• Stale third-party profiles. A directory listing with a three-year-old starting price is still a fetchable page. An engine may quote it.
• Prices behind an inquiry form. Many planners and photographers only say "contact for pricing". With no number on your site, the engine fills the gap from somewhere else.
• Contradictions on your own site. A 2023 blog post says packages start at $2,800, the pricing page says $3,500, and an old FAQ says travel is free statewide. The engine has three answers to choose from.
• Availability is live data. No engine can see your calendar. If your booking status isn't in text, assistants answer from old reviews or say nothing useful.

You can't edit a model's training data or decide which source an engine picks. You can remove the gaps and conflicts that hand it wrong material.

Photographer and florist sites are portfolios first. That's right for couples and a problem for crawlers. A price list designed as a graphic, a travel map, or a downloadable pricing guide gives a text crawler no sentence to quote.

JavaScript is the bigger risk. Many portfolio templates load galleries, pricing tabs and FAQ accordions with scripts. Vercel's crawler study found that ChatGPT and Claude crawlers fetch JavaScript files but don't execute them, so they can't read client-side rendered content. Googlebot does render JavaScript. That's how a site can look fine in Google and be blank to other AI crawlers.

Put these in plain HTML text, on a page that loads without scripts:

1. Starting price per package, with the year: "2027 wedding collections start at $3,200."
2. What each package includes, in hours, people and deliverables.
3. Service area and travel policy: "No travel fee within 60 miles of Charleston. Destination weddings quoted separately."
4. Booking status with a date: "As of October 2026, we're booking 2027 dates. 2026 is full."
5. Vendor type and style in one line: "Full-service planner for 50 to 200 guest weddings in Central Texas."

Stating a specific fact on a fetchable page gives an engine a sentence it can quote. It's the only positive on-page signal in the evidence, and it guarantees nothing. To test, open the page source (not the rendered page) and search for your price. If it isn't there, many AI crawlers won't see it either.

For local vendors, engines often answer from pages about you rather than your own site. The evidence shows a strong association between being named on the sites engines cite and appearing in answers, with no promised effect. Wedding vendors usually have more of these pages than most businesses.

Audit these, oldest first:

• Wedding directories and marketplaces where you have or had a profile. Check starting price, service area, vendor category, and whether it still advertises a booking year that has passed.
• Venue preferred-vendor lists. Venues often keep lists for years. Ask them to update your details or remove an old business name.
• Review platforms and your map listing. A review saying "she charged us $2,000 in 2021" is fetchable text. Reply publicly with current information where the platform allows it.
• Styled shoots and real wedding features on blogs, which often carry an outdated name or location.
• Forgotten profiles: a previous business name, a second-shooter collective, a closed studio address.

The rule: every live profile should state the same price floor, area and category as your site. Close the profiles you can't keep current, because each one is a possible source of wrong answers.

These checks have the strongest evidence. They work by removing blocks.

• robots.txt, bot by bot. OpenAI says each crawler setting is independent: blocking GPTBot stops training use, while OAI-SearchBot controls ChatGPT search. A blanket AI block often removes search eligibility by accident. The comparison of training crawlers vs search crawlers lists the bots by vendor.

User-agent: OAI-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

• Firewall and CDN. OpenAI says eligibility means allowing OAI-SearchBot and confirming your host or CDN allows its published IP addresses. A firewall can return 403 to a crawler your robots.txt welcomes. On Cloudflare, review the AI crawler settings: from 15 September 2026, Training and Agent crawlers are blocked by default on ad-displaying pages for new domains and free-tier accounts, with Search allowed. The AI Crawler Checker requests a page as each AI crawler and shows which ones get turned away.
• Snippet controls. noindex, nosnippet, max-snippet:0 and data-nosnippet keep content out of AI answers on Google and Bing. Templates sometimes apply them by accident.
• Website builders. Portfolio platforms manage robots.txt and rendering for you. Check what they actually publish.

Say you run a hypothetical wedding photography studio in Charleston. This month covers what's in your control.

Week 1: access. Read your robots.txt for OAI-SearchBot, PerplexityBot, Claude-SearchBot, Googlebot and Bingbot. Test for firewall blocks. Confirm your key pages are indexed in Google Search Console and Bing Webmaster Tools, separately.

Week 2: facts in text. Build one plain-HTML packages page with starting prices, inclusions, service area, travel policy and booking status, each dated. Update or remove old posts that state different prices.

Week 3: third-party cleanup. List every directory, venue list, review site and feature that names you. Fix the most visible five. Close what you can't maintain.

Week 4: check the answers. Ask each engine five couple-style prompts, logged out. Record which facts are wrong and which source each engine cited. The free checker on this site runs up to three buyer questions as a snapshot. Repeat monthly, because answers vary by query and by day.

Before hiring help, read whether a small business needs an AI search service and whether you need an expert at all. Treat anyone promising citations the way you'd treat GEO case studies with big gains: ask what was measured.