DEV Community: Gyubin Kim

Why Couples Find Another Wedding Photographer When They Ask AI (and How to Fix It, 2026)

Gyubin Kim — Sat, 06 Jun 2026 04:58:14 +0000

Series: Getting Cited by AI — Post #10 (niche deep-dive: wedding photographers & planners). #1: Get Cited by ChatGPT → · #2: Why AI Recommends Your Competitor → · #3: Copy-Paste Schema Templates → · #4: Is Your Site Blocking AI Crawlers? → · #5: Reviews & AggregateRating →

A newly-engaged couple opens ChatGPT or Perplexity and types: "best wedding photographer in [city]" or "documentary wedding photographer near [venue], under $4k." The assistant names three studios, links two, and the couple sends two inquiry forms before they've scrolled a single Instagram feed. If you're not one of those three, you didn't lose on style or price — you lost because the model couldn't read your site well enough to quote you.

This is the general series (#1–#5) applied specifically to wedding photography (and the planners next door), because wedding sites have three quirks that make them especially invisible to AI: galleries that are 100% images, "inquire for pricing" with nothing typed, and testimonials trapped as screenshots.

Honest caveat first: doing everything below does not guarantee a citation, and there's no fixed timeline for when assistants pick up changes. What it does is remove the specific, fixable reasons a photographer gets skipped. No bookings or rankings are promised here — only that the machine can finally read what your couples already love about you.

The three reasons wedding photographers go invisible

1. The site is a gallery, not a page.
Most photographer homepages are a full-bleed slideshow and a logo — gorgeous to a human, nearly empty to a crawler. The model lands on your domain, finds image files and a "Contact" link, and has almost no text to understand your style, your city, your venues, or your packages. A stunning gallery the machine can't parse is, to an answer engine, a blank page.

2. "Inquire for pricing" tells the model nothing.
Couples ask AI very budget-specific questions — "wedding photographer in [city] under $3,500," "how much does an 8-hour wedding package cost." If your site never types out even a starting range ("collections begin at $3,200"), the assistant can't match you to that query and quotes whoever did publish a range. You don't have to post a full price list — you have to be quotable.

3. There's nothing answer-shaped.
Couples ask machines specific questions — "do you travel," "how many photos do we get," "how long until we see our gallery," "do you shoot film or digital," "second shooter included?" If your site never answers those in plain text, the model grabs the answer (and the citation) from a competitor's FAQ or a generic wedding-blog listicle instead of you.

None of these are talent problems. They're readability problems — and readability is fixable in an afternoon, without touching your photography.

The 10-minute wedding-photographer visibility check

Run this on your own site before changing anything:

View source on your homepage (right-click → View Page Source) and Ctrl-F for your city or your style, e.g. Nashville or documentary. If your own city isn't in the page text, the crawler has little to localize you with.
Find your packages as plain text. Is there a real /pricing or /investment page with typed-out collections and at least a starting range, or is it a single "inquire" button and a contact form?
Search the actual question. Open Perplexity and ask "wedding photographer in [your city] for [your style]" — are you named? Who is? Read their page; it's almost always more text-readable, not more talented.
Check the schema. Paste your URL into any schema validator. Most photographer sites have nothing, or a generic WebSite tag — not a LocalBusiness/ProfessionalService with service area, services, and hours.
Check crawler access (see #4) — Squarespace, Showit, and some gallery/security plugins can block AI user-agents by default.

Anything that fails is on the fix list below, roughly in priority order.

The fixes (highest leverage first)

Fix 1 — Turn your galleries into pages with words

Keep the images — just stop letting them be the only content. Give each signature wedding a short text intro: the venue name, the city, the season, the vibe ("a fall elopement at [venue], [city]"). Now the model has real, quotable text tying you to venues and locations couples actually search. This single change does more than any schema tag, because it gives the assistant something to read.

Fix 2 — Publish a starting range and what's included

Add a /investment page that types out your collections in plain text: a starting price ("collections begin at $3,200"), hours of coverage, whether a second shooter and engagement session are included, and turnaround time. You control the numbers; you just have to make them text. This is the single biggest reason budget-qualified couples never reach you through AI.

Fix 3 — Answer the questions couples actually ask

Add a short FAQ in real text — the ones you answer in every consult:

Do you travel / what's your service area? Any travel fee?
How many edited images do we receive?
How long until we get our full gallery?
Is a second shooter included?
Do you shoot film, digital, or both?
How far in advance should we book?

Plain, accurate answers. This is exactly the content assistants love to quote because it is the answer.

Fix 4 — Make your reviews machine-readable

You almost certainly have real reviews on Google, The Knot, or WeddingWire. Surface a few as text on the site and, only if the numbers are true, mark them up (see #5). Real numbers only — a rating in your markup that doesn't match your public profiles gets your whole markup discounted. Never invent a rating or a review.

Fix 5 — Confirm the crawlers are allowed

If your site builder or a security/SEO plugin blocks GPTBot, OAI-SearchBot, PerplexityBot, or ClaudeBot, none of the above matters. #4 walks the check.

Copy-paste schema for a wedding photographer

Drop this in your homepage <head>, replacing every placeholder with your real values. Don't ship a field you can't verify — delete it instead of guessing.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "additionalType": "https://schema.org/Photograph",
  "name": "YOUR STUDIO NAME",
  "description": "Wedding photographer serving CITY and REGION — documentary/editorial coverage, travel available.",
  "url": "https://yourstudio.com",
  "telephone": "+1-555-555-5555",
  "image": "https://yourstudio.com/sample-wedding.jpg",
  "priceRange": "$$$",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "CITY",
    "addressRegion": "ST",
    "addressCountry": "US"
  },
  "areaServed": [
    { "@type": "City", "name": "CITY" },
    { "@type": "AdministrativeArea", "name": "REGION / STATE" }
  ],
  "knowsAbout": ["wedding photography", "elopements", "engagement sessions"],
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Collections",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Full-day wedding coverage" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Elopement / micro-wedding" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Engagement session" } }
    ]
  }
}
</script>

