How to Create a Social Media Style Guide for a Small Team

Short answer: A social media style guide for a small team is a short shared document that defines how your brand sounds, how posts are formatted, which hashtags and images you use, how links are handled, and who replies to comments. Keep it to one or two pages, base it on real examples, and include rules for automated posts so that content published by tools looks the same as content written by hand.

Why small teams need a style guide more than big ones

Large companies have brand departments, approval workflows and dedicated social media managers. Small teams have three people who post “when they get a moment”. One writes in formal full sentences, another uses five emoji per post, and the owner posts late at night in capital letters. Followers notice. The account feels like several different businesses sharing a logo.

A style guide fixes this without adding bureaucracy. It answers the small questions that otherwise get decided differently every day: Do we say “we” or the business name? Do we use hashtags on LinkedIn? How do we write prices? What do we do when someone complains in the comments? Once the answers are written down, anyone on the team can post confidently, a new hire can start in an afternoon, and automated posts can be configured to match.

The goal is not perfection. It is consistency: a follower should recognise your posts before they see your name.

Start with voice: three words and a few examples

Voice is the part most teams struggle to describe, so keep it concrete. Pick three adjectives that describe how you want to sound, and for each one add what it does not mean. For example:

• Helpful, not preachy. We share tips people can use today; we do not lecture.
• Friendly, not jokey. Warm and plain; humour is welcome but never at a customer’s expense.
• Expert, not technical. We know our subject, but we explain it in everyday words.

Then add three or four real posts that you consider good examples, and one or two that missed the mark with a note on why. Examples teach voice far better than definitions. If you are unsure where to start, look at your posts that received genuine comments and replies, not just likes, and describe what they have in common.

Also decide the practical grammar of your voice: first person plural (“we”) or brand name, contractions or not, British or American spelling, and how formal you are in replies compared with posts.

Formatting rules that save daily decisions

This is the part of the guide people will consult most often. Write short, specific rules:

• Length. A target length per network, for example one or two sentences on X and Bluesky, a short paragraph on Facebook and LinkedIn. Our overview of platform character limits helps set realistic targets.
• Capitalisation. Sentence case for headlines or title case? Pick one. Avoid whole words in capitals except for acronyms.
• Emoji. Allowed or not, how many, and which ones fit the brand. A common rule is at most one or two per post and never in place of words.
• Numbers, dates and prices. Write dates in one format (“Tuesday 6 October”), use numerals for figures, and say whether prices appear in posts at all. Many teams keep prices on the website only, because they change.
• Calls to action. A short list of approved phrasing, such as “Read the guide”, “See opening hours” or “Book a table”, so posts do not all end with “Click here”.
• Mentions and tags. When to tag partners, suppliers or customers, and the rule to ask permission before tagging individuals.

Hashtags: a short approved list

Hashtags cause more inconsistency than almost anything else. Settle it in the guide:

