Connect with us

MARKETING

Case Study: How the Cookie Monster Ate 22% of Our Visibility

Published

on

You Can Go Your Own Way: How to Get Things Done When You’re the Only SEO

The author’s views are entirely his or her own (excluding the unlikely event of hypnosis) and may not always reflect the views of Moz.

Last year, the team at Homeday — one of the leading property tech companies in Germany — made the decision to migrate to a new content management system (CMS). The goals of the migration were, among other things, increased page speed and creating a state-of-the-art, future-proof website with all the necessary features. One of the main motivators for the migration was to enable content editors to work more freely in creating pages without the help of developers. 

After evaluating several CMS options, we decided on Contentful for its modern technology stack, with a superior experience for both editors and developers. From a technical viewpoint, Contentful, as a headless CMS, allows us to choose which rendering strategy we want to use. 

We’re currently carrying out the migration in several stages, or waves, to reduce the risk of problems that have a large-scale negative impact. During the first wave, we encountered an issue with our cookie consent, which led to a visibility loss of almost 22% within five days. In this article I’ll describe the problems we were facing during this first migration wave and how we resolved them.

Setting up the first test-wave 

For the first test-wave we chose 10 SEO pages with high traffic but low conversion rates. We established an infrastructure for reporting and monitoring those 10 pages: 

Advertisement
  • Rank-tracking for most relevant keywords 

  • SEO dashboard (DataStudio, Moz Pro,  SEMRush, Search Console, Google Analytics)

  • Regular crawls 

After a comprehensive planning and testing phase, we migrated the first 10 SEO pages to the new CMS in December 2021. Although several challenges occurred during the testing phase (increased loading times, bigger HTML Document Object Model, etc.) we decided to go live as we didn’t see big blocker and we wanted to migrate the first testwave before christmas. 

First performance review

Very excited about achieving the first step of the migration, we took a look at the performance of the migrated pages on the next day. 

What we saw next really didn’t please us. 

Overnight, the visibility of tracked keywords for the migrated pages reduced from 62.35% to 53.59% — we lost 8.76% of visibility in one day

As a result of this steep drop in rankings, we conducted another extensive round of testing. Among other things we tested for coverage/ indexing issues, if all meta tags were included, structured data, internal links, page speed and mobile friendliness.

Second performance review

All the articles had a cache date after the migration and the content was fully indexed and being read by Google. Moreover, we could exclude several migration risk factors (change of URLs, content, meta tags, layout, etc.) as sources of error, as there hasn’t been any changes.

Advertisement

Visibility of our tracked keywords suffered another drop to 40.60% over the next few days, making it a total drop of almost 22% within five days. This was also clearly shown in comparison to the competition of the tracked keywords (here “estimated traffic”), but the visibility looked analogous. 

As other migration risk factors plus Google updates had been excluded as sources of errors, it definitely had to be a technical issue. Too much JavaScript, low Core Web Vitals scores, or a larger, more complex Document Object Model (DOM) could all be potential causes. The DOM represents a page as objects and nodes so that programming languages like JavaScript can interact with the page and change for example style, structure and content.

Following the cookie crumbs

We had to identify issues as quickly as possible and do quick bug-fixing and minimize more negative effects and traffic drops. We finally got the first real hint of which technical reason could be the cause when one of our tools showed us that the number of pages with high external linking, as well as the number of pages with maximum content size, went up. It is important that pages don’t exceed the maximum content size as pages with a very large amount of body content may not be fully indexed. Regarding the high external linking it is important that all external links are trustworthy and relevant for users. It was suspicious that the number of external links went up just like this.

Increase of URLs with high external linking (more than 10)
Increase of URLs which exceed the specified maximum content size (51.200 bytes)

Both metrics were disproportionately high compared to the number of pages we migrated. But why?

After checking which external links had been added to the migrated pages, we saw that Google was reading and indexing the cookie consent form for all migrated pages. We performed a site search, checking for the content of the cookie consent, and saw our theory confirmed: 

A site search confirmed that the cookie consent was indexed by Google

This led to several problems: 

  1. There was tons of duplicated content created for each page due to indexing the cookie consent form. 

  2. The content size of the migrated pages drastically increased. This is a problem as pages with a very large amount of body content may not be fully indexed. 

  3. The number of external outgoing links drastically increased. 

  4. Our snippets suddenly showed a date on the SERPs. This would suggest a blog or news article, while most articles on Homeday are evergreen content. In addition, due to the date appearing, the meta description was cut off. 

