A redesigned website can look substantially better while making important pages harder to find. URLs disappear, service copy becomes a short slogan, internal links lead to old locations and a development setting accidentally remains active at launch.
An SEO-conscious website redesign preserves useful search paths while improving how the business communicates and converts. The work begins before visual design is approved. You need to know which pages exist, what they help visitors do and what should happen to each of them after launch.
This checklist is designed for a service business or growing product company planning a redesign on the same domain. Domain migrations introduce additional work, so do not treat this as a complete migration specification for every technical situation.
Before design: establish the current position
Build a useful URL inventory
Collect the URLs the site currently exposes through its sitemap, navigation, internal links and CMS. Add relevant landing pages from Search Console and analytics. Include PDFs or other files if they receive meaningful traffic or links.
Record each URL’s purpose, current title, main topic, status and intended conversion. Where reliable data exists, add search clicks, landing-page sessions and relevant business outcomes. Keep the reporting periods explicit; a seasonal page can look unimportant if you only inspect a quiet month.
The inventory is a decision document. It helps the team distinguish a page that is genuinely unnecessary from one that simply does not fit the new navigation design.
Separate URL changes from visual changes
A new design does not automatically require new URLs. If an existing address remains accurate and useful, retaining it removes one source of migration work.
When a URL must change, create a direct mapping to the most relevant replacement. Google’s site-move guidance recommends mapping old addresses to their new destinations and using appropriate permanent redirects. Avoid sending unrelated old pages to the homepage merely to make a list of errors disappear.
For each existing URL, choose one outcome: keep, improve at the same address, merge into a relevant page, move to a new address, or remove with an appropriate response. Name the person responsible for the decision.
During design: protect the information customers need
Design around page intent
A service page and a journal article answer different questions. Someone comparing providers needs fit, scope, evidence and a next action. Someone learning about a problem may need a fuller explanation and supporting examples.
Do not force both into an identical short landing-page format. Equally, do not turn every service page into a long general article. Map one primary intent to each important page and let the layout support that intent.
Brano’s portfolio includes Kirkland Dental Excellence and Teza Doors. These are useful reminders that practical service or product information is part of the buying journey. A redesign should improve access to relevant details, not replace them with impressive but less useful visual space.
Keep titles, headings and descriptions specific
Write a unique page title and a clear visible main heading for each priority URL. They should describe the same subject, although they do not need to be identical. Google explains how several page signals can influence title links in search; the supplied title is not a guarantee of the exact wording that will appear.
Write the meta description as an accurate invitation to the page. Google may choose a different snippet based on the query and page content, as its snippet documentation explains. Avoid treating a particular character count as a ranking formula.
Preserve useful internal links
Check the paths between related services, articles and evidence. Links should help the reader continue the task, and their text should make the destination understandable. A navigation menu alone does not replace contextual links within the content.
Google’s link best practices describe crawlable links and descriptive anchor text. For your redesign, the practical question is simple: can a visitor reach every important page through a meaningful route, without needing its exact URL?
Before launch: test the production configuration
Development and production settings can differ. Run these checks against the version that will actually go live, not only a design preview.
| Check | What to verify |
|---|---|
| Page response | Priority pages return the intended successful response |
| Redirects | Moved URLs reach the relevant final destination |
| Indexing directives | Public pages are not unintentionally marked noindex |
| Canonical URL | The preferred URL is correct for the page |
| Internal links | Navigation and content use the final addresses |
| Rendered content | The page displays its actual article or service copy |
| Mobile journey | Menus, content and conversion paths work on a phone |
| Forms and bookings | A completed test reaches the right destination |
| Analytics | Important events describe successful actions accurately |
A particularly important check is rendered content. A CMS can contain an article while a custom theme displays something else at the article’s address. Checking the editor alone will not reveal that problem. Open several real URLs, inspect their visible heading and confirm the body belongs to that page.
Check canonical and language relationships
A canonical identifies a preferred URL among duplicate or very similar versions. It does not replace a redirect when a page has moved, and it should not point every service page to the homepage. Google’s canonicalisation guidance explains the signals used to select a representative URL.
For a multilingual site, maintain real language versions with suitable page relationships. Do not label an untranslated English article as Persian merely because the header has a language switcher. Google’s multilingual-site guidance is a useful reference when defining the language URL structure.
Test language switching on an article as well as on the homepage. If a translation does not exist, the interface should not pretend that it does. Decide how visitors can return to the appropriate language home without creating misleading alternate-page signals.
Give analytics a continuity plan
Record the launch date and any changes in event definitions, consent behaviour, forms or channel tracking. A new measurement implementation can create a discontinuity that looks like a marketing change.
Before comparing “before” and “after,” confirm that the reports still count the same thing. If the old site recorded button clicks and the new site records successful submissions, those numbers should not be presented as a direct conversion improvement.
Use a baseline with enough context: comparable dates, device mix, relevant pages and the same outcome definition. Our lead generation website audit shows how to separate enquiries, valid leads and qualified opportunities.
After launch: monitor the decisions you made
Recheck a sample from every important page type and every redirect pattern. Review your sitemap and use Search Console to inspect priority URLs. Follow changes in indexing, search queries, landing-page behaviour and enquiry quality without assuming every movement was caused by the redesign.
Keep a launch log with three fields: observation, likely explanation and next check. For example, a traffic decline limited to a retired service page calls for a different response from a site-wide noindex setting. Investigate the specific failure before changing several unrelated things at once.
Agree on who owns follow-up fixes. A handover is incomplete if the website is published but nobody is responsible for reviewing technical issues or broken conversion routes.
Frequently asked questions
Can a redesign guarantee better rankings?
No. It can improve technical foundations, useful content and the customer journey, but search performance depends on more than the launch itself. Define the improvements you can verify rather than promising a ranking outcome.
Should every old page be redirected?
No. Retain useful pages where appropriate, redirect genuinely moved or merged content to relevant replacements, and handle removed content according to the actual situation. Avoid irrelevant blanket redirects.
When should SEO be involved?
At the inventory and page-planning stage. Early involvement makes it easier to preserve useful content and URLs, plan internal links and avoid late changes to a nearly finished design.
Explore Brano’s website design and conversion service and SEO and content service to connect the redesign brief with the search journey.