Why repeated copy becomes a problem
A small website may mention its opening hours on the contact page, in a footer and beside a booking form. A service description might appear on the home page, a service page and an FAQ. Repeating useful information is not necessarily a mistake: visitors arrive on different pages and need answers where they are. The problem starts when each copy is edited separately. One page gets the new hours while another keeps the old ones.
Inconsistency can cause more than untidy writing. Visitors may not know which instruction to follow, and the person maintaining the site has to remember every place a detail appears. The aim is not to eliminate all repetition. It is to distinguish information that must stay identical from explanations that can be tailored to a page.
Find the details most likely to drift
Start with a short inventory rather than a full rewrite. List facts that are likely to change or cause confusion if they disagree: hours, addresses, contact methods, prices, eligibility rules, delivery areas, service names and steps in a process. For each item, note the pages where it appears and who is responsible for confirming it. A simple document or spreadsheet is enough for a small site.
Then classify each appearance. Does it need the exact same wording everywhere, or does the page need a short, context-specific summary? For example, a contact page may give full visiting details, while a footer only needs an address and a link. If the information is complicated, make one page the full explanation and let other pages point to it. This gives visitors a clear place to check details without forcing every page to carry the whole answer.
Choose a source of truth for each shared detail
A source of truth is the place an editor checks before changing repeated information. It might be a field in the content management system (CMS), a designated page, or a maintained content document. What matters most is that the team knows which version is authoritative. Record that choice in the inventory so a future editor does not have to guess.
Where the CMS allows it, store genuinely shared details in one reusable field or component. An address entered once and displayed in several places is easier to update than four independent text boxes. Reuse requires care, though: changing a shared block may affect pages the editor has not opened. Give reusable items clear names, check where they appear before editing, and preview the affected pages before publishing.
Not every similar paragraph belongs in a shared block. A home-page introduction and a service-page explanation may describe the same service but answer different visitor questions. Keep those passages separate, while checking that their underlying facts agree. Reusing a sentence simply because it sounds similar can make pages awkward or remove helpful context.
Make changes as one small publishing task
When a shared fact changes, treat the update as a short project. Confirm the new information with the person responsible, check the inventory, and decide whether to edit a shared field or several page-specific passages. Search the site or CMS for old wording, including common abbreviations and previous names. Navigation labels, downloadable files, form confirmation text and automated messages may also contain the detail, if your site uses them.
Before publishing, read each affected page in context. Make sure a shortened version still makes sense, links lead to the fuller explanation, and nearby copy does not contradict the update. If multiple people edit the site, assign one person to coordinate the change so that two editors do not publish different versions. Keep a brief note of what changed and which pages were checked; it will make the next update faster.
Build a light review habit
An inventory is most useful when it stays small enough to maintain. Add a new entry when important information begins appearing in more than one place. During routine content reviews, check high-impact details first, especially those tied to a visitor action such as getting in touch or requesting a service. Pages that rarely change may need only a quick comparison with their source of truth.
When you find a mismatch, fix the pages and look at why it happened. Perhaps the shared field was hard to find, the page list was incomplete, or the update process had no clear owner. Adjust that part of the workflow rather than relying on everyone to remember more. Consistent copy comes from making the correct version easy to find, edit and verify.
