Faro AI Signals·July 12, 2026

Anthropic MCP Goes GA, Perplexity Adds Buy Buttons: AEO Inflection Week

Two converging signals this week: Anthropic's Model Context Protocol reached general availability with a wave of commercial integrations, and Perplexity's in-answer commerce layer began serving transactional results to a broader user base — meaning AI assistants are now both finding and closing business. For operators not yet structured for agent consumption, the gap between visible and invisible just got measurable.

ShareShare

This Week's Signals

1

Anthropic MCP Hits General Availability With Stripe, Shopify, and Salesforce Native Connectors

Source: Anthropic ↗

Why it matters for your score

MCP GA means Claude agents can now query, act on, and transact with business systems without custom integration work — but only for businesses that expose MCP-compatible endpoints. If your product catalog, booking system, or pricing data isn't surfaced through an MCP server or equivalent agent-facing API, you are structurally invisible to this entire class of autonomous buyer. The Stripe connector in particular means agent-initiated purchases are no longer experimental; they are in production for any merchant already on Stripe.

2

Perplexity's 'Buy With Pro' Commerce Layer Expands to All Pro Users in US and UK

Source: Perplexity AI ↗

Why it matters for your score

Perplexity is now surfacing purchasable product cards directly inside answers for millions of Pro subscribers, drawing from merchant feeds and structured product data. Businesses without clean JSON-LD Product schema — including Offer, price, and availability fields — are being skipped in favor of competitors whose data is machine-readable. This is the first major AI assistant to make purchase intent and structured data eligibility directly correlated at scale.

3

Google's Search Liaison Confirms AI Overviews Cite Sources With 'Entity Completeness' as a Ranking Factor

Source: Search Engine Roundtable ↗

Why it matters for your score

Google has now explicitly tied AI Overview citation likelihood to what they are calling 'entity completeness' — the degree to which a business's structured data across its own site, Google Business Profile, and third-party knowledge sources presents a consistent, machine-resolvable entity. Businesses with schema gaps, mismatched NAP data, or no Organization/LocalBusiness JSON-LD are measurably less likely to be cited. This closes the loop between traditional structured data hygiene and AI-era discoverability — they are the same problem.

What to do this week

  1. 1

    Run your site through Faro's AI Readiness Scan (/tools/ai-readiness-scan) this week specifically looking at your Organization and Offer schema completeness — Google's entity completeness signal and Perplexity's product card eligibility both key off the same JSON-LD fields. Fix any missing 'priceValidUntil', 'availability', or 'sameAs' properties before next crawl cycles.

  2. 2

    If you are on Stripe or Shopify, register your business endpoint in Faro's MCP exposure checker and use the agent-facing API guide to determine whether your product or service data is reachable via MCP-compatible calls — Anthropic GA means Claude agents are actively traversing these connections now, not in a future beta.

  3. 3

    Generate or update your llms.txt file via Faro's tool (/tools/llms-txt) to explicitly declare your pricing structure, service categories, and geographic coverage in plain machine-readable terms — Perplexity's commerce expansion and Claude's MCP connectors both benefit from an accurate llms.txt as a low-latency index of what your business offers before an agent decides whether to go deeper.

Sources

← All editionsScan your site now →