The Internet Marketing Driver

  • GSQi Home
  • About Glenn Gabe
  • SEO Services
    • Algorithm Update Recovery
    • Technical SEO Audits
    • Website Redesigns and Site Migrations
    • SEO Training
  • Blog
    • Web Stories
  • Contact GSQi

Bitlygeddon Arrives On 6/29/16 – How To Update A Branded Short Domain Name So Your Shared Links Don’t Break

June 14, 2016 By Glenn Gabe 2 Comments

Share
Tweet
Share
Email
106 Shares

Bitlygeddon arrives on 6/29/16

For years I’ve been using a short branded domain name combined with bitly to shorten links I share across social media. For example, I registered glennga.be as the short domain name, and whenever I share a link on Twitter, that’s the domain name in the urls for all shares.

Here’s a quick example that leads to one of my recent blog posts: http://glennga.be/24GmaI3. When clicking that link, users are taken to my post, but the link that gets shared is branded. It’s a popular way for companies to keep their brand in front of a lot of people. Again, many have set this up through bitly, which handles and tracks shortened links.

Now, setting up and using a short branded domain name is often one of those things that simply never gets revisited. You know, you set it up, it works great, and you just assume it will always work. Well, THINK AGAIN. Bitlygeddon is upon us.

Bitlygeddon – Poof, your links will stop working on 6/29/16
We are quickly approaching what I’m calling Bitlygeddon, or the day that many heavy social media users realize that all of their shortened links using a branded domain name stopped working. Poof, they’re dead.

That’s because bitly is moving to a new hosting provider and the IP address you originally used to set up your branded short domain name is changing. Actually, there are two IP addresses now that you can use. And without changing your A record for the branded domain name, your links will not resolve starting on June 29, 2016. Yes, that means you have to change DNS settings, and soon.

So, you might still be sharing links like crazy on Twitter, but those links will not lead anywhere after 6/29 if you don’t make the necessary changes. Embarrassing, right? And then you’ll be scrambling to make the change, only to be confused with how to do it. Therefore, I decided to write this post to 1) remind you that you need to make the change, and 2) explain a little more about how to change your A record.

Note, I made the necessary changes this past weekend. Once I knew where to go and exactly which settings to change, it only took a few minutes. I’ll cover more about this below.

Bitly Documentation
If you’re like many heavy social media users, you set up your short branded domain name a long time ago. That means you might be confused with what you need to change, where those settings are, etc. Well, bitly did send out an email explaining more about the situation, as well as including a link to a blog post with instructions. I didn’t find the instructions to be perfectly clear, but they did get me moving in the right direction. The red underscore is from me, not bitly.

The email Bitly sent out about the 6/29/16 deadline

Action Item: So, the first thing you should do is visit the post and thoroughly read the instructions. There are also links to popular hosting providers and how to change the A record for your domain name. But again, you might still leave that post a little confused. Don’t worry, I’ll explain more about what to do.

Where To Make The Change – Your Hosting Provider
I’ve received a few emails about this situation and it seems that a confusing part of the process is understanding where to actually make the change. Many jump to their domain registrar (like GoDaddy or Network Solutions) thinking that’s where the change needs to take place. But when you get there and check the DNS settings for your branded domain, you’ll see this:

Changes need to be made at your hosting provider, not domain registrar

That’s right, since you set up your branded short domain name to point to your hosting provider, that’s where you will need to change the A record. So leave your domain name registrar and hop over to your hosting provider.

Once there, you will need to follow instructions specific to your hosting provider for changing the A record. Depending on how tech-savvy you are (or not), now might be a good time to call your hosting provider. They will know all about your domains and how to quickly change an A record. And for those of you that are tech-savvy, then just access your DNS settings for your branded short domain name and update the A record.

Action Item: Don’t jump to your domain name registrar to make the change. The changes need to be made at your hosting provider. Once you find your branded short domain name, you’ll need to update the DNS records, and specifically the A record settings.

An example of what this looks like:
Once I accessed my admin settings at my hosting provider, I needed to update DNS settings for the branded domain. I did that by simply clicking the DNS link in my admin console.

Edit the DNS settings for your short domain name.

