Iron Goo
---
title: "SEO Checklist for Website Redesign"
seoTitle: "SEO Checklist for Website Redesign"
description: "Ask your developer ten SEO questions before a redesign, from URL mapping and staging protection to redirect retention and Search Console ownership."
datePublished: "2026-04-16T16:09:57.000Z"
dateModified: "2026-11-01T19:32:00Z"
category: "seo"
imageAlt: "Business owner reviews a printed document across from a web developer, with website mockups on the table"
tags: ["website-redesign", "site-migration", "redirects", "technical-seo", "search-console"]
faq: true
headQuery: "seo checklist for website redesign"
featuredImageFile: "/blog/art/en/seo-friendly-website-hero.ee5865a2.webp"
---

An SEO checklist for website redesign is a set of written requirements your developer answers before work starts. If the proposal on your desk has mockups, a launch date, and a price but says nothing about URLs, redirects, or what Google sees on launch day, start with Google's instruction: "Prepare a URL mapping from the current URLs to their corresponding new format." [Google's site-move guide](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes), last updated 20 August 2026, puts that work before redirecting the old URLs.

The deciding attribute is whether user-visible URLs change: a template redesign can keep them, a site move changes them through a domain, HTTP-to-HTTPS, or path change, and a hosting change can leave them untouched. Google has separate documents for a move with changed URLs and [changing hosting without URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-no-url-changes). Ask the first four questions before the build, the next four during it, and the last two for launch and the weeks after.

## What exactly is changing, and are we changing one thing at a time?

Google's site-move guide tells you to "Change only one thing at a time" when a project combines a new domain, CMS, and layout. Its example moves to the new domain first and changes the layout afterward, giving Google and your team fewer simultaneous changes to interpret.

