Writing a social media style guide people actually use
Most style guides get written once and opened never. A useful one is short, specific to social, and full of examples. Here's what to put in yours.
2 min read

Ask a social team where their style guide lives and you'll often get a pause, followed by a link to a forty-page brand PDF last updated two rebrands ago. It has the logo clear-space rules. It does not tell you whether to use emoji on LinkedIn.
A social media style guide is a different document. It's a working reference for people who publish many times a day, across channels that each have their own culture. Here's how to write one that earns a bookmark.
Keep it short enough to skim
If it takes more than five minutes to find an answer, people will guess instead. Aim for something that fits on a few screens, with clear headings and examples rather than paragraphs of principle.
What to include
Voice, with examples on both sides
"Friendly but professional" means something different to everyone. Show it instead. For each trait, give a line that gets it right and a line that misses:
- Helpful, not salesy: "Here's how to set this up in two minutes" works; "Don't miss out on this game-changing feature!" doesn't.
- Confident, not stiff: "We fixed it" works; "The issue has been remediated" doesn't.
Channel by channel differences
Your brand voice should be recognizable everywhere, but its volume can change. Note what's different per network: post length, hashtag use, emoji, how formal replies should be, and which formats you favor.
Mechanics
The small decisions that otherwise get argued about in comments:
- Capitalization of product names and features.
- Dates, times and time zones.
- Numbers, currencies and units.
- How to write links, and which tracking parameters to add.
- Words and phrases you avoid.
Visuals and assets
Say where approved images, logos and templates live, and make it the easy option. If your team pulls assets from a DAM, connect it to where they publish. Our digital asset integrations bring Bynder, Acquia DAM, SharePoint, Box, Google Drive and OneDrive files straight into the Hootsuite media library, so the approved version is also the closest one.
Accessibility
Include a short section on alt text for images, captions for video, readable contrast on graphics, and writing hashtags in CamelCase so screen readers can pronounce them.
Replies and escalation
Write down how you respond to common situations: a compliment, a complaint, a question you can't answer publicly, and something that needs to go to legal or support. Include who to escalate to and how fast.
Make it easy to keep current
Give the guide an owner and a review date. When a new platform feature appears or a reply goes wrong, update the guide that week, while everyone still remembers why. A guide that changes with the team stays useful; one that's carved in stone gets ignored.
Put it where people work
Pin it in your team chat, link it from your content calendar and walk new hires through it in their first week. The best style guide is the one that's already open when someone needs it.


