Website redesign without losing your SEO foundation
A redesign changes how a site looks, but it can also change how search engines find it. Preserve useful URLs, content, and search signals while giving the business a better website.
Take an inventory before changing the site
A website redesign is a good moment to improve content and structure. It is also a moment when useful pages can disappear, internal links can break, and metadata can be replaced with generic defaults. Start by recording the current public URLs, page titles, main headings, articles, images, and internal links. Include pages that are not in the main navigation.
If you have Search Console and analytics, use them to identify pages that receive search visits or lead to inquiries. Without that access, you can still preserve the existing structure and record what you cannot measure. Do not infer a page’s search value from its appearance. An old article may be useful even when it no longer matches the visual identity you want.
Keep useful URLs whenever you can
A visual redesign does not require a new URL structure. Keeping an existing article at the same address avoids an unnecessary migration and allows old bookmarks and external links to continue working. If a URL genuinely needs to change, map its old address to the most relevant new page with a permanent redirect. Sending every removed page to the homepage is rarely a helpful substitute.
For bilingual sites, plan the two language versions together. Keep each version directly accessible even when the site offers browser-based language selection at the root. Someone following an English article link should reach that article in English, rather than being redirected by a saved preference. Language selection is a convenience at entry points; it should not override explicit page addresses.
Preserve meaning while improving the copy
A better headline can make the offer easier to understand, but removing useful explanations to make a layout look cleaner can leave visitors with less information. Keep the facts a customer needs: services, relevant examples, process, contact options, and any important constraints. Rewrite around the intended buyer rather than squeezing everything into short promotional phrases.
Existing articles deserve an editorial review rather than a bulk rewrite. Check whether their advice is still accurate, whether their examples are real, and whether their links work. Keep original publication dates. Change the modification date when the content actually changes, and explain significant updates where useful. A new visual template alone does not make an old article newly published.
Carry the technical signals into the new templates
Each indexable page needs a title, a useful description, a clear heading structure, and a canonical address that matches the intended public URL. Check the rendered HTML, not only the source configuration. A shared layout can accidentally give every page the same canonical, while a social image can be inherited from a page that no longer represents the content.
For translated pages, use reciprocal language alternates linking the corresponding versions. Keep those alternates consistent with the sitemap. Structured data should describe what the page actually contains: an article, the service, the person doing the work, or a breadcrumb trail. Additional markup is not a substitute for missing evidence, and no schema should invent reviews or business results.
Give images and interactions a performance budget
Large project imagery may be the right way to sell design, but its delivery still matters. Use appropriately sized modern image formats, declare the image dimensions or aspect ratio, and load below-fold images when they are needed. Prioritize the actual opening image instead of loading every portfolio screenshot at once.
Keep essential content available without waiting for a large interactive scene. Use motion to clarify transitions and respect reduced-motion preferences. Measure performance on representative mobile conditions after implementation. Lab measurements help find problems, while field measurements describe real visits when there is enough data. Neither should be presented as a ranking guarantee.
Verify the complete journey before launch
Open every retained URL and any redirects, then test links between the homepage, articles, language versions, and inquiry form. Confirm that private dashboards and APIs are excluded from public discovery. Check the generated sitemap and robots file rather than assuming the framework produced the intended result. A successful build is necessary, but it does not prove these behaviors.
After launch, use Search Console to review crawling and indexing, and compare inquiry quality with your pre-launch baseline if one exists. Some changes will need observation over time. Keep a list of what changed so an unexpected result can be investigated. The aim is to remove avoidable migration errors while making the site more useful to people; no redesign can promise unchanged search positions.
- Retained pages respond successfully at their original addresses.
- Changed URLs redirect to relevant replacements without loops.
- Canonicals, language alternates, and sitemap entries agree.
- Forms save real inquiries and show usable failure states.
- Search and performance measurements distinguish observed data from assumptions.