Platform field guides
AI search optimization happens in your actual website builder.
The useful fix is different on a Framer CMS page, a Shopify product, and a WordPress service page. Choose your platform for specific editing steps, constraints and evidence to keep after publishing.
Updated
What all five workflows share
Check what the live page serves, make it answer one real buyer question, keep markup consistent with visible facts, publish through the platform’s normal review path, then save actual search and AI-answer evidence. An accessible page is eligible for consideration; it is not a guaranteed recommendation.
Choose your platform
Framer SEO for AI Search: Pages, Schema and Crawl Checks
A practical Framer AI search checklist: inspect the published HTML, make your offer explicit, add page-specific JSON-LD and verify the live result.
Read the guide 02 / WebflowWebflow AEO: Improve AI Search Visibility in the Designer
Work through Webflow's page settings, Collection schema, sitemap and staging publish before measuring AI mentions and citations.
Read the guide 03 / WordPressWordPress AI SEO: Audit Indexing, Pages and Schema
A WordPress AEO workflow for diagnosing indexing settings, conflicting plugins, page copy and the live schema that search systems actually receive.
Read the guide 04 / ShopifyShopify AEO: Make Products and Collections Clear to AI Search
Audit Shopify product, collection and comparison pages, check existing theme schema and test changes safely on a duplicate theme.
Read the guide 05 / WixWix AEO: Edit the Page AI Search Can Actually Read
A Wix AI SEO guide covering visible service content, SEO & GEO settings, JSON-LD limits, collaborator access and live-page verification.
Read the guideHow to use these guides
Start with one important URL and one buyer question. The platform guide shows where to inspect and change that page; our AI search workflow covers the broader research method. Use the free HTML checker to inspect served content, then record mentions and citations separately. These guides are editorial instructions, not claims about a connected platform API.