Skip to content

Instantly share code, notes, and snippets.

@rjgux
Last active February 17, 2017 08:52
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save rjgux/85627790772f3e0209bb068b9d5f651f to your computer and use it in GitHub Desktop.
Save rjgux/85627790772f3e0209bb068b9d5f651f to your computer and use it in GitHub Desktop.

Site Move (With URL Changes)

Useful guide - How to 301 to a new domain

  • Delete .htaccess from new host in /public (removes redirect from viperinnovations to vipersubsea)
  • Deploy to new host (on DeployHQ)
  • Import database (details on Cipher, already added creds to db.php)
  • Check/test viperinnovations
  • Add 301 redirects to vipersubsea .htaccess
  • Update search console/analytics (see below)

Best practices

  • Use 301 redirects
  • Keep 301 redirects for as long as possible & consider keeping indefinitely
  • Enable SSL on destination
  • Use site verification (old & new domains)
  • Update incoming links (from external sites/social media profiles/ad campaigns)
  • Provide errors for deleted or merged content

Prep

  • Generate 301 redirects
  • Get sitemap file of new URL
  • Get sitemap file of old URLs
  • Confirm new domain management access (?)
  • Confirm Search Console access (?)
  • Confirm Google Analytics access (?)

Steps

The time it takes Googlebot and our systems to discover and process all URLs in the site move depends on how fast your servers are and how many URLs are involved. As a general rule, a medium-sized website can take a few weeks for most pages to move, and larger sites take longer. The speed at which Googlebot and our systems discover and process moved URLs depends the number of URLs and the server speed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment