cZgiv09RetB ↗

2026-05-29 00:22 UTC · ready · vertical: product · schema score: 0/100

Can IA help — https://stocktwits.com/news-articles/markets/equity/path-stock-slips-after-hours-on-q1-earnings-miss-but-q2-and-full-year-guidance-beats-expectations/cZgiv09RetB?

Yes — quickly

Yes — quickly. AI already reads your content; the gap is that your commerce isn't legible or attributed. That's exactly what IA injects at the edge — typically a zero-dev-lift deploy.

Are AI bots reaching you? AI search bots can reach your content — you're eligible to be cited.

Are your links coming through? Your content is read, but your commerce links aren't coming through: commerce data trapped in __NEXT_DATA__.

Implementation friction: Low — you're on Cloudflare, so IA deploys via an edge connector with no changes to your site.

Next step:Introduce us to your SEO / dev teamBook a 20-min intro call

Summary

The page is a financial news article about PATH stock earnings performance with no product offers or pricing information present. The structured data layer includes NewsArticle, Organization, and Person schemas but lacks all commerce-oriented types—Product, Offer, Review, AggregateRating, and BuyAction are absent, which is expected given the article's editorial focus rather than transactional intent. Citation bots can reach and cite the page by URL; both explicit mentions resolved to the source. The enrichment layer would make ticker symbol, earnings metrics, and guidance figures machine-readable as structured claims tied to a financial instrument entity, allowing downstream systems to infer relationships between the news event, the underlying security, and market-moving data without requiring human extraction.

Citation bots reachable — oai_searchbot, claude_searchbot

This URL is reachable by the AI search indexes that drive live citations. Enrichment (next panel) is applicable here.

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

Offers detected (0)

none

In the JSON-LD layer

Types present (9)

BreadcrumbList, ContactPoint, ImageObject, ListItem, NewsArticle, Occupation, Organization, Person, WebPage

Commerce types present

none

Commerce types missing

Product, Offer, AggregateOffer, BuyAction, Review, AggregateRating

The gap

Offers visible to humans0

Offers in machine-readable form0

Click-throughs wrapped as BuyAction0

AI bot — with IA enrichment

IA enrichment adds (derived from existing page content)

Page already has explicit commerce schema — no enrichment delta to add.

Result for AI extractors

A bot fetching the URL pulls all 0 offers from JSON-LD in microseconds — no LLM inference, no prose parsing, no guessing at which discount applies.

View IA-rendered flattened HTML

PATH Stock Slips After-Hours On Q1 Earnings Miss, But Q2 And Full-Year Guidance Beats Expectations — Stocktwits

View IA-generated JSON-LD @graph

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "NewsArticle",
      "headline": "PATH Stock Slips After-Hours On Q1 Earnings Miss, But Q2 And Full-Year Guidance Beats Expectations",
      "url": "https://stocktwits.com/news-articles/markets/equity/path-stock-slips-after-hours-on-q1-earnings-miss-but-q2-and-full-year-guidance-beats-expectations/cZgiv09RetB",
      "publisher": {
        "@type": "Organization",
        "name": "Stocktwits"
      }
    }
  ]
}
</script>

Surface — do AI models cite this publisher?

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

Edge / CDN: cloudflare· cf-ray header · server: cloudflare · cf-cache-status header

Search / index crawlers

2 of 2 accessible to scanner

Build the search index AI assistants query when answering. Allowing these is what makes a publisher AI-citation-eligible.

oai_searchbot200

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

6 of 6 accessible to scanner

Build training datasets. Blocking these is the lawsuit-safe posture — does not affect AI citation eligibility.

gptbot200

claudebot200

perplexitybot200

ccbot200

google_extended200

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	286,795	no	1116ms
chatgpt_user	200	286,775	no	1650ms
oai_searchbot	200	286,099	no	1114ms
claudebot	200	286,822	no	1663ms
claude_user	200	286,795	no	1405ms
claude_searchbot	200	286,775	no	861ms
perplexitybot	200	286,795	no	1480ms
perplexity_user	200	286,795	no	1376ms
googlebot	200	286,805	no	1257ms
google_extended	200	286,795	no	920ms
bingbot	200	286,807	no	1267ms
applebot	200	286,796	no	1212ms
applebot_extended	200	286,795	no	1119ms
ccbot	200	286,795	no	797ms
human	200	286,821	no	953ms

robots.txt policy per AI bot

CCBot: disallowed

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: disallowed

Render risk — what AI bots can actually parse

75/100

Moderate — significant content trapped behind hydration

FrameworkNext.jsHydration gap28%

Hydration gap: 28%
AI bots see 72% of the rendered content. The remaining 28% loads via client-side JavaScript and is invisible to crawlers that don't execute JS.
Large JSON-in-script payload (141 KB)
Content trapped in <script type="application/json"> blobs that AI bots don't execute.

What AI bots are missing

links missing

rendered 99 · bot 55

paragraphs missing

rendered 39 · bot 12

list items missing

rendered 21 · bot 6

images missing

rendered 45 · bot 42

headings missing

rendered 5 · bot 4

Sample content only humans see:

“©2026 StockTwits, Inc. All rights reserved.Market Data by Xignite and BATS BZX Real-Time Price. Futures data provided by Barchart Solutions. Overnight pricing provided by Blue Ocean Technologies LLC. Earnings Call Data by Quartr. Crypto data provided by Coingecko. Earnings Summary data by Fiscal.ai”
“Stocktwits, Inc. (“Stocktwits”) is not a securities broker-dealer, investment adviser, or any other type of financial professional. No content on the Stocktwits platform should be considered an offer, solicitation of an offer, or advice to buy or sell securities or any other type of investment or financial product.”
“By using the Stocktwits platform, you understand and agree that Stocktwits does not provide investment advice, recommend any security, transaction, or order, issue securities, produce or provide research. For additional disclosures, please see here.”

JSON traps — where the missing content is hiding

Found 2 large script-tag JSON blobs (137.1 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. At least one blob contains commerce data — product, price, or offer fields trapped where bots can’t reach.

window.mParticlecustom

3.6 KB of serialized data

__NEXT_DATA__next.js

133.5 KB of serialized data

Commerce data detected — keys present: price

Top-level keys: props, page, query, buildId, assetPrefix, isFallback, isExperimentalCompile, dynamicIds · +2

Schema audit

0/100

Present · 9

BreadcrumbListContactPointImageObjectListItemNewsArticleOccupationOrganizationPersonWebPage

Missing · 5

ProductOfferReviewAggregateRatingBuyAction

Rubric breakdown (0 of 5 criteria met)

✗Offer	0 pts
✗Review	0 pts
✗Product	0 pts
✗BuyAction	0 pts
✗AggregateRating	0 pts

potentialAction — commerce paths

⚠ No commerce-action schema present — AI has no canonical path back to this publisher.

Present · 0

(none)

Missing · 1

BuyAction

Affiliate footprint

No affiliate links detected in the page's raw HTML.