Pair it with an FAQPage block built from your real answers (template in #3). Together they cover who/where/what you offer and the questions couples ask — the two things assistants need to cite you with confidence.

A note for planners: the same three fixes apply, with one swap — your "quotable" content is your vendor knowledge and venue coverage, not packages. Type out the venues, regions, and wedding sizes you handle, and answer "what does a planner cost / what's the difference between full and partial planning" in plain text. Use @type": "ProfessionalService" with areaServed and an FAQ. Couples ask AI for planners exactly the way they ask for photographers.

Priority order, if you only do three things

Words on your galleries (Fix 1) — venue + city + vibe as text the model can quote.
A starting range with what's included (Fix 2) — so budget-qualified couples can be matched to you.
ProfessionalService + FAQPage schema (Fix 3) — label it so the machine is sure.

Everything else (reviews markup, crawler access) compounds on top, but those three are where an invisible studio becomes a readable one.

FAQ

My work speaks for itself — isn't great photography enough?
For a human who already found you, yes. But an AI assistant choosing who to name can't see your photos the way a couple does; it reads text. Give it words about your style, venues, and packages and you become quotable. The photography still closes the booking — this just gets you into the shortlist.

Do I have to post my full price list?
No. A single honest starting line ("collections begin at $3,200") is enough to get matched to budget queries. The goal is a quotable range, not a public menu.

Will this get me into ChatGPT's answers?
It makes you eligible and readable, which is the part you control. No one can guarantee a citation or a timeline — anyone who does is overselling. This removes the fixable reasons you're skipped; pickup still depends on the assistant.

Is it okay to mark up reviews if they're real but I'm not sure of the exact count?
Use only numbers you can verify against your public Google/The Knot/WeddingWire profiles. A mismatch discounts your entire markup. See #5.

Two ways to act on this:

🔎 Free, no-strings: send your site URL to faithpath25@gmail.com with the subject "GEO snapshot" — I'll send back a 1-page read of exactly what AI assistants can and can't currently see on your site, plus the specific fixes. Free pilot, wherever you operate; if it's useful, a short review is all I ask.

🧰 Do it yourself: the copy-paste schema kits, checklists, and the full GEO audit live at SprintLanding → (includes a free starter). Prices in USD; Gumroad converts to your local currency at checkout.

Why ChatGPT Sends Clients to Another Trainer or Coach — Not You (2026)

Gyubin Kim — Sat, 06 Jun 2026 04:52:52 +0000

Series: Getting Cited by AI — Post #9 (niche deep-dive: personal trainers, gyms, fitness studios, and 1:1 coaches). #1: Get Cited by ChatGPT → · #2: Why AI Recommends Your Competitor → · #3: Copy-Paste Schema Templates → · #4: Is Your Site Blocking AI Crawlers? → · #5: Reviews & AggregateRating → · #6: Med Spas → · #7: Real Estate → · #8: Local Trades →

Someone who just decided to get in shape opens ChatGPT or Perplexity and types: "best personal trainer near [city] for weight loss?" or "strength coach in [neighborhood] who takes beginners?" or "online running coach for a first marathon?" The assistant names two or three options and links one. If you're not on that list, it's rarely because your coaching is worse — it's because the model couldn't read who you train, what you specialize in, where (or whether) you work online, and whether anyone trusts you from your site.

This post applies the general series (#1–#5) specifically to trainers, gyms, studios, and 1:1 coaches, because fitness and coaching sites share three quirks that make them especially invisible to AI: a homepage built around photos and a "Book a Free Consult" button, no plain-text statement of who you help and how, and zero answer-shaped content for the very specific questions prospects actually type.

Honest caveat first: doing everything below does not guarantee a citation, and there's no fixed timeline for when assistants pick changes up. What it does is remove the specific, fixable reasons a coach gets skipped. No new clients, rankings, or sign-ups are promised here — only that the machine can finally read who you train and what you do.

The three reasons fitness & coaching sites go invisible

1. The homepage is photos and a "Book Now" button — not readable content.
A lot of trainer and studio sites lead with transformation photos, a video loop, and a big CTA. That can move a human who already trusts you, but to a crawler it's images and a booking link. Your specialties, your training style, your client types, your location or online availability, your certifications — the facts an AI needs to recommend you — live inside images or aren't in text at all. The model lands, finds nothing quotable, and recommends a coach whose homepage spells it out.

2. Who you help and how isn't in plain text.
"Transform your life" and "unlock your potential" tell a machine nothing. Answer engines cite specifics: what you specialize in (weight loss, strength, postpartum, marathon prep, mobility, senior fitness), who you work with (beginners, athletes, busy professionals), format (in-person at [studio/city], online/remote, hybrid), and how sessions work (1:1, small group, programming-only). If those aren't in plain text, the model can't match you to "online beginner strength coach" — so it picks whoever did write it down.

3. There's nothing answer-shaped.
Prospects ask machines very specific things — "how much does a personal trainer cost in [city]," "do online coaches actually work for beginners," "how often should I train to lose weight," "do you offer a free consultation." If your site never answers those in plain text, the AI grabs the answer (and the citation) from a national directory, a big-box gym, or the coach who wrote a real FAQ.

None of these are ranking problems. They're readability problems — and readability is fixable in an afternoon, usually without touching your design or your booking flow.

The 10-minute fitness/coaching visibility check

Run this on your own site before changing anything:

View source on your homepage and search (Ctrl+F) for your specialty and your city — the actual words "weight loss" / "strength" / "marathon" / "online coaching" and your location. If they only live in a photo or video, or aren't there at all, a crawler can't see them.
Read your site as a machine would. Is there a plain-text statement of who you help, what you specialize in, and whether you work in-person, online, or both? Or just a gallery and a "Start Now" button?
Search your site for a real prospect question — "cost," "consultation," "beginner," "online," "how often." Any plain-text answers? Or only a booking widget?
Check your trust facts. Are your certifications (NASM, ACE, CSCS, RYT, etc.), years coaching, client results stated honestly, and reviews in text on the page — or buried in images or pulled silently from Instagram/Google? (See #5.)
Confirm crawlers aren't blocked. A quick robots.txt / meta-robots check (see #4) — some site builders (and Linktree-style link pages) leave almost nothing for a crawler to read.

If you failed 2 or more, that's why you're not in the AI's short list — and it's all fixable text, not a rebuild.

The priority fixes (in order)

Fix #1 — Put who you help and how, in plain text on the homepage. A short, scannable block a machine can quote:

"[Name] is a [certification]-certified [personal trainer / strength coach] in [City] working with [beginners and busy professionals] on [weight loss and strength]. Sessions are [1:1 in-person at [studio] and online worldwide]. [Free intro consultation]."
Specifics beat slogans every time. If you coach online only, say so explicitly and name it — "online coaching, clients anywhere" — so you're not silently filtered out of local-only or remote-only queries.

Fix #2 — Add a plain-text FAQ answering the 5 questions prospects actually ask. Typical cost or package range, whether you offer a free consultation, who it's right for (beginner-friendly?), in-person vs. online, and how often clients train. Two or three honest sentences each, in text — not an image, not a PDF.

Fix #3 — Add the right schema — HealthClub or SportsActivityLocation for a studio/gym, or Person + ProfessionalService for a solo coach — so the machine can label what you do and where (template below).

Fix #4 — Surface reviews and honest results as on-page text with AggregateRating, not just an Instagram highlight or a screenshot (#5). Keep client outcomes truthful and non-guaranteeing.

Fix #5 — Make sure crawlers can reach it all (#4).

Do #1 and #2 even if you do nothing else. Most coaching sites have neither, so a plain statement of who-you-help plus a real FAQ is often the single biggest readability win.

Copy-paste schema for a trainer, studio, or coach

Fill every bracket with verified values from your own site. Use HealthClub or SportsActivityLocation for a physical gym/studio; use the Person + ProfessionalService shape for a solo or online coach. Delete any field you can't confirm — never ship a placeholder or an invented number.

{
  "@context": "https://schema.org",
  "@type": "HealthClub",
  "name": "[Studio / Coach Name]",
  "image": "[https://yoursite.com/photo.jpg]",
  "url": "[https://yoursite.com]",
  "telephone": "[+1-555-555-5555]",
  "email": "[you@yoursite.com]",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street]",
    "addressLocality": "[City]",
    "addressRegion": "[Region/State/Province]",
    "postalCode": "[Postcode/ZIP]",
    "addressCountry": "[your ISO country code, e.g. GB/AU/CA/SG/IN]"
  },
  "areaServed": ["[City]", "Online — clients anywhere"],
  "openingHours": "[Mo-Fr 06:00-20:00]",
  "priceRange": "[$$]",
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Coaching Services",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "[1:1 Personal Training]" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "[Online Coaching]" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "[Small-Group Strength]" } }
    ]
  }
}

And a FAQPage block for the prospect questions (answers in plain text, kept truthful and current):

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer a free consultation?",
      "acceptedAnswer": { "@type": "Answer", "text": "[Honest answer for your business.]" }
    },
    {
      "@type": "Question",
      "name": "Do you work with beginners?",
      "acceptedAnswer": { "@type": "Answer", "text": "[Honest answer — who you're a good fit for.]" }
    },
    {
      "@type": "Question",
      "name": "Do you coach online or only in person?",
      "acceptedAnswer": { "@type": "Answer", "text": "[In-person at [City], online, or both — stated plainly.]" }
    }
  ]
}

Compliance note: fitness and health coaching carry real claim risks. Keep results honest and individual ("results vary"), don't promise specific weight-loss numbers or outcomes, only list certifications you actually hold, and avoid medical or rehab claims unless you're licensed for them. Schema describes what's already true on the page — it is not a place to inflate anything.

What this is and isn't

This removes the readability reasons an AI skips your fitness or coaching site. It does not guarantee you'll be cited, doesn't promise new clients, sign-ups, or a timeline, and won't outweigh a genuinely thin track record. But most coaching sites fail the basics — who you help and how in text, in-person vs. online stated plainly, a real FAQ, honest results, and clean schema — so fixing them is often the difference between "the model couldn't read me" and "the model can finally recommend me to the client I'm actually best for."

Two ways to act on this:

Why ChatGPT Recommends a Different Roofer (or Plumber) Than You (2026)

Gyubin Kim — Sat, 06 Jun 2026 04:47:31 +0000

Series: Getting Cited by AI — Post #8 (niche deep-dive: local trades — roofing, plumbing, HVAC, electrical). #1: Get Cited by ChatGPT → · #2: Why AI Recommends Your Competitor → · #3: Copy-Paste Schema Templates → · #4: Is Your Site Blocking AI Crawlers? → · #5: Reviews & AggregateRating → · #6: Med Spas → · #7: Real Estate →

A homeowner with a leak opens ChatGPT or Perplexity and types: "who's a good roofer near [city] for storm damage?" or "emergency plumber in [neighborhood] open now?" The assistant names two or three companies, links one, and the homeowner calls it. If you're not on that short list, it's usually not because your work is worse — it's because the model couldn't confidently read what you do, where you do it, and whether you're trustworthy from your site.

