Done-for-you GoHighLevel setup, optimization, and support for agencies and service businesses.
    Back to Guides & Articles

    Naming Conventions That Keep Your GoHighLevel Account Organized

    A messy GoHighLevel account almost always shares one root problem: nobody agreed on how to name anything. This guide shows you how to set simple naming conventions that keep your GoHighLevel account organized, scalable, and easy for your team to use.

    Need Help Organizing Your GoHighLevel Account?

    We clean up, restructure, and document GoHighLevel accounts so your team can find and manage everything easily.

    Why Naming Conventions Matter in GoHighLevel

    Good naming conventions help you:

    • Find the right asset quickly, without guessing.
    • See how things connect just by looking at names.
    • Onboard new team members faster.
    • Avoid breaking important workflows by editing the wrong thing.

    You don't need a complex system. You just need consistent rules everyone follows.

    Principle 1: Make Names Descriptive, Not Cute

    Avoid vague names like "Workflow 1" or "New Funnel." Instead, include:

    • Type of asset
    • Purpose
    • Trigger or audience (when useful)

    Ask: "If someone new joined tomorrow, would they understand this name?"

    Principle 2: Use Prefixes for Quick Scanning

    Prefixes help you visually group assets and scan lists quickly.

    Common prefixes:

    • Workflows: WF –
    • Campaigns: CMP –
    • Funnels: FNL –
    • Websites: WEB –
    • Pipelines: PIPE –
    • Tags: SRC:, BEH:, LIFECYCLE:, FLAG:
    • Calendars: CAL –

    Naming Conventions for Workflows

    Recommended pattern: WF – [Purpose] – [Trigger or Source]

    • WF – New Lead – Website Contact Form
    • WF – New Lead – Facebook Ads Opt-In
    • WF – Appt Reminders – Sales Calendar
    • WF – Onboarding – New Client Welcome
    • WF – Reactivation – Old Leads 90+ Days

    Tips:

    • Include the specific calendar, form, or trigger when relevant.
    • Avoid "Workflow (copy)"—rename as soon as you duplicate something.
    • Use descriptions to document what the workflow does in more detail.

    Naming Conventions for Funnels and Websites

    Suggested pattern: FNL – [Offer] – [Objective]

    • FNL – GoHighLevel Audit – Booked Calls
    • FNL – Local Service – Quote Requests
    • FNL – Webinar – Registration & Replay
    • WEB – Main Marketing Site
    • WEB – Client Onboarding Portal

    Inside funnels, name steps clearly and number them:

    • 01 – Landing Page
    • 02 – Application Form
    • 03 – Booking Calendar
    • 04 – Thank You / Next Steps

    Naming Conventions for Pipelines and Stages

    Pattern: PIPE – [Department or Flow] – [Purpose]

    • PIPE – Sales – New Deals
    • PIPE – Delivery – Onboarding & Fulfillment
    • PIPE – Renewals – Existing Clients

    Stages – use short, outcome‑based names:

    • New Lead → Contacted / Qualifying → Call Booked → Call Completed → Proposal Sent → Closed Won / Closed Lost

    Naming Conventions for Tags

    Use prefixes to group them:

    • SRC: Facebook Ads, Website, Referral
    • BEH: Downloaded Checklist, Attended Webinar
    • LIFECYCLE: Lead, Client
    • FLAG: VIP, Do Not Contact

    Rules:

    • Don't create multiple tags that mean the same thing.
    • Don't use tags for data that should be in a field (e.g., industry).
    • Review tags regularly and merge/clean up as needed.

    Naming Conventions for Custom Fields and Custom Values

    Custom fields: [Group] – [Descriptive Name]

    • Business Info – Industry
    • Business Info – Monthly Revenue
    • Sales Data – Primary Offer
    • Onboarding – Start Date

    Custom values – use lower‑case with underscores:

    • business_name, support_email, main_booking_link, footer_disclaimer

    Naming Conventions for Calendars

    Pattern: CAL – [Role/Team] – [Purpose]

    • CAL – Sales – Discovery Calls
    • CAL – Delivery – Onboarding Calls
    • CAL – Strategy – Follow-Up Calls
    • CAL – Sales – John – Discovery Calls (for individual reps)

    Implementing Naming Conventions Without Chaos

    If your account is already full of inconsistently named assets, introduce naming conventions in phases:

    1. Define your naming rules in a simple document.
    2. Start renaming new assets using the new system immediately.
    3. Gradually rename high‑impact existing assets (critical workflows, main funnels, core pipelines).
    4. During a cleanup project, rename and reorganize legacy items.
    5. Communicate your conventions to everyone who builds in the account and make them part of your SOPs.

    Need help organizing your account? Our GoHighLevel Optimization & Cleanup service includes full naming convention implementation and asset reorganization.

    Ready to Organize Your GoHighLevel Account?

    Let us clean up and standardize your account so everything is easy to find, understand, and maintain.