How to edit text in WordPress, wherever it lives

Key takeaways

  • Most failed text edits happen in the wrong place. The words belong to a template, a synced pattern, a builder widget, a WooCommerce field or a theme setting, not to the page you opened.
  • If you edit a template, template part or synced pattern, the change shows on every page that uses it. Detach a synced pattern when you only want to change one page.
  • W3Techs detects Elementor on 31.5% of WordPress sites in its November 2026 data. Edit those pages in the builder and don’t switch between the builder and the block editor.
  • “Updating failed. The response is not a valid JSON response” means the save never happened. Re-save permalinks, check Site Health, then ask your host whether something is blocking /wp-json/.
  • If your edit saved but the old text still shows, you are looking at a cached copy. Clear the browser, plugin, host, CDN and builder caches in that order. Google can take days to weeks to update its snippet.

A price changed yesterday, the Saturday hours are wrong, or there’s a typo in the homepage headline. Typing the fix takes ten seconds. Most of the time goes into finding where WordPress keeps that sentence. On a plain block editor page the steps are short. On a site with a page builder, a block theme, WooCommerce or a commercial theme, the same visible sentence could be stored in one of six places.

Start with the basic steps. Then use the table further down to track text that isn’t where you expected. For the wider picture of how pages are put together, see our guide to editing pages in WordPress safely.

How do you edit text on a normal WordPress page?

Open the page, click the text, type, and press Save or Update. WordPress keeps text inside blocks, and the Paragraph block holds ordinary body text. Here are the steps in full:

  1. Open the right item. Go to Pages > All Pages (or Posts > All Posts), hover over the title and click Edit. Check the status column first, so you don’t edit an old draft or a duplicate called “Home (copy)”.
  2. Select the block. Click the sentence. A small toolbar appears above it, showing which block you selected. On long pages, open List View from the top toolbar and jump straight to the block.
  3. Edit the words. Type the change. Ctrl+Z (Cmd+Z on a Mac) undoes a mistake.
  4. Format with the right tool. Bold, italic and links are in the block toolbar. Size, colour and spacing are in the Settings sidebar, opened from the panel icon at the top right. If you want a heading, use a Heading block. Large bold text is not a heading to a screen reader or a search engine.
  5. Save or publish on purpose. Save draft keeps the change private. Publish or Update makes it live. Preview shows roughly how the page will look.
  6. Check the live page. Open the public URL in a private window. Read the edited sentence and the text around it, then click any link you touched.

It worked if the new wording shows on the live page, the layout around it is unchanged, and links still go where they should. If the page opened but the sentence isn’t in the editor, the text lives somewhere else. Use the next section to find it.

The text isn’t in the editor. Where does it live?

It belongs to something other than the page. WordPress.org’s FAQ on changes that don’t appear lists editing in the wrong location as one of the usual causes, alongside caching. Match what you see to the table below.

What you seeWhere the text livesWhere to edit it
The editor is nearly empty, or shows an “Edit with Elementor” style buttonA page builder widgetOpen the page in that builder
The same text appears on every page (header, footer, contact strip)A template part or theme settingAppearance > Editor on block themes; Appearance > Customize or Widgets on classic themes
Editing one copy changes the text on other pagesA synced patternEdit the pattern, or detach it for this page only
Homepage text isn’t in the page chosen under Settings > ReadingA Front Page or Home templateAppearance > Editor > Templates
The page body shows only [woocommerce_checkout] or another shortcodeOutput from a pluginThe plugin’s settings or the theme’s Customizer options
Product wordingA product fieldProducts > All Products > Edit
None of the aboveTheme options or a hard-coded theme fileThe theme’s settings panel, the theme’s support team, or a child theme

Templates and synced patterns change every page that uses them

Headers, footers and some page sections on block themes come from templates and template parts. WordPress.org’s Site Editor Pages documentation says template blocks stay locked while you edit a page, until you choose to enable template editing. That lock is there for a reason. Once you edit the template, the change shows on every page built from it.

The homepage often catches people out. WordPress.org’s guide to the Site Editor explains that a Front Page template can take priority over the page you picked in Settings > Reading. If you changed the setting and nothing moved, the template is winning. Our guides to editing your WordPress homepage and changing footer text safely cover both cases step by step.

Synced patterns, once called reusable blocks, are shared in the same way. WordPress.org’s synced patterns documentation says that editing one updates it everywhere it is used. If you want to change it on one page only, choose Detach pattern. The detached copy is now ordinary content and won’t receive future changes to the shared pattern. Detach only when that is what you want.

Page builder text has to be edited in the builder

W3Techs detects Elementor on 31.5% of WordPress sites in its November 2026 figures. That means many readers are not editing text in the block editor at all. In Elementor, text sits in the Text Editor widget. Open the page with the builder, click the widget, edit it in the left panel or directly on the canvas, then click Update inside the builder. Divi text modules and Beaver Builder modules work the same way.

Don’t switch editors. Builders store their content separately from normal post content, so editing in the ordinary WordPress screen can leave the builder version untouched. A wordpress.org support thread from 2024 followed exactly that problem on a Beaver Builder site: the edits had been made in the WordPress editor, and a builder cache made the confusion worse. Volunteers advised sticking to one editor for each piece of content.

WooCommerce text is split across several places

Each product has two text fields. WooCommerce’s Product Editor documentation lists the product description (usually shown in a tab below the product) separately from the short description (usually shown next to the price). If you edit one, the other stays as it was. Where those fields appear on the page is set by the Single Product template.

