Agility CMS Integration
Connect Agility CMS to Cleversearch for headless content publishing with custom content model mapping.
Overview
The Agility CMS integration connects Cleversearch to your headless CMS for seamless content publishing. Unlike traditional CMS platforms, Agility uses flexible content models that let you define your own content structure. Cleversearch adapts to your models dynamically, mapping generated content fields to your specific Agility schema.
This integration supports Agility's built-in approval workflows, allowing you to push content as drafts, publish immediately, or submit for editorial approval depending on your team's process.
Prerequisites
Ensure these are ready before connecting Agility CMS.
Setup Steps
Connect Agility CMS to Cleversearch step by step.
Content Model Mapping
Cleversearch reads your Agility content model definitions and presents each field for mapping. You assign Cleversearch content roles (Title, Body, Excerpt, Featured Image, SEO Title, SEO Description) to the corresponding fields in your Agility model. Fields without a mapping are left empty during publishing.
If you update your Agility content model later, revisit the integration settings to remap any new or changed fields. Cleversearch will detect structural changes automatically.
Publishing Workflows
Choose the workflow that matches your editorial process.
Security
Publishing authorization uses OAuth 2.0, ensuring your Agility credentials are never stored in Cleversearch. Your API key and GUID are encrypted at rest and used only for content model discovery. You can revoke access at any time from either the Cleversearch integration settings or your Agility dashboard.
Frequently Asked Questions
Cleversearch supports both US and Canada regions for Agility CMS. Select your region during the connection setup to ensure API calls route to the correct data center.
Both are supported. The Fetch API provides published content, while the Preview API includes draft and unpublished items. For the integration to work properly with content creation, the Preview API is recommended.
Cleversearch reads your Agility content model definitions dynamically. Whatever fields you have defined in your model will appear in the field mapping step. This means the integration adapts to your specific content structure rather than requiring a fixed schema.
If content is rejected in Agility's approval workflow, it remains as a draft in Agility. Cleversearch shows the publish status as pending. You can edit the content in Agility directly or regenerate it in Cleversearch and republish.
Each Cleversearch site connects to one Agility instance. If you manage multiple Agility instances, create separate Cleversearch sites for each and configure the integration independently.
Additional Guidance
Use this checklist to improve reliability and performance for this area.
Execution Phases
Week 1: Foundation
Finish installation and validate data flow.
Output: Connected tracker, imported sitemap, baseline analysis report.
Week 2: Prioritization
Select high-impact pages and define task backlog.
Output: Prioritized optimization list with owners and due dates.
Week 3-4: Iteration
Ship updates and verify score + business impact.
Output: Before/after snapshots with measurable deltas.
Common Mistakes
Success Metrics
Analyzed Coverage
>= 90% priority URLs analyzed monthly
Ensures optimization decisions are based on current data.
Score Movement
+8 to +15 points on target templates in 30-60 days
Validates that executed recommendations are improving quality.
Execution Velocity
At least 1 improvement cycle per week
Creates compounding gains from consistent iteration.