This post applies the general series (#1–#5) specifically to the trades, because roofing, plumbing, HVAC, and electrical sites share three quirks that make them especially invisible to AI: a homepage that's a phone number and a hero image, no plain-text list of services and service area, and zero answer-shaped content for the urgent questions homeowners actually type.

Honest caveat first: doing everything below does not guarantee a citation, and there's no fixed timeline for when assistants pick changes up. What it does is remove the specific, fixable reasons a contractor gets skipped. No rankings, leads, or call volume are promised here — only that the machine can finally read what you do and where.

The three reasons trades sites go invisible

1. The homepage is a hero image and a "Call Now" button — not readable content.
A lot of contractor sites lead with a full-bleed photo, a logo, and a giant phone number. That converts a human who already found you, but to a crawler it's an image and a tel: link. Your services, your trades, your towns, your license number, your hours — the facts an AI needs to recommend you — live in the photo or aren't on the page at all. The model lands, finds nothing quotable, and moves on to a competitor whose homepage spells it out in text.

2. Services and service area aren't in plain text.
"Quality work you can trust" tells a machine nothing. Answer engines cite specifics: which trades (roof repair, re-roof, gutters / drain cleaning, water heaters, repipe / AC install, furnace repair), which towns / postcodes / service areas, emergency vs. scheduled, residential vs. commercial, licensed/insured/bonded. If those aren't in plain text a crawler can read, the model can't match you to "emergency roofer in [town]" — so it picks whoever did list it.

3. There's nothing answer-shaped.
Homeowners ask machines very specific things — "how much does a roof replacement cost in [area]," "how long does a water heater install take," "do you charge for estimates," "signs I need a new boiler/furnace." If your site never answers those in plain text, the AI grabs the answer (and the citation) from a national aggregator (Angi, Checkatrade, hipages, and the like) or the competitor who wrote a real FAQ.

None of these are ranking problems. They're readability problems — and readability is fixable in an afternoon, usually without touching your design.

The 10-minute trades visibility check

Run this on your own site before changing anything:

View source on your homepage and search (Ctrl+F) for your trade and your towns — the actual words "roof repair" / "drain cleaning" / "AC install" and your city / area names. If they only live in the hero image or aren't there at all, a crawler can't see them.
Read your site as a machine would. Is there a plain-text list of services and the towns you cover? Or just a photo gallery and a contact form?
Search your site for a real homeowner question — "cost," "estimate," "how long," "emergency." Any plain-text answers? Or only a "Request a Quote" button?
Check your trust facts. Are your license number, "licensed & insured," years in business, and reviews in text on the page — or buried in an image or pulled silently from Google? (See #5.)
Confirm crawlers aren't blocked. A quick robots.txt / meta-robots check (see #4) — some site builders and security plugins quietly block AI crawlers.

If you failed 2 or more, that's why you're not in the AI's short list — and it's all fixable text, not a rebuild.

The priority fixes (in order)

Fix #1 — Put your services and service area in plain text on the homepage. A short, scannable block a machine can quote:

"[Company] provides [roof repair, re-roofing, and gutter installation] for homeowners in [Town A, Town B, Town C] since [year]. Licensed & insured ([license #]). Free estimates. Emergency service available."
Specifics beat slogans every time.

Fix #2 — Add a plain-text FAQ answering the 5 questions homeowners actually ask. Do you charge for estimates, typical cost range for your most common job, how long it takes, emergency availability, and warranty. Two or three honest sentences each, in text — not a downloadable PDF, not an image.

Fix #3 — Add the right LocalBusiness subtype schema (RoofingContractor, Plumber, HVACBusiness, or Electrician) so the machine can label what you do and where (template below).

Fix #4 — Surface reviews as on-page text with AggregateRating, not just a Google badge or a screenshot (#5).

Fix #5 — Make sure crawlers can reach it all (#4).

Do #1 and #2 even if you do nothing else. Most contractor sites have neither, so plain services + service area + a real FAQ is often the single biggest readability win.

Copy-paste schema for a trades business

Fill every bracket with verified values from your own site. Pick the @type that matches your trade — RoofingContractor, Plumber, HVACBusiness, or Electrician. Delete any field you can't confirm — never ship a placeholder or an invented number.

{
  "@context": "https://schema.org",
  "@type": "RoofingContractor",
  "name": "[Company Name]",
  "image": "[https://yoursite.com/photo.jpg]",
  "url": "[https://yoursite.com]",
  "telephone": "[+1-555-555-5555]",
  "email": "[you@yoursite.com]",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street]",
    "addressLocality": "[City]",
    "addressRegion": "[Region/State/Province]",
    "postalCode": "[Postcode/ZIP]",
    "addressCountry": "[your ISO country code, e.g. GB/AU/CA/SG/IN]"
  },
  "areaServed": ["[Town 1]", "[Town 2]", "[Town 3]"],
  "openingHours": "[Mo-Fr 08:00-17:00]",
  "priceRange": "[$$]",
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Services",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "[Roof Repair]" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "[Roof Replacement]" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "[Gutter Installation]" } }
    ]
  }
}

And a FAQPage block for the homeowner questions (answers in plain text, kept truthful and current):

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you charge for estimates?",
      "acceptedAnswer": { "@type": "Answer", "text": "[Honest answer for your business.]" }
    },
    {
      "@type": "Question",
      "name": "How long does a [roof replacement] take?",
      "acceptedAnswer": { "@type": "Answer", "text": "[Typical timeline, honestly stated.]" }
    }
  ]
}

Compliance note: the trades are licensed and regulated. Keep claims truthful, only state "licensed & insured" and a licence/registration number that are real and current, follow your local contractor licensing and advertising rules, and don't promise prices or outcomes you can't substantiate. Schema describes what's already true on the page — it is not a place to inflate anything.

What this is and isn't

This removes the readability reasons an AI skips your trades site. It does not guarantee you'll be cited, doesn't promise leads or call volume or a timeline, and won't outweigh a genuinely thin reputation. But most contractor sites fail the basics — services and towns in text, a real FAQ, honest trust facts, and clean schema — so fixing them is often the difference between "the model couldn't read me" and "the model can finally recommend me for the job I actually do."

Two ways to act on this:

Why Buyers Find Your Competitor (Not You) When They Ask AI About Real Estate (2026)

Gyubin Kim — Sat, 06 Jun 2026 04:42:10 +0000

Series: Getting Cited by AI — Post #7 (niche deep-dive: real estate agents & brokerages). #1: Get Cited by ChatGPT → · #2: Why AI Recommends Your Competitor → · #3: Copy-Paste Schema Templates → · #4: Is Your Site Blocking AI Crawlers? → · #5: Reviews & AggregateRating → · #6: Med Spas →

A buyer relocating to your city opens ChatGPT or Perplexity and asks: "who's a good real estate agent in [city] for first-time buyers?" or "which agent in [neighborhood] knows the apartment market?" The assistant names two or three agents, links one, and the buyer reaches out. If you're not in that shortlist, it usually isn't because you're worse — it's because the model couldn't confidently read who you are or what you specialize in.

This post applies the general series (#1–#5) specifically to real estate, because agent and brokerage sites have three quirks that make them especially invisible to AI: IDX/MLS widgets that swallow the homepage, agent bios that say nothing quotable, and zero answer-shaped content for the questions buyers and sellers actually type.

Honest caveat first: doing everything below does not guarantee a citation, and there's no fixed timeline for when assistants pick changes up. What it does is remove the specific, fixable reasons an agent gets skipped. No rankings, leads, or commissions are promised here — only that the machine can finally read who you serve and how.

The three reasons real estate sites go invisible

1. The homepage is an IDX search widget, not a page.
Most agent sites lead with a full-width MLS/IDX property search (iHomefinder, Showcase IDX, a brokerage iframe). That's useful for humans browsing listings, but to a crawler it's a search box and a script — your name, your market, your specialties, and your service area live inside a third-party widget the model often can't read. The AI lands on your domain, finds listings that belong to the whole MLS, and learns nothing specific about you.

2. The agent bio is a vibe, not a fact sheet.
"Passionate about helping families find their dream home" tells a machine nothing it can quote. Answer engines cite specifics: years in the market, neighborhoods covered, languages spoken, buyer-vs-seller focus, condo vs. luxury vs. first-time. If those facts aren't in plain text, the model can't match you to "agent for first-time buyers in [neighborhood]" — so it picks whoever did spell it out.

3. There's nothing answer-shaped.
Buyers and sellers ask machines very specific questions — "how much are the costs to buy in [area]," "what are the property/transfer taxes in [area]," "is now a good time to sell an apartment in [city]," "how long does the purchase process take." If your site never answers those in plain text, the model grabs the answer (and the citation) from a national property portal (Zillow, Rightmove, realestate.com.au, and the like) or a competitor who did.

None of these are ranking problems. They're readability problems — and readability is fixable in an afternoon.

The 10-minute real-estate visibility check

Run this on your own site before changing anything:

View source on your homepage and search (Ctrl+F) for your service area and specialty — the actual city/neighborhood names and "first-time buyers" / "luxury" / "condos." If they only appear inside the IDX widget's script, a crawler probably can't see them.
Read your bio as a machine would. Does it state, in text, how many years you've worked the market, which areas you cover, and who you focus on? Or is it adjectives?
Search your site for a real buyer/seller question — "costs to buy," "property tax," "how long does the process take." Any plain-text answers? Or only listings and a contact form?
Check your reviews. Are testimonials sitting in an image slider or pulled from a portal/Google with no text on your own pages? (See #5.)
Confirm crawlers aren't blocked. A quick robots.txt / meta-robots check (see #4) — IDX setups sometimes noindex large swaths of the site.

If you failed 2 or more, that's why you're not in the AI's shortlist — and it's all fixable text, not a rebuild.

The priority fixes (in order)

Fix #1 — Put your facts in plain text on the homepage and About page. A short, scannable block a machine can quote:

"[Name] is a licensed real estate agent serving [neighborhoods/city] since [year], focused on first-time buyers and condos. Speaks English and [language]. [N] homes closed in [area]."
Specifics beat adjectives every time.

Fix #2 — Add a plain-text FAQ answering the 5 questions buyers/sellers actually ask. Costs to buy in your area, property/transfer taxes for your area, typical timeline for the purchase process, buyer vs. seller process, and one local-market question. Two or three sentences each, in text — not a downloadable PDF.

Fix #3 — Add RealEstateAgent schema so the machine can label who and where you are (template below).

Fix #4 — Surface reviews as on-page text with AggregateRating, not just an embedded slider (#5).

Fix #5 — Make sure crawlers can reach it all (#4).

Do #1 and #2 even if you do nothing else. Most agent sites have neither, so plain facts + a real FAQ is often the single biggest readability win.

Copy-paste schema for a real estate agent

Fill every bracket with verified values from your own site. Delete any field you can't confirm — never ship a placeholder or an invented number.

{
  "@context": "https://schema.org",
  "@type": "RealEstateAgent",
  "name": "[Full Name or Team Name]",
  "image": "[https://yoursite.com/headshot.jpg]",
  "url": "[https://yoursite.com]",
  "telephone": "[+1-555-555-5555]",
  "email": "[you@yoursite.com]",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street]",
    "addressLocality": "[City]",
    "addressRegion": "[Region/State/Province]",
    "postalCode": "[Postcode/ZIP]",
    "addressCountry": "[your ISO country code, e.g. GB/AU/CA/SG/IN]"
  },
  "areaServed": ["[Neighborhood/City 1]", "[Neighborhood/City 2]"],
  "knowsLanguage": ["English"],
  "memberOf": { "@type": "Organization", "name": "[Brokerage Name]" }
}

