The editing route
Use the page as the control surface
Start with the public-facing view and let the selected wording lead the change.
01
Bring the page into view
Sign in with a user who has WordPress permission to edit the current post, then open its public-facing view.
02
Put the editor on the page
Choose Frontend Text Edit from the WordPress admin bar.
03
Point to the wording
Click the visible value that needs attention.
04
Make the local change
Replace the selected value in the frontend editing control.
05
Confirm the correction
Save the edit and check that the page now shows the intended value.
06
When the target is outside the editor
With editing mode on, send a report from the public page with its URL, text excerpt, selector hint, and site details to the local WordPress administrator. The site can explicitly change or disable report recipients.
Supported surfaces
Find the text target that fits the job
The frontend route reaches several WordPress text surfaces when the site makes them available.
01
Core block copy
Paragraphs, headings, list items, and buttons can be corrected inside the standard block surfaces.
02
Presentation metadata
Titles and excerpts are available when the site’s presentation Adapter exposes those fields.
03
Text inside richer markup
A supported text-node segment can be selected without replacing the surrounding block.
04
Linked list entries
Change the visible wording while keeping the existing URL attached to the item.
05
Generated controls
GenerateBlocks exposes headline and button labels as text targets.
06
FAQ questions and answers
The supported Rank Math surface keeps its existing wording available for correction.
Content safety
Three safeguards keep a small edit small
The operation protects newer work, narrows its scope, and leaves stored page content under WordPress ownership.
01
Newer content wins
Optimistic conflict protection rejects a stale edit instead of overwriting a more recent change.
02
The surrounding page stays out of scope
Frontend Text Edit changes supported text only. It does not edit layout, design settings, media, templates, or block structure.
03
Deactivation does not erase the result
WordPress stores the change in native Gutenberg post content. That ordinary content remains after the plugin is disabled; only the frontend editing interface disappears.
Dependencies
Dependencies
WordPress supplies the editing and storage surfaces; PHP supplies the server runtime.
6.9 or later
WordPress 6.9 or laterProvides the block editor, REST API, post permissions, and native content storage used by Frontend Text Edit.
8.0 or later
PHP 8.0 or laterRuns Frontend Text Edit on the server.
Stable package
Start with the download
For a wording correction, get the stable self-hosted ZIP, install and activate the editor, then return to the target page to begin.