Most business websites look great on launch day. Every page is current, the team photos are recent and the pricing is correct. Then time passes. A service is discontinued but its page stays live. A staff member leaves but still appears on the team page. Prices change in the sales team’s spreadsheet but not on the website. Blog posts from five years ago still give advice that’s no longer true. Nobody notices because nobody is responsible. Content governance is how organisations stop that slow decay.
I see this on almost every site I audit. The site isn’t broken. It’s simply been neglected, one small inaccuracy at a time, until visitors start noticing that things don’t add up.
Content governance is the set of roles, rules and routines that prevent this. It sounds formal, but for most organisations it can be quite light: a few decisions written down and a handful of recurring tasks.
Why it matters
Outdated or inconsistent content has real costs:
- Lost trust. A visitor who spots an old price or a discontinued service wonders what else is wrong.
- Wasted sales time. Prospects arrive with wrong expectations based on outdated pages.
- Legal and compliance risk. Incorrect product information, outdated policies or old terms can create real liability.
- SEO decline. Thin, outdated and overlapping pages dilute a site’s quality and compete with each other.
- Editor confusion. Without standards, every editor formats pages differently, and the site looks inconsistent.
The core idea: every page has an owner
The single most useful governance rule is that every page, or every section, has a named owner. The owner is responsible for the accuracy of that content. They don’t have to make every edit themselves, but they’re the person who confirms it’s correct and notices when it isn’t.
Typical ownership might look like this:
- Service pages owned by the head of each service
- Pricing owned by the sales lead
- Team page owned by HR or the office manager
- Legal pages owned by whoever handles compliance
- Blog posts owned by their authors, or by the marketing lead for older posts
- Homepage and navigation owned by marketing
Ownership should be by role where possible, not by person, so it survives staff changes.
Record ownership somewhere visible. A spreadsheet works. A custom field in WordPress, such as “Content owner” and “Next review date”, shown in the admin list, works even better, because editors see it where they work.
Review schedules
Content goes out of date at different speeds. Set review frequencies by type:
- Pricing, offers and availability: monthly, or whenever they change
- Service and product pages: every six months
- Team, contact and location information: quarterly
- Legal pages and policies: annually, and whenever laws or practices change
- Evergreen articles and guides: annually
- News and time-bound posts: no review needed, but clearly dated
A “next review date” field makes this practical. A simple dashboard widget or filtered admin list showing pages due for review turns it into a routine task rather than something people have to remember.
A style guide
A style guide keeps content consistent regardless of who writes it. It doesn’t need to be long. Two or three pages covering the essentials is enough:
- Voice and tone. How the organisation sounds: formal or conversational, technical or plain.
- Terminology. Preferred terms, product names, capitalisation and words to avoid.
- Formatting. Heading styles, list usage, link text, date and number formats.
- Spelling conventions. British or American English, for example.
- Images. Style, sizes, alt text requirements and sources.
- Calls to action. Standard wording and placement.
- Accessibility basics. Descriptive links, heading order, alt text and readable language.
In WordPress, reinforce the style guide with the design system: limited block styles, a restricted colour palette, reusable patterns and locked templates. If editors can only choose from approved options, consistency happens automatically.
Publishing standards
Define what a page needs before it can go live. For example:
- Clear owner assigned
- Meta title and description written
- Featured image with alt text
- At least one internal link to related content
- Checked for spelling and broken links
- Approved by the owner if written by someone else
Pre-publish checklists in WordPress, either built into editorial plugins or added by your SEO plugin, make these standards visible at the moment they matter.
Regular content audits
Even with owners and reviews, a full audit once or twice a year catches what slips through. An audit looks at every page and asks:
- Is it still accurate?
- Is it still needed?
- Does it perform? Check traffic and engagement in analytics and Search Console.
- Does it overlap with other pages?
- Does it meet current standards?
For each page, decide on an action: keep, update, merge, redirect or remove.
A crawl tool like Screaming Frog gives you a full list of URLs with titles, word counts and status codes. Add traffic data from analytics and Search Console, and you have an audit spreadsheet.
Archiving and removal rules
One of the hardest governance decisions is when to remove content. People are often reluctant to delete anything. But a site full of outdated pages is worse than a smaller, accurate one.
Clear rules help:
- Discontinued services and products: redirect to the closest alternative, or to the parent category.
- Outdated news: keep it, clearly dated, unless it’s misleading. Consider adding a note if circumstances changed.
- Old blog posts with no traffic and no links: update if the topic is still relevant, merge if overlapping, otherwise remove and redirect to a related page.
- Event pages after the event: update to a summary with outcomes, or redirect to the events archive.
- Team members who’ve left: remove promptly, and redirect their profile page to the team page.
Always redirect removed pages with backlinks or traffic. A 404 loses that value and frustrates visitors.
Roles and permissions
WordPress roles support governance. Give people the level of access their responsibilities need:
- Content owners who review but rarely edit might be Editors or a custom reviewer role.
- Regular contributors might be Authors or Contributors, so their work is reviewed before publishing.
- Only a small number of people should be Administrators.
Review user accounts quarterly and remove anyone who no longer needs access.
Tools that help
You don’t need specialist software, but some tools make governance easier:
- Custom fields for owner and review dates, with admin columns
- An editorial workflow plugin for statuses and approvals
- An activity log to see who changed what
- A broken link checker, run periodically rather than constantly
- Scheduled reports from Search Console and analytics
- A shared calendar for review tasks
Start with the simplest version that works. A spreadsheet and a monthly reminder are far better than an elaborate system nobody uses.
Making it stick
Governance fails when it feels like bureaucracy. A few things help it last:
- Keep the rules short and practical.
- Explain the reason behind each rule.
- Make the right thing easy, through templates, patterns and checklists.
- Celebrate improvements, such as a cleaner site or better search performance.
- Review the governance itself once a year and drop what isn’t working.
The goal isn’t control for its own sake. It’s a website that stays as trustworthy in its fifth year as it was on launch day.
A simple governance starter kit
If all of this feels like a lot, start with four things. A spreadsheet listing your main pages with an owner and review date for each. A one-page style guide covering voice, terminology and formatting. A recurring monthly calendar reminder to check pages due for review. And a twice-yearly half-day audit of the whole site. That’s enough to stop most of the slow decay that affects business websites, and you can build on it as the site and team grow.
Governance for multilingual sites
If your site runs in more than one language, ownership needs to cover each version. A price change in English must reach the Hindi and Marathi pages too. Assign an owner per language, or make the main owner responsible for triggering translation updates, and include translated pages in every review cycle.
Frequently asked questions
Is content governance only for large organisations?
No. Small sites benefit too. A business with one editor still needs review dates and a rule for removing outdated pages. The system just stays lighter.
Who should lead content governance?
Usually marketing or whoever owns the website overall. They coordinate owners, run audits and maintain the style guide.
How long does a content audit take?
For a site with a few hundred pages, a thorough audit might take a few days spread over a couple of weeks. Larger sites can be audited in sections.
Should we delete old blog posts?
Only after checking traffic, links and relevance. Many old posts are worth updating. Truly obsolete posts with no value can be removed and redirected.




