Scrunch’s Agent Pages approach is fundamentally different from publishing AI-friendly content directly in a CMS because it optimizes content for AI without touching the live website. The CMS stays the same; Agent Pages simply creates an AI-friendly layer on top of what already exists.

Additional context: Agent Pages doesn't publish new content. Instead, it creates an AI-optimized version of existing pages and automatically delivers them to AI agents at the edge.

Example

For example, a user deploying content via Agent Pages and a CMS would follow two very different workflows:

CMS workflow:

• User creates content in CMS and manually structures it for AI readability.
• User publishes content.
• AI retrieves content from URL.
• AI consumption is limited by JavaScript-heavy website and human-focused layout.

Agent Pages workflow:

• Content is already live on site.
• Agent Pages sits at the CDN layer and automatically detects AI agents.
• Agent Pages serves the content as clean, structured, server-rendered HTML to AI agents.
• Normal website and CMS stay unchanged for human visitors.

Follow-up question: What happens to AI-optimized content if I update a page in my CMS?

If a user updates a page in their CMS, they should apply any necessary updates to the content being delivered to AI via Agent Pages.