News

Email Alias Naming for Beginners: Three Simple Rules

Most people create their first Gmail email alias on impulse, usually while signing up for something they do not fully trust with their primary address. The alias works, the signup goes through, and six months later nobody remembers which alias went where or why three of them contain a fragment of a real name. A small set of naming rules prevents that drift. The starting point is simple: use role words for shared addresses, project words for plus tags, and never put personal names inside a privacy alias, because a predictable name is the easiest kind to reverse-engineer.

Rule one: shared addresses get role words, not people

An address that more than one person reads should describe a function, not an individual. Support desks, billing teams, and event coordinators all outlive the person who first set them up. If the alias reads support@ or billing@, ownership can change hands without breaking every bookmark, invoice template, and contact card that points at it. If it reads with a person’s name in front, the address becomes a liability the moment that person leaves.

This matters even inside a single Gmail account. Google documents alias limits on its help pages, and Google Workspace allows 30 aliases per user, which sounds generous until a team burns half of them on personal-looking addresses that nobody wants to retire. Role words also make filtering trivial. A Gmail filter can be created on plus alias addresses or on any address that matches a pattern, so a naming scheme like support+orders@ and support+refunds@ routes mail into labeled folders without anyone opening a settings panel to check which alias is which.

The same logic applies to small operations running on consumer Gmail. A solo operator who runs a shop can still name an alias after the function it serves, and the address stays readable when a contractor or virtual assistant is given access later. As explained at allmail.one/blog/gmail-email-alias, predictability is the whole point: the name tells you what the mailbox is for before you read a single message.

Rule two: plus tags carry project words, and the base stays stable

Gmail plus aliases work by appending a plus sign and a label to an existing address. Mail sent to janedoe+shop@gmail.com and janedoe+newsletters@gmail.com both deliver to the same inbox, which makes plus tags the cheapest way to segment incoming mail without creating new accounts. The tag should name the project, vendor, or signup context, not the sender’s mood or the date. shop, taxes, travel, and conferences are durable labels. tryit, temp2, and test are not, because nobody can reconstruct what they meant a year later.

Keep the base address boring and the tags descriptive

The base address is the part before the plus sign, and it should stay fixed for years. Changing your gmail.com address is allowed once every 12 months, which is a real constraint if you have spent that change on a vanity tweak and then need a cleaner name for professional use. Treat the base as infrastructure and the tag as a label. If a project ends, stop using the tag; there is no cleanup required, and the old tag simply goes quiet.

Plus tags also give you a diagnostic tool. When a tag starts receiving spam, you know which signup leaked the address, and a filter can send that tag straight to trash while the rest of the inbox stays clean. That only works if the tag is specific enough to identify the source. A tag called info tells you nothing.

Rule three: privacy aliases never contain personal names

An alias used to shield your identity should be as uninformative as possible. The failure mode is easy to picture: a forum signup under janedoe+forum@gmail.com embeds the real first and last name in plain text, and anyone who sees the address can guess the base account. Predictable names are the easiest to reverse-engineer, which is exactly why privacy aliases should use neutral words, random strings, or project codes that have no connection to you. A tag like reader7 or acct42 does the job without handing over a clue.

The same caution applies to dot aliases. Gmail treats john.smith@gmail.com and johnsmith@gmail.com as the same mailbox, so inserting dots does not create a new address and does not hide anything. Anyone who knows the undotted form can reconstruct the dotted one. If the goal is separation rather than disguise, a second Google account provides a separate inbox with its own storage, recovery options, and filter rules, which is a stronger boundary than any naming trick.

There is a practical wrinkle worth planning for. Gmail will discontinue Send as for third-party addresses starting January 2027, so anyone who has been routing Yahoo or Outlook addresses through Gmail settings under Accounts and Import should expect to rework that setup. Send mail as currently supports up to 99 addresses, and the verification email that confirms each one lands at the external address rather than in Gmail. Naming discipline helps here too: label each send-as identity by the domain or role it represents so the migration list is readable when the time comes. Publications like AllMail, which publishes Gmail alias guides, are worth checking for current steps before you rebuild anything.

For beginners, the safest sequence is to write down the three categories before creating a single address: role words for anything shared, project words for plus tags, and neutral codes for anything private. Then check the limits, since Google Workspace allows 30 aliases per user and consumer Gmail has its own rules for plus addressing and username changes. A naming sheet with two columns, the alias and its purpose, takes ten minutes and saves hours of guesswork later. Keep the base address stable, keep the tags descriptive, and keep your name out of anything meant to be anonymous. That is the whole system, and it scales from one person to a small team without a rewrite.