The [Change of Address help](https://support.google.com/webmasters/answer/9370220) explains the consequence: "If you combine a site move with a redesign of the site's content and URL structure in the new location, you will probably see some traffic loss as Google might need to relearn and reassess the individual pages." Our rule is to split a domain, platform, and design project: move the domain first with URLs kept one to one, then change the design.

**Good answer:** “The domain moves first, with every path kept identical for one-to-one URLs. The CMS, layout, and any URL structure changes will follow in a later phase with their own launch date.”

**Red flag:** “We'll switch domain, platform, design, and every URL on launch day.” If traffic falls, you will have several overlapping changes to investigate, and Google may need to reassess the changed pages.

## Where does the list of old URLs come from?

An old URL inventory gives the developer the addresses that need a destination or an explicit removal decision. Google names sitemaps, server logs or analytics for the most visited URLs, Search Console's Links report, and the CMS URL listing as sources.

The inventory needs more than the pages visible in your menu. Images, PDFs, videos, JavaScript, and CSS files can have URLs that people or other sites request too. Ask for the list early enough to review omissions and assign each retained resource a destination before launch.

**Good answer:** “We'll combine the sitemap, analytics, Search Console Links report, and CMS listing. The inventory will include images and PDFs, and we'll check other files and videos for URLs that need to move.”

**Red flag:** “We'll copy the navigation menu into a spreadsheet,” or “We'll crawl the site the day before launch.” A menu can omit pages that receive search visits or external links, and a late inventory leaves little time to decide where those URLs belong.

## Can I see the redirect map?

A redirect map records each old URL's destination. Google recommends server-side permanent redirects, such as 301 or 308, to the final destination.

[Google's site-move guide](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) says Googlebot can follow up to 10 hops, but advises a direct redirect or, if that is impossible, ideally no more than three and fewer than five. URLs with no equivalent should return HTTP 404 or 410; sending many old URLs to the home page “might be treated as a soft 404 error.” Google also states: "301 and other permanent redirects don't cause a loss in PageRank."

:::figure{src="/blog/art/en/seo-friendly-website-fig.1d92ff57.webp" alt="Old URLs redirect to matching pages, a removed page returns 404, and homepage redirects are crossed out" width="1440" height="810"}
Each retained page has its own matching destination. The removed page returns 404, while the crossed-out arrows show unrelated pages being sent to the home page.
:::

The [technical SEO guide](/guides/seo/technical-seo-and-crawl-cost) gives your developer the status-code and redirect test procedure; [URL signals](/blog/url-signals) addresses whether the URLs need to change at all.

**Good answer:** “The spreadsheet has one row per old URL, its new URL or 404/410 decision, and the expected status code. We'll run a scripted test of every row after launch.”

**Red flag:** “Everything we drop goes to the homepage,” “We'll use 302s,” or “JavaScript will handle the redirects.” Google says temporary redirects “Show the source page in search results,” while permanent redirects show the new target; Google “might never see” a JavaScript redirect if rendering fails.

## How is the staging site kept out of Google, and what is the launch-day unblock plan?

Staging protection needs an access method and a launch-day removal plan because a block copied to the live site can stop Google from crawling it. Google's [noindex documentation](https://developers.google.com/search/docs/crawling-indexing/block-indexing) says that when robots.txt blocks a page, "the crawler will never see the noindex rule, and the page can still appear in search results".

A robots.txt Disallow blocks crawling, not indexing, and Google does not support putting a noindex rule in robots.txt. Google's hosting guidance describes IP-restricted testing and noindex in HTML or HTTP headers on a test hostname; password protection can also keep content out of Search. Prepare the live robots.txt and a list of pages from which development noindex rules must be removed.

**Good answer:** “Staging requires a password or an approved IP address. Our launch checklist removes the restriction and checks the live robots.txt and robots meta tags.”

**Red flag:** “We'll use Disallow plus noindex to be doubly safe,” or “We'll copy staging live as is.” The first can hide the noindex instruction; the second can leave the public site blocked from crawlers or marked noindex.

## Will the content and every link be in the HTML the server sends?

Server-rendered or pre-rendered content gives crawlers page content without requiring them to run JavaScript first. Google's [JavaScript SEO guidance](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics) calls server-side or pre-rendering “still a great idea” because “not all bots can run JavaScript.”

Google says it can generally crawl links when they are `<a>` elements with an `href`; buttons with click handlers do not provide the same crawlable link. A single-page application should use the History API for routes, rather than `#/` fragments that load different page content. On 17 December 2024, Vercel reported that none of the major AI crawlers then rendered JavaScript; the [blank-page rendering test](/blog/blank-page-render) checks what your server sends in ten minutes.

**Good answer:** “The page content is server-rendered or pre-rendered, and navigation uses `<a href>` links. If the application changes pages in the browser, its routes use the History API.”

**Red flag:** “The links are buttons with click handlers, and the pages load at `#/` routes.” Search crawlers may miss routes or links, leaving pages harder to discover even though a person can click through the site.

## What happens to each page's title, headings, canonical and hreflang?

Page titles, headings, canonicals, and hreflang need page-level decisions when templates or URLs change. Google recommends a `<title>` on every page, warns against repeated or boilerplate titles, and calls for self-referencing canonicals on new URLs and hreflang annotations updated to those URLs.

A canonical identifies a page's preferred version; hreflang connects language or regional versions. A staging-host canonical on live pages gives Google a conflicting address. Request examples from several page types and any language versions you maintain.

**Good answer:** “We'll carry over each page's title and H1 unless that page is deliberately rewritten. Canonicals will use the live domain, and we'll update any hreflang targets to the new URLs.”

**Red flag:** “Every page gets the same title pattern, and canonical tags come from staging.” Repeated titles can make pages harder to distinguish in search, and staging canonicals can point Google away from the intended live URLs.

## Are internal links rewritten to the new URLs?

Internal links need to point to new URLs. Google tells site owners to update them using the redirect map.

Redirects take visitors from old addresses to new ones, but leaving old addresses on the rebuilt site adds avoidable requests. Use the map to check whether pages earning search traffic remain reachable from navigation or a relevant hub, and ask where those links will appear before approving navigation.

**Good answer:** “We'll rewrite internal links using the approved map. Pages that earn traffic will retain a link from the new navigation or a relevant hub, and we'll check those links on the live site.”

**Red flag:** “The redirects take care of internal links.” The new site would depend on old addresses, with no evidence that valuable pages remain linked.

## Is structured data carried over and validated?

Structured data can break when templates or serving setups change. Google's [structured data guidance](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) recommends JSON-LD, the Rich Results Test during development, and rich result status reports after deployment.

List markup types on current and replacement templates. Compare staging results with live pages and check the report for deployment failures. Valid markup does not guarantee a particular search appearance.

**Good answer:** “We'll list the markup types for each template, test representative staging pages with the Rich Results Test, and check the rich result status reports after launch.”

**Red flag:** “We'll add FAQ markup to win FAQ rich results.” Google stopped showing the FAQ rich result on 7 May 2026. That promise is outdated and leaves existing markup's survival unanswered.

## Who owns Search Console, and do we need the Change of Address tool?

Your company should own Search Console access. Google's [Change of Address tool](https://support.google.com/webmasters/answer/9370220) is for moves from one domain or subdomain to another, including a domain moved to a path on another domain.

The tool excludes HTTP-to-HTTPS, same-domain path and www-to-non-www changes, and hosting or CDN moves without user-visible URL changes. The same Google account must own both properties. Submit the tool for each old subdomain variant, including www, non-www, and m. where applicable, not separately for HTTP and HTTPS.

**Good answer:** “Your company holds owner access. We'll verify old and new properties and their www, non-www, HTTP, and HTTPS variants; preserve the verification file or meta tag; re-upload any disavow file; and submit the new sitemap. We'll use Change of Address only if the move qualifies.”

**Red flag:** “The agency owns the account,” or “We'll file a change of address for your same-domain HTTPS redesign.” You may lose access to the evidence you need, and the proposed filing does not apply to that change.

## How long do the redirects stay, and what is watched in the first weeks?

Redirect retention needs a contract term because Google's site-move guide says: "Keep the redirects for as long as possible, generally at least 1 year." Its Change of Address help says: "Maintain the redirects for at least 180 days--longer if you still see any traffic to them from Google Search."

For sites using Change of Address, the tool's actions continue for 180 days after migration starts in Search Console. Google says: "After the 180 day period, Google does not recognize any relationship between the old and new sites, and treats the old site as an unrelated site, if still present and crawlable."

Our rule is to contract the longer, one-year redirect minimum. Google also recommends paying for the old domain for at least a year to prevent someone else from buying and using it maliciously.

Google says most pages on a small or medium site can take a few weeks to move, search visibility may fluctuate temporarily, and a move is complete only after Googlebot visits every old and new URL at least once. The new server needs capacity for heavier-than-usual crawling.

**Good answer:** “We'll keep redirects for at least a year, submit both old and new sitemaps, and name someone to check Search Console weekly. We'll watch indexed counts shift from old URLs to new ones and investigate spikes in Not found errors, including redirects to nonexistent destinations.”

**Red flag:** “The redirects disappear when the old hosting plan ends.” Visitors and crawlers can then lose the route from an old address to its replacement. If new pages are not indexed at all, use the [Google rankings troubleshooting article](/blog/google-rankings) to investigate.

Our decision rule: if the developer cannot answer questions 3 and 4 in writing before you sign the contract, the launch date is not ready. If you want a rebuild commissioned with these requirements in the brief, consider the [Foundation service](/services/foundation).