I got up early in the morning and found out that the domain I've been using for two years is due to expire in a month, reminding me to renew it. After dealing with some things, I went to renew it, only to find out that the renewal fee is 72 yuan per year, which shocked me. It was only a few yuan when I first opened it, and the first year's renewal was only about twenty to thirty yuan. The change was too drastic, and for a small personal site like mine, it's indeed expensive. I checked the current domain prices and found that the price of the .club suffix is indeed uniquely expensive, even more expensive than some .cn suffixes, which is a bit outrageous. So, I decisively chose to switch back to the .top domain I first used, which only costs 25 yuan a year to renew, and with the first year discount, I spent less than 60 yuan for three years.
On the other hand, changing domains also has quite a few costs, and the longer you use it, the higher the sunk cost. Accumulated SEO and RSS subscriptions are difficult to follow the domain switch and convert over, and may need to be accumulated again, and various statistical analyses may need to be discarded. But it still needs to be done, after all, the characteristic of the internet should be open and free, and should not be overly constrained.
The site has now moved to the domain https://scottyeung.top/
Related Work
Here are some of the tasks performed in migrating the domain:
✅ Github Pages switched to resolve to new domain
- Add DNS resolution to the domain, two A records point to GitHub's IP address, a cname is bound to the subdomain www pointing to the source address of the blog
- Modify the Github Pages Custom domain in the Github Repo
- Modify the content of the CNAME file in the public folder to the new domain (I've forgotten what this does 2333
✅ Coding.net added resolution (it's now almost entirely owned by Tencent). Originally it was used as a dedicated resolution for the domestic Baidu search engine, but because the Google Search below needs the old URL to redirect, it is temporarily used to provide Pages service.
✅ LeanCloud modified the security domain, added support for the new domain. Found that you can directly use the past reading data and comment data
✅ Google Analytics: Just modify the monitoring URL.
💤 Google Adsense: Just add a new URL, need to re-review, waiting for approval.
- ❌ Because of the epidemic, they rejected me twice, the reason is actually because of the epidemic and unable to review
- ❌ Both times they said my site was offline or inaccessible, I searched the internet and found that some people also have this problem, it may be that DNS has a problem with the resolution of the domain for foreign access, it is recommended to add additional foreign line resolution. At that time, I was using the pages service provided by coding.net, which seems to be a domestic service (doubtful), and all the resolution was transferred there.
- 💤 The fifth review is in progress. Added additional overseas line resolution to Github Pages. Overseas lines go to Github, domestic access goes to coding.net.
- ❌ Because of multiple review failures, I was banned from applying for a while, alas
- ✅ A few days after the ban period passed, I applied on the second day, and then I felt that the amount of ads was much less, and the clicks were even more
✅ Google Search
- Add a new domain and verify ownership
- Add a site map crawl to the new domain
- Try to inherit the SEO resources of the old site's index to the new domain, Google Search Console does have a site transfer function, requiring the old URL to send a 301 response redirect to the new site. Optional methods include: adding explicit URL redirection in the old domain DNS resolution, redirecting to the new domain, but the target redirect domain needs to be filed. Choose a Pages service provider that supports binding multiple domains, such as coding.net, you can bind multiple domains, and then choose a preferred domain, other domains redirect to this domain, browser debugging verification is indeed feasible, but Google Search Console does not know why it can't pass, temporarily give up. After more than an hour, it worked again, but it takes some time to process, I don't know how long, but it suggests that it is best to keep the redirect for 180 days, and the old domain only has a month left, if it can't be migrated successfully within a month, it's all for nothing.
- The migration was basically successful in the end, but the display volume and click volume of the search have dropped a bit, but it seems to have returned to almost the same level as before now
✅ Baidu Webmaster Tools: Similar to Google Search, just add a new URL for ownership verification. Still using proactive push and sitemap to submit links.
✅ 360 Webmaster Tools: The same, the operation is simple, but actually do not expect much effect.
Some Loss
Losses caused by data that cannot be inherited due to domain switching:
- ❌ Diviner site statistics. Because its statistics seem to be based on the site URL as the key for statistics, after the change, it directly starts to re-statistics. (The consequence of too simple service startup is the sacrifice of maintainability/extensibility
- ❌ Loss of some rss subscriptions (although there were not many to begin with
Information Modification
Here are some places where I need to change my URL:
- ✅ The description of the blog's repo on GitHub and personal introduction
- ✅ The blog list in the Chinese independent blog repo needs to modify the URL, send PR to change
- ✅ The personal URL written on twitter