Skip to main content
For supported JavaScript and Sanity sites, Cleo can move from identifying a problem to preparing a code change. The Operations section appears only when the active site supports this workflow.

​
Remediation

The remediation workspace connects Cleo’s findings to the fields or files that control the site. Depending on the site, it can help with titles, descriptions, canonicals, structured data, image text, headings, redirects, and new pages.
1

Connect the site

Open Integrations and connect GitHub, GitLab, or Sanity as required for the site.
2

Review detected mappings

Cleo proposes where each SEO concept lives. Confirm the document type and field path before enabling writes.
3

Prepare a fix

Open a supported finding, review the current and proposed value, and choose the repository-backed fix path.
4

Verify and submit

Cleo runs the available preflight and build checks, then opens a pull or merge request for review.

​
CI Cleo

CI Cleo explains how Cleo verifies a change before it becomes a pull or merge request. It can show the verification level available to the connected project and recent results. Verification may include:
  • Schema and mapping checks
  • File and route validation
  • Project build or test commands
  • Rendered-output checks for supported changes
  • A final report attached to the proposed change
A passing Cleo check does not replace your team’s normal code review, staging review, or deployment controls. Review the diff and the affected page before merging.

​
When Operations is absent

The site may use a CMS flow instead, may not have a connected repository, or may not support code-backed remediation. You can still use the SEO tool’s recommendation, create a Task, or apply the change manually.