In this follow-up tutorial to my Custom Login & Register Pages, I'll show you how to add email verification to your Bricks Builder registration flow without installing a single plugin.
Right now, anyone can register on your site with any email address, real or not, and be logged into the dashboard seconds later.
Nothing verifies that the person owns that inbox. Nothing verifies the inbox exists.
Bricks has a built-in fix. One setting, two pages, and about ten minutes.
What Changes After You Turn This On
The new flow works like this:
User submits the registration form
They see "Please check your inbox to verify your email address"
WordPress sends them an activation email with a unique link
Until they click it, the account stays inactive
If they try to log in first, they get "Your account is inactive"
Clicking a valid link lands them on your verification successful page
Clicking a broken or tampered link lands them on your verification failed page, and the account stays inactive
What You'll Learn
Enable Bricks Builder's built-in User Activation feature
Send automatic activation emails to new users
Block inactive users from logging in until they verify
Create a Verification Successful page
Create a Verification Failed page (for invalid/tampered tokens)
Auto-login users after successful email verification
Manually activate/deactivate users from the WordPress dashboard
Resend activation emails to users who didn't receive them
Reuse your existing Bricks template for verification pages
Why This Matters More Than It Looks
Three things you get from a single setting:
Fake signups stop working: A bot filling your form with throwaway addresses ends up with a pile of inactive accounts that can do nothing. Combined with the Turnstile spam protection, most automated signup abuse dies at the door.
Your email list stays clean: Every verified account is an address that provably receives mail. If you push registrations to an email tool, you are not building a list full of bounces.
You get a suspension mechanism: The activation status column doubles as a way to lock out a problem user without touching their content.