And a FAQPage block for the buyer/seller questions (answers in plain text, kept truthful and current):

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How much are the costs to buy a home in [area]?",
      "acceptedAnswer": { "@type": "Answer", "text": "[Plain, accurate range/explanation for your market.]" }
    },
    {
      "@type": "Question",
      "name": "How long does it take to close on a home in [City]?",
      "acceptedAnswer": { "@type": "Answer", "text": "[Typical timeline, honestly stated.]" }
    }
  ]
}

Compliance note: real estate is regulated. Keep claims truthful, avoid promising prices, returns, or "best agent" superlatives you can't substantiate, and follow your local and brokerage real-estate advertising rules. Schema describes what's already true on the page — it is not a place to inflate anything.

What this is and isn't

This removes the readability reasons an AI skips your real estate site. It does not guarantee you'll be cited, doesn't promise leads or a timeline, and won't outweigh a genuinely thin reputation. But most agent sites fail the basics — facts in text, a real FAQ, and clean schema — so fixing them is often the difference between "the model couldn't read me" and "the model can finally match me to the right buyer."

Two ways to act on this:

Why Your Med Spa Doesn't Show Up in ChatGPT (and How to Fix It, 2026)

Gyubin Kim — Sat, 06 Jun 2026 04:36:49 +0000

Series: Getting Cited by AI — Post #6 (niche deep-dive: med spas & aesthetics). #1: Get Cited by ChatGPT → · #2: Why AI Recommends Your Competitor → · #3: Copy-Paste Schema Templates → · #4: Is Your Site Blocking AI Crawlers? → · #5: Reviews & AggregateRating →

A patient opens ChatGPT or Perplexity and types: "best med spa near me for Botox" or "where can I get a HydraFacial in [city]?" The assistant names three clinics, links two of them, and books a mental appointment. If your med spa isn't one of those three, you didn't lose on price or reviews — you lost because the model couldn't confidently read you.

This post is the general series (#1–#5) applied specifically to aesthetics clinics, because med spas have three quirks that make them especially invisible to AI: booking-widget homepages, service menus buried in images, and "before/after" galleries that say nothing a machine can quote.

Honest caveat first: doing everything below does not guarantee a citation, and there's no fixed timeline for when assistants pick changes up. What it does is remove the specific, fixable reasons a med spa gets skipped. No rankings or revenue are promised here — only that the machine can finally read what your front desk already knows.

The three reasons med spas go invisible

1. The homepage is a booking widget, not a page.
Most aesthetics sites lead with a full-screen "Book Now" embed (Vagaro, Boulevard, Mindbody, an iframe). That widget is great for humans and nearly empty to a crawler — the services, prices, and hours live inside a third-party script the model often can't read. The AI lands on your domain, finds a hero image and a button, and moves on.

2. The service menu is an image or a PDF.
"Botox $12/unit, Lip Filler from $650, Morpheus8 packages" — if that lives in a designed graphic or a downloadable price sheet, it's invisible as text. Answer engines quote text. A pretty menu the model can't parse is the same as no menu.

3. There's nothing answer-shaped.
Patients ask machines very specific questions — "how long does filler last," "is Botox safe while breastfeeding," "what's the downtime for a chemical peel." If your site never answers those in plain text, the model grabs the answer (and the citation) from a competitor or a generic health site instead of you.

None of these are ranking problems. They're readability problems — and readability is fixable in an afternoon.

The 10-minute med-spa visibility check

Run this on your own site before changing anything:

View source on your homepage (right-click → View Page Source) and Ctrl-F for one of your real services, e.g. Botox or HydraFacial. If it's not in the page text — only inside an iframe/widget — the crawler probably can't see it either.
Find your services as plain text. Is there a real /services or /pricing page with typed-out treatments and at least price ranges, or is it all images/PDF?
Search the actual question. Open Perplexity and ask "med spa in [your city] for [your top treatment]" — are you named? Who is? Read their page; it's usually more text-readable, not fancier.
Check the schema. Paste your URL into any schema validator. Most med spas have either nothing or a generic WebSite tag — not MedicalBusiness/HealthAndBeautyBusiness with services and hours.
Check crawler access (see #4) — booking platforms and security plugins sometimes block AI user-agents by default.

Anything that fails is on the fix list below, roughly in priority order.

The fixes (highest leverage first)

Fix 1 — Put your service menu on the page as text

Create or rewrite a /services page where every treatment is a typed heading with a one-line plain-text description and a price or an honest range ("Lip filler from $650"). Keep the booking widget — just stop letting it be the only source of truth. This single change does more than any schema tag, because it gives the model something quotable.

Fix 2 — Answer the five questions patients actually ask

Add a short FAQ in real text — five questions, two-to-three honest sentences each. Pick the ones your front desk answers on the phone all day:

How long does [Botox/filler] last?
What's the downtime for [your top treatment]?
Who performs the treatments (RN, NP, MD supervision)?
How much does [treatment] cost?
Is there a consultation, and is it free?

Plain, accurate answers. This is the content AI assistants love to quote because it is the answer.

Fix 3 — Add the right schema (copy-paste below)

Tell the machine, in its own language, what kind of business you are, where, when you're open, and what you offer. Med spas should use MedicalBusiness (or HealthAndBeautyBusiness) — not a generic LocalBusiness. Template in the next section.

Fix 4 — Make your reviews machine-readable

You almost certainly have real reviews on Google. Surface them as text on the site and, only if the numbers are true, mark them up (see #5). Real numbers only — a rating in your markup that doesn't match your public Google profile gets your whole markup discounted. Never invent a rating.

Fix 5 — Confirm the crawlers are allowed

If your booking platform or a security/SEO plugin blocks GPTBot, OAI-SearchBot, PerplexityBot, or ClaudeBot, none of the above matters. #4 walks the check.

Copy-paste schema for a med spa

Drop this in your homepage <head>, replacing every placeholder with your real values. Don't ship a field you can't verify — delete it instead of guessing.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalBusiness",
  "additionalType": "https://schema.org/HealthAndBeautyBusiness",
  "name": "YOUR MED SPA NAME",
  "description": "Medical spa offering injectables, facials, and skin treatments in CITY, STATE.",
  "url": "https://yourmedspa.com",
  "telephone": "+1-555-555-5555",
  "image": "https://yourmedspa.com/exterior.jpg",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "CITY",
    "addressRegion": "REGION",
    "postalCode": "00000",
    "addressCountry": "<your ISO country code, e.g. GB/AU/CA/SG/IN — don't ship unverified>"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 0.000000,
    "longitude": 0.000000
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "10:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "10:00",
      "closes": "16:00"
    }
  ],
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Treatments",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Botox / Neurotoxin" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Dermal Filler" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "HydraFacial" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Chemical Peel" } }
    ]
  }
}
</script>

