Migrate the Tails website to the tails.net namespace

• The tails.net domain already redirects to the Tails Website: https://tails.net/
• We need to plan and migrate the website to use the tails.net domain as its main entry point and namespace.

• Phase 0: Preparation steps
• Phase 1: Start serving the website also on tails.net
• Phase 2: Make https://tails.net our canonical website
• Phase 3: Redirect from tails.boum.org without breaking the Tails Upgrader and security notifications
• Follow-ups

Phase 0: Preparation steps

• Figure out how the domain change impacts SEO (eg. integration with DuckDuckGo and Google Search Console, if any)
• Read-through Google's How to move a site doc and map into actionable items
• Add the new domain to Google Search Console
• Add DNS-based verification to the old domain in Google Search Console so it continues to be verified after the migration
• Add DNS-based verification for the tails.boum.org domain in Google Search Console
• Come up with a plan for invalidated translations
• Migrate the Puppet config to voxpupuli/puppet-nginx -- puppet-tails!113 (merged)
• Check how/whether to inform DuckDuckGo and Bing about the domain change.

Phase 1: Start serving the website also on tails.net

• Start serving the website on tails.net -- puppet-tails!116 (merged)
• Add an HTTP Link: header with rel="canonical" on both domains, both pointing to the new domain
• Remove the <meta name="google-site-verification" /> tag from the website (not needed anymore, as we now have DNS-based verification)

Phase 2: Make https://tails.net our canonical website

• Make all references to our website in tails/tails point to the new canonical location, except for the ones under wiki/src
  • There may be regexps, not only hardcoded strings, so start with git grep -E 'tails.*boum.*org' to try & catch as many as possible.
  • This will e.g. make our test suite and tails-security-check start using the new website.
  • Target the stable branch.
  • Replace 'tails.boum.org' by 'tails.net' (except... (tails!1145 - merged)
• Prepare: Use the new tails.net domain on the website (tails!1143 - merged)
  • Change all URLs on wiki/src to use the new domain
  • Migrate QR codes (tails@2072b224)
• Schedule the website source change to a low traffic period (eg. in-between releases)
  • Inform tails-l10n about the change, when it'll happen, and its effects on translations
  • Inform tails-dev about the change, when it'll happen, and its effects on monthly stats
• Start using tails.net on the website source (i.e. merge tails!1143 (merged))
• Fix translations invalidated by the change above (potentially with help from tails-l10n)
• Inform tails-l10n that the change has been made and how to deal with it.
• Check whether we should add tails.net to the HSTS preload list of major browsers, see tails@7bd22b11

Phase 3: Redirect from tails.boum.org without breaking the Tails Upgrader and security notifications

• Make sure a release happened before proceeding, so all code in the new release will be using the new domain.
• Merge 302 redirections: Redirect from tails.boum.org to tails.net witho... (puppet-tails!124 - merged)
• Make sure upgrading from a pre-5.14 Tails still works.
• Switch HTTP status code: 302 → 301
• Inform Google about the domain change in the Google Search Console
• Check Google Search Console for successful migration
  • Ref: Page Indexing report
  • Ref: Manage your sitemaps using the Sitemaps report
• Update the address on Twitter, Wikipedia and other social media
• Announce on the website: Add news about the new tails.net domain (tails!1201 - merged)
• Announce on Twitter
• Announce on mailing lists

Follow-ups

• Deprecate the Tails Upgrader for Tails versions... (#18024)
• Deal with pages not indexed by Google (#18025)
• Rename website log files to use the new domain (#18026 - closed)
• Redirect www.tails.net to tails.net (tails#19915 - closed)