The steps
- Proposed. A fix from a report, the AI Plan, a tool or a person creates a change. It waits in Act → Changes. Nothing is sent yet.
- Preview. SEOmise reads the current values from your site through the connector and shows Now and After for each page. Refresh preview reads them again.
- Approve. Someone whose role allows it presses Approve, or Dismiss to turn it down.
- Publish. Publish to site sends the change. It is signed with SEOmise's key, and your site checks the signature before applying anything. Each command is applied only once, even if it is sent again.
- Verify. SEOmise checks the live page.
- Live. The change passed its checks.
Each change tells this story under What happened: who proposed it and from which tool, who approved it, how many items your site saved ("Your site saved 17 of 17"), how many the live page shows, and whether the change was kept or undone and why.
The list filters by state: Open (everything still in progress), Proposed, Approved, Verifying, Live, Failed, Rolled back or All. A change your site saved but the live page does not show yet is Saved, not visible yet.
How SEOmise checks the change is live
- Straight after publishing, your site's connector reads back what it saved. If that does not match, the change is rolled back by itself.
- SEOmise then opens the public page, skipping caches, and checks what the change touched: the title, description, canonical address, robots tag, structured data, links, new text or new pages.
- If a page cache still shows the old page, the change stays Verifying and is checked again after 15 minutes.
- If it is still not visible then, but your site confirmed it saved the change, what happens depends on the kind of change (a setting your platform admin can change):
- Titles and descriptions, image alt text, structured data, sharing tags, internal links and page text are kept. The change shows Saved, not visible yet, SEOmise checks the page again every hour for three days, and you can press Clear cache and check again or Undo.
- Redirects, robots.txt rules and noindex are undone automatically, because they can hide pages or send visitors elsewhere.
- Your platform admin can also choose Ask: the change is kept and the screen asks you to Keep it or Undo.
- A change your site did not confirm is still undone automatically.
- An hour after it went live, a last check looks again. If the change is no longer there, it is marked Needs checking and the people who asked for it and approved it get an e-mail. This check never rolls anything back.
Why an item is not on the live page yet
On the live page lists every item with its status and what to do:
- Visible on the page. Done.
- Saved, waiting for the cache. Your site saved it, but a cache still serves the old page: a cache plugin, your host's cache, a CDN, or Elementor's stored copy of the page (Elementor keeps one for up to 24 hours unless you changed that). Press Clear cache and check again, or wait.
- Placed by your page builder. The picture sits in a part of the page your page builder (Elementor's text editor, Divi, WPBakery and others) or a slider keeps its own alt text for. Open the page in the builder, select the picture and add the alt text there; SEOmise checks again.
- Placed by your theme or a widget. The picture is chosen in your theme's or a widget's settings (a logo, a header picture). Add the alt text there.
- Not found on the page. The picture was not on the page checked: it may be loaded by a script (a slider or a gallery), shown as a background, or have moved to another page.
SEOmise finds each picture by its media library number on the page, or by its file: the sizes, WebP copies and CDN addresses of the same file count.
Clear cache and check again
With the WordPress connector, SEOmise clears the page caches it can find for the pages of the change (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache and Elementor's stored copies) and checks again. It does this by itself after every change too. With a CDN connection (Cloudflare, under CDN and edge), it also asks for a purge of those addresses, which waits for approval there. The Laravel connector tells your app to clear its own page cache. On other platforms, or with an older connector, the screen gives the steps to clear the cache by hand, then press Check again. You can clear the cache a few times an hour.
Press Check again to check now. The raw checks, the commands sent to your site and the audit trail are under Technical details.
What you need
- A site connector paired under Settings → Connect your website → Site connector.
- A plan with direct publishing. Without it, you can preview and approve changes but not publish them.
- The site owner must allow that kind of change in the connector's settings.
Without a connector, SEOmise prepares the fix for you to make by hand instead.
Not what you needed? Ask Mise or contact support.
