Changes to live pages

#Why live changes are different

A draft can be changed freely: nobody sees it yet. A published page is different. A wrong word on it is seen by every visitor, and a broken title or a lost canonical address can cost you in search. So when Rekhu Builder changes a page, post or product that is already live, it follows a fixed set of steps, and you can always go back.

#What happens on every live change

1. Rekhu asks first. It says what will change on which page, and waits for your yes. For a big batch, such as the SEO titles of 80 pages, it asks once for the whole batch, not page by page.
2. The site saves the page. Before the first change of a message, the plugin saves the page as it is: its texts, SEO fields, Elementor data, page template and terms. A picture whose alt text changes is saved the same way, because its alt text shows on every page that uses it. For a WooCommerce product, its price, sale, stock and SKU are saved too, and put back through WooCommerce, so the shop shows the right price everywhere after an undo. A saved page or picture is kept 30 days.
3. The change is made where the text is. A text on the page, such as a sentence, a name, a price or a phone number, is replaced only when it is found exactly once. Found nowhere or found more than once, nothing changes, and Rekhu sees every place it was found so it can be more precise.
4. Caches are emptied. Elementor's CSS for that page, the object cache, and the page caches of LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache and SiteGround Optimizer when they are active. Visitors get the new page at once.
5. The live page is checked. Rekhu opens the page as a visitor gets it, before it answers you.
6. The change is logged on the project's Activity tab, with an undo.

#Changes made outside a chat

Publishing from the account is a live change too: an article or page published from the Article maker (also by the publishing rhythm), a refreshed page, or a draft published from Chat → Drafts. Each is logged on the Activity tab under what it was, such as Draft published: Our prices, with who did it, checked on the live page in the background, and can be undone. Undoing a publish takes the page back to a draft; undoing a refresh puts the earlier text and SEO fields back.

#What the check looks at

When a check fails, Rekhu tries to fix the page, or puts it back, before it answers; at most twice. What is still wrong after that is said plainly in the answer, with what you can do. Rekhu never says a change is done while a check fails.

Note: a description, canonical, index or sitemap problem that was already there before the change, and that the change did not touch, shows as a warning, not as a failure.

#The Activity tab

The project's Activity tab starts with Changes to live pages: every change Rekhu made to a published page, newest first. Changes are grouped by the message that made them. Each one shows:

• the page and its address;
• what it was before and what it is after;
• the result of the check on the live page, or "Not checked yet".

Below it, Activity lists everything else Rekhu changed on the site: drafts, plugins, settings, form entries.

#Undo a change

A change can be undone for 30 days. The page goes back to how it was before that message.

1. Open the Activity tab of the project.
2. Find the change under Changes to live pages.
3. Choose what to put back.
   • Undo this change puts back one page.
   • Undo everything this message changed puts back every page one message changed.
4. Confirm with Yes, undo.

An undo is a change like any other: the site saves the page first, so the undo can be undone too, and the live page is checked again. The page says how many pages are back as before, and what the check found.

Undo needs manage access to the project and Rekhu Builder 0.9.56 or later on the site.

#Your switch for asking first

Ask before changing a published page under Preferences → Safety is on by default. With it on, drafts change at once and a live page only after you agree. Next to it you can name Pages to leave alone: they are never changed, trashed or unpublished.

A client changes a live page only with the right Change existing live pages. See Clients.

A schedule changes the live site only when you set it up to. See Schedules.

#Nothing is claimed that did not happen

Rekhu changes a site only through its tools, and every tool call is logged. When an answer says work was done but no tool ran in that turn, Rekhu gets one more round to really do it. If still no tool ran, the answer ends with a plain note: nothing on the site was changed, and you can say "do it" to have it done.

#Next

• Drafts and publishing: new pages go live the other way, from a draft.
• Schedules: what a job that runs on its own may change.