Skip to content
Dev Ring Technologies
Let’s talk
All articles

Website redesign: a practical checklist to protect your SEO

A new design should help visitors understand your offer and contact your business. A redesign can also remove a page that already brings useful enquiries. For a company in Tunisia or a team serving international customers, start by deciding what needs to survive before deciding what should change.

1. Agree on the outcome and save a baseline

Write an observable goal: explain an offer more clearly, simplify a quote request or improve a service presentation. “Modernise the website” is too vague to help choose between proposals. Name the person who approves content and the person who makes the launch decision.

Keep a copy of the existing website and a record of important pages: URL, title, purpose, enquiries and organic visits across a period that represents your business. Separate pages that generate contacts, pages that answer customer questions and pages that no longer have a role. A rarely visited page may still matter to a specific customer.

Our project recommendation is to choose indicators and their measurement method before launch. For example, count quote requests actually received each week alongside visits to the relevant pages. Falling visits and a broken contact form require different responses.

2. Decide what happens to each important URL

A new design does not require new addresses everywhere. If a page keeps the same purpose, retaining its URL avoids an unnecessary move. When you rename or combine pages, prepare a mapping sheet with a considered destination for every old address.

Google recommends preparing this mapping and testing the new site before moving URLs. Rankings can fluctuate while changes are processed. Planning reduces avoidable risks; it cannot promise unchanged positions.

Make an explicit decision for deleted pages: is there a replacement that meets the same need? An old mobile-development page should not land on a vague homepage simply because the new menu is shorter. The example below is fictional and should be adapted to your own inventory.

Google reference : Google Search Central — Site moves

An example mapping sheet for your provider

These fictional addresses illustrate redesign decisions; they are not Dev Ring pages.

An example mapping sheet for your provider
Old addressDecisionDestination to check
/services/business-websiteKeep the offer/services/business-website
/online-shop-creationRename the offer/services/e-commerce
/expired-spring-offerNo relevant replacementHelpful removal page, 404 or 410 status

3. Test redirects using the actual old addresses

For a permanent move, Google recommends a permanent server-side redirect where possible. HTTP 301 and 308 represent that situation. Choose a destination that fits what the visitor was looking for, then check the result.

Open URLs from the mapping sheet and verify the final address, the content and useful next steps. Record missing pages, wrong destinations and unnecessary sequences of redirects separately. Also try an existing link from a sales document or an earlier campaign.

Ask your provider for a readable report: old URL, intended destination, observed destination and result. “Redirects are configured” does not show whether your most important commercial page works.

Google reference : Google Search Central — Redirects

4. Align pages, internal links and the sitemap

Check links in navigation, the footer and articles against the new destinations. A published page can still be difficult to find from the pages customers actually read. Review titles, descriptions and calls to action on your priority pages as well.

A canonical tag indicates a preferred representative address for similar or duplicate content. Google advises keeping canonical signals consistent. Check that a new page does not mistakenly identify an old address as its preferred version.

A sitemap helps search engines discover URLs; it does not guarantee crawling or indexing. Check that it contains the pages you intend to publish at their correct addresses. For a multilingual site, also test language-switch links to the equivalent page.

Google reference : Google Search Central — Canonical URLs · Google Search Central — Sitemaps

5. Run a mobile acceptance check before launch

Choose a realistic journey: open a service page from an article, understand the offer, reach contact and prepare an enquiry. Repeat it on a phone and a computer. On a dedicated preview environment, use clearly identified test details to check form delivery without contaminating your sales reporting.

Base the launch decision on evidence: priority pages load, links work, text is readable, there is no horizontal overflow and the test enquiry arrived. Agree who responds to problems and how to restore the previous version if a critical issue appears.

After publishing, repeat the journey on the real domain. A working preview does not prove that the public contact form or old URLs work.

6. Investigate changes rather than one headline number

Compare the same page groups across comparable periods. Record the launch date and other business changes: a paused campaign, a revised offer or a closed week may affect enquiries. A change in total contacts alone does not identify an SEO problem.

Use Search Console to observe pages and queries, then relate those observations to visits and enquiries actually received. If an important page suddenly loses visibility, start with its address, accessibility and content. If visits remain but contacts fall, repeat the conversion journey first.

Keep the migration sheet and acceptance report. They make it easier to investigate a problem reported weeks later without relying on anyone’s memory.

Questions to ask before agreeing to a redesign

Does every page need new copy?

Start with visitor needs and each page’s role. Keep useful information, correct inaccuracies and rewrite unclear content. A new design alone is not a reason to remove content that helps prospective customers.

Can a redesign promise absolutely no traffic loss?

That promise is too absolute. Ask for a documented inventory, migration decisions, checks before and after publication and monitoring that supports a practical response to changes.

What should the agency deliver?

An agreed scope, a saved baseline, the URL mapping sheet, checks and results, access that belongs to you and a monitoring plan with a named owner. Have these included in the proposal.

Prepare your redesign brief

Gather your website address, your three priority goals and the pages customers use most. Dev Ring describes its web and SEO work on its service pages; send us this initial scope to discuss your project.

Sources and scope

Primary sources checked on October 27, 2026. The project-management steps are our proposed working method; the Google references explain migration, redirect, canonical and sitemap mechanisms.