Update: TinyMCE, the plugin mentioned in this article, has reversed the change that was causing the referral data to be lost. Once WordPress has updated their distribution to utilise the latest version, and websites update to the latest version of WordPress, this issue should be resolved - great news!
A recent change to WordPress may lower the number of reported referral visitors to your website.
An update to a plugin - TinyMCE - that is widely used by WordPress (a CMS that powers 24% of all websites) has been updated. This is a positive change that resolves a potential security exploit that could allow an attacker to steal your details. This security fix has, however, caused a change that affects how web analytics software can report the number of referrals your website receives.
The security fix applies the attribute rel="noreferrer noopener" to all external links from a WordPress website. The "noreferrer" attribute advises web browsers to hide the originating website URL from the destination website (i.e. when you click on a link on a WordPress website the site you visit will not know that you came from the originating source). Web analytics software vendors rely on this field to provide referral website data, and without it will not be able to provide data on these referring visitors. Instead, it will track all of these visits as "Direct".
[caption id="attachment_2255" align="aligncenter" width="304"] The noreferrer attribute moves your referral traffic to direct.[/caption]
This has no effect on SEO
This attribute, although similar to "nofollow", is completely separate and will not impact your websites' SEO efforts. Backlinks from websites that contain the "noreferrer noopener" attribute will continue to provide their full SEO value.
Unfortunately, there is very little that can be done to avoid losing this data, in a similar way to the (not provided) change to organic keywords a few years ago. Without a change from WordPress, and/or TinyMCE, that reverses this change, the data will be lost moving forward and any website that uses WordPress will not show up in your referral logs - even if they do send significant numbers of visitors to your website. We suggest you keep this in mind when reviewing your data, it may not be showing you the whole truth.
Auditing your Google Analytics account for query parameters can be tedious but helps keep page reports clear of unwanted row duplication. We talk about the effects of collecting unwanted queries on your reporting and how to fix it. We’ve also built a free tool to make the process easier.
When a form has been successfully submitted to HubSpot, HubSpot propagates an event that we can listen to and use to trigger marketing tags within Google Tag Manager. Below we create a Custom HTML Tag that listens for a form success, trigger a dataLayer event which can then be used to trigger a marketing tag to push this data into Google Analytics.
Service Provider and Network Domain dimensions are no more. Let’s get Service Provider data back online. We’ll show you how to re-enable ISP data using Google Tag Manager and an IP Lookup Service.
Track when users leave your site to visit your social media pages. Understand when your content is driving positive move to your social assets.
The use of social sharing widgets is commonplace. But who’s actually tracking interactions with these? Let’s make a count of how many people are clicking these buttons and record a social share rate to see how many readers amplify content on social media.
Anybody who uses DoubleClick Floodlight knows the slow process of implementing a new tag for each activity for a campaign interaction or conversion. If you’re using Google Tag Manager to add a tag, trigger and maybe some new variables for every new Floodlight – it won’t take long for your container to overfill with almost identical tags. While there’s nothing wrong with this style of implementation, there is another way.