1. Brand hashtag. If you use one, spell it exactly once in the guide and use it everywhere.
2. Topic hashtags. A list of five to fifteen hashtags that match your main content themes. Check each one first to see what other people post under it.
3. Per-network rules. Hashtags matter differently on each network. Many brands use none or one on Facebook, a few on LinkedIn and Instagram, and relevant ones on Mastodon, where they help discovery.
4. Formatting. Use capital letters for each word in multi-word hashtags (#SmallBusinessTips) so screen readers pronounce them correctly.

If your posts are automated from a blog feed, note in the guide how hashtags are generated. Some tools create hashtags from post categories or tags, so the blog’s category list effectively becomes your hashtag list. For a deeper look, see the hashtag strategy guide for automated posts.

Images, colours and accessibility

A visual section does not need a designer. Include:

• Image sources. Your own photos first, licensed stock second, and a rule that nobody uses images found through web search.
• Sizes. The recommended upload sizes for your main networks, or one safe default such as a 1200 by 630 pixel landscape image for link posts.
• Brand colours and fonts for graphics made in a design tool, with hex codes.
• Text on images. Keep it short and large enough to read on a phone.
• Alt text. A rule to describe images for people using screen readers, where the network allows it. The MDN accessibility documentation is a good primer on why this matters.
• Link preview images. For posts linking to your website, the preview image comes from the page’s featured image or Open Graph tag. Make “set a featured image” part of the publishing checklist.

Replies, comments and difficult situations

Publishing is only half of social media. The guide should say who reads comments and messages, how quickly you aim to reply (for example, within one working day), and how you handle common situations:

• Questions: answer publicly if the answer helps others, move to private messages if it involves personal details or orders.
• Complaints: acknowledge, apologise where appropriate, and offer a private channel to resolve it. Never argue in public.
• Spam and abuse: hide or delete according to a written rule, and block repeat offenders.
• Sensitive news: who decides to pause scheduled or automated posts when something serious happens locally or globally.

Add two or three template replies in your voice. They are starting points, not scripts; each reply should still be personal.

Rules for automated and scheduled posts

If some of your posts are created automatically, for example from your blog’s RSS feed, the style guide should cover them explicitly. Otherwise automation quietly introduces a second voice. Decide:

• What text the post uses. Usually the article title, sometimes the title plus the excerpt. This means headline writing on the blog is now social copywriting, and the guide’s formatting rules apply to blog titles too.
• Which excerpt appears. If the excerpt is auto-generated from the first paragraph, make sure your first paragraphs read well on their own.
• Link tracking. A standard set of UTM parameters, for example utm_source set to the network name and utm_medium=social, so reports stay comparable.
• Timing. Posting windows for each network, so automated posts do not appear at 3 a.m. local time.
• Which content goes where. For example, product news to Facebook and Instagram, industry articles to LinkedIn, everything to the Telegram channel.

Writing these rules down also makes it easy to review the automation later: if a post looks wrong, you can check whether the configuration or the rule needs to change.

A one-page template you can copy

Here is a simple structure. Fill it in during one meeting and revisit it every six months:

1. Who we are for: one sentence describing the audience.
2. Voice: three adjectives with “not” statements, plus good and bad examples.
3. Grammar basics: we or brand name, spelling variant, date and number formats.
4. Per-network notes: length, hashtags, emoji and best content type for each network you use.
5. Hashtag list: brand hashtag and approved topic hashtags.
6. Visuals: image sources, sizes, colours, alt text rule.
7. Links: UTM standard, whether to use link shorteners.
8. Automation: what is automated, from which feed, to which accounts, at which times.
9. Replies: who, how fast, templates, escalation.
10. Owner: the person who keeps the guide up to date.

Store it where the team already works: a shared document, the team chat’s pinned messages or the intranet. A guide nobody can find is a guide nobody follows.

Rolling the guide out without a fuss

A style guide only works if people use it. For a small team, rollout can be simple, but it helps to be deliberate about it:

1. Draft it together. Spend one hour with everyone who posts. Pull up ten recent posts and discuss which ones felt right. The rules that come out of that conversation will be accepted far more easily than rules handed down.
2. Start with the most common questions. You do not need every section on day one. Voice, hashtags and reply rules solve most inconsistencies; visuals and automation can follow a week later.
3. Apply it to your settings. Update your scheduling and automation tools to match the guide: default hashtags, UTM parameters, posting hours and the text template used for automated posts.
4. Review a sample every month. Pick five posts from the last month and check them against the guide. If a rule is ignored repeatedly, either explain it better or change it; a rule nobody follows is a sign that it does not fit how you work.
5. Onboard new people with it. When someone joins, the guide plus a few example posts is usually all they need to start posting on their first day.

Treat the guide as a living document. Small teams change quickly: new products, new networks, new people. A quick update every few months keeps it relevant without turning it into a project.

How PostRSS fits into your style guide

PostRSS publishes new items from your RSS or Atom feed to 66 networks, so the settings you choose there become part of your style guide. You can build each post from the item title, the item description, the page title or your own static text (nine combinations in total), turn feed categories into hashtags up to a set limit, add UTM parameters to every link, and restrict posting to chosen hours or exact times on paid plans. One feed can go to several targets with different wording for each. The features page describes every option, and the pricing page shows which networks each plan includes.

Related reading

• How to Make Auto-Posted Social Media Captions Sound Human, Not Robotic
• Team Workflows and Permissions for RSS Auto-Posting
• Social Media Accessibility: How to Make Automated Posts Readable for Everyone

The bottom line

A style guide turns a group of people who post occasionally into a brand with one recognisable voice. Keep it short, fill it with real examples, write concrete formatting and hashtag rules, cover replies, and include your automated posts so that tools follow the same rules as people. Review it twice a year and it will keep paying off.

FAQ

How long should a social media style guide be?

For a small team, one or two pages is enough. The guide should answer everyday questions quickly. Longer documents tend to go unread, so link to separate brand assets instead of pasting everything in.

Do we need different rules for each social network?

Keep one voice everywhere, but add short per-network notes on length, hashtags and content type. Those details differ between networks, while your tone and values should not.

Should automated posts follow the style guide?

Yes. Automated posts appear in the same feed as hand-written ones, so followers judge them the same way. Apply your headline, hashtag, link tracking and timing rules to the automation settings.

How often should we update the guide?

Review it every six months, or whenever you add a network, change your brand or notice repeated inconsistencies. Assign one person as the owner so updates actually happen.

What is the most common mistake in social media style guides?

Being too abstract. Describing the voice as professional and friendly does not help anyone write a post. Concrete rules and real examples of good and bad posts are what make a guide usable.