unknown

AI crawlers are reshaping how content gets discovered, and most CMS implementations built for traditional SEO aren't ready. This covers 15 practical changes needed at the content model, template, and server configuration level to support Generative Engine Optimisation (GEO) and Answer Engine Optimisation (AEO). Key points include: server-side rendering is non-negotiable since most AI crawlers don't execute JavaScript; schema markup must be generated from the content model and output server-side; FAQ and Q&A fields should be added to multiple page types; visible page summaries near the top improve AI citation rates; accurate lastmod dates in sitemaps affect AI crawl prioritisation; and robots.txt must distinguish between training crawlers and inference retrieval agents. Code examples use Optimizely CMS (C#) but the principles apply to any platform. A prioritised checklist is provided for both new builds and existing implementations.