Pair it with an FAQPage block built from your five real answers (template in #3). Together they cover who/where/when/what and the questions patients ask — the two things assistants need to cite you with confidence.

A note on medical claims: keep service descriptions factual and avoid outcome guarantees ("erases wrinkles permanently," "100% safe"). Aesthetics advertising is regulated, and overclaiming is both a compliance risk and exactly the kind of unverifiable language models discount. Accurate beats impressive.

Priority order, if you only do three things

Service menu as real text (Fix 1) — the model needs something to quote.
Five-question FAQ in plain text (Fix 2) — match the exact questions patients ask AI.
MedicalBusiness + FAQPage schema (Fix 3) — label it so the machine is sure.

Everything else (reviews markup, crawler access) compounds on top, but those three are where an invisible med spa becomes a readable one.

FAQ

My booking widget already shows my services. Isn't that enough?
For humans, yes. For crawlers, usually not — the content inside a third-party widget/iframe often isn't read as your page's text. Keep the widget; add a plain-text services page beside it.

Do I need to publish my exact prices?
No. Honest ranges ("from $650") are fine and still quotable. The goal is readable text, not a public price war.

Is marking up reviews I don't really have okay if they're positive?
No. Real numbers only, matching your public Google profile. A mismatch discounts your entire markup. See #5.

Two ways to act on this:

Reviews & AggregateRating: The Citation Multiplier AI Looks For (2026)

Gyubin Kim — Sat, 06 Jun 2026 04:31:27 +0000

Series: Getting Cited by AI — Post #5. Post #1: How to Get Cited by ChatGPT → · Post #2: Why AI Recommends Your Competitor → · Post #3: Copy-Paste Schema Templates → · Post #4: Is Your Site Blocking the AI Crawlers? →

By now you've got the crawler letting the bots in (Post #4), your facts labeled in schema (Post #3), and answer-shaped copy on the page (Posts #1–2). There's one signal left that quietly decides which of several legible businesses an AI assistant actually names — and it's the one most small sites leave on the table.

Reviews. Not just having them — making them machine-readable and consistent across the web.

When someone asks ChatGPT or Perplexity "who's the best roofer near me?", the model isn't only checking who exists. It's checking who looks trusted and verifiable. A business with a visible, structured rating reads as a safer thing to recommend than an identical business with no rating signal at all. This post is about turning the reviews you already have into a citation signal.

One honest caveat up front: structured reviews don't guarantee a citation, and you must never fabricate ratings or invent review counts — that's both dishonest and a schema violation that can get your markup ignored or penalized. Everything below assumes you mark up only real, verifiable numbers that match what's publicly visible. If you have two reviews, you mark up two.

Why reviews are a multiplier, not just a checkbox

Schema tells the model what you are. Reviews tell it whether to vouch for you. The difference matters because answer engines are optimizing to not embarrass themselves — a wrong or sketchy recommendation is worse for them than no recommendation. Three things make reviews punch above their weight in 2026:

They're a trust proxy the model can quantify. "4.8 from 130 reviews" is a number it can compare across candidates. Vague social proof ("trusted by locals!") is not.
They appear in multiple sources at once. Your Google Business Profile, your site, and directories all carry the same rating — that cross-source agreement is exactly the consistency signal from Post #2. When all three agree, confidence goes up.
Review text is quotable. When a customer writes "they fixed our leak the same day," that sentence is answer-shaped content the model can lift to justify naming you. Your own marketing copy can't do that — it's not credible coming from you.

The 10-minute review-signal audit

Do these in order. No developer required for steps 1–4.

1. Count your real, public rating. Open your Google Business Profile (or Yelp, or the platform where you have the most reviews). Note the exact average and exact count. This is your source of truth — every other place must match it.

2. Check your site for any rating display. Most small sites show reviews as a screenshot or a wall of unlabeled testimonials. To a crawler, a screenshot is invisible and unlabeled text is just decoration. If your rating isn't in text + schema, it doesn't count as a signal.

3. Check consistency across sources. Does your Google rating roughly match Yelp/Facebook/industry directories? Wild disagreement (4.9 one place, 3.2 another) reads as noise and weakens all of them. You can't fake the numbers up, but you can make sure stale/duplicate listings aren't dragging the average.

4. Check for individual review markup. Do you have a few standout reviews quoted as text on your site (not images)? These are the quotable sentences models love.

5. Validate any existing markup. If you (or a plugin) already output AggregateRating, paste your page URL into validator.schema.org and confirm the numbers match reality and parse cleanly.

If you fail steps 2 or 4, the fix is below.

Copy-paste: AggregateRating + Review markup

Drop this into the <head> of your homepage or a dedicated reviews page. Replace every value with your real, public numbers. Do not invent. If a field doesn't apply, delete it rather than guessing.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "YOUR BUSINESS NAME",
  "url": "https://yourdomain.com",
  "telephone": "+1-555-555-5555",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "City",
    "addressRegion": "ST",
    "postalCode": "00000",
    "addressCountry": "<your ISO country code, e.g. GB/AU/CA/SG/IN — don't ship unverified>"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "130",
    "bestRating": "5",
    "worstRating": "1"
  },
  "review": [
    {
      "@type": "Review",
      "author": { "@type": "Person", "name": "First L." },
      "datePublished": "2026-05-12",
      "reviewRating": {
        "@type": "Rating",
        "ratingValue": "5",
        "bestRating": "5"
      },
      "reviewBody": "They fixed our roof leak the same day we called. Honest pricing, no upsell."
    },
    {
      "@type": "Review",
      "author": { "@type": "Person", "name": "Second R." },
      "datePublished": "2026-04-28",
      "reviewRating": {
        "@type": "Rating",
        "ratingValue": "5",
        "bestRating": "5"
      },
      "reviewBody": "Showed up on time, explained everything, cleaned up after. Would hire again."
    }
  ]
}
</script>

Three rules that keep this honest and working:

ratingValue and reviewCount must match what's publicly visible (e.g. your Google profile). Mismatched numbers are the #1 reason this markup gets ignored.
Every review you mark up must be a real review that actually appears somewhere a person can verify — ideally also shown as visible text on the same page. Don't mark up reviews that exist only in the JSON.
Use real first name + last initial (or however the reviewer is publicly shown). Don't anonymize to "A Customer" — that reads as synthetic.

Make the reviews visible and readable (not screenshots)

Schema without visible text is fragile. Pair the markup above with real on-page text:

Put your rating in a headline as text: "Rated 4.8 ★ across 130 reviews" — not baked into an image.
Quote 3–5 reviews as text on the page. This is the quotable raw material for live-retrieval answers.
If your platform shows reviews via an embedded widget (an <iframe>), assume crawlers may not read inside it — add a plain-text version alongside it.

This is the same principle from Post #2: facts trapped in images don't count. Ratings are facts.

Don't just mark up reviews — get more of them

The signal is only as strong as the underlying number. Two low-effort, honest plays:

Ask, with a direct link. After a finished job, text or email the customer a one-tap Google review link. The single biggest reason small businesses have 6 reviews instead of 60 is that they never ask.
Reply to every review, good or bad. Replies add fresh, relevant text to the listing and signal an active, real business — which is exactly the "is this legit?" question the model is trying to answer.

Neither requires new software. Both compound.

Where this sits in the priority order

