What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
AI Assistants
A step-by-step recipe with prompts to paste: have an AI assistant run a read-only audit for empty descriptions, missing alt text, stale content and suspect links, then fix issues in reviewed batches.
Before a redesign, a migration, an accessibility push or just a spring clean, it helps to know what state your content is in. An AI assistant connected to Agility can read through your content lists and pages and report on what's missing or out of date, without changing anything.
If you haven't connected an assistant yet, start with Using AI Assistants with Agility CMS.
A clear, shareable report of content that needs attention:
The audit is read-only. You decide what to fix afterwards, and fix it in small, reviewed batches.
Start by asking the assistant what it can see, so the audit covers the right lists:
In the [instance name] Agility instance, [en-us] locale, list the content
lists and how many items each has, and list the sitemaps.
This is a read-only audit: don't save, publish or delete anything.
Pick the lists that matter. Lists your developers use for settings or navigation usually don't need auditing.
Paste this, editing the lists and the date:
Read-only audit. Don't save, publish or delete anything.
In the [instance name] instance, [en-us] locale, check the [Blog Posts],
[Case Studies] and [Resources] content lists, and the pages on the [website]
sitemap. For each, report:
1. Empty descriptions: items with an empty summary or SEO description field,
and pages with an empty Meta Description.
2. Missing alt text: image fields with no alt text, and images in rich text
with an empty or missing alt attribute.
3. Stale content: items last modified before [January 1, 2025].
4. Links: every link in rich text and link fields that points to a page path
that isn't on the sitemap, and every external link, grouped by domain.
Give me one table per check with: item or page name, content list, the field,
the problem, and a link to open it in Agility. Finish with a summary count.
Large lists take a while. If the assistant stops part way, say "Continue from where you stopped."
In plain words, behind the scenes:
get_available_instances, get_locales, get_containers).get_content_model_details).get_content_items, get_content_item). Each item comes with its last modified date and who changed it.get_sitemap, get_page), including each page's SEO fields.The Agility tools can read your links but can't visit them, so be clear about what the link check means:
~/). The assistant can compare these with the page paths on your sitemap and flag any that don't match a page. That catches most links to renamed or removed pages, but some may be valid routes your developers handle outside the sitemap, so check before you change them.Once you've reviewed the report, fix one kind of problem at a time, with a show-before-save step:
Every fix the assistant saves lands in Staging for you to review and publish, as usual, unless your organization has set that content up for autonomous publishing.
list_media.publish_content, and send the rest of the report to your team. The audit step itself stays read-only. See Choose how much the assistant does.