WordPress Synced Patterns for Repeating Guide Blocks
Our clan wiki had a small box at the top of every guide: a line about which patch the guide was written for, a note that times were listed in UTC, and an invite link to the Discord.

Our clan wiki had a small box at the top of every guide: a line about which patch the guide was written for, a note that times were listed in UTC, and an invite link to the Discord. It was two paragraphs and a button, and it sat on 183 pages. When the Discord invite rotated, I spent most of a Saturday morning opening posts, scrolling to the top, pasting a URL and clicking update. Forty minutes in I started making mistakes, and three pages carried the dead link for another two months before a reader told me.
That box is exactly what synced patterns are for, and almost nobody on a fan site uses them until they have already paid for the lesson. They are not a plugin, they cost nothing, and they have been part of the block editor for years under two different names, which is part of why people miss them. Here is how they work, where they quietly cause problems, and the three jobs on a game guide site that justify setting them up this afternoon.
What a synced pattern is, and what changed in 6.3
A synced pattern is a saved group of blocks that lives in one place and appears in many posts by reference. Edit the saved copy once and every post showing it updates, with no republishing. If you have been running WordPress for a while you knew these as reusable blocks. WordPress 6.3 renamed them to synced patterns and added a second kind, the unsynced pattern, which inserts a copy that you are then free to edit per page.
They are stored as their own post type called wp_block, which is useful to know when things look broken. You can list every one you have at the Patterns screen under Appearance, or by visiting the admin edit screen for that post type directly. Deleting a pattern there does not clean up the posts that point at it. Those posts render nothing where the box used to be, which on a wiki means 183 pages silently lose their patch notice.
In WordPress 6.6 a further option arrived: pattern overrides, which let you mark specific fields inside a synced pattern as editable per post while the rest stays locked to the master copy. That is the feature that makes patterns genuinely practical for guide templates, because a guide header almost always has one field that must differ, usually the game version.
Which tool to reach for, since there are four
Most of the confusion I see in community admin channels comes from people picking the wrong one of these and then blaming the editor.
| Tool | Edit once, changes everywhere? | Per page variation | Good for |
|---|---|---|---|
| Synced pattern | Yes | Only through pattern overrides | Discord invite boxes, disclaimers, patch notices, donation appeals |
| Unsynced pattern | No, it inserts a copy | Full, every copy is independent | Guide skeletons, tier list layouts, boss page structure |
| Template part | Yes | None | Header, footer, sidebar, things outside the post content |
| Shortcode or block plugin | Yes | Through attributes | Anything needing logic, such as a countdown or a live roster pull |
The distinction worth memorising is the second column against the third. If the content must stay identical, sync it. If the content is a starting shape that each writer fills differently, do not sync it, because the first writer who edits it will overwrite the box on every other page and nobody will connect the two events.
The advice to turn everything into a reusable block is wrong
Search for this topic and you will find a dozen tutorials telling you to save any repeated layout as a reusable block to keep your site consistent. I followed that advice on the wiki in 2021 and ended up with 31 saved blocks, of which maybe six were doing real work. The other twenty five caused three specific problems.
The first is that volunteers cannot tell they are editing a shared object. The editor marks a synced pattern with a coloured outline, which is easy to miss on a long page, and a new guide writer who deletes a sentence from it has just edited every guide on the site. I have had that happen twice, both times from people acting in good faith. The fix that worked was not training. It was reducing the count to the handful that genuinely needed syncing.
The second is portability. Synced patterns live in the database, not in the post content, so a plain content export of a single post does not carry the box with it. Moving one guide to another site brings an empty gap. You can export each pattern as a JSON file from the Patterns screen, which I now do before any migration, but it is a separate step that is easy to forget. If you are moving hosts, add it to the checklist beside the rest of the pre flight work covered in using a staging site before big updates.
The third is that plugin generated blocks inside a synced pattern break in a particularly annoying way. If the pattern contains a block from a plugin you later deactivate, every post shows the block validation warning rather than a clean fallback. One of the quickest wins during a plugin cleanup is checking which of your saved patterns depend on plugins at all, which pairs well with a proper plugin audit.
Three jobs on a guide site that pay for themselves
The patch notice header is the obvious one. Build it as a synced pattern with pattern overrides on the version number field, so each guide shows its own version while the wording, styling and links stay central. When your game ships a major update you edit the notice once to say that guides are being revised, and 183 pages say it immediately.
The second is the guide skeleton, and this one must be unsynced. Mine holds an intro placeholder, a requirements heading, three numbered step headings, a common mistakes heading and a credits line. New contributors insert it and start typing into a shape that already matches the site, which cut the editing time on submitted guides more than any style document ever did. A table of contents block sits inside it, and if you are not generating one yet, our guide to adding a table of contents to long guides covers the options.
The third is the thing you will need at the worst possible moment: a site wide notice. Keep one synced pattern that is empty most of the time, placed at the top of your busiest twenty pages. On a launch night when your host starts struggling, or when a tournament bracket changes an hour before matches, you type one sentence into that pattern and every one of those pages carries it. I have used ours four times in two years, and on the night the ladder reset early it was the only reason the forum did not fill with the same question ninety times.
Two habits keep the whole arrangement from rotting. Name every pattern with a prefix so the insert list stays readable, something like notice, layout or box, and write the name as it would appear to someone who has never seen your site. And review the Patterns screen once a quarter, deleting anything used nowhere. Ten minutes, and it is how you avoid finding a pattern in 2027 that nobody remembers creating. The rest of the WordPress guides cover the surrounding maintenance jobs.
FAQ
Are reusable blocks and synced patterns the same thing?
Yes. The name changed in WordPress 6.3 and old reusable blocks became synced patterns automatically, keeping the same wp_block post type underneath. Older tutorials using the previous name are still broadly accurate, except where they discuss the newer unsynced option or overrides.
Do synced patterns slow a site down?
Not in any way I have been able to measure on a wiki with around 1,200 posts. Each pattern is one extra lookup, which page caching removes entirely for anonymous readers. If a guide page feels slow, the cause is almost always images or plugin scripts rather than patterns.
Can I stop contributors from editing a shared pattern?
Partly. Core gives you locking on individual blocks, which stops movement and removal, and pattern overrides restrict editing to the fields you choose. For firmer control you need capability editing so that only editors and administrators can modify the wp_block post type, which is worth doing alongside a sensible set of roles for a volunteer team.
What happens if I delete one by accident?
The posts referencing it render nothing in that spot, with no warning on the front end. Deleted patterns do go to the trash first, so recovery within thirty days is straightforward. Exporting your handful of important patterns as JSON and keeping them beside your backups is the safer answer.
More in WordPress
WordPress
How to Fix WP-Cron When Scheduled Posts Miss on a Fan Site
You schedule the patch notes summary for 03:00, right when the servers come back from maintenance.
WordPress
How to Increase the WordPress Max Upload Size Safely
You try to upload a 40 MB match replay or a mod pack to your guild site and WordPress stops you with "The uploaded file exceeds...
WordPress
How to Migrate WordPress to a New Host Without Downtime
Your current host is slow, expensive or about to double its renewal price, and you want out.