Ship code to every client site. No second plugin.
Add tracking tags, custom CSS or a script to one website or forty, straight from your dashboard. The code travels through the connector you already installed, so nothing new ever lands on a client's server.
Available now in early access. Included on every plan.
Updated
What is a WordPress code snippet?
A WordPress code snippet is a small piece of HTML, CSS or JavaScript added to a site, such as a tracking tag, a verification meta tag or a style fix, usually placed in the header, just after the opening body tag or in the footer. Pasted into a theme file it disappears with the next theme update; a snippet tool keeps it separate.
WPCentrify adds snippets to any connected WordPress site, or to many sites at once, through the connector the site already runs, so there is no snippet plugin to install. Before you add anything it shows the tracking code already on each site, and a snippet can be switched off without deleting it.
WPCentrify code snippets at a glance
- HTML, CSS or JavaScript in the header, after the opening body tag or in the footer.
- One snippet on one site, chosen pages or many sites at once.
- Shows the tracking code each site already carries before you add more.
- Switch a snippet off without deleting it.
- Survives theme updates, because nothing is written into theme files.
- No second plugin on the site.
Every tag has to go somewhere, and it always ends up somewhere different
A client wants a conversion pixel. On one site someone adds it through a snippet plugin. On the next it goes into the theme footer, where it vanishes at the next theme update. On a third it is pasted into a page builder's custom code box only one person knows about. A year later nobody can say what is running where.
The failure this quietly causes is duplicate tracking: a second analytics tag added on top of one nobody knew was there, doubling a client's numbers until someone notices the reporting has been wrong for months. Doing this by hand across five to fifty sites is where the mistakes live.
Where code usually hides
- A snippet plugin, installed on some sites and not others
- The theme's functions.php or footer template
- A page builder's custom code panel
- A tag manager container nobody has the login for
- Hardcoded into a child theme by a developer who has moved on
No plugin, and no new way in
Every other way of doing this asks a client's site to run another plugin. WPCentrify does not. The code is delivered by the WPCentrify connector that is already there, so the plugin count on your client's site stays exactly where it was.
Nothing new on the server
The connector you installed to manage the site is the same one that delivers its code. No second plugin to install, license or keep updated, on any of the sites you run.
The site asks for its own code
Nothing is pushed at a website. It requests its snippets over a signed, per-site channel, and a website can only ever ask for its own, so it can never be handed somebody else's.
If we go down, the page does not
If WPCentrify is unreachable, the page renders exactly as it would if the feature were switched off. A broken connection is never a broken site. This is the reassuring part.
See what is already there, before you add anything
Most sites already carry code from somewhere: a header and footer plugin, a tag pasted into a theme years ago, something a previous agency left behind. So before you add anything, WPCentrify looks. It reads the snippet plugins the site runs and shows their real names, walks everything hooked into the page to work out what put it there, then opens the site's own front page to find the tracking tags themselves, the only way to catch a tag hardcoded into a theme or fired by a tag manager.
| Pass | What it catches |
|---|---|
| Snippet plugins | WPCode, Header Footer Code Manager, Elementor Custom Code and Simple Custom CSS and JS, read directly, with the real snippet names and where each one prints. |
| Hook attribution | Anything else adding code to the page, attributed to the plugin or theme responsible for it rather than left as an anonymous script. |
| Rendered page scan | The tracking tags themselves, however they got onto the page, read from the site's own rendered front page. It counts duplicates. |
Tags the rendered scan recognizes
The third pass knows the tags that actually cause the duplicate-reporting mistakes:
Paste something carrying a tag the site already serves and the editor tells you at the moment you paste it, not after it is live.
<script async src="https://www.googletagmanager.com/gtag/js?id=G-7QH2R"></script>
<script>gtag('config', 'G-7QH2R');</script>Where the code goes
Header, body or footer, and either every page or a set of pages you choose. The ordinary part of the job, kept out of your way.
Our guide to where each tracking tag goes in WordPress lists each vendor's own placement instructions.
Header, body or footer
Three placements cover effectively every tag you are asked to add, from a verification meta tag in the head to a chat widget that has to load last in the footer. Titles, descriptions and canonicals belong in on-page SEO management, not here. Our guide to WordPress SEO tags explains the difference.
Every page, or the ones you pick
Apply a snippet across the whole site, or choose the exact pages and posts it runs on from the site's own content list rather than typing URLs by hand.
One snippet, forty websites
Write the code once and apply it to as many websites as you like. Edit it in one place and every copy updates. That is the easy half.
The part that matters is taking it off again. A tag that breaks a checkout has to come off all forty in one press, not forty visits to forty screens on a Friday afternoon.
If somebody edits one website's copy on its own, that copy stops taking updates from the shared one, and the editor says so before the edit rather than after. Nothing changes silently.
The website confirms it, we do not just claim it
Knowing that we saved your code is not the same as knowing the page printed it. A site whose theme is unusual, or whose cache is misbehaving, can look perfectly healthy while the code reaches thirty-eight of forty.
So the website reports back what it actually printed, and the dashboard shows you the difference between printing, not printing, and we cannot tell yet. A site with no visitors since you added the snippet has not rendered a page, so there is nothing to confirm. That is reported as unknown, never as a failure.
This reports what a page printed. It is not continuous monitoring and it does not raise an alarm.
What to know before you rely on it
This is a delivery mechanism, not a safety net. Code you add runs on the front end of a live site, so a JavaScript error is still a JavaScript error and a heavy third-party tag is still heavy. Placing it through WPCentrify makes it visible and removable, not harmless. Our guide on how to improve Core Web Vitals on WordPress explains how tags like these affect INP and LCP.
Body placement depends on the theme calling the standard WordPress hook, wp_body_open, added in version 5.2. Most modern themes do. A theme that does not simply never receives body-placed snippets, while header and footer placement keep working normally.
The discovery scan is deliberately read-only and best-effort. If a site cannot be reached it reports that it could not look, rather than reporting the site is clean. It is there to stop the common duplicate-tag mistake, not to prove a site is spotless.
Worth knowing
- Header and footer work on every theme; body placement needs wp_body_open (WordPress 5.2+)
- Up to 65,535 characters, about 64KB, per snippet, so this is not for shipping a whole library
- Discovery is read-only: it never edits, disables or removes what it finds
- Deactivating the connector stops snippets being served, and leaves nothing behind in the theme
- Every add, edit, enable and removal is written to the activity log
Related
Content management
The page and post list a snippet's targeting is picked from, across every site.
See the featureTraffic analytics
Cookieless traffic measurement, counted on the site without adding a tag at all.
Read moreActivity log
Every snippet change, attributed to a person and a site, and timestamped.
Read moreQuestions about WordPress code snippets
No. Code is delivered by the WPCentrify connector that is already installed to manage the site, so there is no second plugin to add or keep updated. If a site already runs a snippet manager like WPCode you can keep it, and the discovery scan will show you what it is running.
The page renders exactly as it would without the feature. The site asks for its code and simply does not receive it that request, so a broken connection never breaks the site.
Straight away, on the next page load. Saving sends a signed nudge that clears the site's cache. If the site is briefly unreachable and the nudge does not land, the change still arrives within five minutes on its own.
Name the snippet, paste the code and choose header or footer, on one site or on many at once. Header and footer placement work on every theme; body placement needs the theme to support the standard wp_body_open hook. Nothing is written into the theme files, so a theme update never removes it.
Paste the GA4 tag as a header snippet and it loads on every page, with no analytics plugin and no second plugin on the site. Before it goes live the discovery scan reads the rendered page, so if the site already serves a GA4 tag the editor warns you at the moment you paste rather than letting you double the client's numbers.
Yes, on a single website: pick the exact pages and posts from the site's own content list. Shared code that goes to many websites is always site-wide, because a page id means a different page on every website.
Yes. Write it once and apply it to as many websites as you like, edit it in one place to update every copy, and remove it from all of them in a single press. If you edit one site's copy on its own, that copy stops taking updates from the shared one, and the editor tells you before you do it.
No, and that is one of the main reasons to do it this way. The code lives in WPCentrify rather than in a theme file, so switching or updating a theme has no effect on it and nobody has to remember to put it back.
No. It is entirely read-only. It reports what it finds so you can decide, and it never edits, disables or removes code that something else installed.
Open the site's Snippets tab and run the discovery scan. It reads the snippet plugins the site runs, attributes anything else hooked into the page to the plugin or theme responsible, and reads the rendered front page for the tracking tags themselves, so it catches a tag hardcoded into a theme or fired by a tag manager. It is read-only and best-effort: if a site cannot be reached it tells you it could not look, rather than reporting the site is clean.
The rendered-page pass counts how many times each tracking tag appears, so a GA4 or Google Tag Manager tag served twice shows up as a duplicate. Paste a tag the site already serves and the editor flags it as you paste, which is how you catch the second analytics tag that would otherwise sit on top of one nobody knew was there and quietly double the reporting.
Yes. Disable it to take it out of circulation while keeping the code and its history, which is usually what you want while you work out whether it caused something.
The delivery does not. The connector prints your code on a standard WordPress hook and caches the response, so there is no per-request call to us on the visitor's path. What can slow a site is the code itself: a heavy third-party tag is heavy wherever it is placed. Adding it through WPCentrify makes it visible and removable, which is how you find the slow one later.
No, and it is not trying to be. There is no browsable library of ready-made snippets and no code generator. This is for delivering your own code to many client sites from one place, seeing what is already installed before you add more, and taking it off again in one press. If a site already runs WPCode or another snippet manager, you can keep it, and the discovery scan will show you what it holds.
Up to 65,535 characters, which is roughly 64KB. That covers tags, tracking scripts and reasonable custom CSS or JavaScript; it is not meant for shipping an entire library.
Use one tool that adds the same snippet to every site you choose and shows what each site already carries. WPCentrify adds HTML, CSS and JavaScript snippets to any connected site from one dashboard, without a snippet plugin on each site.
See what is running before you add more
Header, body and footer code across every connected site, scoped to the pages you choose, delivered through the connector you already have, with a scan that shows what is already there.
Free during early access. No credit card required.