Do synced patterns (reusable blocks) cause duplicate content?
No. A synced pattern, formerly called a reusable block, is saved once and inserted into every page that references it. It has no public address, so it cannot be indexed separately. Repeating a call-to-action or author box across many pages is ordinary boilerplate, which search engines expect and discount.
How synced patterns are stored and output
When you create a synced pattern, WordPress saves its blocks as a post of an internal type called wp_block. That type is registered as not public and has no rewrite rules, so there is no front-end URL at which the pattern can be viewed by itself.
In each post that uses it, the content holds only a short reference to the pattern's ID. When the page is built, core fetches the pattern and prints its HTML in place, on the server. The visitor and the crawler receive one finished page in which the pattern's markup looks like any other part of the content.
Two consequences:
- Editing the pattern changes every page that uses it at once. The posts themselves are not re-saved, so their modified dates do not change.
- Unsynced patterns are different. They are copied into the post when inserted and become ordinary blocks with no link back to the original.
Why repeated blocks are not duplicate content
Duplicate content, in the sense search engines care about, means substantially the same page available at more than one URL. A block repeated across fifty pages is not that. Each page still has its own main content, and the shared block is a small part of it.
Every site repeats things: header, navigation, footer, sidebar, sign-up boxes, legal lines. Search engines separate this template material from the main content as a matter of routine. A synced pattern holding a newsletter form or a "book a call" banner falls into the same class.
So the following are all fine:
- a call-to-action at the end of every post;
- an author bio pattern on each of that author's articles;
- a pricing table on several landing pages;
- a disclosure or disclaimer paragraph wherever it applies.
None of these needs a canonical tag, a noindex or any other treatment.
When repetition does become a problem
The risk appears when shared blocks stop being the frame and become the picture.
Pages that are mostly pattern. Twenty "service in [city]" pages that each consist of one synced pattern of 600 words plus a changed headline are near-duplicates. That is a content problem, and Google's spam policies describe the extreme version as doorway pages. The pattern feature makes such pages quick to build; it does not make them a good idea.
Short posts with long shared blocks. A 150-word update followed by a 400-word pattern has more shared text than unique text. One such page is nothing to worry about. A whole section of the site built that way looks thin.
Shared text that should have been a link. If the same three paragraphs of explanation appear on thirty pages, move them to one page and link to it. That page can then rank for the explanation, and the thirty stay focused.
A rough test: cover the synced patterns with your hand. Is what remains a complete, useful page on its own subject? If so, you are fine.
Things worth checking in patterns
Because one pattern appears on many pages, a flaw in it is multiplied.
- Headings. A pattern containing an H2 inserts that H2 into every page's outline. An H1 inside a pattern gives each page a second H1. Use a lower heading level, or bold text, for small boxes. The heading structure checker shows the outline of a finished page.
- Links. A link inside a synced pattern becomes a link from every page that uses it. That is useful for a key page, and it is a reason to keep the anchor text descriptive and the destination final, not a redirect. Note that Hydrogen SEO's internal link counter reads links saved in each post's own content, and a pattern's links are stored in the pattern.
- Images. Give the image alt text inside the pattern; it will be the same everywhere, which is correct for a repeated element.
- Schema. Avoid FAQ or review markup inside a pattern used on many pages, since identical structured data on unrelated pages does not describe them accurately.
- Weight. A heavy pattern, such as a large image or an embedded form script, is loaded on every page that includes it.
To see everything a site has, open Appearance → Patterns (or Appearance → Editor → Patterns in a block theme) and review the synced ones. Delete those no longer used, after removing them from the posts that reference them, since a deleted pattern simply stops appearing wherever it was used.
Common questions
Can Google index a synced pattern as its own page?
No. Patterns are stored as a non-public content type with no address, so there is nothing to crawl except the pages that include them.
Does repeating the same call-to-action on every post hurt rankings?
No. Repeated elements are treated as template content. Rankings depend on the main content of each page.
Does editing a synced pattern change my posts' modified dates?
No. Only the pattern is saved. Posts that reference it show the new version without being updated themselves.
Are theme template parts treated the same way?
Yes. Headers, footers and other template parts are shared layout printed into each page, and they have no public URL of their own.