Remove the 'Rendered with Bricks' Badge (Fixes)

What That Badge Is

If you’ve ever logged into a Bricks site, you’ve seen it: a small link at the top of the page that reads “Rendered with Bricks.” It lives inside the WordPress admin bar — the dark toolbar that appears above your site when you’re logged in — and clicking it drops you straight into the Bricks editor for that page.

Two facts set the tone for everything below:

• Only logged-in users ever see it. The admin bar itself only renders for logged-in users, and this item rides inside it. Visitors get a completely clean page.
• It’s a shortcut, not a watermark. It’s not a “Powered by” footer credit baked into your pages. It’s a toolbar node added by Bricks on the admin_bar_menu hook, with the node id editor_mode — you can confirm by inspecting the toolbar HTML and finding #wp-admin-bar-editor_mode.

Why You Might Want It Gone

The reasons are aesthetic, not technical:

• Client demos. Showing a finished site to a client who’s logged in? “Rendered with Bricks” is a dead giveaway of the stack — and it invites “why didn’t you use X” conversations.
• White-label work. Agencies strip tool branding all the time. This is the same instinct.
• Clutter. If you live in the front-end admin bar, every extra item is noise.

And the reassurance: removing it has zero effect on SEO or performance. It’s a toolbar element rendered only for logged-in users — Google never sees it, and visitors never see it. This is purely cosmetic, so there’s no risk in cleaning it up.

Method 1: Hide It for Everyone

The cleanest fix is a tiny PHP snippet that removes the toolbar node — the approach confirmed on the official Bricks forum. Add it with the Code Snippets plugin or your child theme’s functions.php:

/**
 * Remove the "Rendered with Bricks" admin bar link.
 */
add_action( 'admin_bar_menu', function ( WP_Admin_Bar $wp_admin_bar ) {
    $wp_admin_bar->remove_node( 'editor_mode' );
}, 999 );

Why priority 999? The admin_bar_menu action builds the toolbar, and Bricks adds its node partway through. Hooking late — after everything else has run — guarantees the node exists by the time you remove it. remove_node() is core WordPress API, so no Bricks-specific functions are involved.

Method 2: Keep It, Restyle It

Don’t want it gone entirely? Three lighter options:

Hide it with CSS only. The item renders with the id wp-admin-bar-editor_mode, so a one-liner works from Bricks → Settings → Custom Code → Custom CSS:

#wp-admin-bar-editor_mode { display: none; }

Hide it for specific users. If you want the shortcut for yourself but not for editors or clients, gate it by capability:

add_action( 'admin_bar_menu', function ( WP_Admin_Bar $wp_admin_bar ) {
    if ( ! current_user_can( 'manage_options' ) ) {
        $wp_admin_bar->remove_node( 'editor_mode' );
    }
}, 999 );

Rename it. If the label feels too vendor-y but the shortcut is handy, rewrite it:

add_action( 'admin_bar_menu', function ( WP_Admin_Bar $wp_admin_bar ) {
    $node = $wp_admin_bar->get_node( 'editor_mode' );
    if ( $node ) {
        $node->title = 'Edit with Bricks';
        $wp_admin_bar->add_node( $node );
    }
}, 999 );

Method 3: The Cleaner Route

Whatever snippet you pick, never edit Bricks core files — anything inside /wp-content/plugins/bricks/. Plugin updates silently overwrite core files, so your fix vanishes on the next update, and a sloppy edit can break the builder itself.

Two update-safe homes for the code:

• Child theme functions.php — survives theme updates and travels with the theme.
• Code Snippets plugin — my default for one-off fixes like this. You toggle snippets on and off from the admin without touching a file, and it’s free on wordpress.org.

Rule of thumb: if a fix is three lines, it belongs in a snippet plugin — not in a file you’ll forget about.

Verify the Fix

• Log in and load the front end: the link should be gone from the toolbar.
• Hard-refresh (Ctrl/Cmd + Shift + R) — the toolbar is cached by the browser like any other element.
• Open the site in a private window: the badge was never there for visitors anyway, which doubles as proof that nothing else changed.
• If the snippet ever stops working after a Bricks update, inspect the toolbar HTML and look for the element whose id starts with wp-admin-bar- — that id is the node name to pass to remove_node().

The Takeaway

Small annoyances like this badge are the most searchable problems in the Bricks ecosystem — but the skill is in telling the two fix families apart. Pure CSS (hide, restyle) needs no PHP and survives anything. Hook-based fixes (remove, gate, rename) are more robust but must live in a child theme or snippet plugin — never in plugin core. Do that, and this cleanup stays cleaned through every update.

This is exactly the kind of tiny thing that eats build time, so it’s on my running list of five pitfalls every beginner hits with Bricks. And if you’re shopping for a snippet manager, the tools page covers the plugins I actually use — Code Snippets included.