AI & Emerging Tech
The same Core dna MCP works with ChatGPT, Claude, Gemini, Copilot, and Cursor. Connect whichever your team already uses.
Yes. Once connected, ChatGPT can update pages, refresh content, fix SEO, and manage your existing Core dna site through conversation.
Not for everyday work. The person who wants a change makes it by describing it. Developers get their time back for what genuinely needs engineering.
Always. Changes land as drafts on your real Core dna site, so you can fine-tune them in the editor, ask for more changes, or roll back, all before publishing.
Yes. ChatGPT acts inside your roles and permissions, every change lands as a draft for approval, and everything is versioned and logged. You can preview, diff, and roll back before anything goes live.
Add Core dna as a connector in ChatGPT, then authorize it with your existing Core dna login. ChatGPT's setup has a few more steps than Claude's (you turn on developer mode and add the connector), but it's all clicks, no code.
Want the exact steps? See the full setup guide.
The same Core dna MCP works with Claude, ChatGPT, Gemini, Copilot, and Cursor. Connect whichever your team already uses.
Yes. Once connected, Claude can update pages, refresh content, fix SEO, and manage your existing Core dna site through conversation.
Not for everyday work. The person who wants a change makes it by describing it. Developers get their time back for what genuinely needs engineering.
Always. Changes land as drafts on your real Core dna site, so you can fine-tune them in the editor, ask for more changes, or roll back, all before publishing.
Yes. Claude acts inside your roles and permissions, every change lands as a draft for approval, and everything is versioned and logged. You can preview, diff, and roll back before anything goes live.
No. Add Core dna as a connector in Claude, sign in with your existing login, and approve. No code, no config files, no IT ticket. If you can describe what you want, you can build it.
Want the exact steps? See the full setup guide.
Short answer: AI shopping agents don't browse your site the way people do — they query structured data, ingest feeds, and increasingly call APIs to evaluate and transact. To be discoverable you have to make your catalog machine-readable (structured data), reachable (feeds and APIs pushed to the surfaces agents use), and trustworthy (accurate, fresh, well-reviewed). Get those three layers right and your products enter the agent's consideration set; skip any of them and you're simply invisible on the fastest-growing discovery channel in retail.
This is now a revenue question, not an IT-backlog one. Adobe's reporting showed AI-driven traffic to retail sites grew roughly sevenfold over the 2025 holiday season, and by early 2026 AI-referred shoppers were converting better than traditional traffic — a reversal from a year earlier, when the same cohort converted worse. The gap between merchants whose catalogs are agent-ready and those who aren't is widening fast.