The document discusses website migration goals and best practices. It outlines the importance of both protecting existing rankings and visibility through defensive strategies like redirects and accessibility, as well as forging new opportunities through improved information architecture, authority signals, and content. A good migration example is shown where rankings were maintained through a clean swap between the old and new sites.
5. Don’t just maintain traffic, rankings &
revenue
but IMPROVE on these key metrics
also.
6. A successful migration.
Our philosophy on delivering a successful migration can be broken
down into two distinct parts:
DEFENSIVE
Protecting the rankings and visibility you already have:
• IA compatibility
• Redirect management
• Crawling & accessibility
• Relevancy transition
OFFENSIVE
Forging new opportunities via an improved technical
environment:
• Improved IA for added relevancy
• Enhanced authority management
• Content & depth enhancements
• Best in class category / product pages
• Correcting the basics
10. Planning for a migration can be
broken down into four key areas…
RESPONSIBILITIES
Get everyone into a
room and discuss
who’s responsible
for each factor of
the migration.
Ensure everyone
knows what they’re
supposed to do and
when.
RESOURCE
It’s crucial to
ensure you have the
correct resource
available at
various stages
during a migration.
Don’t let the team
go on holiday on
migration day!
PROJECT PLANNING
Will you be using any
project planning
software such as
Jira/Trello to manage
the day to day
workflow of the
migration?
CHECKLIST
This needs to be
defined as early as
possible and
tailored to each
individual project.
Each migration
comes with its own
unique issues and
challenges.
11. Responsibilities
Involve as many stakeholders as
possible.
UX / Design
Analytics
SEO
Product
PR / Content
Paid
Dev
DON’T WORK IN SILO!
12. Resource
NO HOLIDAYS!
Estimate time and effort required.
Ensure budget is allocated to
resource.
Include a buffer for additional
resource.
Check availability of the migration
13. ProjectPlanning
CRUCIAL FOR A SMOOTH MIGRATION!
Determine the plan as early as
possible.
Share the plan with all stakeholders.
Ensure it’s clear & concise.
Include responsibilities.
Utilize project management software.
Consistently keep track of progress.
14. MigrationChecklist
DETERMINE WHAT NEEDS CHECKING
Often varies per project.
Break into key phases.
Include technical and on page factors.
Don’t forget to include 3rd party
elements.
Ensure responsibilities are defined.
15. MigrationChecklist
COMMON ITEMS TO CHECK OFF
Who’s creating the sitemap & when is it
needed.
Who is responsible for creating Redirect,
Robots.txt & Sitemap files and when for.
Which pages will need to be redirected.
Who is handling the transfer of tracking
elements.
19. Wireframes
Often overlooked – input into wireframe designs to determine key on page
factors is crucial from the onset.
20. StagingAccess
Probably one of the most important factors is getting staging
site access.
Remember – Staging sites need to be
inaccessible to search engines!
Robots.txt
NoIndex
Password Protect
IP Restricted Access
22. GatheringURLs
To ensure a smooth migration, we need to capture as many URLs as possible
to map to the new site structure.
23. GatheringURLs
Get access to your server log files to discover
even more URLs including those that bot’s crawl
the most.
24. RedirectMapping
Likely the most crucial part of any migration is
ensuring that all URLs are correctly mapped to
their new counterpart.
Old URL Redirect Type New URL
example.com/old-url-1 301 example.com/new-url-1
example.com/old-url-2 301 example.com/new-url-2
example.com/old-url-3 301 example.com/new-url-3
example.com/old-url-4 301 example.com/new-url-4
example.com/old-url-5 301 example.com/new-url-5
example.com/old-url-6 301 example.com/new-url-6
example.com/old-url-7 301 example.com/new-url-7
example.com/old-url-8 301 example.com/new-url-8
example.com/old-url-9 301 example.com/new-url-9
example.com/old-url-10 301 example.com/new-url-10
example.com/old-url-11 301 example.com/new-url-11
example.com/old-url-12 301 example.com/new-url-12
example.com/old-url-13 301 example.com/new-url-13
example.com/old-url-14 301 example.com/new-url-14
example.com/old-url-15 301 example.com/new-url-15
example.com/old-url-16 301 example.com/new-url-16
example.com/old-url-17 301 example.com/new-url-17
25. Legacy Redirects
Don’t forget any existing redirects!
URL A redirects to URL B (legacy redirect)
URL B redirects to URL C (new redirect)
Which results in the following redirect
chain:
URL A –> URL B –> URL C
To eliminate this, amend the existing
legacy redirect and create a new one so
that:
URL A redirects to URL C (amended legacy
redirect)
URL B redirects to URL C (new redirect)
EXAMPLE
27. Internal Link Updates
Internal Link
Updates
HTML LINKS
• Links to other URLs
• JavaScript Resource Links
• CSS Resource Links
• Image resource links
• Video Files
CSS LINKS
• Image Resources
• Internal Web Fonts
MISCELLANEOUS LINKS
• Robots.txt XML Sitemap Links
JAVASCRIPT LINKS
• Internal URLs
• Internal Image Files
• Internal CSS Links
28. RankingBenchmark
During a migration, it is always advisable to
start tracking keywords daily when possible for
a period both pre-migration and post-migration.
29. GSC- Configuration
When changing to a new domain name, you need to ensure GSC is
configured correctly.
Target country is specified.
All HTTP / HTTPS / WWW variants are added.
Preferred domain is set up.
URL Parameters are configured.
Disavow has been added to all relevant
properties!
Use change of address.
UX / Page / Analytics / SEO / Product Teams Etc
Paid -
Needs doing early on in the project or set up for a fuck up
Budget – Man hours in-house as well as enough to cover agency support
Buffer – Often can be under estimated the time required – include a buffer and plan effectively.
Holidays – make sure people are about!
IA / Wireframes – makes sure SEO’s are involved!
Legacy Redirects
Paid Team
Key phases:
Pre-launch
Staging
Post Launch
3rd Parties
GA Tracking Checks
GSC Checks etc
Key phases:
Pre-launch
Staging
Post Launch
3rd Parties
GA Tracking Checks
GSC Checks etc
Mention Weekends
Ensure Hierarchy is optimized to Keywords bla blab lab
Review the new site’s prototypes or wireframes before development commences. Reviewing the new site’s main templates can help identify both SEO and UX issues at an early stage. For example, you may find that large portions of content have been removed from the category pages, which should be instantly flagged. Or you may discover that some high traffic-driving pages no longer appear in the main navigation. Any radical changes in the design or copy of the pages should be thoroughly reviewed for potential SEO issues.
From here you’re likely to create a more technical spec, URL Structures, Headings, Schema Etc
Robots.txt – If linked could cause some pages in the index without META data
No Index – Hard to test indexing rules
Password Protect – Solid approach to avoid indexation, but some external tools might not be able to handle Password Authentication
IP Access – Again secure approach avoiding URLS being indexed – Might have some issues with external tools.
Robots.txt – If linked could cause some pages in the index without META data
No Index – Hard to test indexing rules
Password Protect – Solid approach to avoid indexation, but some external tools might not be able to handle Password Authentication
IP Access – Again secure approach avoiding URLS being indexed – Might have some issues with external tools.
Ignore robots.txt (in case any vital parts are accidentally blocked)
Follow internal “nofollow” links (so the crawler reaches more pages)
Crawl all subdomains (depending on scope)
Crawl outside start folder (depending on scope)
Change the user agent to Googlebot (desktop)
Change the user agent to Googlebot (smartphone)
Legacy URL (include only the indexable ones from the craw data)
Organic visits during the last 12 months (Analytics)
Revenue, conversions, and conversion rate during the last 12 months (Analytics)
Pageviews during the last 12 months (Analytics)
Number of clicks from the last 90 days (Search Console)
Top linked pages (Majestic SEO/Ahrefs)
SKU’s can speed stuff up
Catch All Redirects etc.
When redirects are poorly implemented, the consequences can be catastrophic. Users will either land on Not Found pages (404s) or irrelevant pages that do not meet the user intent. In either case, the site’s bounce and conversion rates will be negatively affected. The consequences for search engines can be equally catastrophic: they’ll be unable to associate the old site’s pages with those on the new site if the URLs aren’t identical. Ranking signals won’t be passed over from the old to the new site, which will result in ranking drops and organic search visibility loss. In addition, it will take search engines longer to discover and index the new site’s pages.
If the site’s images have moved to a new location
Mention Other Benchmarking:
SCOT
Traffic
Engagement
Speed
The new site’s page loading times can have a big impact on both traffic and sales. Several studies have shown that the longer a page takes to load, the higher the bounce rate. U
Commonly forgotten the Disavow..!
- Other bits you could do is fetch and render
Mention Exporting Data out if your moving to a new domain, ensuring you keep a back up of elements such as
Internal Links
Errors
Links to your site
if there are critical issues they SHOULD NOT push ahead regardless to hit a deadline - there should at any stage pre migration or on migration day be the ability to instigate a no go decision and postpone
Also Check META Robots Tags!
Worth checking Canoncials – not linked back to staging site
Redirect loops (a URL that infinitely redirects to itself)
Redirects with a 4xx or 5xx server response.
Redirect chains (a URL that redirects to another URL, which in turn redirects to another URL, etc).
Canonical URLs that return a 4xx or 5xx server response.
Canonical loops (page A has a canonical pointing to page B, which has a canonical pointing to page A).
Canonical chains (a canonical that points to another page that has a canonical pointing to another page, etc).
Protocol/host inconsistencies e.g. URLs are redirected to both HTTP and HTTPS URLs or www and non-www URLs.
Leading/trailing whitespace characters. Use trim() in Excel to eliminate them.
Invalid characters in URLs.
Tackle the redirect chains,
Legacy Redirects causing it?
Internal Links?
General poor mapping …
Redirect loops need to be removed because they result in infinitely loading pages that are inaccessible to users and search engines. Redirect loops must be eliminated because they are instant traffic, conversion, and ranking killers
Use Screaming Frog or Deepcrawl to help identify issues
Analyze over time – make sure we’re tackling issues that have become present from the log files
Works like way back tracked daily WOW
Before indexation always fetch and render a number of the different template files
Obvs need to check mobile too – Mobile-first and that
May want to collaborate with Paid to increase aggression on KW’s that may drop during the migration
Mention SCOT Again
Desktop & mobile visibility (from SearchMetrics, SEMrush, Sistrix)
Desktop and mobile rankings (from any reliable rank tracking tool)
User engagement (bounce rate, average time on page)
Sessions per page type (i.e. are the category pages driving as many sessions as before?)
Conversion rate per page type (i.e. are the product pages converting the same way as before?)
Conversion rate by device (i.e. has the desktop/mobile conversion rate increased/decreased since launching the new site?)