Can IA help — https://charleston.wellabsplus.com/?
Maybe — limited lift
Maybe limited lift here — your page is already reachable and your commerce is legible. We'd look at competitive positioning and citation share rather than basic legibility.
✅Are AI bots reaching you? AI search bots can reach your content — you're eligible to be cited.
✅Are your links coming through? Your commerce links are legible to AI crawlers.
🔌Implementation friction: Needs a quick scoping call — no first-class edge/CMS connector auto-detected.
Next step:Introduce us to your SEO / dev teamBook a 20-min intro call
Summary
The page displays a single free service offer ("Unlock Free Tox") alongside five booking-oriented CTAs for a medical aesthetics practice in Charleston, with three outbound merchant URLs routing to appointment systems. The schema layer includes organizational and geo metadata but lacks commerce-type coverage entirely—no Product, Offer, AggregateOffer, BuyAction, or Review entities are present despite the page's transactional intent. Citation bots reach the page at partial capacity (1 of 2 search-index crawlers succeed), and the explicit-mention probe returned one URL citation from two mentions detected. Adding structured Offer and Product entities plus BuyAction wrappers would make the service offering and its transaction pathway machine-readable, allowing inference systems to distinguish between the free tox screening, downstream paid services, and the booking funnel without relying on heuristic text parsing.
Citation bots reachable — claude_searchbot
This URL is reachable by the AI search indexes that drive live citations. Enrichment (next panel) is applicable here.
Blocked: oai_searchbot 429
What humans see vs what AI extracts today vs with IA enrichment
The gap between these columns is the enrichment IA layers on top of the page for AI extractors. Edge-level blocking is a separate dimension — see the bot-accessibility section.
Human view
AI Bot Today — During Live Search
On the page
Brand
Well Labs+ Charleston
Offers detected (1)
Unlock Free Tox — FREE
CTAs (8)
Book Your Consultation · Book Now · Book Your Appointment · Unlock Free Tox + more
Each model is queried twice — with web search off (training memory) and on (live fetch). The diff shows whether your AI presence is stale, current, or absent.
Bot accessibility
Search / index crawlers
1 of 2 accessible to scanner
Build the search index AI assistants query when answering. Allowing these is what makes a publisher AI-citation-eligible.
1 declared allowed in robots.txt — scanner observed a 4xx. We can’t verify what real bots see from outside; the publisher edge logs are ground truth.
oai_searchbot429
robots.txt: allowed · scanner: blocked
claude_searchbot200
User-initiated fetchers
3 of 3 accessible to scanner
Fetch a specific page when a user shares it in chat. Allowing these lets users reference your content in AI conversations.
chatgpt_user200
claude_user200
perplexity_user200
Training-data crawlers
4 of 6 accessible to scanner
Build training datasets. Blocking these is the lawsuit-safe posture — does not affect AI citation eligibility.
2 declared allowed in robots.txt — scanner observed 4xx. We can’t verify what real bots see from outside; the publisher edge logs are ground truth.
gptbot200
claudebot200
perplexitybot200
ccbot429
robots.txt: allowed · scanner: blocked
google_extended429
robots.txt: allowed · scanner: blocked
applebot_extended200
Traditional search engines
3 of 3 accessible to scanner
Bingbot, Googlebot, Applebot — not AI-specific.
bingbot200
googlebot200
applebot200
Raw fetch detail (status, bytes, timing)
Identity
Status
Bytes
Blocked?
Timing
gptbot
200
605,629
no
867ms
chatgpt_user
200
605,629
no
756ms
oai_searchbot
429
1,168
yes
694ms
claudebot
200
605,629
no
684ms
claude_user
200
605,629
no
693ms
claude_searchbot
200
605,629
no
593ms
perplexitybot
200
605,629
no
527ms
perplexity_user
200
605,629
no
575ms
googlebot
200
605,629
no
419ms
google_extended
429
229
yes
392ms
bingbot
200
605,629
no
464ms
applebot
200
605,629
no
389ms
applebot_extended
200
605,629
no
372ms
ccbot
429
229
yes
206ms
human
200
605,629
no
199ms
robots.txt policy per AI bot
CCBot: allowed
GPTBot: allowed
Bingbot: allowed
Applebot: allowed
ClaudeBot: allowed
Googlebot: allowed
Claude-User: allowed
ChatGPT-User: allowed
OAI-SearchBot: allowed
PerplexityBot: allowed
Google-Extended: allowed
Perplexity-User: allowed
Claude-SearchBot: allowed
Applebot-Extended: allowed
Render risk — what AI bots can actually parse
100/100
Low — AI bots receive most of the text content
FrameworkWordPressHydration gap0%
No render-risk signals triggered. AI bots receive substantially the same content as humans.
What AI bots are missing
1
images missing
rendered 55 · bot 54
JSON traps — where the missing content is hiding
Found 1 large script-tag JSON blob (1.8 KB of serialized data total). AI crawlers do not evaluate JavaScript or parse arbitrary inline state — content stored in these blobs is invisible to GPTBot, ClaudeBot, and the other AI indexers, even when the rest of the page renders correctly for humans.
