A WordPress synced pattern updates every page that uses it when you save a change to the original. To change just one page, edit a field that supports a local override or detach that copy before changing its layout. The right choice depends on whether that page should still receive future updates to the pattern.
Imagine two service pages use the same enquiry panel. You need a different button link on one page, but both panels should keep the same design. Editing the original could send visitors on both pages to the same destination. Detaching the panel would keep the link local but also disconnect that copy from future design updates.
Check what you selected before you save
- Open the page in the WordPress block editor and use List View to select the whole section. Selecting the button inside it may hide the controls for the enclosing pattern.
- Look for Edit original on the pattern toolbar. If it appears, assume the original is shared. Open a second page that uses the section in a separate tab to see what must stay unchanged.
- Check that the section is in the page’s content. A header or footer in a template part is a different shared document. If the page is built in Elementor, check the owning Elementor document instead of switching editors.
An editing control alone does not prove the section is synced. WordPress 7.0 also lets you open up the design controls for an unsynced pattern that initially shows only text and media controls. The WordPress core editor notes explain the difference.
Decide what should change
| Your goal | What to edit | What happens later |
|---|---|---|
| Change the layout or default content everywhere | Use Edit original on the synced pattern. | Connected copies get the shared change. Check separately for fields already overridden on individual pages. |
| Change one page’s button link but keep the shared layout | Edit the button on the page if the pattern already allows a local override for that field. | The local value stays on that page while the rest of the pattern remains connected. |
| Give one page a different layout from now on | Select the whole pattern, open its options menu and choose Detach or Detach pattern, where available. | That page now has ordinary blocks and no longer receives future edits from the original. |
For a layout that editors should freely customize on every new page, an unsynced pattern is a better starting point. It copies the layout without creating a shared connection.
Keep one button different without forking the layout
In the two-service-page example, leave the first page alone. On the second page, select the button inside the synced pattern. If its link is already editable there, change the link in that page’s editor without opening Edit original. Check the save screen: if it also lists the shared pattern as a changed item, stop and inspect what was edited before confirming.
If the link isn’t editable locally, a site maintainer can configure an override on a supported block in the original. In the pattern editor, the relevant setting is under the block’s Advanced panel. Use Learn WordPress’s override walkthrough and test on staging first. Enabling an override is a change to the shared pattern itself. Do not assume it is available for every block, field, role or locked pattern.
After saving, view both pages outside the editor. On the second page, confirm the actual link destination, not just the button text. On the first, confirm that the old link and layout still work. If the shared pattern has a mobile layout, check both pages at a narrow width too.
If an edit already changed several pages
Stop saving from any older open tabs. Record the affected URLs, pattern name and approximate change time, and preserve the current saved versions before touching them. If both pages changed, inspect the shared pattern before restoring either page. A page revision can restore that page’s own content without necessarily restoring the original of a separate synced pattern.
Recover the smallest document that owns the change. On staging, compare a known-good copy of the shared pattern with the current one and check whether any page has its own overrides. Do not delete the pattern, detach every copy or restore the live database just to reverse one edit. Escalate if the original cannot be identified or if the change affects a live booking, checkout or lead form and you cannot verify the correct destination.
The official WordPress synced-pattern guide covers the native editing and detaching controls.