Can a Website Be Rebuilt Using the Content You Already Have?
A website can reuse valuable existing content, but every page should be reviewed for accuracy, purpose, originality and fit before migration.
Part of our guide: How Much Does a Small Business Website Redesign Cost in the UK?
Yes, a website can be rebuilt using content you already have, and useful material should not be discarded merely because the design is changing. The safe approach is to inventory every page, decide whether to keep, update, merge or remove it, and then adapt approved content to the new structure.
Reusing content is not the same as copying the old website automatically. A rebuild is an opportunity to preserve genuine value while correcting outdated, duplicated or unclear information.
This guide covers page decisions and the migration workflow. Review asset permissions and approvals separately, then record the page-level decisions in the content inventory worksheet.
Begin with a complete inventory
List public pages, articles, downloads, images and important hidden landing pages. Record each URL, title, purpose, audience, owner and available performance evidence.
A crawl can find many assets, but staff knowledge and analytics reveal pages that support unusual customer journeys. Include material linked from campaigns and external websites.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Decide what each page is for
Every retained page should help a recognisable customer task or business need. Identify the question it answers and the next action it supports.
Pages without a clear purpose may need merging or removal. Low traffic alone is not proof of low value if the page serves a small but important audience.
Write the decision and reason into the inventory.
Use four content decisions
Classify material as keep, update, merge or remove. Keep content that remains accurate and effective. Update valuable pages whose facts or presentation need work.
Merge overlapping pages when one stronger destination can serve the intent. Remove obsolete content when it has no safe current replacement.
Avoid an ambiguous migrate column that postpones the actual decision.
Preserve accurate core information
Service explanations, contact details, policies, case studies and specialist guidance may remain useful. Confirm them with the responsible people rather than assuming the old site is authoritative.
Check names, prices, availability, service areas, qualifications and legal wording. Record approval dates.
Content can be well written and still be wrong.
Update content for customer questions
Restructure pages around what visitors need to understand, compare or do. Move internal company history out of the opening when customers first need a clear service answer.
Use headings that help scanning and links that support the next decision. Keep language specific and avoid unsupported superlatives.
The guide to creating content that attracts customers offers a broader method.
Check originality and sources
Confirm that the business owns or has permission to use existing words and media. Previous suppliers may have licensed stock assets under limited terms.
Rewrite copied or generic passages in the organisation’s own voice. Cite authoritative sources when important facts, standards or statistics depend on external evidence.
A link does not make copied wording acceptable.
Protect useful URLs
When a page keeps the same purpose, retain its established URL where practical. A new design does not require a new address.
Stable URLs protect bookmarks, external links and search understanding. If an address changes, map it to the closest relevant destination.
Do not redirect every removed page to the homepage.
Use search evidence carefully
Review landing-page visits, search queries, backlinks and enquiries. Evidence can show which pages attract useful audiences and which questions deserve clearer coverage.
Do not preserve poor or inaccurate content merely because it receives traffic. Improve it while protecting the relevant intent and route.
Search data informs editorial judgment; it does not replace it.
Merge duplicate pages deliberately
Several pages may compete around the same subject. Choose a primary destination, combine unique value and create redirects from retired URLs.
Update internal links to point directly to the final page. Review headings so the merged result has a coherent flow rather than stacked fragments.
Record which source pages contributed material for approval and traceability.
Handle removed content honestly
Some discontinued products, expired events and unsafe instructions should disappear. Redirect only if another page genuinely meets the same need.
An informative not-found or gone response may be more accurate than an unrelated destination. Preserve required records privately where retention rules apply.
Removal is a content decision as well as a technical one.
Reuse images with care
Check rights, quality, relevance and representation. Old stock photography may weaken a refreshed brand even when technically reusable.
Meaningful images need concise alternative text. Decorative images should be hidden appropriately from assistive technology.
Optimise file sizes and crops for the new layouts. Do not stretch small originals.
Migrate documents thoughtfully
PDFs and office documents can contain valuable information but may be difficult on mobile or inaccessible. Decide whether the material works better as an HTML page.
If a file remains, update it, check accessibility and preserve or redirect its URL. Remove private metadata and obsolete versions.
Do not upload files simply because they existed in the old media library.
Adapt content to the new design
Real text should influence components and layout. Artificially shortening every page to fit a mockup reverses the correct relationship.
Editors may split long sections, add summaries or convert suitable information into lists. Preserve nuance where the subject needs it.
Test long titles, tables, quotations and images on small screens.
Preserve metadata selectively
Review titles, descriptions, canonical settings and structured data. Keep strong accurate metadata when the page purpose is stable, but fix duplication or outdated claims.
Do not copy obsolete keyword fields. Generate a sitemap from final public routes.
Metadata should describe the new page, not the migration history.
Plan internal links again
Old links may point to retired or redirected pages. Update them to the final route and add useful connections created by the new structure.
Every supporting article should connect to an appropriate pillar or service, while links remain natural and selective.
Automated link checks find errors; editorial review judges relevance.
Reuse testimonials and case studies
Confirm permission, accuracy and current context. A testimonial may refer to an old service or a company name that has changed.
Keep evidence specific and avoid editing quotations in a way that alters meaning. Record the source and approval.
Refresh case studies with outcomes only when those claims can be supported.
Review legal and policy content
Privacy, cookies, terms and accessibility statements must reflect the current site and organisation. Do not copy them blindly from the old build or another company.
Identify data flows, tools and business decisions, then obtain appropriate advice where needed.
Update policies when the new website changes forms, analytics or third-party services.
Assign content owners
Each important page needs somebody who can confirm facts and approve changes. A central editor can protect tone and structure, but subject specialists own accuracy.
Set deadlines and provide content in a controlled format. Avoid simultaneous untracked edits across email attachments.
Record unresolved claims instead of publishing assumptions.
Manage version control
Choose a single approved source for each page during migration. Track decisions and freeze old-site edits close to launch or create a process to copy late changes.
Without this step, the replacement can launch with older information than the website it replaces.
Keep an archive of approvals and final migrated material.
Test after migration
Compare the built site with the approved inventory. Check headings, formatting, images, links, downloads and calls to action.
Run spelling, link and metadata checks, then read the published page. Automated migration can introduce encoding, spacing and component errors.
The pre-launch website checklist covers the wider test process.
Avoid content migration shortcuts
Copying every database record may preserve drafts, duplication and broken formatting. Rewriting everything can discard search value and organisational knowledge.
Another mistake is leaving content until after design approval, which produces layouts based on unrealistic placeholders.
Audit early, then migrate intentionally.
When a full rewrite is justified
Rewrite when positioning, services, audience or accuracy has changed substantially. A new structure may also expose that existing pages never answered customer questions.
Even then, preserve useful facts, evidence, URLs and media rights. Starting fresh should not mean ignoring the inventory.
Plan enough review time for subject specialists.
When light editing is enough
Stable, accurate guidance with good performance may need only updated examples, links and presentation. Do not rewrite proven content merely to make every sentence different.
Check that it still matches the new site’s voice and call to action. Retest sources and dates.
Content value comes from usefulness, not visible novelty.
Estimate migration effort
Count pages by decision and complexity. A simple text page differs from a long guide with tables, downloads, images and structured data.
Include audit, editing, entry, review, redirects and testing. Clarify who does each step in supplier proposals.
Content migration is often a major reason website redesign prices vary.
Frequently asked questions
Can all old content be imported automatically?
It may be technically possible, but it is rarely editorially wise. Review and classify content before migration.
Will rewriting content hurt SEO?
It can change relevance, but thoughtful improvements can help users. Protect useful intent, URLs and evidence while monitoring results.
Should old blog articles be deleted?
Not solely because they are old. Update useful evergreen material and remove or merge content that is inaccurate, duplicated or purposeless.
Can we reuse old photographs?
Yes when rights, quality and relevance remain suitable. Verify licences and provide appropriate alt text.
Who should approve migrated content?
The business owner responsible for the subject should confirm facts, supported by an editor who protects clarity and consistency.
Preserve value, not every word
Existing content is an asset when it is accurate, purposeful and owned. Inventory it, make explicit decisions, protect useful routes and give every migrated page a final human review.
Afterworks treats content as a core part of website rebuilds, preserving what works while improving the structure and customer experience around it.
