Two settings in the GoDaddy dashboard look almost identical and behave nothing alike. One creates a forwarder that pushes mail to your Gmail inbox. The other creates an alias that drops mail into a mailbox on your own domain, which is fine only if someone actually reads that mailbox. Pick the wrong radio button and messages vanish into a void with no bounce, no error, and no warning. This guide is a mistake-avoidance checklist for anyone setting up GoDaddy email forwarding in 2026.
Know which tool you are actually configuring
The GoDaddy Email & Office Dashboard, the control panel at email.godaddy.com, is where both features live. The interface presents forwarding options close together, and the labels are not as distinct as they should be. A forwarder takes mail arriving at an address on your domain and relays it to a destination outside that domain, usually a Gmail or Outlook address. An alias is a second name for an existing mailbox on the same domain; mail sent to the alias lands in that mailbox’s inbox. These are different products with different outcomes, and the dashboard does not always spell that out.
Before you touch anything, answer one question: where should this mail physically live? If the answer is a Gmail account you check on your phone, you need a forwarder. If the answer is a mailbox you or a colleague already open in webmail, you need an alias. Write the answer down. Most forwarding failures I have seen trace back to someone creating an alias when they meant a forwarder, then wondering weeks later why a contact’s messages never appeared in Gmail.
Alias versus forwarder in plain terms
An alias is a pointer. It resolves to a mailbox that must already exist on your domain, and delivery happens inside GoDaddy’s system. A forwarder is a redirect. It accepts the message at your domain and hands it to an external destination such as Gmail. The practical difference: delete the mailbox behind an alias and the alias breaks; change the destination of a forwarder and mail follows you anywhere. If your goal is to forward GoDaddy email to Gmail, you want the forwarder, full stop.
Check what your plan actually includes before building anything
GoDaddy retired Workspace Email, and the replacement products do not all include the same forwarding features. Professional Email, which is powered by Titan, offers external forwarding on its Pro Plus, Premium and Ultra plans. The entry-level tier does not. If you are on a basic Professional Email plan and the forwarder option is greyed out, that is not a bug; it is the plan boundary. Check your subscription tier in the Email & Office Dashboard before you start, because discovering the limitation halfway through setup wastes time.
The free option changed too. GoDaddy no longer bundles free email forwarding with domains the way it once did. Email Forwarding now requires existing forwarding credits, which typically come from a legacy setup or a specific purchase. If you bought a domain last week expecting free forwarding and cannot find the toggle, that is why. The old advice floating around forums is simply out of date, and GoDaddy updates its help pages frequently enough that a guide from two years ago may describe an interface that no longer exists.
Forwarding credits and legacy accounts
Email Forwarding is independent of other GoDaddy email products, which cuts both ways. You can run a forwarder without owning a Professional Email mailbox at all, as long as you hold forwarding credits. Users can forward mail without a GoDaddy email product in that scenario. But if you have no credits and no paid plan with external forwarding included, the free path is closed. Confirm which situation you are in before promising a client that their mail will reach Gmail by Friday.
Avoid the silent-failure traps in the dashboard
The worst forwarding mistakes are the ones that produce no error message. A misconfigured alias is the classic case: the dashboard accepts it, the DNS records look healthy, senders get no bounce, and mail quietly accumulates in a mailbox nobody opens. Test every forwarder you create by sending a message from an outside account, not from the same domain, and confirm it arrives at the destination. If it does not arrive within a few minutes, check whether you built an alias by accident.
Watch for catch-all address settings. A catch-all forwards every misspelled or nonexistent address on your domain to one destination. That is useful for recovering typos in customer emails, but it also means spam aimed at random addresses lands in your inbox. If you enable a catch-all, point it at a mailbox you actually monitor, and review it monthly. A catch-all aimed at an alias on an unread mailbox is the worst of both worlds.
Distribution groups and email aliases are also easy to confuse. A distribution group delivers to several members at once, which is what you want for sales@ or support@ when multiple people handle those messages. An alias delivers to one mailbox. If three people need to see incoming mail, a distribution group is correct and a forwarder to one person’s Gmail is not, unless that person is prepared to relay everything manually.
Third-party forwarding rules can break your setup
If your destination is a Microsoft 365 mailbox, know that Microsoft 365 restricts automatic external forwarding by default. Messages forwarded from GoDaddy into an Outlook mailbox may be blocked or quarantined by the tenant’s outbound and inbound spam policies, depending on how the admin configured them. The fix is administrative: an admin adjusts the anti-spam outbound policy in the Microsoft 365 security center to allow automatic forwarding, ideally scoped to specific addresses rather than turned on globally. If you are forwarding into Outlook on the web and mail stops after a few days, this policy is the first thing to check.
Gmail is more permissive but not immune. Large volumes of forwarded mail from a single source can trip spam filters, especially if the original sender’s domain has weak authentication records. Set up SPF and DKIM on your GoDaddy domain so forwarded messages carry some credibility, and check the Gmail spam folder during the first week after setup. A forwarder that works for a week and then starts landing in spam is usually an authentication problem, not a GoDaddy problem.
One more trap: forwarding loops. If a forwarder on your domain sends to a Gmail address that itself auto-forwards back to your domain, you have created an infinite loop that fills both mailboxes and may get your domain flagged. Audit any existing auto-forward rules in Gmail before you add a GoDaddy forwarder that points there.
The checklist for a clean setup is short. Confirm your plan includes external forwarding or that you hold forwarding credits. Decide whether you need a forwarder or an alias, and write down the destination. Create the entry in the Email & Office Dashboard. Send a test from an external account. Check the destination inbox and spam folder. If the destination is Microsoft 365, confirm the tenant allows automatic external forwarding. Repeat the test after 48 hours to catch delayed policy blocks. That sequence catches the alias confusion, the plan limitation, and the tenant restriction in one pass, which covers nearly every way this setup goes wrong.