Reviews are a multiplier, which means they multiply something. If the bots can't reach you (Post #4) or your facts aren't legible (Posts #1–3), there's nothing to multiply. So the order stands:

Access — let the crawlers in (Post #4)
Labeling — schema your core facts (Post #3)
Trust — structured, consistent, visible reviews (this post)

Do them in that order and you've covered the full stack of "why AI ignores me."

FAQ

I only have 4 reviews. Should I still mark them up?
Yes — mark up the real 4. A small honest number beats no signal, and it's truthful. Then run the "ask with a link" play to grow it.

Can I mark up reviews from Google/Yelp on my own site?
Mark up reviews you can legitimately display and that a person can verify. The safest pattern is reviews collected on or syndicated to your own site. Don't scrape and re-host a platform's reviews in a way that violates its terms — when in doubt, quote a few as visible testimonials with attribution and mark those up.

Will AggregateRating get me star ratings in Google again?
Google has changed self-serving review snippet rules over the years for LocalBusiness, so don't count on stars in classic search. This post is about AI citation trust, which is a separate (and currently more lenient) consumer — the markup still helps models assess you even when Google hides the stars.

Is more reviews or higher rating more important?
Both, but consistency and recency matter more than chasing a perfect 5.0. A 4.7 with 120 recent reviews reads as more real than a 5.0 with 3 reviews from 2021.

Does fake-but-positive review markup ever work?
No — and don't. It's dishonest, it violates schema guidelines, and a mismatch with your public profile is exactly what gets your entire markup discounted. Real numbers only. This whole series only works because the markup is true.

Two ways to act on this:

Is Your Site Blocking the AI Crawlers? (How to Check & Fix It, 2026)

Gyubin Kim — Sat, 06 Jun 2026 04:25:39 +0000

Series: Getting Cited by AI — Post #4. Post #1: How to Get Cited by ChatGPT → · Post #2: Why AI Recommends Your Competitor → · Post #3: Copy-Paste Schema Templates →

The last three posts assumed one thing that isn't always true: that AI assistants can actually read your site in the first place. You can have perfect schema, clean facts, and answer-shaped copy — and still be invisible, because the crawler that feeds the model never got past your front door.

This post is the part almost nobody checks: AI crawler access. It's the plumbing under everything else. Five minutes here can be the difference between "my schema isn't working" and "the bot was blocked the whole time."

One honest caveat up front: allowing AI crawlers doesn't guarantee you get cited, and blocking them isn't always wrong (some businesses deliberately opt out). There's no fixed timeline for pickup either. What this post does is make sure the choice is yours — not an accidental default from your site builder or an SEO plugin you installed two years ago.

How AI actually sees your site

There are two different ways a model can end up quoting you, and they have different gatekeepers:

Training / index crawl — bots like GPTBot (OpenAI), ClaudeBot (Anthropic), Google-Extended (Gemini), and Amazonbot crawl the open web ahead of time. If your robots.txt blocks them, your pages may never enter the corpus those models draw on.
Live retrieval ("answer engines") — when someone asks ChatGPT, Perplexity, or Copilot a question right now, a separate fetcher (e.g. OAI-SearchBot, PerplexityBot, ChatGPT-User) hits live pages to ground the answer. This is where most local-business citations come from in 2026, and it has its own set of user-agents.

The trap: people block one and assume they've allowed the other, or an SEO/security plugin quietly blocks all of them. You have to handle both.

The 5-minute access check

Do these in order. No developer required.

1. Read your robots.txt. Go to https://yourdomain.com/robots.txt in a browser. Look for any line like Disallow: / paired with an AI user-agent, or a blanket block. Common offenders:

User-agent: GPTBot
Disallow: /

User-agent: *
Disallow: /

The second one blocks everything, AI crawlers included. If you see either and you want AI visibility, that's your culprit.

2. Check for a firewall / WAF block. Cloudflare, Wordfence, and similar tools have "block AI bots / block AI scrapers" toggles that became default-on for many accounts in 2024–2025. These block at the network layer, so your robots.txt can say "allowed" while the request still gets a 403. Log into your CDN/security dashboard and look for an "AI Scrapers & Crawlers" or "Bot Fight Mode" setting.

3. Confirm the page renders without JavaScript. Many fetchers grab the raw HTML and don't run your JavaScript. If your prices, hours, or FAQ only appear after a script runs, the bot sees a blank shell. Quick test: right-click → "View Page Source" (not Inspect). If your key facts aren't in that raw HTML, they may be invisible to retrieval bots.

4. Check meta tags. Look in your page's <head> for <meta name="robots" content="noindex"> or noai / noimageai directives. These tell crawlers to skip the page.

5. Test a live fetch. Ask ChatGPT or Perplexity directly: "What can you tell me about [your business name] in [city] from their website?" If it can't find anything or pulls only from a directory (Yelp, Google) and never your own site, that's a signal your site isn't being reached or read.

The fix: an explicit "allow" robots.txt

If you've decided you want AI visibility, make it explicit rather than relying on defaults. Here's a clean, permissive robots.txt that welcomes the major AI crawlers while keeping normal SEO intact:

# Allow standard search engines
User-agent: *
Allow: /

# Explicitly welcome AI crawlers (training + retrieval)
User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://yourdomain.com/sitemap.xml

Replace the sitemap URL with your real one. Most site builders (Squarespace, Wix, Shopify, WordPress) either generate robots.txt automatically or let you edit it under SEO/crawling settings — search your builder's help for "edit robots.txt."

Note: user-agent names change as vendors add new bots. The list above covers the major ones in 2026, but the principle — Allow: / for the crawlers you want — is what lasts. Don't over-engineer it.

Bonus: the `llms.txt` file (optional, low-effort, forward-looking)

A newer, emerging convention is llms.txt — a plain-text file at https://yourdomain.com/llms.txt that gives AI models a clean, curated summary of your site and links to your most important pages. Think of it as a "table of contents for machines."

It is not an official standard and not guaranteed to be read by any model today — so treat it as a low-cost bet, not a fix. But it's a single small file, it can't hurt, and a few retrieval systems have started honoring it. A minimal version:

# Acme Roofing — Phoenix, AZ

> Family-owned roofing contractor serving the Phoenix metro since 1998.
> Free written estimates. Repairs and full replacements.

## Key pages
- [Services & pricing](https://yourdomain.com/services): repairs $400–$1,200; replacements from ~$9,000
- [Service area](https://yourdomain.com/areas): Phoenix, Scottsdale, Tempe, Mesa
- [Reviews](https://yourdomain.com/reviews): 4.8 average across 120+ Google reviews
- [Contact](https://yourdomain.com/contact): (555) 010-1234, open Mon–Sat 7am–6pm

Same honesty rule as everywhere in this series: only put in facts that are true and match your Google profile.

Priority order (do these in this sequence)

Unblock first. If a robots.txt rule or WAF toggle is blocking AI bots, nothing else matters until that's fixed.
Render facts in raw HTML. Make sure prices, hours, and answers appear in View Source, not just after JavaScript.
Add the explicit allow list so the choice is deliberate and survives plugin updates.
Add schema (see Post #3) so the now-readable facts are labeled.
llms.txt last as a cheap, optional extra.

Access before labeling before optimizing. Skip step 1 and the rest is wasted effort.

If you'd rather not crawl through your CDN settings and robots files yourself, I run a free AI-visibility snapshot: I check exactly which AI crawlers can and can't reach your site, whether your facts render for them, and what's blocking citation — then send you the specific fixes. No cost, no pitch. If it's useful and you want it done for you, we can talk from there. Reach out: faithpath25 (sales) — ask for the snapshot.

FAQ

Should every business allow AI crawlers?
No. If your content is your product (paywalled media, proprietary databases) you may want to block training bots. For a local service business that wants to be found and recommended, allowing them is almost always the right call.

If I allow GPTBot, will ChatGPT start citing me right away?
No — there's no guarantee and no fixed timeline. Allowing access is necessary, not sufficient. Whether and when you get picked up still depends on your schema, reviews, and how quotable your pages are.

I allowed the bots in robots.txt but still get blocked — why?
Almost always a firewall/WAF (Cloudflare, Wordfence) blocking at the network layer above robots.txt. Check your security dashboard for an "AI bots" or "Bot Fight" toggle.

Is llms.txt required?
No. It's an emerging, unofficial convention. It's a cheap optional extra — do the robots.txt and schema work first.

Will blocking AI bots hurt my normal Google ranking?
Blocking AI-specific bots (GPTBot, Google-Extended) does not affect classic Google Search ranking, which uses Googlebot. But a blanket Disallow: / for User-agent: * blocks everything, including Googlebot — that one will hurt you badly.

Two ways to act on this:

Copy-Paste Schema Templates to Get Cited by AI (2026)

Gyubin Kim — Sat, 06 Jun 2026 04:25:38 +0000

Series: Getting Cited by AI — Post #3. Post #1: How to Get Cited by ChatGPT → · Post #2: Why AI Recommends Your Competitor →

In the last two posts we covered why AI assistants skip over great businesses: their facts live in images, they have no structured data, and they're hard to quote. This post is the fix you can actually paste in today — ready-to-use schema (JSON-LD) templates for the most common local-business types, plus how to install and verify them.

Schema is a small block of code that labels your facts for machines: this is the business name, this is the price range, these are the hours, this is an FAQ answer. It's the difference between handing a model a labeled spreadsheet and handing it a wall of prose. You don't need a developer to add it — you need the right block and a place to paste it.

One honest caveat up front: schema doesn't guarantee an AI will recommend you, and there's no fixed timeline for pickup. It makes your facts clean, labeled, and quotable — the necessary groundwork. Everything below is real, valid schema.org markup. Fill in your facts; never invent reviews or ratings you don't have.

How to use these templates (3 steps)

Copy the block for your business type below.
Replace every REPLACE_* value with your real information. Delete any line you can't fill in honestly (e.g. if you don't track a price range, remove priceRange).
Paste it into the <head> of your homepage, inside a <script type="application/ld+json"> tag (already included in each block). One block per page is plenty for the homepage.

Then validate (see the last section) before you trust it.

Template 1 — Service business / trades (roofer, plumber, HVAC, electrician, landscaper)

This uses LocalBusiness. Swap the @type for a more specific one if it fits (Plumber, HVACBusiness, Electrician, RoofingContractor — all valid schema.org types).

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "RoofingContractor",
  "name": "REPLACE_Business Name",
  "description": "REPLACE_One plain sentence: what you do, where, and for whom. e.g. Family-owned roofing company in Austin, TX specializing in storm-damage repair and metal roofs.",
  "url": "https://REPLACE_yourdomain.com",
  "telephone": "+1-REPLACE-555-0100",
  "email": "REPLACE_hello@yourdomain.com",
  "priceRange": "$$",
  "image": "https://REPLACE_yourdomain.com/photo.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "REPLACE_123 Main St",
    "addressLocality": "REPLACE_Austin",
    "addressRegion": "REPLACE_TX",
    "postalCode": "REPLACE_78701",
    "addressCountry": "REPLACE_your ISO country code (GB/AU/CA/SG/IN…)"
  },
  "areaServed": ["REPLACE_Travis County", "REPLACE_Williamson County"],
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "08:00",
    "closes": "17:00"
  }],
  "founder": "REPLACE_Owner Name",
  "foundingDate": "REPLACE_2009"
}
</script>

Template 2 — Solo professional / photographer / coach / consultant

Pairs a LocalBusiness-style entity with a Person, so the AI knows who you are — important for personal brands. Use Photographer as the @type for photographers (valid schema.org type), or ProfessionalService for coaches/consultants.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Photographer",
  "name": "REPLACE_Studio or Your Name Photography",
  "description": "REPLACE_Wedding and elopement photographer based in Nashville, TN, serving the Southeast.",
  "url": "https://REPLACE_yourdomain.com",
  "email": "REPLACE_hello@yourdomain.com",
  "image": "https://REPLACE_yourdomain.com/headshot.jpg",
  "priceRange": "$$$",
  "areaServed": "REPLACE_Nashville, TN and the Southeast US",
  "founder": {
    "@type": "Person",
    "name": "REPLACE_Your Name",
    "jobTitle": "REPLACE_Wedding Photographer",
    "knowsAbout": ["REPLACE_wedding photography", "REPLACE_elopements", "REPLACE_engagement sessions"]
  }
}
</script>

Template 3 — Health / wellness (med spa, dentist, PT, clinic)

Use a specific medical subtype where it fits (MedicalClinic, Dentist, Physiotherapy) — they're all valid and signal more clearly than a bare LocalBusiness.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalClinic",
  "name": "REPLACE_Clinic Name",
  "description": "REPLACE_Med spa in Phoenix, AZ offering injectables, laser treatments, and skin care.",
  "url": "https://REPLACE_yourdomain.com",
  "telephone": "+1-REPLACE-555-0100",
  "priceRange": "$$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "REPLACE_123 Main St",
    "addressLocality": "REPLACE_Phoenix",
    "addressRegion": "REPLACE_AZ",
    "postalCode": "REPLACE_85001",
    "addressCountry": "REPLACE_your ISO country code (GB/AU/CA/SG/IN…)"
  },
  "medicalSpecialty": "REPLACE_Dermatology",
  "availableService": [
    {"@type": "MedicalProcedure", "name": "REPLACE_Botox / injectables"},
    {"@type": "MedicalProcedure", "name": "REPLACE_Laser skin resurfacing"}
  ]
}
</script>

Add-on A — FAQ schema (works for any business)

This is one of the highest-leverage blocks for AI visibility: it hands the model pre-written question-and-answer pairs it can quote almost verbatim. Put your 3–6 most common customer questions here, in plain language.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "REPLACE_What areas do you serve?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "REPLACE_We serve Austin and the surrounding Travis and Williamson counties."
      }
    },
    {
      "@type": "Question",
      "name": "REPLACE_How much does a typical job cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "REPLACE_Most repairs run $400–$1,200; full replacements start around $9,000. We give free written estimates."
      }
    },
    {
      "@type": "Question",
      "name": "REPLACE_Are you licensed and insured?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "REPLACE_Yes — licensed in Texas (#000000) and fully insured."
      }
    }
  ]
}
</script>

