Why did my change fail or get rolled back?

Find the reason

1. Open Plan & changes → Changes and choose Failed or Rolled back.
2. Open the change. The reason is in the red notice at the top.
3. Verification shows what SEOmise checked on the live page, and Connector commands shows what your site answered.

Common reasons

• The public page did not show the change. A page cache or CDN kept the old page past the follow-up check, 15 minutes later. SEOmise rolled the change back. Clear the cache, or set it to refresh sooner, then propose the change again.
• The site did not keep the change. The connector's read-back did not match, so SEOmise rolled it back straight away.
• The text was edited on the site. Someone changed the same text after SEOmise read it, so the site refused to overwrite it. Press Refresh preview and try again.
• The site has not allowed this kind of change. The site owner can allow it in the connector's settings on the site.
• Your connector cannot do this yet, or is too old. The change says which version you need. Update the connector, or make the change by hand.
• No connector is paired. Pair one under Settings → Site connector.
• Your plan does not include direct publishing. You can preview and approve changes, but not publish them.
• Your role cannot publish. Someone with the owner, admin or SEO manager role publishes it.
• The site could not be reached. SEOmise tries again several times before it gives up.

Publishing again

If nothing reached your site, press Try publishing again. If part of the change reached your site, roll it back first, then propose it again.

E-mails

When a published change is rolled back, cannot be rolled back, or is later found to be no longer in place, the person who asked for it and the person who approved it get an e-mail. If nothing reached the site, there is no e-mail: the list shows it.

"Needs checking"

A change that passed but is gone an hour later is marked Needs checking. SEOmise does not undo anything then. Check whether someone changed the page, or whether another plugin or setting overrides it.