Domain redirection helps ensure visitors always land on the right website, even if they type your domain without www or use a subdomain (like blog. or mail.). This guide shows you how to configure redirects in lemlist and highlights current limitations.
Learning objective
By the end of this tutorial, you’ll know how to add domain redirects in lemlist to cover subdomains and direct domain entries, and you’ll understand when redirects are not supported.
Why this matters
A complete redirection setup prevents broken links, lost traffic, and confusing user experiences. It also helps you standardize where your audience ends up (for example, always redirecting to https://example.com).
Prerequisites
You have access to your lemlist workspace with permission to manage domains.
Your domain is already added to lemlist (via Google provider integration where applicable).
Overview: Domain redirection in lemlist
Supported: It is possible to set up redirection for Google domains (feature availability may depend on the domain/provider configuration).
Not supported (current limitation): Redirections for Google domains purchased directly via lemlist are not currently supported.
Core lesson — Step-by-step workflow
Phase 1: Open your domain settings
From your lemlist dashboard, open your user menu (bottom-left) and click Settings.
Why: Domain redirections are managed from the workspace settings area.
In the left sidebar, go to Buy domains & emails.
Then, find the domain you want to configure and click Settings on the right.
Why: Redirects are configured per domain, so you must open the correct domain’s settings panel.
Phase 2: Add your URL redirections
Scroll to the URL Redirections section and use Create redirection to define your redirect rules.
Why: Adding the right combination of redirects ensures all common variations of your domain resolve correctly.
Method 1: Create a wildcard redirect (covers all subdomains)
In the From (left) field, enter: *
In Target url, enter your destination domain (example: https://example.com).
Click Add redirection.
Result: Any subdomain (for example, blog.example.com or mail.example.com) redirects to your primary destination.
Method 2: Cover direct domain entries (without subdomains)
Leave the From (left) field blank.
In Target url, enter your destination domain (example: https://example.com).
Click Add redirection.
Tip: Sometimes a minor display issue may show a . before the URL. If that happens, reload the page—this typically resolves it.
Best practice: Set up both redirects (wildcard + blank “From”) so you cover:
Subdomains (anything like *.example.com)
Direct domain entries (like example.com)
Practical application (recommended setup)
If your main website is https://example.com, a robust redirect configuration usually includes:
From:
*→ Target url:https://example.comFrom:
(blank)→ Target url:https://example.com
This combination reduces the chance of visitors landing on unexpected subdomains or incorrect versions of your site.
Troubleshooting & pitfalls
Issue: You can’t set up redirects for a Google domain you bought inside lemlist.
Root cause: Redirects for Google domains purchased directly via lemlist are currently not supported.
What to do: Use an alternative domain/provider setup that supports redirects, or manage redirects outside of lemlist (where applicable).Issue: A dot (.) appears before the URL in the interface.
Root cause: Minor UI display glitch.
Fix: Reload the page and re-check the redirection entry.Issue: Only some domain variations redirect correctly.
Root cause: Only one rule was created (e.g., wildcard but not direct domain, or vice versa).
Fix: Add both the*wildcard redirect and the blank “From” redirect.
Summary
lemlist provides flexible domain redirection options to help you manage traffic across domain variations. For the most complete setup, combine a wildcard redirect (for all subdomains) with a blank “From” redirect (for direct domain entries). Keep in mind the current limitation: Google domains purchased directly via lemlist do not support redirections at this time.