Checkout and shop pages are harder. The checkout page body often contains nothing but a shortcode, and any extra text may come from the theme’s Customizer options. An r/woocommerce thread from 2025 found that a shop page description was generated by the theme. The poster fixed it by editing a theme file, and replies pointed out that the next theme update would wipe that change. A child theme override keeps the edit through updates.

Why won’t WordPress save my text?

If you see a red notice in the editor, the problem is not caching. The save failed. These are the common causes and what to try for each.

“Updating failed. The response is not a valid JSON response.” The block editor saves through the REST API at /wp-json/, and something interrupted that request. The fixes that keep coming up in wordpress.org support threads are:

  • Open Settings > Permalinks and click Save without changing anything.
  • Check Tools > Site Health for REST API errors.
  • Make sure the WordPress Address and Site Address under Settings > General match.
  • Ask your host whether a firewall or ModSecurity rule is blocking /wp-json/.

A plugin or theme conflict. WordPress.org’s troubleshooting FAQ names plugins competing over JavaScript as a cause of editor problems. Test on a staging copy, not on the live site that visitors use. The Health Check & Troubleshooting plugin turns plugins off for your session only, but its directory listing currently warns that it hasn’t been tested with the latest three major WordPress releases. Use staging if your host offers it. Switching to the Classic Editor can get the page saved, but the conflict is still there.

“This block contains unexpected or invalid content.” WordPress.org’s block error page says this usually comes from pasted or hand-edited HTML, or from a plugin or theme conflict. Try Attempt Block Recovery first. Convert to HTML and Convert to Classic Block will also make the error go away, but they change the block, so check the result. Our guide to editing WordPress in HTML explains when raw markup is worth the risk.

No Edit link at all. Your user role doesn’t allow it. Pages need the edit_pages capability. Authors can edit only their own posts, while Editors can edit everyone’s. Ask an administrator for the smallest role that covers the job.

Saved, but the live page still shows the old text

You are looking at a stored copy. The edit saved, but one of the cache layers between WordPress and your browser is still serving the old version. Clear them in this order, and check the page in a private window after each one:

  1. Confirm the page actually shows Published, not Draft or Scheduled.
  2. Clear your browser cache, or simply use a private window.
  3. Purge your caching plugin.
  4. Purge the host’s page cache from the hosting dashboard.
  5. Purge the CDN (Cloudflare or your host’s own).
  6. On builder pages, clear the builder’s cache or regenerate its CSS.

Clearing one layer can leave another still serving the old page. WP Engine’s cache documentation also notes that a full purge can slow the site for a short time while pages are cached again. Clear what you need, not everything, every time. Don’t keep re-editing the page while you wait. That adds revisions without changing anything. Our guide to pages that won’t update goes through each layer in detail.

If Google still shows the old wording, that is a separate, slower problem. Google’s recrawl documentation says crawling can take days to weeks, and asking repeatedly doesn’t speed it up. Request indexing once with URL Inspection in Search Console, then leave it.

How do you undo a text edit?

Use revisions. WordPress.org’s revisions documentation describes a record of each saved draft and published update. The comparison screen marks what was added, kept and removed. Open the Revisions link in the page settings, drag the slider to the version you want, click Restore, then check the live page.

There are two things to watch. Builders keep their own history, so the WordPress revision list may not include a builder edit. And if someone else edited the page after you, compare before restoring. Restoring your version would overwrite their newer work.

When should you stop and get help?

Stop when finding the text turns into experimenting on the live site. The warning signs keep repeating in support threads: switching themes to see what happens, turning off plugins while customers are shopping, editing a parent theme file, or copying a hard-coded sentence over the old one. Hand it off in these cases:

  • You inherited the site and can’t tell which builder or theme generates the page.
  • The text comes from the theme and there’s no setting for it.
  • The JSON error survives the checklist above. That usually needs the host.
  • The fix means changing a theme file, and there’s no child theme.

When you hand it off, give the page URL, the exact current sentence, the replacement, and whether it should go live or stay a draft. If you’d rather send that in chat than track down the template yourself, SiteSelf’s website edits page explains how the agent makes text changes on your existing site and reports what it checked. It refuses pages owned by Elementor, Divi or Beaver Builder and tells you why.

Frequently asked questions

Do I need to know code to edit text in WordPress?

Not for ordinary content. Blocks, builders and product fields are all edited visually. Edit as HTML and the Code editor are there if you need them, but hand-edited markup is the most common source of block validation errors. Only use them when the visual controls can’t do the job.

Should I use the block editor or the Classic Editor?

Use whichever editor the page was built with. The block editor is the default. The Classic Editor plugin brings back the older single text box with Visual and Text tabs. A page made of blocks may not open cleanly in the Classic Editor, so don’t switch just to make one edit.

Why can’t I select or change a block?

It’s probably locked, part of a synced pattern, or part of a template. Look for an unlock option in the block’s toolbar menu, an edit option for the pattern, or the Edit template control. Whatever you edit through a pattern or template changes every place it appears.

How do I change the size, font or colour of text?

Select the block and open the Settings sidebar. Typography and colour controls are there if your theme allows them. For a change across the whole site, use global styles under Appearance > Editor on block themes, or the Customizer on classic themes. Changing a heading’s level just to make it smaller breaks the page outline.

Can I edit text by typing directly on the live site?

No. Edits happen in the dashboard, the Site Editor or your builder. When you’re logged in, the admin bar on the live page has an Edit link that takes you to the right editor for that page.

Google still shows my old wording. Did the edit fail?

Not if the live page in a private window shows the new text. Google updates its copy when it next crawls the page, which can take days to weeks. Request indexing once with URL Inspection in Search Console, then wait.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *