Tracking links only helps when everyone names them the same way. Without a shared convention, reports become hard to read, campaigns become hard to compare, and small spelling differences split one campaign into several unrelated rows. A naming convention solves this problem before it starts by giving every team member the same simple rules.
Agree on the Building Blocks First
Start with the fields you will use for every link: the source that sends the traffic, the medium that describes the channel, and the campaign name. Decide whether to use lowercase letters throughout, how to separate words, and how to handle abbreviations. Write these choices down in one short document, with examples of correct and incorrect names, so new team members can follow the same pattern without guessing.
Keep campaign names short, descriptive, and consistent. A name should tell a reader what the campaign is about without needing extra explanation, and it should stay the same across every channel where that campaign runs. Avoid vague labels, internal jokes, and names that change halfway through a campaign, because each change breaks the comparison you wanted to make.
Make the Convention Easy to Use
The best convention is the one people actually follow. Provide a simple template or form where team members select values from a list instead of typing free text. Limit the number of choices, use clear labels, and review new campaign names regularly during the first few weeks. When someone creates a name outside the rules, correct it kindly and explain the reason, rather than letting the exception quietly become the new habit.
Also decide who owns the list of approved names and how new ones get added. A single owner, or a small group, prevents duplicates and keeps the list tidy. Store the guide where the team already works, and mention it during onboarding so it becomes part of the normal workflow, not an extra document nobody opens.
Review Reports and Refine the Rules
After a campaign ends, review the report together. Look for names that were misspelled, inconsistent, or unclear, and update the guide to prevent the same issue next time. A convention should evolve slowly, based on real problems, not change with every campaign. With steady use, your reports will become easier to read, easier to trust, and easier to compare over time.
For related guides, read How to Read a Search Console Coverage Report and Fix Common Issues and A 30-Minute Technical SEO Check You Can Run Every Month.