A fascinating article popped up yesterday which underlines the importance of SEO and domain names: From BetaKit – Looka lays off 80% of staff as failed rebrand from Logojoy cuts revenue in half. Read the article – it’s a concise story about how Logojoy rebranded and moved to a different domain name; due to a series of errors, the company lost 80% of its organic traffic. In other words: because of a name/domain change Google and other search engines lowered or removed LogoJoy from their search results.
The typical wisdom when moving domain names is that a site will lose 20-30% of visits coming from search engines for 5 – 7 months after the move. However LogoJoy made two major errors which helped to drastically decrease the visitors they saw:
During the rebrand from LogoJoy to Looka, the company also added more services; initially they were only creating logos, but they also added additional services such as business card designs, social media support, etc. Adding services is great, but doing so simultaneously to a rename only serves to dilute the value of a site in the eyes of a search engine.
The name LogoJoy quickly summarizes what the site is about: it’s a place to get logos and possibly other services related to branding. In short: it’s a great, easily-memorable name that also helps SEO since it includes the word “logo”. The new name “Looka” is ambiguous: you can easily imagine multiple different companies in many sectors having that name. In addition, “Looka” doesn’t help SEO: it’s not immediately connectable to branding, logo, social media, etc.
It wouldn’t surprise me if at least 10-15% of the traffic loss was due to the unclear new name: losing “logo” from the site name and not replacing it with a similar word strongly linked with branding (for example: media, brand, public relations, etc).
These issues could have been fixed by multiple ways, some of them pricy, some of them not so much.
The most obvious solution is not to rebrand. LogoJoy could have kept their logo-generating business at logojoy.com, then spun up another site ( BrandJoy.com? MediaJoy? ) to host their additional sales of business cards, social media assistance, etc. Once both sites were established and running for at least 6 months, then they could have been merged under the Looka brand.
A pricy-but-possible solution for LogoJoy would be – considering they had millions of dollars from venture capital funding – to simply buy their way out of the problem. LogoJoy could have bought up Google, FB and Twitter advertising for keywords relating to branding: logo, social media, how to brand my site, etc. Although this would be a very expensive move: easily at least several million dollars if not more.
The easiest solution would be to keep the LogoJoy name and sell the additional services they wanted to offer (business cards, social media) under the LogoJoy name as well.
Bottom Line Summary: Be very careful when moving domain names. When moving domain names keep the focus on the domain change. Make sure to appropriately 301 (Moved Permanently) the old site to point to pages on the new site. But most importantly, keep the focus on the move. Don’t dilute the value of your site by trying to enter new areas. If you can afford it, buy ads on Google for keywords relating to your site – the ads can do double duty by (1) referring users to you new site and (2) informing users about the name change.
In 2015, CNIL [French privacy regulator] ordered the firm to globally remove search result listings to pages containing damaging or false information about a person. But it [Google] resisted censoring search results for people in other parts of the world. And the firm challenged a 100,000 euro fine that CNIL had tried to impose.
In short, this ruling means that any European right to be forgotten requests are limited to search results from EU users; US and other countries’ search results won’t be affected.
Essentially: in more than half of Google searches, the user is not clicking on a result link. This can be because the user has their question answered via Google’s featured snippet section (example below), or the web browser launched a separate app (for example, a mobile user clicking a link which opens up the Android/iOS Google Maps app), or simply because the user got frustrated and stopped searching.
This article is just another reason why good Google marketers need to target high value keywords to get users to click through.
News came out recently that Verizon’s Oath unit (which is partly made up of Yahoo’s web assets) sold Tumblr to Automattic (they develop WordPress and run WordPress.com) for $3 million.
Obviously, this is a big drop from Yahoo’s original $1+ billion purchase, but there’s still quite a lot of value to be salvaged from Tumblr. This HN discussion comments that Tumblr is still receiving 2.5+ billion page views per month, which doesn’t even include their mobile views. I see a lot of articles moaning about Tumblr’s problems, but it is still a powerful brand and I’m quite surprised another company didn’t buy it up – $3 million is a firesale price.
Of all the articles discussing Tumblr’s sale, I like this one the best: a post from one of VCs who originally invested in Tumblr. Regardless of what happens to Tumblr, I think it will be remembered as one of the first places to easily and quickly share thoughts, a place which made it easy to create communities and fandoms, and a surprisingly upbeat and positive place compared to other social media sites.
Bottom line: He recommends building your services to use AWS EC2, DynamoDB, etc but avoiding abstractions such as Lambda and API Gateway. There’s an interesting discussion on this thread on HN: https://news.ycombinator.com/item?id=20545561 .
Quite a few news outlets are reporting a mistake in Google Maps that led to cars being stuck on a muddy road.
Apparently, the highway to Denver International Airport was backed up so Google Maps suggested a detour route – unfortunately this detour route was a dirt road that became mud after earlier rainstorms. A number of cars were stuck in the deep mud and had to be pulled out. See the video at this CNN article: https://www.cnn.com/2019/06/26/us/google-maps-detour-colorado-trnd/index.html .
It’s fun to blame Maps for incidents such as this, but it underlines how important it is to review maps and confirm where the route takes you. It would have been easy to pop open Google Maps Satellite View and quickly thumb through the overhead view to see where the detour took you – if you see a poorly maintained road, or any other warning signs, it’s definitely a good idea to avoid.
Last October, Google announced that all applications accessing and storing Gmail data must pass a security audit from an outside firm – Google estimated that such an audit would cost $15,000 – $75,000 or more. Many useful Gmail plugins and integrations are shutting down due to this requirement, even open source applications where the code is available for all to review.
Historically, Google has been slowly repositioning Gmail from an email inbox to an app platform itself: there are Chrome addons and Gmail plugins to turn Gmail into a CRM, a todo list, a kanban board, and so many other integrations – which is why I’m surprised to see Google seemingly reduce the usefulness of Gmail by adding these requirements and losing these plugins.
We’ll see how this goes, but I would bet on Google slowly loosening up restrictions over time, or possibly offering subsidies for the security audits of popular Gmail plugins.
Google Reader Strikes Again
A particularly cheeky ArsTechnica commenter wrote the following insightful comment:
I think the WordPress Twenty Seventeen theme is pretty close to the ideal starter WP template – it’s simple yet looks very nice, especially if there’s a nice header image.
One of the major annoyances with using the theme is that there’s so much empty space in a default page. For example, here’s how my /about page looked like with just the default CSS (note how small the “ABOUT” text is, and it’s a H1 heading!):
I added the following custom CSS to help reduce the space and slightly increase the size of the H1 text: