Crawlable URLs
Crawl the website, sitemaps, menus, internal links, orphan pages, parameters, PDFs, images and useful public resources.
Guides
Website redesign without losing SEO: migration guide
Change design, CMS, URLs, domain or hosting without throwing away pages, links and signals built over time. Method, checks and responsibilities before, during and after launch.
In brief
No one can guarantee unchanged rankings after a redesign. Avoidable risk can, however, be reduced: measure the current website, inventory every useful URL, define an equivalent destination, implement permanent redirects, keep content and technical signals consistent, test the new website and monitor Google and Bing after launch.
Gian Luca Partengo
Web developer since 1995 · bespoke websites · Updated:
Can you redesign a website without losing SEO?
Yes—if “without losing” means protecting what exists and reducing controllable mistakes, rather than promising that Google will freeze every ranking.
- 01Measure pages, queries, links and conversions before changing anything
- 02Decide whether each old URL should remain, move, merge or be removed
- 03Align redirects, canonicals, links, sitemaps and content with the same destination
- 04Monitor crawling, indexing, traffic and errors for weeks after launch
“Migration” can mean five very different projects
Before estimating risk, timing and checks, establish what actually changes for users and crawlers.
| Project | What changes | Main risk | Decisive check |
|---|---|---|---|
| Redesign | Visuals, components and journeys; URLs may remain unchanged | Reduced content, removed links, worse HTML or performance | Page-by-page comparison of old and new output |
| CMS or technology change | Publishing system, templates, markup and often URLs | Slugs, metadata, schema and status codes rewritten without a map | Complete inventory and final-response testing |
| New URL architecture | Paths, categories, languages or parameters change | 404s, chains and non-equivalent destinations | One-to-one map and server-side permanent redirects |
| Domain change | The host changes for all or many pages | Signals split across properties, variants and subdomains | Redirects, verified properties and Change of Address where applicable |
| Hosting or CDN change | Infrastructure and DNS, without changing visible URLs | Downtime, DNS, TLS, headers, WAF or insufficient capacity | New-origin tests, TTL, monitoring and the old server kept available |
Prudent rule
Google recommends changing one thing at a time where possible. Combining domain, CMS, architecture, design and content changes at the same moment makes transferring signals and identifying the cause of a problem more difficult.
Record the current website before designing the new one
Without a starting point, you cannot distinguish a migration loss from seasonality or a page that was already producing nothing.
Indexing
Search Console and Bing show indexed and excluded URLs, selected canonicals, errors, redirects and blocks that must be understood before they are copied.
Organic performance
Export at least pages, queries, clicks, impressions, countries and devices over a period long enough to identify seasonality.
Backlinks and citations
Identify URLs receiving external links, referrals, mentions, downloads or direct traffic: they are not always the most visited pages.
Content and metadata
Save main copy, titles, descriptions, headings, images, alt text, structured data, canonicals, hreflang and editorial dates.
Real goals
Enquiries, sales, calls, sign-ups and lead quality prevent a useful page from being sacrificed merely because its design looks old.
The URL map is the central migration document
Every old resource needs an explicit decision, a destination and a verifiable technical outcome.
One row for every URL
Old address, new address, rationale and check
The map connects source URL, current status, traffic, backlinks, content, proposed destination, redirect type, expected canonical and responsible person.
It is not generated from the sitemap alone: historic URLs can exist in Search Console, backlinks, logs, old feeds, images, PDFs, campaigns and users’ saved links.
Equivalence before resemblance
The destination must answer the same need. Redirecting a specific detail page to a generic homepage does not transfer useful context.
One final destination
The old URL should reach the definitive page directly, avoiding chains, loops, HTTP hops and intermediate www variants.
Verifiable priority
Test pages with traffic, links, sales or reputational importance first; then cover the full inventory.
Versioned decisions
The map must accompany development, testing and monitoring: it cannot remain a forgotten spreadsheet before go-live.
301 redirects, canonicals, 404s and 410s are not interchangeable
Each tool communicates a different situation. Using one for convenience rather than meaning creates contradictory signals.
| Situation | Tool | Message | Common mistake |
|---|---|---|---|
| The resource has moved permanently | Server-side 301 or 308 | The destination should replace the source as the primary URL | 302, JavaScript or chains when a direct redirect is available |
| The move will genuinely be reversed | 302 or 307 | The source may remain the URL shown in results | Using it for months on a permanent migration |
| Two accessible URLs show identical or very similar content | Consistent rel=canonical | Indicates the preferred version without moving the user | Using it instead of a redirect when the old page is being retired |
| The resource no longer exists and has no equivalent | A genuine 404 or 410 | Communicates that the URL no longer provides the requested content | Returning 200 with an empty page or sending everything to the homepage |
Do not migrate URLs alone: preserve meaning and usefulness
A new page can return 200 and have a perfect redirect, yet lose value if the content and relationships that made it useful have disappeared.
Content and intent
Keep the answers, evidence, data, products and sections that satisfy the search need; improve weak material without hollowing out the page.
Titles, headings and snippets
The title, H1, description and main content should describe the same page. Rewriting all of them at once makes the migration effect harder to interpret.
Structured data and entities
Rebuild only markup consistent with what remains visible: organisation, author, products, breadcrumbs, FAQs and relationships must not describe an outdated reality.
Links and internal architecture
Update menus, breadcrumbs, contextual links, footers and feeds directly to the new URLs instead of relying on redirects for internal navigation.
Signal consistency
Redirects, canonicals, sitemaps and links must identify the same page
Google treats redirects and canonicals as strong signals and a sitemap as a weaker one. If they point to different destinations, the search engine has to resolve a contradiction created by the website.
The new URL should be self-canonical, return 200, appear in the sitemap and receive internal links; the old URL should redirect directly to that destination.
Staging must remain private without contaminating production
The new website should be tested as if it were live, without becoming an indexable public copy or carrying development blocks into launch.
-
01
Protect access
Server-side authentication or network restrictions are preferable to a public robots.txt file for preventing unwanted access.
-
02
Plan removal of blocks
If you use noindex or disallow during development, keep an explicit checklist for removing them from the public website.
-
03
Test real status codes
Verify 200s, redirects, 404s, 410s and 5xx responses with HTTP requests, not just by looking at what the browser displays.
-
04
Crawl both versions
Compare old and new inventories, titles, headings, canonicals, hreflang, schema, images, PDFs and internal links.
-
05
Test the complete map
Every source URL must reach the intended destination in one hop, with no rule creating loops or collisions.
-
06
Verify forms and conversions
Enquiries, checkout, calls, emails and confirmations must work before traffic is moved: SEO is pointless if the commercial journey breaks.
-
07
Check performance and accessibility
Layout, images, fonts, JavaScript, focus, keyboard use, errors and assistive technologies must be tested on representative templates.
-
08
Freeze the launch scope
Schedule new ideas, late copy changes and non-essential functions for later: continuous change prevents reliable testing.
A multilingual migration multiplies relationships and opportunities for error
Every language has its own URLs, canonicals, alternatives and content. Translating a template does not automatically rebuild those relationships.
Map each language
Every old language variant points to the equivalent new page in the same language, not the Italian homepage or a default language.
Canonicals in the same language
Translated versions remain self-canonical; canonicalising every language to one page can cause them to be treated as duplicates.
Reciprocal hreflang
Each page lists itself and every definitive alternative, with the same set of relationships on the other versions.
Sitemaps and navigation
Sitemaps, language selectors and internal links must use reachable final URLs, without redirects or legacy variants.
For URLs, hreflang, canonicals and localisation, also read the complete multilingual SEO and GEO guide.
An old page should not be redirected at any cost
The correct outcome depends on whether equivalent content exists and the value that URL still holds for people and search engines.
Keep
Same URL, content still useful
Preserve the address and improve the page in measured steps. This is the lowest-risk route when structure and intent remain valid.
Move
New URL, same need
Use a direct permanent redirect to the equivalent destination and update every internal link to the new URL.
Merge
Several pages become one better resource
The new page must genuinely cover the useful intents of its sources. Automatic redirects to a vague page are not enough.
Remove
No relevant replacement
Return a real 404 or 410, remove the URL from sitemaps and internal links and provide a useful error page without masking the status.
Do not redirect everything to the homepage
A homepage is not a universal equivalent for deleted products, articles, services and documents. This confuses users, can produce soft 404s and hides which content has genuinely disappeared.
Launch is a procedure, not the moment someone presses “publish”
Order, ownership and the ability to restore service reduce the interval in which users and crawlers receive contradictory responses.
-
01
Freeze non-essential changes
Content, the URL map and configuration remain stable throughout the launch window.
-
02
Save evidence and backups
Retain the old website, database, configuration, DNS, certificates, exports and a rollback plan proportionate to the project.
-
03
Publish the website and redirects together
Avoid windows in which new URLs exist while old ones return errors or still point to intermediate destinations.
-
04
Remove temporary blocks
Check noindex, robots.txt, authentication, WAF and headers on the live response after caches, CDN and routing.
-
05
Update sitemaps and properties
Submit the sitemap containing final URLs, preserve verifications and use Change of Address only for supported domain moves.
-
06
Notify Bing and IndexNow
Update Bing Webmaster Tools and submit added, changed, moved or removed URLs; receipt does not guarantee indexing.
-
07
Run a production crawl
Immediately compare status codes, chains, canonicals, links, hreflang, schema and resources against the approved map.
-
08
Verify commercial journeys
Submit test forms, complete representative checkouts and check emails, events and confirmations in the real environment.
Migration also affects Bing, Copilot and AI answers
Systems that search and cite the Web depend on reachable URLs, consistent content and updated indexes. There is, however, no universal button that transfers every citation.
Google Search
Redirects, canonicals, sitemaps and links help Google recognise the new page as it crawls old and new URLs.
Bing and Copilot
Bing Webmaster Tools helps observe redirects, indexed URLs, errors and signals that also support grounded experiences.
IndexNow
It can quickly notify added, updated, moved or deleted URLs; it does not replace sitemaps, crawling or page quality.
AI crawlers
Robots.txt, WAF and CDN should allow only the intended access to new URLs, without inheriting accidental staging blocks.
Historic citations
An AI answer may retain an old URL or outdated passage for a while. A redirect protects the visit but cannot guarantee when the source will be refreshed.
Consistent entities
Name, author, organisation, services, products, contact details and structured data should describe the same reality before and after migration.
For visibility and citation, read how to appear in ChatGPT and AI answers ; for access and bots, read llms.txt, robots.txt and AI crawlers.
After launch, do not look only at total traffic
Comparisons by page, query, error type and time interval distinguish normal settling from problems that require correction.
| When | Check | Signal | Action |
|---|---|---|---|
| First 24 hours | Uptime, DNS, TLS, status codes, redirects, robots, noindex, forms | Immediate technical errors and broken journeys | Fix immediately or apply the planned rollback |
| First week | Logs, crawls, 404s, chains, sitemap, URL Inspection | Discovery and response of priority URLs | Repair the map and inconsistent signals |
| First 4–6 weeks | Indexing, clicks, impressions, queries, pages and conversions | Progressive transfer and persistent changes | Analyse groups of URLs rather than reacting to the total alone |
| Following quarter | Trends, updated backlinks, redirects still active, lead quality | Stability of the new asset and editorial opportunities | Optimise content without confusing migration data |
Eight mistakes that turn a redesign into avoidable loss
These problems are often invisible in a visual preview but obvious to crawlers, users, search engines and measurement systems.
“We no longer need the old URLs”
Changing every slug without an inventory breaks links, history, bookmarks and signals built over time.
“We will redirect everything to the homepage”
The destination is not equivalent, the user loses context and Google may interpret the response as a soft 404.
“The plugin will handle the SEO migration”
A tool can apply rules; it cannot decide which content is equivalent, which pages convert or which signals must be preserved.
“We will change everything together”
Simultaneous domain, CMS, URL, design and copy changes increase risk and make the cause of a drop difficult to isolate.
“The new website looks good, so it is better”
Successful visuals do not compensate for reduced content, poor HTML, worse performance, broken forms or neglected accessibility.
“The canonical replaces the redirect”
A canonical does not move the user and remains a hint. If the old resource is retired, an appropriate permanent redirect is required.
“After launch, we just wait”
Fluctuations may be normal, but errors, blocks and chains must be found immediately: waiting does not fix incorrect configuration.
“We can switch off the old domain immediately”
Redirects, verifications and historic backlinks need continuity. Keep the domain and minimum infrastructure for as long as necessary.
Essential checklist before approving go-live
Ten checks that must produce evidence, not simple verbal assurances.
-
01
Complete inventory
Crawls, sitemaps, Search Console, Bing, logs, backlinks, PDFs, images and campaigns have all contributed to the URL list.
-
02
Approved map
Every source has a decision, a relevant destination, a status code and an owner.
-
03
Tested redirects
Priority URLs, followed by the full list, reach the destination directly without loops or chains.
-
04
Consistent signals
Canonicals, sitemaps, internal links, hreflang and redirects identify the same final URLs.
-
05
Verified content
Intent, information, evidence, products, images, metadata and schema are present and current.
-
06
Blocks removed
The launch plan removes temporary authentication, noindex and disallow rules without exposing private areas.
-
07
Tested templates
Responsive layout, browsers, keyboard, assistive technologies, performance, errors and resources have been tested on representative cases.
-
08
Working conversions
Forms, emails, calls, checkout, payments, consent and confirmations have passed end-to-end tests.
-
09
Properties and monitoring ready
Search Console, Bing Webmaster Tools, proportionate analytics, logs and notifications have access and baselines available.
-
10
Defined rollback and ownership
It is clear who decides, who intervenes, what evidence is retained and how service is restored after a serious error.
How I manage a migration from WordPress to a bespoke website
I do not repair the old theme or transfer plugins and technical debt: I analyse the asset, design the new system and bring across only what has value.
GLP method
First the audit, then a verifiable quotation and scope
The migration audit separates diagnosis from the sale: it records the current website, identifies risks and priorities and produces the plan used to estimate the rebuild.
- Technical, editorial and SEO analysis of the current website
- Inventory of content, URLs, functions, integrations and dependencies
- Preliminary map covering retention, merging, redirects and removal
- A new architecture built without unnecessary CMSs and plugins
- Performance, security, accessibility, SEO and conversion testing
- Selective launch, Search Console, Bing and post-publication monitoring
| Service | Scope | Price before tax |
|---|---|---|
| Migration audit | Analysis, risks, preliminary map, action plan and fixed quotation | €175 |
| Essential | Essential bespoke rebuild according to the approved scope | €1,000 |
| Pro | More complex project, content, components and extended migration | from €2,500 |
| Essential e-commerce | Catalogue, checkout and commercial URLs within the migration plan | from €4,500 |
The final price depends on the assessed scope. See the complete route away from WordPress. No intervention guarantees unchanged rankings, traffic or citations.
Verified primary sources
The technical recommendations derive from Google, Search Console, Bing and IndexNow documentation; the operational and commercial method is an explicitly stated professional synthesis.
-
Google Search Central — Site moves with URL changesOpen source
Preparation, URL mapping, redirects, fluctuations, Search Console and migration monitoring.
-
Google Search Central — Hosting change without URL changesOpen source
DNS, TTL, infrastructure, removal of temporary blocks and monitoring the new server.
-
Google Search Central — Redirects and Google SearchOpen source
Differences between permanent and temporary redirects and the preference for server-side redirects.
-
Google Search Central — CanonicalisationOpen source
Redirects, rel=canonical and sitemaps as signals of different strength for consolidating duplicate URLs.
-
Search Console — Change of Address toolOpen source
When to use it for a domain change, plus requirements, limitations and preliminary checks.
-
Google Search Central — Debugging traffic dropsOpen source
Search Console, time comparisons, seasonality, updates and migration problems.
-
Google Search Central — Crawling errors and soft 404sOpen source
Correct use of 404 and 410 when a resource no longer exists and has no replacement.
-
Google Search Central — Localised versionsOpen source
Language URLs, reciprocal hreflang, absolute URLs and x-default on multilingual websites.
-
IndexNow — Documentation and FAQsOpen source
Notification of added, updated, moved or deleted URLs and use after migrations and redesigns.
-
Bing Webmaster GuidelinesOpen source
Permanent redirects, removals, crawling, rendering and continuity of citations and grounding.
Sources checked on 7 August 2026. Interfaces, report names and search-engine support can change: always recheck official documentation before a migration.
Frequently asked questions about SEO migration
Direct answers about rankings, redirects, domains, WordPress, timing and responsibilities.
Can you guarantee that I will not lose any rankings?
No. Rankings change continuously and a migration requires new crawling and assessment. Professional work preserves useful signals, eliminates avoidable errors and monitors changes; it cannot freeze the algorithm or competitors.
Do 301 redirects lose PageRank?
Google states that 301s and other permanent redirects do not cause PageRank loss. The destination must still be relevant, and the migration must avoid chains, errors and contradictory signals.
Must I keep every old URL exactly as it is?
When a URL is clear, stable and still consistent, keeping it is often sensible. If the architecture must change, every useful old URL needs an equivalent destination and a permanent redirect.
Can I redirect every removed page to the homepage?
No. The homepage is rarely an equivalent substitute. Merged pages should point to the relevant resource; pages with no replacement should return a genuine 404 or 410.
How long does Google take to process a migration?
There is no fixed timeframe. Google says a medium-sized website can take a few weeks for most pages to be moved in its index; size, server speed, links, sitemaps and crawl frequency influence the process.
When should the Change of Address tool be used?
After moving and redirecting a website from one domain or subdomain to another, with both properties verified. It is not used for simple internal path changes or an HTTP-to-HTTPS move alone.
Can I change domain, CMS, design and copy on the same day?
It is technically possible but increases risk and ambiguity. Google recommends separating changes where possible. If they must coincide, a stronger baseline, complete tests and longer monitoring are required.
How do I stop staging from being indexed?
Protect it with authentication or server-side restrictions. Noindex and robots.txt can be additional layers, but they must be removed reliably from the public site, and robots.txt does not protect confidential content.
Does leaving WordPress mean copying the database?
Not with my method. I analyse and recover the necessary content, media, URLs and functions, then build a bespoke website without transferring the theme, plugins and technical debt that prompted the migration.
Does IndexNow replace the sitemap?
No. IndexNow quickly notifies changed URLs; the sitemap maintains the broader canonical inventory. They can work together after a migration, but neither guarantees indexing.
How long should redirects be kept?
Keep them for a long time and often without a useful expiry, especially for domain changes, backlinks, bookmarks and historic campaigns. Removing them early recreates errors for users and crawlers.
How much does a WordPress migration cost?
The process starts with a migration audit from €175. Rebuilding follows the approved scope: Essential €1,000, Pro from €2,500 or Essential e-commerce from €4,500, before tax. Complexity, content and integrations determine the final quotation.
Next step
Want to redesign your website without improvising the migration?
We start with the audit: I record the current website’s URLs, content, signals and risks and prepare a verifiable plan before estimating the rebuild.