But why was this happening? According to our service provider, Cookiebot, search engine crawlers access websites simulating a full consent. Hence, they gain access to all content and copy from the cookie consent banners are not indexed by the crawler. 

So why wasn’t this the case for the migrated pages? We crawled and rendered the pages with different user agents, but still couldn’t find a trace of the Cookiebot in the source code. 

Advertisement

Investigating Google DOMs and searching for a solution

The migrated pages are rendered with dynamic data that comes from Contentful and plugins. The plugins contain just JavaScript code, and sometimes they come from a partner. One of these plugins was the cookie manager partner, which fetches the cookie consent HTML from outside our code base. That is why we didn’t find a trace of the cookie consent HTML code in the HTML source files in the first place. We did see a larger DOM but traced that back to Nuxt’s default, more complex, larger DOM. Nuxt is a JavaScript framework that we work with.

To validate that Google was reading the copy from the cookie consent banner, we used the URL inspection tool of Google Search Console. We compared the DOM of a migrated page with the DOM of a non-migrated page. Within the DOM of a migrated page, we finally found the cookie consent content:

Within the DOM of a migrated page we found the cookie consent content

Something else that got our attention were the JavaScript files loaded on our old pages versus the files loaded on our migrated pages. Our website has two scripts for the cookie consent banner, provided by a 3rd party: one to show the banner and grab the consent (uc) and one that imports the banner content (cd).

  • The only script loaded on our old pages was uc.js, which is responsible for the cookie consent banner. It is the one script we need in every page to handle user consent. It displays the cookie consent banner without indexing the content and saves the user’s decision (if they agree or disagree to the usage of cookies).

  • For the migrated pages, aside from uc.js, there was also a cd.js file loading. If we have a page, where we want to show more information about our cookies to the user and index the cookie data, then we have to use the cd.js. We thought that both files are dependent on each other, which is not correct. The uc.js can run alone. The cd.js file was the reason why the content of the cookie banner got rendered and indexed.

It took a while to find it because we thought the second file was just a pre-requirement for the first one. We determined that simply removing the loaded cd.js file would be the solution.

Performance review after implementing the solution

The day we deleted the file, our keyword visibility was at 41.70%, which was still 21% lower than pre-migration. 

However, the day after deleting the file, our visibility increased to 50.77%, and the next day it was almost back to normal at 60.11%. The estimated traffic behaved similarly. What a relief! 

Quickly after implementing the solution, the organic traffic went back to pre-migration levels

Conclusion

I can imagine that many SEOs have dealt with tiny issues like this. It seems trivial, but led to a significant drop in visibility and traffic during the migration. This is why I suggest migrating in waves and blocking enough time for investigating technical errors before and after the migration. Moreover, keeping a close look at the site’s performance within the weeks after the migration is crucial. These are definitely my key takeaways from this migration wave. We just completed the second migration wave in the beginning of May 2022 and I can state that so far no major bugs appeared. We’ll have two more waves and complete the migration hopefully successfully by the end of June 2022.

The performance of the migrated pages is almost back to normal now, and we will continue with the next wave. 

Advertisement

Source link

Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address

MARKETING

Trends in Content Localization – Moz

Published

on

Trends in Content Localization - Moz

Multinational fast food chains are one of the best-known examples of recognizing that product menus may sometimes have to change significantly to serve distinct audiences. The above video is just a short run-through of the same business selling smokehouse burgers, kofta, paneer, and rice bowls in an effort to appeal to people in a variety of places. I can’t personally judge the validity of these representations, but what I can see is that, in such cases, you don’t merely localize your content but the products on which your content is founded.

Sometimes, even the branding of businesses is different around the world; what we call Burger King in America is Hungry Jack’s in Australia, Lays potato chips here are Sabritas in Mexico, and DiGiorno frozen pizza is familiar in the US, but Canada knows it as Delissio.

Tales of product tailoring failures often become famous, likely because some of them may seem humorous from a distance, but cultural sensitivity should always be taken seriously. If a brand you are marketing is on its way to becoming a large global seller, the best insurance against reputation damage and revenue loss as a result of cultural insensitivity is to employ regional and cultural experts whose first-hand and lived experiences can steward the organization in acting with awareness and respect.

