- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
The order an agency should set up a client blog’s categories in, and which of those decisions are expensive to reverse once posts are live.
Blog Category Setup for a Client Site, Done Once and Done Right
Blog category setup is one of the few decisions in a client build that is expensive to change later. Categories in the platform’s blog builder are not just a filing system for the client’s writer — they sit inside the post URL, they generate the archive pages a reader browses, and they are what the sub-account’s navigation hangs off. Rename one after twenty posts are live and you have twenty changed URLs to redirect.
So the work happens before the first post, not after. This is the order an agency should do it in, the decisions that are hard to reverse, and the traps that only appear once a client site has real traffic on it.
Decide the URL shape before you create anything
The blog lives at a path on the client’s domain, and the category becomes part of the address of every post filed under it. Two choices are locked in at this stage: the blog’s own path prefix, and whether categories appear in post URLs at all.
Pick a short, plain prefix and keep it — /blog/ is the safe default because visitors, clients and crawlers all read it the same way. Resist a clever prefix that matches the client’s brand vocabulary; it reads well in a proposal and badly in a browser bar, and it is the element you are least likely to be allowed to change once the client’s other marketing points at it.
What each element costs to change later
| Element | Set where | Cost of changing it after launch |
|---|---|---|
| Blog path prefix | Blog settings on the sub-account | High — every post URL moves |
| Category slug | The category record | High — every post in it moves |
| Category display name | The category record | Low if the slug stays fixed |
| Primary category on a post | The post editor | Medium — that one URL moves |
| Author record | Blog settings | Low — display only |
| Post slug | The post editor | Medium — one URL, one redirect |
How many categories a client site actually needs
Five to eight is a workable range for most client blogs, and the reasoning is simple: a category exists to hold an archive page a reader would browse. If a category will only ever hold two posts, it is not a section of the site, it is a topic — and a topic with its own thin archive page is worse than no archive at all, because it competes with the posts inside it.
Build the list from the client’s services rather than from the writer’s content plan. Services change slowly, content plans change every quarter, and a category structure built on the plan has to be rebuilt each time the plan does. A plumbing client has emergency work, installations, maintenance and commercial work whatever this quarter’s article list says.
The one-category-per-post rule
Assign each post to a single category, even where the builder allows several. Multiple categories on one post produce the same content on more than one archive page and make the post’s own address ambiguous; the platform will pick a primary for you, and the pick is not always the one you would have made. Where a post genuinely belongs in two places, choose the category the reader would have browsed to find it, and link to it from the other section’s pillar post.
Creating the categories in the sub-account
The steps are short, and doing them in this order avoids the rework:
- Set the blog path prefix in the sub-account’s blog settings, before any category exists.
- Create the author records the client will publish under. An author added later does not retroactively appear on earlier posts.
- Create each category with the display name you want a reader to see, then edit the slug by hand — the auto-generated slug from a long display name is usually longer than it needs to be.
- Write the category description. It is the visible text on the archive page and is often the only content there until several posts exist.
- Publish one placeholder-free post per category before handing the blog over, so no live archive page is empty.
That last step matters more than it looks. An empty archive page is a live URL with nothing on it, and it is exactly the kind of page that gets crawled, indexed and then held against the site. Either fill it or do not create the category yet.
Slugs: the part that is hard to undo
The category slug is the piece of the URL you inherit forever, so write it deliberately. Keep it lowercase, hyphenated and free of stop words. Keep it short — a two-word slug is easier to say aloud and to fit into a navigation label. And keep it general enough to survive the client renaming their own service: a slug tied to a product name has to change when the product does.
If a slug does have to change after launch, treat it as a migration rather than an edit. Note the full list of affected post URLs before you change anything, make the change, then put a redirect in place from every old address to its new one. Doing this in the other order means a window where the client’s existing links resolve to nothing.
Reusing the structure across client accounts
An agency that builds the same blog shape repeatedly should not rebuild it by hand each time. Capture the working sub-account as a snapshot and load new client accounts from it, so the path prefix, the category set and the author scaffolding arrive already configured. Check what the snapshot actually carries before you rely on it — asset-level behaviour is not uniform, and the rules governing protected snapshot assets decide what a client can edit in the account you hand them.
Where the categories are genuinely client-specific, keep a generic set in the snapshot and rename the display names per account while leaving the slugs alone. Renaming a display name is free; renaming a slug is a migration, and doing it on day one of a client build is how agencies end up with redirect debt before the first post is written.
Once the categories exist
Two jobs follow immediately. The first is navigation: link the categories from the site’s menu or footer, because an archive page nothing points at gets very little crawl attention and no human traffic at all. The second is distribution — decide how a new post reaches the client’s list, and build that path once rather than per post. Sending each publication through a maintained sequence is cleaner than an ad-hoc broadcast, and the setup, limits and pause behaviour of email sequences are worth knowing before the client’s list is attached to it.
Finally, write the structure down somewhere the client can see it: the category list, the slug for each, and the rule for which posts go where. The document takes ten minutes and it is the thing that stops a well-meaning client adding a ninth category in month three because they could not tell which of the existing eight a post belonged to. For more on how the agency-side pieces fit together, the platform overview for agencies covers the surrounding build.
See also: Sitemap for Funnel Pages: What Belongs In It
Frequently Asked Questions
How many blog categories should a client site have?
Five to eight suits most client blogs. A category earns its place by holding an archive page a reader would browse, so if it will only ever contain two posts it is a topic, not a section. Build the list from the client’s services rather than from a quarterly content plan, because services change far more slowly.
Should a post be filed under more than one category?
No. Multiple categories put the same content on several archive pages and make the post’s own address ambiguous, because a primary has to be chosen anyway. Pick the category a reader would have browsed to find the post, and link to it from the other section’s main page instead.
Does the category appear in the post URL?
In the common configuration the blog path prefix and the category slug both sit in front of the post slug, which is why the slug is the expensive part of the setup. Confirm the shape in the sub-account’s blog settings before you create categories, not after posts are live.
What happens if I rename a category later?
Renaming the display name is safe. Changing the slug moves the URL of every post filed under it, so treat it as a migration: list the affected post URLs first, make the change, then redirect each old address to its new one. Doing it in the other order leaves existing links resolving to nothing.
Can I carry a blog structure between client sub-accounts?
Yes, through a snapshot. Configure one sub-account with the path prefix, categories and author records you want, then load new client accounts from it. Check what the snapshot carries and what stays editable for the client before relying on it for a handover.
Is it a problem to have an empty category archive?
It is a live URL with no content on it, which is the kind of page that gets crawled and counted against the site. Either publish a post into each category before handover, or create the category later when there is something to put in it.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.