Once in my DNS settings, I found the records that needed to be updated using the two new IP addresses that bitly is using. Remember, there are two new IP addresses, not one. So the first thing to do is to update the records that are present already for www and @. Note, I’m double-checking with bitly about the need to update the A record for @. I’m not sure if that’s necessary, but my original setup did have @ using bitly’s IP address. I’ll update this post once I hear back.

Updating the A record for short domain name.

But again, bitly now has two IP addresses for redundancy purposes. For example, if one fails, the second will be used. That wasn’t the case in the past. But it’s important to note, since you need a second A record for each of the settings listed above. In order to do this, you need add another record via your admin console.

For my setup, I simply clicked “Add a record” and then entered the required information plus the second IP address. I completed this for both www and @.

Action Item: Make sure you update the IP addresses for the current A record for www and @, and if needed, make sure you add two A records for each of items I mentioned above (www and @) so you can include the second IP address that bitly provided. You should add both since bitly is using two IP addresses for redundancy purposes. This will ensure that if one fails, the other can be used as a backup (and your shortened links will still work).

Validate Via Bitly
The last item on our checklist is to validate that the changes are working via your advanced settings in bitly. You can access your advanced settings by clicking the hamburger menu in the upper right corner, clicking “settings”, and then “advanced settings”. Once you do, you’ll see a “Re-validate” button in your advanced settings. When you click that link, bitly will check to ensure all is set up properly.

Note, you can also just wait 24 hours for auto-validation, but why not just validate immediately to make sure all is ok? That’s what I recommend. Once you receive confirmation, you’re good to go. You are now safe from Bitlygeddon. :)

Validating the changes in bitly for a short domain name.

Summary – Beware, Bitlygeddon is Coming.
So now you’re up to speed on bitlygeddon, which is arriving on June 29, 2016. The good news is that you still have over two weeks before it arrives and the changes should only take a few minutes to complete. The bad news is that I fear many users will not know about the change and their short domain names will tank starting on 6/29. And if that happens, there won’t be much “sharing” happening with social sharing. Good luck and pass the news on to anyone you know with a short branded domain name using bitly. A few minutes now might save many in frustration down the line.

GG

 

Share
Tweet
Share
Email
106 Shares

Filed Under: social-media, tools, twitter

Connect with Glenn Gabe today!

Latest Blog Posts

  • Continuous Scroll And The GSC Void: Did The Launch Of Continuous Scroll In Google’s Desktop Search Results Impact Impressions And Clicks? [Study]
  • How to analyze the impact of continuous scroll in Google’s desktop search results using Analytics Edge and the GSC API
  • Percent Human: A list of tools for detecting lower-quality AI content
  • True Destination – Demystifying the confusing, but often accurate, true destination url for redirects in Google Search Console’s coverage reporting
  • Google’s September 2022 Broad Core Product Reviews Update (BCPRU) – The complexity and confusion when major algorithm updates overlap
  • Google Multisearch – Exploring how “Searching outside the box” is being tracked in Google Search Console (GSC) and Google Analytics (GA)
  • Sitebulb Server – Technical Tips And Tricks For Setting Up A Powerful DIY Enterprise Crawler (On A Budget)
  • Google’s Helpful Content Update Introduces A New Site-wide Ranking Signal Targeting “Search engine-first Content”, and It’s Always Running
  • The Google May 2022 Broad Core Update – 5 micro-case studies that once again underscore the complexity of broad core algorithm updates
  • Amazing Search Experiments and New SERP Features In Google Land (2022 Edition)

Web Stories

  • Google’s December 2021 Product Reviews Update – Key Findings
  • Google’s April 2021 Product Reviews Update – Key Points For Site Owners and Affiliate Marketers
  • Google’s New Page Experience Signal
  • Google’s Disqus Indexing Bug
  • Learn more about Web Stories developed by Glenn Gabe

Archives

  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • August 2021
  • July 2021
  • June 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • GSQi Home
  • About Glenn Gabe
  • SEO Services
  • Blog
  • Contact GSQi
Copyright © 2023 G-Squared Interactive LLC. All Rights Reserved. | Privacy Policy
This website uses cookies to improve your experience. Are you ok with the site using cookies? You can opt-out at a later time if you wish. Cookie settings ACCEPT
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience. You can read our privacy policy for more information.
Cookie Consent