Most bloggers write the same things repeatedly: a newsletter signup callout, an “about the author” footer, a specific table format, a tip box that always looks the same. Each one gets rebuilt from scratch every single time, which wastes minutes that add up fast across a year of writing. WordPress patterns solve this problem directly. You set the block up once, and you reuse it forever after.
The terminology
WordPress’s terminology around this feature has shifted more than once, so it helps to untangle it before going further:
- “Reusable blocks”, the old name introduced back in WordPress 5.0. These were synced by default, meaning editing one updated every copy across the site.
- “Patterns”, the newer, unified term that arrived with WordPress 6.3. A pattern can be either synced or unsynced, your choice.
- “Synced patterns”, which behave like the old reusable blocks. Edit the pattern once, and the change appears everywhere it’s used.
- “Unsynced patterns”, which insert as an independent copy each time. Editing one instance leaves every other instance untouched.
Modern WordPress uses “Patterns” as the umbrella term for all of this. The block inserter lets you choose synced or unsynced right at the moment you save one, and the official WordPress.org documentation on block patterns is worth a skim if you want the full technical picture.
When to use each type
Use synced patterns for
- Newsletter signup callouts. When you change email providers, you update the pattern once and every post reflects it.
- “About the author” footers. Your bio changes only occasionally, so a single edit that propagates everywhere saves real effort.
- Disclaimer or affiliate disclosure blocks. Legal language changes from time to time, and you want every post updated the moment it does.
- Product CTAs that link to active offers. Promotions change often enough that a synced update beats hunting through old posts.
Use unsynced patterns for
- Post templates with a standard structure, like an intro plus main sections plus a conclusion, that you’ll customize differently each time.
- Recipe templates where the fields stay the same but the actual values differ every time.
- Comparison tables that share a column structure but hold different data in each post.
- Tip or note callouts where the styling should match but the content genuinely varies post to post.
Don’t use patterns for
- One-off layouts you’ll genuinely never repeat anywhere else.
- Blocks that need unique content each time but happen to share similar formatting. A custom CSS class handles that case better than a pattern does.
How to create a pattern
Step 1: Build the blocks
Create whatever block or group of blocks you want to reuse later. That could be a heading, a paragraph, a callout div, or any combination of blocks working together.
Step 2: Select the blocks
Click and drag to select multiple blocks at once, or click the parent block directly if they’re already grouped together.
Step 3: Save as a pattern
- Click the three-dot menu on the selected block.
- Choose “Create pattern” (this reads “Add to Reusable blocks” on older WordPress versions).
- Give it a descriptive name, something like “Newsletter Signup CTA” rather than a generic “Pattern 1.”
- Choose synced or unsynced based on the guidance above.
- Save it.
Step 4: Use it
In any post, open the block inserter by typing / and search for the pattern by name, then insert it wherever you need it.
Patterns most bloggers should have ready
1. Newsletter signup callout
A box with a brief pitch and a signup form, or a link to your dedicated subscribe page. Make this one synced. If you ever change your email tool, one edit updates it everywhere at once.
2. “About the author” footer
A short bio, a photo, and a link to your About page. Synced makes sense here too, since your bio changes only occasionally and you want that single edit to propagate.
3. Affiliate disclosure
A short “this post contains affiliate links” line placed at the top of relevant posts. Synced, since the legal language behind it might need to change as regulations or your own disclosure policy shifts.
4. Tip, warning, or info callout
The colored box pattern you reach for whenever you want to highlight a tip or a warning. Unsynced makes sense here, since the content varies every time even though the styling stays consistent.
5. Comparison table template
An empty table with predefined columns, like Feature, Option A, and Option B. Unsynced, since you’ll fill in different content for every post that uses it.
6. A short standalone summary box
For posts that genuinely benefit from a compact upfront summary before the full explanation. Keep this unsynced, since the content obviously varies post to post. Use it sparingly and only when it adds real value, rather than as a default habit for every post you write.
7. Post-specific CTA pattern
An end-of-post call-to-action with consistent visual styling. Make it synced if it always points to the same main product or list, and unsynced if the destination varies by post.
Managing your patterns
Where they live
You’ll find them under Appearance, then Patterns, or in some WordPress versions, accessed directly through the inserter’s Patterns tab.
From there, you can do the following:
- Edit any existing pattern.
- Delete patterns you’re no longer using.
- Convert a pattern between synced and unsynced whenever your needs change.
Organizing them
If you build up a large library of patterns over time, you can organize them into categories. The category then appears in the inserter, which makes finding the right one much faster while you’re writing.
The “synced pattern breaks across every post” warning
Synced patterns are powerful, and also slightly dangerous if you’re careless. If you edit one and accidentally break it, say by deleting a critical element or damaging a link, that broken version appears instantly in every single post that uses it.
Best practice here is straightforward. Before editing a synced pattern, check how many posts actually use it. WordPress shows you this count directly in the Patterns admin screen. If the number is high, test your change on a staging site first rather than editing the live version directly.
The “I edited the pattern but the post still shows the old version” issue
This is usually a caching problem rather than an actual bug in the pattern itself. The new version of the pattern saves correctly, but cached page versions keep serving visitors the old one until the cache clears.
Clear your cache after editing any heavily-used synced pattern, including both your WordPress caching plugin and Cloudflare, if you use it for your site.
Converting old reusable blocks to patterns
If you have old “reusable blocks” left over from before the patterns terminology changed, they already work as synced patterns automatically. No manual conversion is needed on your part.
You can still rename or recategorize them through the Patterns admin screen if you’d like them organized more clearly.
Exporting and importing patterns
If you run multiple sites, or you’re migrating content between them, patterns can be exported as JSON files and moved over:
- Go to Appearance, then Patterns, click the three-dot menu on a specific pattern, and choose Export.
- Import that file on another site through the same interface.
This is genuinely useful for sharing a consistent set of patterns across several sites you manage at once.
Patterns vs templates vs template parts
These are three related but distinct concepts worth telling apart:
- Patterns: reusable groups of blocks that get inserted inside individual posts or pages.
- Templates: the overall layout for a given page type, like a single post or an archive page. Block themes let you edit these directly.
- Template parts: sections of templates, such as a header or footer, that can be reused across multiple templates at once.
For most bloggers focused on writing posts, patterns are the right tool for daily use. Templates and template parts matter more when you’re customizing the theme itself. For a closer look at what counts as a “layout” versus a page-builder-style customization, see this explanation of how layouts work in Aurora.
How patterns interact with classic themes
Patterns work in both block themes and classic themes, since the block editor itself is identical either way.
The real difference shows up elsewhere. Block themes let you also use patterns inside headers, footers, and other template areas, while classic themes restrict patterns to the post or page content area only. If you’re running the Aurora theme, its editor integration is built to work smoothly with the standard block editor, so patterns you create behave exactly as documented here. See this guide to using Aurora with the block editor for specifics on how the two work together.
The “I don’t see Patterns in my WordPress” troubleshooting
If your version doesn’t show “Patterns” anywhere in the interface, work through this short checklist:
- Check your WordPress version. The unified Patterns terminology and synced/unsynced choice require WordPress 6.3 or later.
- Look for “Reusable Blocks” instead if you’re running an older version, since that’s the equivalent feature under its previous name.
- Update WordPress if you’re several versions behind. See this guide on updating WordPress safely for a process that won’t break your site in the attempt.
Once you’re comfortable with patterns, it’s worth spending time in the block editor guide as well, since patterns are really just one piece of writing efficiently inside Gutenberg.
Thirty minutes now saves hours later
Patterns save serious time over months of blogging. Build a small set of patterns for the things you repeat most, including newsletter callouts, author bios, tip callouts, and table templates. Use synced for things that should update everywhere; unsynced for things that vary per use. Spend 30 minutes setting up 5 to 8 patterns and you’ll claw back hours of repetitive formatting over a year of writing.