Add-on B — Reviews & rating (ONLY if the numbers are real)

AggregateRating is powerful — but only paste this if the numbers are genuinely yours, ideally matching what's on your Google Business Profile. Fabricating ratings is the fastest way to look untrustworthy (and a policy violation). If you don't have reviews yet, skip this block entirely and focus on collecting them first.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "REPLACE_Business Name",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "REPLACE_4.8",
    "reviewCount": "REPLACE_64"
  }
}
</script>

How to install it (no developer required)

Squarespace / Wix / Webflow: look for "Code Injection" or "Custom Code" → header. Paste the block there.
WordPress: use a header-snippet plugin (e.g. "Insert Headers and Footers") or your theme's custom-code area.
Static HTML site: paste directly inside <head> on the page.
Shopify: edit theme.liquid and paste before </head>.

You can keep your existing design untouched — schema is invisible to visitors. It only talks to machines.

How to verify it works

Never trust a block you haven't validated. Two free checks:

Schema.org Validator — paste your URL or the code. It flags syntax errors and shows what types it detected.
Google Rich Results Test — confirms Google can parse it (a good proxy for "machines can read this").

If either shows errors, the usual culprits are: a stray comma, a missing quote, or a REPLACE_ value you forgot to fill in. Fix and re-test until both come back clean.

A realistic close

