Skip to content
My GoHighLevel MCP
Guide

Tidy up tags and custom values before they get out of hand

Years of "lead", "Lead", "new-lead" and "lead2"? Here's how to review, merge and rename tags and custom values with Claude, safely.

Product team

3 min read

Tags are the cheapest thing in GoHighLevel to create and the most expensive to leave messy. After a year or two, most sub-accounts have tags nobody remembers adding, near duplicates, and custom values with old phone numbers or last year's offer. Workflows and smart lists depend on them, so a mess here quietly breaks automations.

Claude makes the tidy-up quicker because it can read everything at once and make the changes you agree on.

Step 1: Get the full list

In Bright Smile Dental, list every tag, grouped by what looks like the same idea.

Claude lists the tags and points out likely duplicates, such as "new lead", "new-lead" and "NewLead". Scan the groups; you know which ones really mean the same thing.

Step 2: Agree on the names

Decide on one name per idea and a simple rule, for example lower case with hyphens. Tell Claude:

We'll use "new-lead". Rename "NewLead" to "new-lead".

Before you remove any tag, ask where it matters:

Do any workflows use the tag "lead2"?

Claude can read workflow triggers and steps, so you can see whether removing a tag would stop an automation.

Step 3: Move contacts, then delete the extra tag

To merge two tags, first put the right tag on the contacts, then remove the old one:

Add the tag "new-lead" to every contact tagged "lead2", then delete the "lead2" tag.

Because this changes many contacts and deletes something, Claude will check with you before it starts. If your organisation has switched off deletes in the panel, Claude will say so and the tag stays.

Step 4: Review custom values

Custom values hold things like the business phone number, the current offer or the booking link, and they appear in emails, texts and pages.

List the custom values and their current values.

Look for anything out of date:

Change "current_offer" to "Free roof check until 31 October".

One change here updates every template that uses the value.

Step 5: Write the rules down

Ask Claude for a short summary of the naming rules and the tags you kept, and share it with your team:

Summarise the tags we kept and what each one means, as a short list.

How often?

A quick review every quarter keeps things tidy. It takes a few minutes with Claude and saves hours of debugging a workflow that stopped firing because someone typed "Lead" instead of "lead".

Every rename and delete is recorded in the Activity log, with who asked for it, so you can always see what changed and when.

  • #contacts
  • #housekeeping

Written by

Product team

Guides and product news

The people who build My GoHighLevel MCP. We write practical guides for agencies and businesses running GoHighLevel from Claude, and we keep them up to date as the product changes.

More from Product team →

Keep reading

All articles →