Source link

Advertisement
Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address
Continue Reading

MARKETING

How AI Is Redefining Startup GTM Strategy

Published

on

How AI Is Redefining Startup GTM Strategy

AI and startups? It just makes sense.

(more…)

Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address
Continue Reading

MARKETING

More promotions and more layoffs

Published

on

More promotions and more layoffs

For martech professionals salaries are good and promotions are coming faster, unfortunately, layoffs are coming faster, too. That’s according to the just-released 2024 Martech Salary and Career Survey. Another very unfortunate finding: The median salary of women below the C-suite level is 35% less than what men earn.

The last year saw many different economic trends, some at odds with each other. Although unemployment remained very low overall and the economy grew, some businesses — especially those in technology and media — cut both jobs and spending. Reasons cited for the cuts include during the early years of the pandemic, higher interest rates and corporate greed.

Dig deeper: How to overcome marketing budget cuts and hiring freezes

Be that as it may, for the employed it remains a good time to be a martech professional. Salaries remain lucrative compared to many other professions, with an overall median salary of $128,643. 

Advertisement

Here are the median salaries by role:

  • Senior management $199,653
  • Director $157,776
  • Manager $99,510
  • Staff $89,126

Senior managers make more than twice what staff make. Directors and up had a $163,395 median salary compared to manager/staff roles, where the median was $94,818.

One-third of those surveyed said they were promoted in the last 12 months, a finding that was nearly equal among director+ (32%) and managers and staff (30%). 

PX3zocqNZfzMbWNEZhW9dZnAgkdPrLW8fjkrbVrcEkrNJpJiXrVKkjlQ0Tzuj8YKh Ht9HTEvmxDDt0ZsntfYiZHS0NJ7zEZ 6yMT3OjZajbaXBFV1D2Pk5euJeHKdRuzOzM5ZUxwNtsVNaiIbNrd Q

Extend the time frame to two years, and nearly three-quarters of director+ respondents say they received a promotion, while the same can be said for two-thirds of manager and staff respondents.

Dig deeper: Skills-based hiring for modern marketing teams

Employee turnover 

In 2023, we asked survey respondents if they noticed an increase in employee churn and whether they would classify that churn as a “moderate” or “significant” increase. For 2024, given the attention on cost reductions and layoffs, we asked if the churn they witnessed was “voluntary” (e.g., people leaving for another role) or “involuntary” (e.g., a layoff or dismissal). More than half of the marketing technology professionals said churn increased in the last year. Nearly one-third classified most of the churn as “involuntary.”

FIHUBtZJfK3IzbyZl C6WXBPTE64Gzg1URDzQUXCrD8YkAPZS7mmjpmAAiuhhheJUE4dGVcn6e9XW87ogLVz0Ya4rqHwB8WfXTHS W0hRW7yEdr2bQNjlTwnXvNhMv9NZ092pq1ws7lu DYqLV8i6fcFIHUBtZJfK3IzbyZl C6WXBPTE64Gzg1URDzQUXCrD8YkAPZS7mmjpmAAiuhhheJUE4dGVcn6e9XW87ogLVz0Ya4rqHwB8WfXTHS W0hRW7yEdr2bQNjlTwnXvNhMv9NZ092pq1ws7lu DYqLV8i6fc

Men and Women

Screenshot 2024 03 21 124540Screenshot 2024 03 21 124540

This year, instead of using average salary figures, we used the median figures to lessen the impact of outliers in the salary data. As a result, the gap between salaries for men and women is even more glaring than it was previously.

In last year’s report, men earned an average of 24% more than women. This year the median salary of men is 35% more than the median salary of women. That is until you get to the upper echelons. Women at director and up earned 5% more than men.

Methodology

The 2024 MarTech Salary and Career Survey is a joint project of MarTech.org and chiefmartec.com. We surveyed 305 marketers between December 2023 and February 2024; 297 of those provided salary information. Nearly 63% (191) of respondents live in North America; 16% (50) live in Western Europe. The conclusions in this report are limited to responses from those individuals only. Other regions were excluded due to the limited number of respondents. 

Advertisement

Download your copy of the 2024 MarTech Salary and Career Survey here. No registration is required.

Get MarTech! Daily. Free. In your inbox.

Source link

Advertisement
Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address
Continue Reading

Trending

Follow by Email
RSS