Audit your site with an agent

The chat can audit your site, not just change it. The Sage CMS Operations Auditor pairs the Marketer MCP with a custom MCP — a "Sage workshop preview fetch" tool that pulls the rendered HTML of each page's preview. That lets it check what actually ships (markup, structured data), not just the CMS fields.

1. Select the agent

In Agents (or the Chat), select Sage CMS Operations Auditor. It already has the custom preview-fetch MCP attached as a Skill, alongside the Marketer MCP — so it can list pages, resolve preview URLs, and fetch the live HTML.

2. Run an audit

Ask it to check the site for a specific issue. Try:

Prompt

Show me all pages missing FAQ schema and recommend fixes.

Expect: it lists the site's pages, fetches each page's preview HTML, checks for FAQPage JSON-LD, then reports which pages have it and which are missing it — with concrete fix recommendations.

3. Read the report — and its caveats

A good audit is honest about coverage. The agent:

plans the work as to-dos (scope the pages → fetch & check HTML → summarize),
separates pages that have the schema from those missing it,
recommends page-appropriate fixes — e.g. add a FAQPage JSON-LD block built from a landing page's FAQ fields, but don't force FAQ schema onto an article that has no FAQs,
and flags partial coverage — if it only sampled some pages, it says so and offers to finish the rest.

Note

The auditor reports and recommends — it doesn't change pages. Apply the fixes with the editing agents (or by hand), then re-run the audit to confirm.

Tip

Reuse the same fetch-and-check pattern for other audits — "pages missing a meta description", "images without alt text", "meta titles over 60 characters".

References: Marketer MCP · Agent skills · Understanding agents