What Should You Keep When Replacing an Old Website?

When replacing an old website, keep the useful content, valuable URLs, customer evidence, domain ownership, email configuration, analytics history and working integrations that the business still needs. A replacement should improve weak foundations without carelessly discarding assets that already attract visitors, answer questions or keep the organisation running.

Begin with an inventory. Do not decide what to keep by scrolling through the homepage alone, and do not assume the old developer or agency holds a complete copy. Record what exists, who controls it and what purpose it serves before the new structure is finalised.

Keep an inventory of every existing page

Export or list every public URL you can find. Include pages in the navigation, articles, service pages, campaign landing pages, downloadable files and useful pages that are not linked from the menu.

Give each item a decision:

• Keep: retain the subject and usually the URL.
• Improve: preserve its purpose while rewriting or restructuring it.
• Combine: merge overlapping pages into one stronger destination.
• Replace: create a new page that meets the same customer need more effectively.
• Remove: retire material that is inaccurate, unnecessary or unsupported.

Record the reason for each decision. That makes it easier to review scope, plan redirects and prevent a useful page disappearing because nobody remembered it.

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.

Tell us about your project↗

Keep content that still helps customers

Old presentation does not make every sentence obsolete. Service explanations, delivery areas, process details, FAQs and policies may still be accurate and useful.

Preserve the information behind pages that answer recurring customer questions. Rewrite where the language is unclear, but do not replace substantial guidance with a slogan and a contact button merely to make the design look cleaner.

Check facts with the people responsible for each service. Mark claims that need evidence and remove commitments the business cannot consistently meet. Keep a source copy of the old text even when it will not all appear on the new site; it provides a useful audit trail.

Keep important URLs wherever practical

An established address may appear in search results, bookmarks, printed materials, emails and links from other websites. Keeping it avoids an unnecessary migration.

When an address must change, map the old URL to the closest relevant new page and use a server-side permanent redirect. Do not send every retired page to the homepage. Google recommends preparing a URL mapping, redirecting directly to final destinations and keeping redirects for as long as possible (generally at least a year) in its site-move guidance.

Update internal links to use the new destination rather than relying on redirects. Retain the redirect for people and external sites that still use the old address.

Our guide to redesigning a website without losing Google rankings explains the wider search migration process.

Keep pages that already attract relevant search visits

Use Google Search Console and analytics, where available, to identify pages that receive impressions, clicks and useful enquiries. Look beyond raw traffic. A low-volume specialist service page may be commercially important.

Record its title, main subject, useful sections and search intent. A redesigned page can look very different while still answering the need that brought visitors there.

Do not copy weak text simply because it ranks, but do not erase a proven subject without a replacement plan. If several pages are combined, choose the strongest destination and redirect the others appropriately.

Keep genuine evidence and business-specific detail

Save approved testimonials, project photographs, case studies, qualifications and process information that help customers assess the business. Confirm that they are accurate, current and permitted for continued use.

Keep the original high-quality files rather than downloading compressed versions from the website when possible. Record captions, alternative text, credits, licences and customer permissions alongside the assets.

Stock photographs and generated images should not be presented as real staff, customers or completed work. Preserve the distinction when moving content.

Keep control of the domain name

The domain is a business asset and should normally remain in an account controlled by the business. Record:

• the registrar and account owner;
• renewal date and payment method;
• administrative contact details;
• nameservers and current DNS records;
• any transfer lock or authorisation process;
• who can approve changes.

A website replacement rarely requires giving up the existing domain. The new site can be built elsewhere and connected to it at launch.

Use a change plan rather than editing DNS from memory. Export or screenshot existing records before launch and identify who can reverse the change if necessary.

Keep email working during the changeover

Website hosting and email hosting are often separate even when one supplier manages both. DNS records for mail can be affected during a website launch if the whole configuration is replaced carelessly.

Inventory MX, SPF, DKIM and DMARC records and any verification entries used by mail services. The person changing the website should know which records must remain untouched.