Schema is the groundwork, not a magic switch. It makes your facts clean, labeled, and quotable — which is the prerequisite for being named by an AI assistant. Pickup still depends on when your pages get crawled, how often the underlying sources refresh, and whether your reviews and plain-text facts back the schema up (see Post #2).

If you'd rather not hand-edit JSON, I run a free AI-visibility snapshot — I check what AI can and can't currently read on your site and send you the exact fixes (including the filled-in schema for your business). No cost, no pitch. If it's useful and you want it implemented for you, we can talk. Reach out: faithpath25 (sales) — see the snapshot offer.

FAQ

Do I need a developer to add schema?
No. Most site builders have a "custom code" or "header injection" area where you paste the block. The only skill is replacing the placeholder values honestly.

Will adding schema guarantee AI starts recommending me?
No — there's no guarantee and no fixed timeline. Schema makes you readable and quotable; whether and when a model picks you up depends on crawling, source refresh, and your reviews. It's necessary groundwork, not a switch.

Can I just paste a template and leave the placeholders?
No — unfilled REPLACE_ values are worse than no schema. Fill in every line with real facts, and delete any you can't fill honestly.

Is it bad to have schema that doesn't match my Google profile?
Yes. Inconsistent facts across your site, Google Business Profile, and directories make a model less confident, not more. Keep name, address, phone, and hours identical everywhere.

Two ways to act on this:

Why AI Recommends Your Competitor Instead of You (2026)

Gyubin Kim — Wed, 03 Jun 2026 08:09:55 +0000

Series: Getting Cited by AI — Post #2. Read Post #1: How to Get Your Business Cited by ChatGPT →

You typed your own service and city into ChatGPT — "best wedding photographer in Nashville," "roof repair near Austin," "med spa in Phoenix" — and the AI confidently named three businesses. None of them were you. One of them was the competitor you know you out-deliver.

That stings, but it isn't a popularity contest you lost. It's a retrieval problem you can fix. AI models don't rank the "best" business — they recommend the one whose information is easiest to read, easiest to trust, and easiest to quote. Here's why your competitor keeps winning that, and what to change.

AI isn't picking the better business. It's picking the more legible one.

When you ask an AI assistant for a local recommendation, it isn't forming an opinion. Under the hood it's doing some mix of: pulling from what it learned in training, retrieving live pages, and pulling from structured sources (maps, directories, review platforms). Then it stitches a confident-sounding answer from whatever it can cleanly extract.

So the business that gets named is rarely "the best." It's the one that is:

Findable — its pages get crawled and retrieved.
Parseable — its key facts (what it does, where, hours, price range, specialties) are in plain text and structured data, not buried in an image or a slider.
Corroborated — the same facts show up consistently across its site, Google Business Profile, and directories.
Reviewed — it has enough recent, specific reviews that the model treats it as a safe recommendation.

Your competitor probably didn't out-market you. They just happen to clear those four bars — often by accident, because they used a template that ships with schema, or because they have more Google reviews. Let's go through why each one tips the scale.

Reason 1: Their facts are in text. Yours are in pictures.

The single most common reason a great business is invisible to AI: its most important information lives inside images, video, or design elements that models can't read.

Your services are a graphic. Your pricing is a PDF. Your specialties are baked into a hero banner. Your "About" is a beautiful photo with three words on it. A human gets all of this instantly. A language model gets… almost nothing.

Your competitor's site might be uglier — but if it says, in actual selectable text, "We're a family-owned roofing company in Austin, Texas, specializing in storm-damage repair and metal roofs, serving Travis and Williamson counties since 2009," then the AI has a clean, quotable sentence. Yours has a JPG.

Fix: Audit every page for facts that exist only as an image. Put them in real text too. You can keep the pretty version — just make sure the same information also exists as words the page can render. Aim for one plain sentence that answers "what, where, and for whom."

Reason 2: They have schema markup. You don't.

Schema (structured data) is a hidden block of code that labels your facts for machines: this is the business name, this is the price range, these are the hours, this is a review, this is an FAQ answer. It's the difference between handing a model a labeled spreadsheet versus a wall of prose.

Many website builders and templates now include basic schema automatically — which is exactly how a less-polished competitor ends up "more legible" than your custom-built site that has none. They didn't do anything clever. Their template did it for them.

Fix: Add LocalBusiness schema with your name, address, phone, hours, and price range. Add FAQPage schema to your FAQ. If you collect reviews on your own site, mark them up too. On Wix/Squarespace/WordPress you can inject this with a code block or a schema app — no rebuild needed. (Post #3 in this series will give copy-paste templates.)

Reason 3: Their story is consistent. Yours contradicts itself.

AI models hedge against businesses whose facts don't line up. If your website says you're in one suburb, Google says another, an old directory lists a disconnected phone number, and your Instagram bio says something different again — the model sees noise, lowers its confidence, and recommends the business it can describe without contradicting itself.

This is the quietest killer because nothing looks broken. Every individual page is fine. It's the inconsistency across them that demotes you.

Fix: Pick your canonical facts — exact business name, address, phone, primary service — and make them identical everywhere: website footer, Google Business Profile, Yelp, industry directories, social bios. Same spelling, same format. Kill or correct stale listings. Consistency reads as trust.

Reason 4: They have 40 recent reviews. You have 6 from 2022.

Reviews are one of the strongest signals feeding AI local answers, because they're independent corroboration the model can lean on. A business with a steady stream of recent, specific reviews ("they fixed our leak the same day," "great with nervous brides") gives the model concrete, quotable detail. A business with a handful of old, generic reviews gives it nothing to say — so it stays quiet about you and talks about your competitor instead.

It's not just the star rating. It's volume, recency, and specificity.

Fix: Build a simple, repeatable ask — a text or email to every happy customer right after you deliver, with a direct link to your Google review form. Nudge them to mention the specific thing you did. Twenty fresh, detailed reviews over a couple of months will move you more than almost any on-site tweak.

Reason 5: They answer the question. You describe yourself.

Most small-business websites are written like brochures: "Welcome. We're passionate about excellence. Our team brings years of experience." That's invisible to AI because nobody asks an assistant "who is passionate about excellence." People ask specific questions: "Who does same-day roof repair in Austin?" "Which Nashville photographer shoots elopements?" "Is there a med spa in Phoenix open on Sundays?"

The business that gets recommended is the one whose pages literally contain the answer to those questions in plain language. Your competitor's FAQ probably says "Yes, we offer same-day emergency repair across Austin." Yours says "Quality you can trust."

Fix: Write the actual questions your customers ask into your pages — as headings and FAQ entries — and answer them in one or two direct sentences each. Answer-shaped content is quote-shaped content.

The 15-minute reality check

Before you change anything, see what AI says about you right now:

Open ChatGPT (and one other assistant) and ask the exact question a customer would: "best [your service] in [your city]."
Note who gets named — those are your real AI competitors, regardless of who you think they are.
Ask directly: "What do you know about [your business name]?" Read what comes back. Vague, wrong, or "I don't have information" all mean the same thing: you're not legible.
Open a named competitor's website. View its source and search for application/ld+json — that's their schema. Check whether their facts are in text and whether they have more recent reviews.

That comparison usually makes the gap obvious. It's almost never that they're better. It's that they're readable and you're not.

The order to fix it in

You don't need all of this at once. Highest impact first:

Reviews — start the ask today; it compounds slowest, so begin now.
Facts in text — move image-only info into words this week.
Schema — add LocalBusiness + FAQPage; a one-time job.
Consistency — align name/address/phone everywhere.
Answer-shaped content — rewrite key pages as questions-and-answers.

Do the first three and most small businesses go from invisible to quotable.

Free offer: I'll run this exact comparison on your real site versus whoever AI currently recommends in your area, and send you a one-page snapshot — what AI says about you now, who it names instead, and the three highest-impact gaps to close — for free. If it's useful and you want the fixes done, we can talk. If not, keep the snapshot. No catch.

📧 Send your website URL to faithpath25@gmail.com with subject "GEO snapshot" and I'll send yours back.

FAQ

My competitor is objectively worse — how are they ranked above me by AI?
Because AI recommends the more legible business, not the better one. Cleaner structured data, more recent reviews, and facts written in plain text usually explain the whole gap.

Will fixing my site guarantee AI starts recommending me?
No — there's no guarantee and no fixed timeline. These changes make you readable and trustworthy to the models; pickup depends on when your pages are next crawled and how often the underlying sources refresh. They're the necessary groundwork, not a switch.

Is paying for ads the faster route?
Ads buy temporary visibility on ad networks; they don't make you quotable in an AI's organic answer. The legibility fixes here are what get you named when someone asks an assistant directly — and they keep working after you stop paying.

How many reviews is "enough"?
There's no magic number, but recency and specificity matter as much as count. A steady trickle of detailed, recent reviews beats a large pile of old generic ones.

Two ways to act on this:

How to Get Your Business Cited by ChatGPT (2026 Guide)

Gyubin Kim — Wed, 03 Jun 2026 08:08:01 +0000

When someone asks ChatGPT, Perplexity, or Google's AI Overviews "who's the best [your service] near me?" — does your business show up?

For most small businesses, the answer is no. Not because the work isn't good, but because the website was never built in a way an AI model can read, trust, and quote. This guide walks through exactly why that happens and what to fix — in plain language, no jargon dumps.

Quick definition: Getting recommended by AI tools is called Generative Engine Optimization (GEO) — the AI-era cousin of SEO. SEO got you ranked on a page of blue links. GEO gets you named inside the answer itself.

Why AI tools ignore most small-business websites

AI assistants don't "browse" your site the way a customer does. They rely on:

Structured data — machine-readable labels (called schema markup) that say "this is a business, here's the name, address, services, hours, and reviews."
Clear, factual text — pages that state plainly what you do, where, for whom, and at what price.
Corroboration across the web — your business appearing consistently in directories, maps, and reviews.

Most DIY sites (Wix, Squarespace, GoDaddy templates) ship with none of the structured data an AI needs, and bury the key facts inside images or vague marketing copy. To a model, the page is a blur. So it quotes a competitor who happens to be more legible — even if your service is better.

This is the single biggest reason small businesses are invisible in AI search. It is also the most fixable.

The 5 things that decide whether AI quotes you

1. Schema markup (the #1 lever)

Add LocalBusiness (or the specific subtype — Restaurant, Photographer, Plumber, etc.) schema with your name, address, phone, geo coordinates, opening hours, and priceRange. Add FAQPage schema for your most common customer questions. This is JSON-LD code in the page's <head> — invisible to visitors, gold to AI.

How to check yours in 30 seconds: open validator.schema.org, paste your homepage URL, and see what (if anything) comes back. Most small sites return nothing or a bare WebSite tag.

2. Answer-shaped content

AI quotes text that already reads like an answer. Add a short "TL;DR" or summary line near the top of key pages. Write a real FAQ section using the actual questions customers ask ("Do you travel for weddings?" "How far in advance should I book?"). Use clear headings phrased as questions.

3. Consistent NAP across the web

Name, Address, Phone must match exactly on your site, Google Business Profile, Yelp, and industry directories. Mismatches make AI distrust the data and drop you from the answer.

4. Real, recent reviews

Models weigh social proof heavily. A handful of detailed Google reviews from the last few months does more for AI visibility than a dozen old ones. Ask happy customers; reply to every review.

5. Crawlable, fast, legible pages

Facts in real text — not locked inside images or a slow JavaScript widget. If a key detail (your services, your city, your prices) only exists as a picture, AI can't read it.

A 20-minute self-audit you can run today

Ask the AI directly. Open ChatGPT or Perplexity and type: "Best [your service] in [your city]?" and "Tell me about [your business name]." Note whether you appear and whether the facts are right.
Check your schema at validator.schema.org (see above).
View your homepage source (right-click → View Page Source) and search for application/ld+json. Nothing there? That's your gap.
Search your business name + city and confirm your NAP matches everywhere.
Count your Google reviews from the last 90 days. Fewer than 3? That's a lever.

If you fail 2 or more of these, AI tools are almost certainly skipping you right now — and sending those customers to whoever fixed it first.

SEO vs GEO — what actually changed

	Old SEO	GEO (2026)
Goal	Rank on the results page	Get named inside the AI answer
Reads your site	Search crawler	Language model
Wins on	Keywords + backlinks	Structured data + clear facts + trust signals
Customer sees	A list of links	One recommended answer (often just one or two names)

The stakes are higher with GEO because AI answers are winner-take-most. A page of links has ten slots. An AI answer often names one business. You either are it, or you're invisible.

Do it yourself, or get it done

Everything above is doable on your own with a weekend and some patience — the schema generators, the FAQ rewrite, the review push are all learnable. If you'd rather not touch code, that's exactly the kind of implementation work specialists handle in a few days.

Free offer: I'll run the audit above on your actual site and send you a one-page snapshot — what's missing, what AI says about you right now, and the three highest-impact fixes — for free. If it's useful and you want the fixes implemented, we can talk; if not, keep the snapshot. No catch.

📧 Send your website URL to faithpath25@gmail.com with the subject "GEO snapshot" and I'll send yours back.

FAQ

Is GEO just SEO with a new name?
They overlap (clean, fast, well-structured sites win at both), but GEO specifically optimizes for being quoted by AI models — which lean far more on structured data and clear factual text than on backlinks.

How long until AI tools pick up the changes?
There's no guarantee and no fixed timeline — it depends on how often the underlying models and their sources refresh. Schema and on-page fixes are read whenever your pages are next crawled or retrieved; review and directory signals build over weeks.

I'm on Wix/Squarespace — am I stuck?
No. Most builders let you inject custom code or add schema apps. The facts-in-real-text and review fixes work on any platform.

Does this replace Google Business Profile?
No — keep it accurate and active. A consistent, well-reviewed Google Business Profile is one of the strongest signals feeding AI answers.

Two ways to act on this:

DEV Community: Gyubin Kim

Why Couples Find Another Wedding Photographer When They Ask AI (and How to Fix It, 2026)

The three reasons wedding photographers go invisible

The 10-minute wedding-photographer visibility check

The fixes (highest leverage first)

Fix 1 — Turn your galleries into pages with words

Fix 2 — Publish a starting range and what's included

Fix 3 — Answer the questions couples actually ask

Fix 4 — Make your reviews machine-readable

Fix 5 — Confirm the crawlers are allowed

Copy-paste schema for a wedding photographer

Priority order, if you only do three things

FAQ

Why ChatGPT Sends Clients to Another Trainer or Coach — Not You (2026)

The three reasons fitness & coaching sites go invisible

The 10-minute fitness/coaching visibility check

The priority fixes (in order)

Copy-paste schema for a trainer, studio, or coach

What this is and isn't

Why ChatGPT Recommends a Different Roofer (or Plumber) Than You (2026)

The three reasons trades sites go invisible

The 10-minute trades visibility check

The priority fixes (in order)

Copy-paste schema for a trades business

What this is and isn't

Why Buyers Find Your Competitor (Not You) When They Ask AI About Real Estate (2026)

The three reasons real estate sites go invisible

The 10-minute real-estate visibility check

The priority fixes (in order)

Copy-paste schema for a real estate agent

What this is and isn't

Why Your Med Spa Doesn't Show Up in ChatGPT (and How to Fix It, 2026)

The three reasons med spas go invisible

The 10-minute med-spa visibility check

The fixes (highest leverage first)

Fix 1 — Put your service menu on the page as text

Fix 2 — Answer the five questions patients actually ask

Fix 3 — Add the right schema (copy-paste below)

Fix 4 — Make your reviews machine-readable

Fix 5 — Confirm the crawlers are allowed

Copy-paste schema for a med spa

Priority order, if you only do three things

FAQ

Reviews & AggregateRating: The Citation Multiplier AI Looks For (2026)

Why reviews are a multiplier, not just a checkbox

The 10-minute review-signal audit

Copy-paste: AggregateRating + Review markup

Make the reviews visible and readable (not screenshots)

Don't just mark up reviews — get more of them

Where this sits in the priority order

FAQ

Is Your Site Blocking the AI Crawlers? (How to Check & Fix It, 2026)

How AI actually sees your site

The 5-minute access check

The fix: an explicit "allow" robots.txt

Bonus: the llms.txt file (optional, low-effort, forward-looking)

Priority order (do these in this sequence)

FAQ

Copy-Paste Schema Templates to Get Cited by AI (2026)

How to use these templates (3 steps)

Template 1 — Service business / trades (roofer, plumber, HVAC, electrician, landscaper)

Template 2 — Solo professional / photographer / coach / consultant

Template 3 — Health / wellness (med spa, dentist, PT, clinic)

Add-on A — FAQ schema (works for any business)

Add-on B — Reviews & rating (ONLY if the numbers are real)

How to install it (no developer required)

How to verify it works

A realistic close

FAQ

Why AI Recommends Your Competitor Instead of You (2026)

AI isn't picking the better business. It's picking the more legible one.

Reason 1: Their facts are in text. Yours are in pictures.

Reason 2: They have schema markup. You don't.

Reason 3: Their story is consistent. Yours contradicts itself.

Reason 4: They have 40 recent reviews. You have 6 from 2022.

Reason 5: They answer the question. You describe yourself.

The 15-minute reality check

The order to fix it in

FAQ

How to Get Your Business Cited by ChatGPT (2026 Guide)

Bonus: the `llms.txt` file (optional, low-effort, forward-looking)