Why the back catalogue needs a review, and when
Posts outlive the facts inside them. A "visit us" post gives the hours from before the winter change, a carousel quotes a price from before the last increase, a video shows a colleague who has since moved on, a joke that seemed harmless now reads badly. None was a mistake when published. And accounts are read out of order: a visitor who follows a saved link, a share or an embed on the brand's website lands on whatever post they were sent to, and an evergreen post such as a how-to is read as current whenever it was written. The back catalogue is part of what the brand says today, whether or not anyone has looked at it.
The site's existing routines each cover one slice of it, for one reason. The page optimisation guide audits the profile, pinned content and highlights. The rebrand rollout tutorial changes names, handles, images and pinned posts. The sale end SOP takes down pinned sale posts and bio links, and the opening hours SOP corrects the hours on each profile. The tutorial on withdrawing an asset from every channel pulls one asset or claim from everywhere it runs, and the user-generated content guide keeps a register so that one customer's withdrawn content can come down. The social media presence audit scores profile set-up, content mix and cadence. A YouTube channel's videos have their own library audit in the YouTube section, which works on packaging and traffic sources. None works through the posts already published and asks whether each still holds against today's facts, claims, people and voice. That is this tutorial's job, and it sits with the other routines in the social media management section.
A review runs on a schedule the team sets for itself, or on a trigger:
- A rebrand or new positioning. Posts that name the old brand or promise what it no longer stands for.
- A product, price or offer change. Posts that quote a discontinued line, an old price or an ended promotion.
- A retired claim. Posts that repeat or paraphrase wording the claims library no longer supports.
- Someone asking to be removed. A colleague, a former colleague or a customer whose content was reposted.
- Inheriting the account. A new social lead, an agency handover or a forgotten account, where nobody knows yet what the posts say.
Neighbouring jobs stay out. A post that is wrong now and that customers are acting on is an error, and the live ad and page error response SOP pulls the wrong version and fixes it through approval straight away; the review is for what has drifted, not what is on fire. This tutorial is general practice, not legal advice. It sets no record-keeping duties or retention periods, does not describe how any platform treats an edited, hidden or deleted post or the ads built on it, and makes no claim about whether old posts affect how new ones are shown.
Before you start
- The profile work done. The page optimisation guide and the social page optimisation checklist cover the profile and what is pinned; the community management guide supplies the published moderation rules and the moderation log.
- The account register, with working access. The securing social media accounts tutorial lists every account, dormant ones included. Where an account should not exist, the guide to structuring social accounts decides whether it is revived, merged or closed before anyone reviews its posts.
- The reference documents. The voice guide, the claims library with its retired entries, the tracking scheme for links, and the registers of who agreed to appear and which customer content the brand may use.
- A named decision-maker for removals. Someone who can say yes to hiding or deleting, and a route to whoever handles data protection, legal and compliance. A regulated business asks compliance before deleting anything.
- A log in business storage. A row per post that changes: its link, the account, when it was published, the question it failed, what depends on it, the action, who decided and when. That record is the review's audit trailThe record, attached to the work item, of what was reviewed, which version, who reviewed it, when, what they decided and the evidence relied on..
The steps
Name the trigger and the scope
Write down why the review is happening, because the reason sets how far it reaches and what comes first. A former colleague asking for the videos she presented to come down is narrow and urgent: the scope is every post she appears in, on every account and in the scheduled queue, and it is handled before any broader work. A rebrand reaches every post that names the brand or sends people somewhere that has moved. A retired claim reaches every post that repeats the wording or makes the same point in other words. An inherited account reaches everything. Record the trigger, the accounts in scope, the span of posts, the questions that apply, the owner and the decision-maker.
Keep a copy of what is already published
Take a copy of the accounts in scope before changing a single post. The choosing platforms guide advises exporting whatever a platform allows before leaving it; a review needs the same habit for other reasons. A copy lets the team reverse a mistake, answer a later question about what a post used to say, and show what the review found. Each platform documents its own export options in its help centre, Meta's in the Meta Business Help Centre; where no export covers what you need, links and screenshots will do. A copy that includes customers' comments and messages is customer information, so it goes into business storage, as the securing tutorial advises for exports. How long to keep it, and whether anything must be kept at all, are questions for whoever handles data protection and compliance.
Check what visitors meet first
Start where visitors start. The profile, pinned posts, highlights and the first screen of the feed already have an owner: the page audit covers them, and a rebrand changes them on launch day. Run that audit first, or confirm that it ran recently, rather than repeating it here; a tidy back catalogue under a stale pinned post has fixed the wrong end of the account. Then list the older posts that still draw visitors: those the platform's own reporting shows still being viewed or shared, those the website, emails or partners link to, and those whose tracked links still bring traffic in web analytics. They go to the front of the queue.
Sort posts against the review questions
Work through the posts in scope, priority list first. Searching the account or the copy speeds this up: try the old brand name, the retired claim's wording, old prices and offer names, discontinued products, the old booking address and the names of anyone who asked to come down. Check the scheduled queue too, which the withdrawal tutorial lists among the places assets hide, because a post queued before the change is the next old post.
- Facts and offers. Hours, addresses, prices, products, services, codes and promotions that have changed or ended, in a post a visitor would read as current.
- Claims. Every objective claim, checked against the claims libraryA record of every marketing claim in its exact approved wording, with the evidence behind it, the conditions and markets it is approved for and the approver..
- People. Colleagues checked against what they agreed; customers and creators against the permission recorded for their contentContent about a brand made by customers or creators rather than by the brand itself..
- Voice. Tone, jokes and references measured against the current voice guide.
- Links. Destinations that have gone or moved, and links without the tracking the scheme asks for.
- Accessibility. Image descriptions and captions on posts that still draw visitors.
- Comments. Complaints, corrections and arguments underneath. They do not fail a post; they limit what may be done to it.
Record which question each flagged post failed and group the flags into categories, such as evergreen posts with old hours or a former colleague's series, so that the decision is made once per category with exceptions noted.
Find what depends on a post before changing it
Chesterton's fence applies to old posts as much as to old reports: learn the reason a thing exists and what still depends on it before removing it. For each post marked for anything but keep, check:
- Why it went up. An apology, a correction, the answer to a public complaint or a competition result was posted to be on the record, and removing it can look like withdrawing it.
- What links to it. Embeds and links on the website, in emails and automated journeys, and on partners' or press pages. Ask each owner before the post changes.
- Whether it runs as an ad. If the post was ever promoted or sits behind a running ad, talk to the paid team first. What happens to an ad when its post is edited, hidden or deleted is for each platform's help centre to say.
- Whose content it is. A repost of a customer's or creator's work is governed by its permission and credit.
- What sits under it. The community management guide is plain that criticism is not removed and that screenshots travel faster than deletions. Whatever a platform does with the comments when a post goes, the customer who complained sees a brand that made the complaint disappear. A post with criticism under it stays; if its content must change, the change is made by an edit or a reply.
Note what you find in the log beside the post.
Choose keep, edit, hide or delete for each category
Sort the options by how easily each can be undone, as the one-way and two-way doors framework suggests. Keep costs nothing and suits posts plainly tied to a past season, event or date, posts with criticism under them, and anything that forms part of the public record. Edit, where the platform allows it, or a reply giving the current position, suits evergreen posts with an outdated fact, price or link, and leaves the conversation in place. Hide or archive, where a platform offers it and its help centre confirms the post can be restored, is treated as the reversible way to take a post out of view and suits retired claims, off-brand posts and posts that cannot be fixed; each platform documents whether it offers this and what it does, Meta in its Business Help Centre, so read the current page before relying on it. Delete is the one-way door: treat it as permanent, because the brand cannot count on getting a post back and a removal the audience noticed cannot be un-noticed. Keep it for what a person asked to have removed, and for posts that cannot be fixed, with nothing depending on them, a copy kept and no complaint underneath.
A few rules sit on top. People decide what happens to posts about them: the agreement in the guide to featuring employees in social content says what happens when a colleague leaves or changes their mind, customer permission is revocable, and the employer brand guide says to remove content when someone leaves if they ask. If it is unclear whether hiding meets a request, ask the person. A retired claim comes out of view: the claims library's retire step sends it to the withdrawal tutorial to be found wherever it runs, and an old post is one of those places. The approvals and compliance guide gives the reason, citing the ASA and the FTC's business guidance: marketing must not mislead, and every claim needs supporting evidence in hand before it is published. Where a complaint or challenge caused the retirement, anything beyond taking it down is for legal advisers, as the claims library tutorial says. Any new wording that touches a claim, a price or an offer, whether an edit or a reply, goes through the levels in the social media approval workflow.
Apply the changes in batches and log them
Work category by category: people's requests first, because someone is waiting; retired claims next; then facts and offers; then links, descriptions and voice. When a link points at a page that has moved, a redirect on the website may mend every post that uses it at once, so ask the web team before editing posts one by one. Where a post that still draws visitors lacks an image description or captions, add alt textThe text alternative to an image, read by screen readers and used by search engines. or captions where the platform allows, as the guide to accessible social media posts describes; an edited link follows the UTMURL tags identifying traffic source. scheme in the naming conventions and UTM guide. For voice, the measure is the brand voiceThe consistent personality a brand expresses in its words across channels, with tone adjusting to the situation and the audience. as the brand voice and cadence guide defines it now: a post that is merely dated can stay, while one that would embarrass the brand or hurt someone is hidden.
After each batch, look at the result as a visitor would and check that anything which pointed at a changed post still works. Log every post: what it was, the reason, the action, who decided and when. If a batch breaks something, stop, reverse what can be reversed and fix the dependency first.
Tell the people affected
Close each loop the review opened.
- The person who asked. Confirm that what they asked to have removed has come down everywhere the register lists, the scheduled queue and any ads included.
- Website, email and partner owners. Which posts changed or went, so embeds and links are updated, not found broken.
- The paid team. Any post that was promoted or sits behind an ad.
- Customer service and the community manager. A short note of what changed and why. If someone asks in public where a post went, answer honestly.
- The owners of the registers. Update the claims library's record of where retired wording ran, and the permission registers for featured colleagues and customer content.
A routine review needs no announcement to the audience; a rebrand's rollout already tells customers about the change.
Set the triggers for the next review
Attach a search of older posts to the procedures that cause drift: price and hours changes, the claims library's retire step, a featured colleague leaving or a customer withdrawing permission, a rename, and an account changing hands. Then set a scheduled review at an interval the team chooses, add it to the diary of whoever is accountable for the accounts, and note in the log the date, the scope and what was found, so that the next reviewer starts from the history. A reserve of approved evergreen posts is one more place where posts age, and the tutorial on building a reserve of evergreen social posts gives each of its posts a review date and the reserve a fixed review of its own.
Review questions and actions in one table
| Question | What fails it | Usual action | Where the rule lives |
|---|---|---|---|
| Are the facts still true? | Changed hours, address, prices or products in a post that reads as current | Edit, or correct in a reply; hide if it cannot be fixed; keep if tied to a past date | Opening hours and sale end SOPs |
| Is the offer still running? | An ended code, promotion or competition with nothing to show it ended | Correct or hide; keep dated event posts | Sale end SOP |
| Is the claim still approved? | Wording the claims library marks retired, or never approved | Hide where offered, otherwise edit or remove; record against the library entry | Claims library and withdrawal tutorial |
| Does everyone shown still agree? | A colleague who left or withdrew; a customer whose permission was withdrawn or lapsed | As the agreement says; remove what the person asked to have removed | Featuring employees, user-generated content and employer brand guides |
| Does it sound like the brand? | Tone, jokes or references the voice guide now rules out | Keep if merely dated; hide if it embarrasses or could hurt someone | Brand voice and cadence guide |
| Do the links work and carry tracking? | Gone or moved destinations; untracked links in posts still drawing visitors | Redirect the destination, edit the link, or correct in a reply | Naming conventions and UTM guide |
| Can everyone use it? | No image description or captions on a post still drawing visitors | Add them where the platform allows | Accessible social media posts guide |
| Is there criticism under it? | A complaint, a correction or an argument in the comments | Keep; change content only by edit or reply | Community management guide |
| Does anything depend on it? | An embed, an email link, a partner page, a running ad | Ask the owner before any change | Chesterton's fence |
A garden centre reviews its post archive (illustrative)
Drefnovalk Garden Centre reviews its back catalogue
Drefnovalk Garden Centre, an invented garden centre that runs its own cafe, starts a review for 2 reasons in the same month: the cafe has been renamed, and a former member of the plant team asks for the 12 care videos she presented to come down. Her agreement says existing videos stay unless she asks, and she has asked, so after the social lead logs the link to each video and checks that none is embedded on the website or used in an ad, all 12 come down from the centre's 3 accounts within 2 days, a scheduled repost is pulled from the queue, and she is told it is done.
The wider review covers 3 years of posts, about 900 in all. The social lead exports what each platform allows, screenshots the rest into the centre's shared drive, and checks the pinned posts first under the page audit: 2 still name the old cafe and are replaced. Searching the copy produces these categories:
| Category | Posts | Decision |
|---|---|---|
| Old opening hours in "visit us" posts | 31 | 9 still drawing visitors edited; the rest corrected by a reply with the current hours |
| The closed play area | 14 | Seasonal event posts kept; 3 evergreen "family day out" posts edited; the closure announcement, with 40 complaints and the centre's replies under it, kept |
| "Lowest prices in the area", retired in the claims library | 6 | 5 hidden where the platform offers it; 1 edited where it does not; recorded against the library entry |
| Links to the old booking page | 22 | The web team redirects the old address, so the posts stay as they are |
| Care guides with outdated product names | 18 | Edited, with image descriptions added to the 10 still drawing visitors |
| Seasonal posts naming the old cafe | 47 | Kept as history |
The web team, asked first, checks that the 4 care guides embedded on the website show the edited text. Nothing is deleted apart from the former colleague's videos. Every decision goes into the log with the reason, the action, who decided and the date, and the review closes with 2 triggers written into the centre's routines: the next price change includes a search of older posts for the old prices, and the leaver procedure for anyone featured on the accounts points to the register of their posts.
Common mistakes
- Deleting as the first resort. Deletion is the one-way door. Keep, edit and hide come first, and a regulated business asks compliance before deleting anything.
- Reviewing only the profile. The pinned post is right and the post beneath it still gives last year's price.
- Taking a post down to take its comments down. Criticism stays up; a vanished complaint thread is noticed.
- Treating every old post as an error. History can stay.
- Changing a post without asking what depends on it. An embed, an email link, a partner's page or a running ad breaks without anyone noticing.
- Deciding for the people in the posts. What a colleague or customer asked for, and agreed to, decides the action.
- No copy and no log. Nothing can be reversed or explained.
- A one-off clean-up. Without triggers in the procedures that cause the drift, the next review starts from the same position.