Test business email after launch from an external address. Check sending and receiving, not just whether an existing inbox opens. Keep a copy of the previous DNS configuration until the change has been verified.

Keep analytics and measurement continuity

Preserve access to Search Console, analytics, tag management, advertising accounts and consent configuration. Record current measurements before launch so later comparisons have context.

Avoid creating a new analytics property merely because the website is new unless there is a clear reason. A continuous history helps you distinguish normal variation from migration problems.

Review what is collected, why it is needed and how consent works. Do not copy tracking scripts automatically; retire tools the business no longer uses.

Keep working integrations and operational routes

List every service connected to the website:

• enquiry forms and receiving inboxes;
• bookings and calendars;
• payments and ecommerce;
• customer relationship systems;
• newsletter subscriptions;
• maps, reviews and social feeds;
• downloads and document storage;
• authentication or member areas;
• telephone tracking where legitimately used.

For each one, record the owner, credentials, data flow and test method. A visual redesign is incomplete if enquiries stop reaching the team.

Keep legal and accessibility essentials

Carry forward accurate privacy, cookie, terms and accessibility information, then review it against the new implementation. A policy should describe what the current website actually does.

Preserve helpful heading structures, alternative text, form labels and keyboard behaviour where they work. Test the new components rather than assuming the old compliance carries across. The WCAG 2.2 quick reference covers reflow, keyboard access, focus, labels and error handling.

Keep a recoverable copy of the old website

Before launch, save the files, database and configuration needed to understand or restore the old site, subject to data-protection and contractual responsibilities.

A browser screenshot is not a backup. Confirm who holds the archive, how long it will be retained and whether it can actually be restored. Avoid keeping personal data indefinitely without a purpose.

The old site can usually remain live while the replacement is developed. This gives the team time to compare pages, test forms and approve the launch without disrupting customers.

What should you leave behind?

Do not preserve problems merely for familiarity. Candidates for removal include duplicate pages, obsolete offers, unsupported plugins, unused tracking tools, inaccessible components and claims nobody can substantiate.

Retire content deliberately. Check whether a removed URL has visits or links, decide whether a genuine replacement exists and document the outcome.

The decision is easier when you separate the business asset from its current presentation. Keep the useful answer, photograph or URL; leave behind the confusing layout or fragile implementation.

Use the complete guide to upgrading an outdated business website and our comparison of whether to repair or replace your existing website to choose the wider approach.

A practical preservation checklist

Before approving the replacement, confirm that you have:

• a complete page and file inventory;
• keep, improve, combine and remove decisions;
• current search and enquiry baselines;
• a URL redirect map;
• original photographs and licence records;
• domain registrar access;
• a copy of all DNS and email records;
• analytics and Search Console access;
• an integrations and form-delivery list;
• reviewed legal content;
• a recoverable archive;
• named people responsible for launch and rollback.

Frequently asked questions

Should I keep the same domain when replacing a website?

Usually, yes. A redesign does not require a new domain. Retaining an established domain also avoids a more complex domain migration.

Do I need to keep every old page?

No. Keep or replace pages that serve a useful purpose. Remove weak or obsolete material carefully, with redirects where a relevant replacement exists.

Can I reuse old website photographs?

Only when the business has the necessary rights and the images remain accurate and suitable. Record the source, licence and permissions before reusing them.

What happens to old customer data?

Decide what must be migrated, retained or deleted under the business’s legal and operational responsibilities. Do not copy personal information into a new system without a defined need and appropriate safeguards.

Replace the website, not its useful foundations

A good replacement project is selective. It protects the domain, email, valuable content and established customer routes while removing the constraints that made change necessary.

Afterworks builds a separate replacement for review while the existing website remains live. Explore our website rebuild service or contact us to discuss what your new site should preserve.

• website replacement
• website migration
• website content
• technical SEO
• domain and email