WordPress revisions: recover text and keep newer edits

A paragraph disappears from your service page after an update. Yesterday’s version has the missing copy, but it also has your old opening hours and an outdated booking link. Restoring that entire version would solve one problem and bring two others back.

WordPress revisions can help you find earlier page content. For a small repair, use the saved version as a source: recover the passage you need, add it to the current page, and check the result before saving. Start by deciding exactly what should come back.

Write down what the repair must preserve

Here is a fictional example from a home-services website. The owner updated the estimate-request page on Tuesday. On Wednesday, a team member noticed that the explanation of what an estimate includes had disappeared.

Part of the page	Desired result
Estimate explanation	Recover Monday’s paragraph after checking that it is still accurate.
Office hours	Keep Tuesday’s change to 8 a.m.–6 p.m.
Booking button	Keep Tuesday’s new destination and button wording.
Page address and layout	Keep the current URL, headings, images and layout.

This is also a useful handoff to whoever manages the website. “Restore Monday’s page” leaves room for a much larger change than “bring back the estimate paragraph and preserve these three things.” Save a copy of the current content and note the public URL before working through the history.

Find the earlier text in WordPress revisions

Open the page in the WordPress editor. In the Settings sidebar, choose the Page tab and select the number beside Revisions. Browse the saved versions until you find the missing passage.

The screen depends on your WordPress version. WordPress 7.0 introduced a visual revisions screen; older versions use the classic comparison. The classic view is also available from the newer screen and shows HTML differences side by side. The official WordPress revisions guide illustrates both interfaces.

If the loss followed a browser crash before you saved, check any autosave recovery notice too. An autosave is not an unlimited archive: a newer autosave replaces the previous one for that user and page.

Look for the actual words, not just a promising timestamp. In our example, Monday’s paragraph explains whether the estimate visit includes a written quote. Copy that passage into a separate note, record which saved version it came from, and check the wording with the person responsible for the service.

Choose between restoring a version and repairing a section

The Restore control is appropriate when you want the saved revision’s content back as a whole. WordPress’s revision restoration function updates the page from saved revision fields; it does not decide which old sentences should be combined with your latest edits.

For the estimate-page example, return to the current page and insert only the recovered paragraph in its intended position. Keep its links if they are still correct. If you are copying from an HTML comparison, take care to preserve complete block markup; do not paste a fragment of HTML into a normal paragraph block. Use the matching editor block, or ask the site’s editor to handle the markup.

Read the surrounding paragraphs as well. A recovered sentence might now repeat another section or contradict a newer policy. A historically accurate copy is not automatically accurate for today’s business.

Check that you are editing the right content

A standard page revision is not a record of every setting on the site. WordPress includes custom metadata in revisions according to its revision-enabled metadata rules. Do not assume that restoring body text will also restore every plugin field, SEO setting or template.

If the missing text is a homepage headline, first identify where that headline comes from. The page’s stored title and the heading visitors see can be different. Our guide to a WordPress homepage title that will not change explains that distinction.

For an Elementor page, inspect its editor history. Elementor’s history documentation distinguishes actions in the current editing session from saved page revisions. Work through that editor’s page structure instead of treating a builder layout as plain text. For ongoing changes, see our guide to updating Elementor landing pages with Niwa.

Use Niwa for a bounded page update

Once you have found the earlier passage, Niwa can help with the current page edit. Its page tools can retrieve a WordPress page’s stored content and prepare a page update. Availability depends on the site’s enabled tools and permissions. This workflow starts with text recovered from an actual saved version; it does not ask AI to invent what the page used to say.

For a standard WordPress page, give Niwa the verified page ID, the recovered passage and the placement. A request can be as specific as:

Read the current estimate-request page using the page ID I provided. Prepare a change that inserts the recovered paragraph below “What happens at the visit.” Preserve the current office hours, booking link, title, URL and every other section. Show the proposed change for approval before applying it.

Include the exact recovered passage with that request. Niwa’s standard content update supplies the page’s content field, so the proposed content must preserve the rest of the page. Review the complete result before authorizing the change; a short instruction to “add this paragraph” is not itself proof that every other block stayed intact.

After the update, read the saved page again and open its public URL on desktop and mobile. In this example, check the restored explanation, the 8 a.m.–6 p.m. hours and the booking button’s destination. Also check the paragraph above and below the insertion for duplicated text or broken formatting.

What if the revision you need is missing?

First confirm that you opened the correct page and editor. Then ask the site maintainer about revision retention. WordPress’s revision retention rules allow limits and depend on revision support for the content type. Changing a limit now does not recreate history that was never saved or has already been removed.

A backup may contain another copy, but recovering one passage and restoring a whole site are different operations. The WordPress backup handbook separates database backups from file backups and explains why a full site recovery usually needs both.

Our recommendation for a missing paragraph is to have the maintainer inspect a backup in an isolated recovery environment and extract the text, if available. Replacing the live database with an older copy could also replace newer work elsewhere. Keep the recovery scope tied to the missing content.

Bring a real page-editing task to a Niwa demo to see the read, review and approved-update workflow. During your Niwa demo, we cover the subscription and AI usage. There is no obligation to buy.