Most people who save templates and hashtag groups do it in one burst of enthusiasm, then stop using them within a month. The library fills up with “Launch 2”, “Launch final” and a hashtag set that still mentions a sale from March.
The mechanics of saving are simple and covered on the Post templates and Hashtag groups pages. This post is about the part those pages cannot do for you: deciding what to save, naming it so you can find it, and keeping the whole thing small enough to trust.
A worked example: one bakery, one afternoon
Say you run social media for a neighborhood bakery. You post five or six times a week across Instagram, Facebook and Google Business Profile. Open your last 30 posts and sort them by shape rather than topic. You will probably find something like this:
- Fresh batch. “Out of the oven: [item]. Come by before [time].” About eight posts.
- Weekly special. The same four-line structure every Monday. Four posts.
- Event or market stall. Date, place, what you are bringing. Three posts.
- Behind the scenes. No fixed shape. Eleven posts, all different.
- Closed or hours change. Two posts, both written in a hurry.
The first three are templates. The behind-the-scenes posts are not, and trying to force them into one would flatten the thing that makes them work. The hours-change post is the interesting one: you rarely write it, but when you do, you are stressed and likely to leave out the date. A template with the date and reopening time laid out as blanks earns its place even at two uses.
Now the hashtags. Look at what you actually typed under those posts and cluster it by what the tags are for:
| Group name | What it holds | Used on |
|---|---|---|
| Local | Neighborhood, city, “support local” style tags | Almost everything |
| Sourdough | Tags for bread and baking communities | Fresh batch posts |
| Market days | The market’s own tag, the city’s farmers market tags | Event posts |
Three groups, each answering a different question: where are we, what is this, and which event is it. Notice what is missing: a single giant “All bakery tags” group. That one is easy to build and hard to use well, because every post ends up with the same 25 tags whether they fit or not.
The whole library is four templates and three groups. That is deliberately small.
What deserves a template
A rule of thumb that works: save it when you have written the same structure three times. Two might be a coincidence. Three is a format.
Questions to ask before saving:
- Would the fixed words survive six months? If a template names a price, a date or “this week”, it will be wrong the day you forget to edit it. Templates have no placeholders, so what you save is exactly what comes back. Either leave the changing parts as obvious blanks, such as
[item]or[date], or do not save it. - Is the structure the valuable part? Order of information, the call to action, the sign-off. If yes, save it. If the value is in a particular turn of phrase that only works once, it is a one-off.
- Does it need media, channels or a time? Those are not saved. If the hard part of the post is choosing the right photo, a template will not help. If you want something to go out on its own on a rule, look at recurring posts instead.
A trick for blanks: use square brackets and a word you would never publish by accident, like [ITEM] in capitals. When you scan the finished caption before scheduling, an unfilled bracket jumps out.
Name things for the person searching at 8 a.m.
You will pick from a list, usually in a hurry. Names that sort and scan well:
- Start with the format, not the date. “Weekly special” beats “Special March”.
- Add the channel only if it changes the text. “Event, short” and “Event, long” are useful. “Event Instagram” is not, unless the wording really is Instagram-only.
- Never use “new”, “final” or a version number. If you want a new version, edit the old one through the API or delete it and save the replacement. A list with “Launch”, “Launch new” and “Launch new 2” has told you nothing.
- Keep first-comment snippets obviously separate in your head. They live in their own list, so give them names that describe the content, such as “Local tags and link”, not the post type.
Hashtag group names follow the same logic. Name them after the question they answer (where, what, which event), not after a campaign that will end.
Build hashtag groups small and stack them
Because adding a group skips tags the post already contains, you can add two or three groups to one post without producing duplicates. That makes narrow groups more useful than wide ones. The bakery’s fresh-batch post takes “Local” plus “Sourdough”. The market post takes “Local” plus “Market days”. Change one group and every post you build from now on picks up the change.
Two practical points:
- A group holds up to 30 hashtags, but that is a ceiling, not a target. A group of six or eight that you actually believe in is better than 30 pasted from a list. How many tags help on a given platform is its own question; how many hashtags to use on Instagram covers it.
- Editing a group changes what gets added from then on. It does not rewrite posts you have already made, which is also why a stale group quietly keeps going out until you look at it.
If you would rather keep the caption clean, add the group, then move the tags to the first comment. First comment ideas has more on what belongs there.
Mistakes that make a library rot
Saving a finished post as a template. The caption you are proudest of is full of specifics. Saved as-is, it becomes a trap. Strip it down to the structure first.
Saving the “perfect” tags once and never looking again. Tags drift. A community tag gets taken over by spam, an event ends, a competitor starts using your branded tag. A group is a snapshot of your judgment on the day you built it.
One template for every platform. The same words rarely suit LinkedIn and X. If a template reads wrongly on half your channels, write a shorter variant and name it for the difference, or start from the template and adjust each network’s version before scheduling.
Treating the template as the draft. A template gets you to a first paragraph faster. It does not replace reading the post once more before it goes out, especially the places where you left blanks.
Letting the list grow because nothing ever gets deleted. There is a cap per organization, but the practical limit is much lower: the number of names you can scan in a few seconds.
A quarterly pruning checklist
Put this on the calendar, with a calendar note if you like. It takes ten minutes.
- Open the Templates list. For each one, can you remember the last time you used it? If not, delete it.
- Read every template aloud. Any date, price, season or offer that has gone stale?
- Open the Snippets list and do the same. Are the links in your first-comment snippets still the right ones?
- Open each hashtag group. Is every tag one you would still choose today? Look a few at a time on the platform itself.
- Are two groups so similar you always add both together? Merge them.
- Does a group exist for a campaign that ended? Delete it.
- Have two teammates saved the same format under different names? Everything is shared across the organization, so agree on one.
Everyone who can create posts sees the same lists, which is good for consistency and bad for tidiness. Decide who prunes, or the job goes to nobody.
When to skip all of this
If you post a handful of times a month, every post is different and you rarely use the same tags twice, a library is overhead. Use it when you notice yourself copying an old post to start a new one. That moment is the signal.
For teams that script their own content, both lists are also available through the API and the MCP server, so an assistant can list what you have and create or update entries. The API guide covers authentication. Renaming a template or changing a group’s tags currently happens there rather than in the composer panels.
Where to go next
If you are writing a month of posts in one sitting, templates pair well with bulk scheduling. If drafting is the bottleneck rather than structure, the caption assistant can write a first pass. And if you landed here looking for a downloadable planner, the content calendar template is the one you want.
To set up the library, open the composer, write out the structure you keep retyping, and save it. You can start free; templates and hashtag groups have the same limits on every plan.