Followup and follow-up: fixing your GoHighLevel tags
Tags are powerful! They drive workflow filters, segmentations and automations, but they’re also one of the easiest ways to turn a sub-account into a bit of a mess. And it happens organically. Every duplicate was defensible the day somebody typed it. It’s the accumulation that quietly becomes a problem.
Start with categories
The fix starts in Settings → Tags, and the first thing to look at is tags separately from their categories.
- Complete list — every tag in the account, in one flat list. This is what most people see and never revisit.
- Categories — like folders. They organise your tags but don’t change how a tag behaves: nothing stops you finding it, using it, or running automations on it. It just makes tidying possible.
Start with one category: lead source is the obvious first one, because “where did this lead come from” is where most tagging actually starts.
Lowercase, and lowercase only
This is where the duplicates come from: all of my tags are lowercase — no capitals, no special characters, just a simple list.
It sounds overly fussy until you see how the mess starts. Case variance is the classic one — “followup” and “Follow-Up” genuinely read as one tag, right up until the picker shows you both. Special characters and spacing do the same job a bit more subtly: “source / facebook” and “source-facebook” separate the moment somebody types the other one. A lowercase-only rule removes that whole class of mess.
Prefix with three letters
I’ve put every tag in a category — and then I’ve also still prefix it with three letters, so lead source tags all start with src.
Why both? Because of the moment you actually use them: typing “src” into the tag picker brings up all the source tags at once. You don’t scroll through folders hunting for the right one, and you don’t have to remember the exact spelling — just the family it belongs to. The prefix is doing the useful work when you’re in a hurry; the categories are what keep the list honest on the settings page.
Write the description
GHL lets you write a short description for a tag. Use it. It’s a line that tells people what the tag is for, gives some meaning behind it, and generally makes the list more self-explanatory.
Which matters most when it isn’t only you tagging. “High priority” and “important” coexist happily when one person is going through the list — in a team they eventually escape, and someone has to guess. A one-line description quietly answers it before anyone has to ask.
The payoff
Tag the contact again, and instead of scrolling screens of near-matches, you type “src”, the few that apply show up straight away, you tick them and you’re done. It’s a small, boring improvement — but the tags you search every day stay clean, the automations fire off them without surprises later, and your CRM environment stays nice and tidy.
An hour with your tag list now beats untangling it after six months of accumulated duplicates. I’ve seen it repeatedly — if you’d rather someone went through the tags, categories and workflows with you, that’s exactly the kind of thing I do.
Not got GoHighLevel yet? Grab your free trial here.