The movement to create the web safer through HTTPS brings many helpful advancements for webmasters. additionally to security enhancements, HTTPS guarantees future technological advances and potential SEO advantages for marketers.
HTTPS in search results is rising. Recent MozCast knowledge from Dr. Pete shows nearly 2 hundredth of initial page Google results area unit currently HTTPS.
Sadly, HTTPS conjointly has its downsides.
Marketers run into their initial challenge once they switch regular hypertext transfer protocol sites over to HTTPS. Technically difficult, the switch generally involves routing your website through a series of 301 redirects. traditionally, these sorts of redirects area unit related to a loss of link equity (thought to be around 15%) which might result in a loss in rankings. this will offset any SEO advantage that Google claims change.
Ross Hudgens utterly summed it up during this tweet:
Ross Hudgens
Many SEOs have anecdotally shared stories of HTTPS sites performing arts well in Google search results (and our soon-to-be-published Ranking Factors knowledge appears to support this.) However, the short term impact of an oversized migration is arduous to require. once Moz recently switched to HTTPS to produce higher security to our logged-in users, we tend to saw associate degree 8-9% dip in our organic search traffic.
Problem variety 2 is that the subject of this post. It involves the loss of referral knowledge. Typically, once one website sends traffic to a different, data is distributed that identifies the originating website because the supply of traffic. This valuable knowledge permits folks to visualize wherever their traffic is coming back from, and helps unfold the flow of knowledge across the online.
SEOs have long used referrer knowledge for variety of helpful functions. Oftentimes, folks can link back or look into the positioning causing traffic once they see the referrer in their analytics knowledge. Spammers understand this works, as proved by the recent increase in referrer spam:
This method stops once traffic flows from associate degree hypertext transfer protocolS {site|website|web website} to a non-secure HTTP site. during this case, no referrer knowledge is distributed. Webmasters cannot understand wherever their traffic is coming back from.
Here's however referral knowledge to my personal website looked once Moz switched to HTTPS. I lost all visibility into wherever my traffic came from.
Enter the meta referrer tag
While we won't solve the ranking challenges obligatory by change a website to HTTPS, we are able to solve the loss of referral knowledge, and it's really super-simple.
Almost utterly unknown to most marketers, the comparatively new meta referrer tag (it's really been around for some years) was designed to assist go in these things.
Better yet, the tag permits you to manage however your referrer data is passed.
The meta referrer tag works with most browsers to pass referrer data during a manner outlined by the user. Traffic stays encrypted and every one the advantages of exploitation HTTPS remain in situ, however currently you'll pass referrer knowledge to any or all websites, even people who use hypertext transfer protocol.
How to use the meta referrer tag
What follows area unit extraordinarily simplified directions for exploitation the meta referrer tag. For a lot of in-depth understanding, we tend to extremely suggest concerning the W3C operating draft of the specification.
The meta referrer tag is placed within the section of your hypertext markup language, and references one amongst 5 states, that management however browsers send referrer data from your website. The 5 states are:
None: ne'er pass referral knowledge
None once Downgrade: Sends referrer data to secure HTTPS sites, however not insecure hypertext transfer protocol sites
Origin Only: Sends the theme, host, and port (basically, the subdomain) stripped of the complete uniform resource locator as a referrer, i.e. https://moz.com/example.html would merely send https://moz.com
Origin once Cross-Origin: Sends the complete uniform resource locator because the referrer once the target has constant theme, host, and port (i.e. subdomain) regardless if it's hypertext transfer protocol or HTTPS, whereas causing origin-only referral data to external sites. (note: there's a misprint within the official specification. Future versions ought to be "origin-when-cross-origin")
Unsafe uniform resource locator: continuously passes the URL string as a referrer. Note if you have got any sensitive data contained in your uniform resource locator, this is not the safest possibility. By default, uniform resource locator fragments, username, and watchword area unit mechanically stripped out.
Emoticon Emoticon