My name is Jean-Dominique Nguele and this is my blog. FLVCTVAT NEC MERGITVR
I originally started writing another post last week but in the meantime I did a domain name migration. What is a domain name migration you will ask? It is the act of migrating content from a domain to another domain. Not host, domain. If this was about host migration there would be no need for a post as the changes would be straightforward. People may give you a different or more precise description but it is basically what I did. And also what it sounds like. I like to name things so that when they are described or revealed they turn out to be pretty much what you expect. It’s like coding. If I have a piece of code with a method
boolean validatePassword(string username, string password) when looking at the code you pretty much expect to see some user retrieval and maybe encoded password validation. You definitely do not expect a session to be started or anything funny like that. Enough with this, let’s get back onto today’s topic. Domain name migration.
I decided to separate my blog from my main domain iamnguele.com a couple of weeks ago as I picked a new pseudo that you may have noticed by now: Coding Nagger. Why that name and why move only the blog? I thought I should pick a different and more playful pseudo than IamNguele. IamNguele was more of a statement, some “Hey I’m here” kinda thing. Also, my english was not great and nguele.com was taken. On top of that, iamnguele gets me on top of the SEO rankings on my name. On top of that, I gain rankings for the search term
coding nagger as you can see below.
Now, after five years living in London I like to think I somewhat improved my english speaking and writing skills. Also I picked a name that would be more fitting. The Coding part is pretty self-explanatory, and Nagger because I can try to push you something that I believe is the right thing whether you like it or not. Just to precise the context I’m talking about code reviews, solution analysis/design. So here we are, Coding Nagger and I still have not mentioned anything about domain name migration but you get the context at least.
Changing domain name in itself is relatively easy. Most hosting providers allow you to point and click your way through it even if you go for tech saavy stuff like Amazon Web Services. However, there are a few things that you need to take into consideration before you get started. If your website or blog is part of your personal brand and ranks well either you are a probably a pioneer in your field, no matter how niche it can be. If it is the case, congrats you may not need SEO as much as others such as myself.
What is SEO? I hear you ask. SEO stands for Search Engine Optimisation. The rules seem to change pretty constantly and vary based on which search engine you use. Basically, put out quality content, stay on focus of the topic you want your article/blog/website to rank up and voila. The problem with domain name migration is that if you are not careful, it will take a while before your pages rank back up. It will happen because your search engine will consider that your “renamed” site is a new site. Therefore whatever counter or algorithm search engines use to rank sites will see your website as having a score of 0 out of 100 instead of let’s say 42 figuratively speaking.
Do your pages have a decent SEO rating? Do you intend to keep things like this? If the answer to either of this questions is no, feel free to skip the end of the post and rejoice for the now more useful introduction I gave you.
Eventually, you need to consider whether your existing website requires a SSL certificate and whether the links you find through your favorite search engine use the
https protocol. If your website has secure links the they are likely to rank higher and be prioritised over their non-secure version by your browser or search enine.
Once you figured your constraints we (mostly you) can get to work.
This probably should have been the title of this post, really clickbait worthy. The gist of what needs to happen is redirecting your existing website links towards the new domain name. Let’s get down to business.
If you do not have your new domain name, the obvious first step is to buy. Just the domain name, nothing more, nothing less, yet. Once you have the domain name, get it to point to the location where your existing website is hosted. Some hosting providers will allow you to do so with a couple clicks. If you manage your domain names separately from your hosting you will need to CNAME entries of your new domain yourself to point at the IP address where you host your website.
After a few minutes, you can try to access your website using your new domain name. You should be able to navigate it with the right links and the same structure you have for your existing domain.
You may remember that I mentioned something about
https links visible through a search engine result page. If your existing website has its pages indexed with the
https protocol prefix you have one last thing to deal with before setting up the redirect. You need to setup a SSL certificate so that browsers allow people to access your new site. Believe me, you do not want to just reassign the certificate to the new domain. I tried and had a micro-heart attack when I realised 5 minutes later that the links to my existing blog would not even open redirect or not. This is because if your website tells a browser it has a secure link but have no certificate it will simply be blocked. If it has an invalid certificate it will prompt users that your website is unsafe to access or stole another site’s certificate. Just buy a new certificate and assign it to your new domain. Keep the existing stuff where it is.
Here we do the easy bit. Your hosting provider should give you access to at least a FTP containing a bunch of folders and one of these contains your website. From there, you need to create a new folder sitting next to your website folder that will contain the
.htaccess file where you shall write the permanent redirection configuration. Once that folder is created you will have to upload a
.htaccess file with these contents:
Obviously you may replace
www.codingnagger.com with your domain name unless you want to send me more traffic. I would be more than fine with that. Also, if you do not have nor require a SSL certificate on your existing and new domain, replace
Here I chose not to detail the specific of each step as there is multiple ways to achieve this for all providers. Also, for most hosting provider the process is trivial in itself and if you manage your domain name yourself you definitely know your way around your provider dashboard. The one thing you may need is a bit of experience, of guidance. A flow showing in which order you should proceed to avoid losing your SEO ranking. I mean, personally it did not go so bad. My blog went from top hit when googling myself to bottom of the first page with a title change on top of the domain change. Just look:
Note that I had a look at some of my most popular posts, the one that have the best SEO rankings. Some still appear under the
blog.iamnguele.com domain. Try to google
nsattributedstring color image and see what comes up maybe not first everywhere but at least second.
This is why SEO matters. And I will update the post in a few days/weeks to see if it still pops up on top after Google’s indexer sees it as a
codingnagger.com entry. It has been there for a couple years now and I doubt it changes. Unless I screwed up completely and give you an excellent reason to disregard this whole post.
Thank you for reading and hopefully this will help you doing some domain name migration without losing your content rankings. Till next time.
Two years ago at the WWDC, Apple introduced to the world a new programming language: Swift. Bringing to life a new programming language is always a challenge because even if it is the most beautiful syntactically, the lack of use cases may make it only a nice-to-have in some developers mind.
Apple announced to be the future of iOS and OS X apps, which is quite bold since not all developers may learn especially with the expansion of the cross-platform app development using the likes of Xamarin or Titanium.
However, bringing an open-source language allows the community to port it to multiple platforms allowing the benefits of Java without the need of a JVM to run it. I even found out that you can now do scripting using Swift which opens a lots of doors even in terms of DevOps.
However what drew my attention to Swift at first is that summit that occurred a few months ago between Google, Facebook and Uber in London were discussing the language with the possibility of it getting a grown interest in each party. Add another powerhouse like IBM massively supporting and you get what smells like an IETF meeting for a new norm.
Facebook and Uber are both companies trying to use cutting-edge technologies to get the best services possible for their users and are known to use variety of platforms/languages. About Google I can not really say as I do not have a direct input about it, however based on what I read in “How Google test software” it seems they are in a similar position.
Then comes the big IF, what if Google was to drop Java for Android development in favour of Swift ? It might seem unlikely considering the massive following and use of Android in the developers community along with the fact that Java not only is one of the most used languages in the world but also learn in pretty much any computer science related-school.
However Google may have £8.8 billion reasons to make the big jump, those sum up in one word: Oracle. Oracles, always bringers of bad news in Antic Greece but here it is not about them. It is about the Oracle that acquired Sun Microsystems in January 2010, the same Oracle which is now suing Google only to cash in on their investment. Some even speculate that Oracle purchased Sun only so they can sue Google on the conditions of use of Java, even thought I have not made myself an opinion on the matter it is quite intriguing that the beginning of “Oracle VS Google” case was only 7 months after the acquisition.
With this lawsuit hanging over Google’s Android SDK, Swift is more than a valuable option. Along with the fact it is clearly Open-source, it can draw the iOS developers community to port their apps to Android without the heavy refactoring nor the code converters that are not always on point and may not follow the latest updates of this new language that is now on the verge of publishing its third version in two years.
If Google was to make Swift slowly replace Java as the “First class” language for Android development that would not be before a couple of years. But at least if you read it here first and that it turns out to be true, you can still say that you saw it here first and talk about that oracle guy able to predict the future tech trends.
Now imagine a world where you can build Android, iOS and OS X apps with only one language. Add the fact that this language can be compiled on UNIX systems and now even on Microsoft systems thanks to initiatives like Silver for Windows development using the .NET and Windows Phone APIs or Perfect allowing to build easily RESTful server applications. The possibilities are limitless, desktop clients, servers, scripts. You can do so much, so if you were looking to learn a new language, you know what to pick next: Swift.
Thank you for reading, here is a Taylor Swift video