Cleo Orbit

Orbit is the client workspace for Cleo’s done-for-you service: Cleo prepares work, you review it, and approved work is published to its configured destination.

​

How Orbit works

​

Orbit sections

​

Statuses you will see

• Needs approval: your decision is required.
• Being written: work is in progress.
• To publish: approved and queued for delivery.
• Live: we wrote the change and then loaded your public page to confirm visitors see it. For a change across several pages, the status says how many show the change, for example Live on 8 of 10 pages. Open the item to see which pages did not change and why. We only email you that a change is live once every page shows it.
• Saved, not yet confirmed live: the change was saved, but we could not confirm it on the live page. That can happen when the page did not load for us, or for a kind of change we cannot check yet.
• You said no: declined by an approver.
• Not published: delivery failed or was stopped; open the item for the reason.

Orbit applies site changes through WordPress, or as a pull request on a connected code repository for a site not on WordPress. If Orbit is set up only for site changes and neither is connected, the Awaiting tab says so and nothing arrives until you connect one. Orbit cannot be switched on in that state.

​

If your website blocks Orbit

A firewall, security plugin or hosting rule can block Orbit’s server. When that happens, a banner on the Overview and SEO tabs says what is wrong, the date it started, how many approved changes are waiting, and exactly what to ask your developer for. Your approvers also get one email.

• Your website’s firewall is blocking Orbit: Orbit cannot read your pages. Ask your developer to allowlist the address shown in the banner.
• Your site lets Orbit read pages but refuses changes: ask your developer to allow PUT requests to /wp-json/code-snippets/ from the address shown.
• Your site is limiting how fast Orbit can read it: ask your developer to exempt the address shown from rate limiting.

While reads or changes are blocked, Orbit sends no new suggestions and holds the changes you have already approved (nothing is lost, and nothing is marked as failed). Once your site lets Orbit in again, the banner clears and the held changes are applied by themselves, usually within the hour. You do not need to tell us. Some heading problems come from a part of your site that repeats on every page, such as footer column titles coded as headings, or a hidden fallback block (noscript) that carries your homepage’s headings on every route. Orbit does not propose page-by-page changes for these, because the fix is made once in your site’s layout. When the pages our audit flagged share such headings, the Awaiting tab shows one note naming them. It goes away once a later audit finds them fixed. Images work the same way. Orbit only offers image descriptions for images in a page’s own content. An image that sits only in your site’s header or footer, such as a floating call or WhatsApp button, is shown on every page, so Orbit does not change it page by page. When two or more of the pages our audit flagged show such an image without a description, the Overview tab shows one note naming them, and you add the description once in your site’s layout. A page counts as live when the images in its own content show their new descriptions.