Tag Archive | "work"

One of these sessions is not like the other. Google Analytics data is used to support tons of important work, ranging from our everyday marketing reporting all the way to investment decisions. To that end, it’s integral that we’re aware of just how that data works.

In this week’s edition of Whiteboard Friday, we welcome Tom Capper to explain how the sessions metric in Google Analytics works, several ways that it can have unexpected results, and as a bonus, how sessions affect the time on page metric (and why you should rethink using time on page for reporting).

Click on the whiteboard image above to open a high-resolution version in a new tab!

Video Transcription

Hello, Moz fans, and welcome to another edition of Whiteboard Friday. I am Tom Capper. I am a consultant at Distilled, and today I’m going to be talking to you about how sessions work in Google Analytics. Obviously, all of us use Google Analytics. Pretty much all of us use Google Analytics in our day-to-day work.

Data from the platform is used these days in everything from investment decisions to press reporting to the actual marketing that we use it for. So it’s important to understand the basic building blocks of these platforms. Up here I’ve got the absolute basics. So in the blue squares I’ve got hits being sent to Google Analytics.

So when you first put Google Analytics on your site, you get that bit of tracking code, you put it on every page, and what that means is when someone loads the page, it sends a page view. So those are the ones I’ve marked P. So we’ve got page view and page view and so on as you’re going around the site. I’ve also got events with an E and transactions with a T. Those are two other hit types that you might have added.

The job of Google Analytics is to take all this hit data that you’re sending it and try and bring it together into something that actually makes sense as sessions. So they’re grouped into sessions that I’ve put in black, and then if you have multiple sessions from the same browser, then that would be a user that I’ve marked in pink. The issue here is it’s kind of arbitrary how you divide these up.

These eight hits could be one long session. They could be eight tiny ones or anything in between. So I want to talk today about the different ways that Google Analytics will actually split up those hit types into sessions. So over here I’ve got some examples I’m going to go through. But first I’m going to go through a real-world example of a brick-and-mortar store, because I think that’s what they’re trying to emulate, and it kind of makes more sense with that context.

Brick-and-mortar example

So in this example, say a supermarket, we enter by a passing trade. That’s going to be our source. Then we’ve got an entrance is in the lobby of the supermarket when we walk in. We got passed from there to the beer aisle to the cashier, or at least I do. So that’s one big, long session with the source passing trade. That makes sense.

In the case of a brick-and-mortar store, it’s not to difficult to divide that up and try and decide how many sessions are going on here. There’s not really any ambiguity. In the case of websites, when you have people leaving their keyboard for a while or leaving the computer on while they go on holiday or just having the same computer over a period of time, it becomes harder to divide things up, because you don’t know when people are actually coming and going.

So what they’ve tried to do is in the very basic case something quite similar: arrive by Google, category page, product page, checkout. Great. We’ve got one long session, and the source is Google. Okay, so what are the different ways that that might go wrong or that that might get divided up?

Several things that can change the meaning of a session

1. Time zone

The first and possibly most annoying one, although it doesn’t tend to be a huge issue for some sites, is whatever time zone you’ve set in your Google Analytics settings, the midnight in that time zone can break up a session. So say we’ve got midnight here. This is 12:00 at night, and we happen to be browsing. We’re doing some shopping quite late.

Because Google Analytics won’t allow a session to have two dates, this is going to be one session with the source Google, and this is going to be one session and the source will be this page. So this is a self-referral unless you’ve chosen to exclude that in your settings. So not necessarily hugely helpful.

2. Half-hour cutoff for “coffee breaks”

Another thing that can happen is you might go and make a cup of coffee. So ideally if you went and had a cup of coffee while in you’re in Tesco or a supermarket that’s popular in whatever country you’re from, you might want to consider that one long session. Google has made the executive decision that we’re actually going to have a cutoff of half an hour by default.

If you leave for half an hour, then again you’ve got two sessions. One, the category page is the landing page and the source of Google, and one in this case where the blog is the landing page, and this would be another self-referral, because when you come back after your coffee break, you’re going to click through from here to here. This time period, the 30 minutes, that is actually adjustable in your settings, but most people do just leave it as it is, and there isn’t really an obvious number that would make this always correct either. It’s kind of, like I said earlier, an arbitrary distinction.

3. Leaving the site and coming back

The next issue I want to talk about is if you leave the site and come back. So obviously it makes sense that if you enter the site from Google, browse for a bit, and then enter again from Bing, you might want to count that as two different sessions with two different sources. However, where this gets a little murky is with things like external payment providers.

If you had to click through from the category page to PayPal to the checkout, then unless PayPal is excluded from your referral list, then this would be one session, entrance from Google, one session, entrance from checkout. The last issue I want to talk about is not necessarily a way that sessions are divided, but a quirk of how they are.

4. Return direct sessions

If you were to enter by Google to the category page, go on holiday and then use a bookmark or something or just type in the URL to come back, then obviously this is going to be two different sessions. You would hope that it would be one session from Google and one session from direct. That would make sense, right?

But instead, what actually happens is that, because Google and most Google Analytics and most of its reports uses last non-direct click, we pass through that source all the way over here, so you’ve got two sessions from Google. Again, you can change this timeout period. So that’s some ways that sessions work that you might not expect.

As a bonus, I want to give you some extra information about how this affects a certain metric, mainly because I want to persuade you to stop using it, and that metric is time on page.

Bonus: Three scenarios where this affects time on page

So I’ve got three different scenarios here that I want to talk you through, and we’ll see how the time on page metric works out.

I want you to bear in mind that, basically, because Google Analytics really has very little data to work with typically, they only know that you’ve landed on a page, and that sent a page view and then potentially nothing else. If you were to have a single page visit to a site, or a bounce in other words, then they don’t know whether you were on that page for 10 seconds or the rest of your life.

They’ve got no further data to work with. So what they do is they say, “Okay, we’re not going to include that in our average time on page metrics.” So we’ve got the formula of time divided by views minus exits. However, this fudge has some really unfortunate consequences. So let’s talk through these scenarios.

Example 1: Intuitive time on page = actual time on page

In the first scenario, I arrive on the page. It sends a page view. Great. Ten seconds later I trigger some kind of event that the site has added. Twenty seconds later I click through to the next page on the site. In this case, everything is working as intended in a sense, because there’s a next page on the site, so Google Analytics has that extra data of another page view 20 seconds after the first one. So they know that I was on here for 20 seconds.

In this case, the intuitive time on page is 20 seconds, and the actual time on page is also 20 seconds. Great.

Example 2: Intuitive time on page is higher than measured time on page

However, let’s think about this next example. We’ve got a page view, event 10 seconds later, except this time instead of clicking somewhere else on the site, I’m going to just leave altogether. So there’s no data available, but Google Analytics knows we’re here for 10 seconds.

So the intuitive time on page here is still 20 seconds. That’s how long I actually spent looking at the page. But the measured time or the reported time is going to be 10 seconds.

Example 3: Measured time on page is zero

The last example, I browse for 20 seconds. I leave. I haven’t triggered an event. So we’ve got an intuitive time on page of 20 seconds and an actual time on page or a measured time on page of 0.

The interesting bit is when we then come to calculate the average time on page for this page that appeared here, here, and here, you would initially hope it would be 20 seconds, because that’s how long we actually spent. But your next guess, when you look at the reported or the available data that Google Analytics has in terms of how long we’re on these pages, the average of these three numbers would be 10 seconds.

So that would make some sense. What they actually do, because of this formula, is they end up with 30 seconds. So you’ve got the total time here, which is 30, divided by the number of views, we’ve got 3 views, minus 2 exits. Thirty divided 3 minus 2, 30 divided by 1, so we’ve got 30 seconds as the average across these 3 sessions.

Well, the average across these three page views, sorry, for the amount of time we’re spending, and that is longer than any of them, and it doesn’t make any sense with the constituent data. So that’s just one final tip to please not use average time on page as a reporting metric.

I hope that’s all been useful to you. I’d love to hear what you think in the comments below. Thanks.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

Phishing emails are just plain thievery. While phishing emails don’t ultimately deliver value, they do communicate value. Not to everyone, but to a specific audience. And that is why some people act on them.MarketingSherpa Blog

If you’ve spent any time in marketing discussion groups, you’ve probably heard how difficult it can be to get Facebook to approve your ads … depending on which industry you’re in. You may have thought: “Zuckerberg sure seems like a tyrant who hates marketers.” But when you look at ads from Facebook’s point of view, Read More…

Tell me if this rings a bell. Are your search recommendations overlooked and misunderstood? Do you feel like you hit roadblocks at every turn? Are you worried that people don’t understand the value of your work?

I had an eye-opening moment when my colleague David Mitchell, Chief Technology Officer at VML, said to me, “You know the best creatives here aren’t the ones who are the best artists — they’re the ones who are best at talking about the work.”

I have found that the same holds true in search. As an industry, we are great at talking about the work — we’re fabulous about sharing technical knowledge and new developments in search. But we’re not so great at talking about how we talk about the work. And that can make all the difference between our work getting implementing and achieving great results, or languishing in a backlog.

It’s so important to learn how to navigate corporate bureaucracy and cut through red tape to help your clients and colleagues understand your search work — and actually get it implemented. From diagnosing client maturity to communicating where search fits into the big picture, the tools I share in this article can help equip you to overcome obstacles to doing your best work.

Buying Your Services ≠ Buying In

Just because a client signed a contract with you does not mean they are bought-in to implement every change you recommend. It seemingly defies all logic that someone would agree that they need organic search help enough to sign a contract and pay you to make recommendations, only for the recommendations to never go live.

When I was an independent contractor serving small businesses, they were often overwhelmed by their marketing and willing to hand over the keys to the website so my developers could implement SEO recommendations.

Then, as I got into agency life and worked on larger and larger businesses, I quickly realized it was a lot harder to get SEO work implemented. I started hitting roadblocks with a number of clients, and it was a slow, arduous process to get even small projects pushed through. It was easy to get impatient and fed up.

Worse, it was hard for some of my team members to see their colleagues getting great search work implemented and earning awesome results for their clients, while their own clients couldn’t seem to get anything implemented. It left them frustrated, jaded, feeling inadequate, and burned out — all the while the client was asking where the results were for the projects they didn’t implement.

What Stands in the Way of Getting Your Work Implemented

I surveyed colleagues in our industry about the common challenges they experience when trying to get their recommendations implemented. (Thank you to the 141 people who submitted!) The results were roughly one-third in-house marketers and two-thirds external marketers providing services to clients.

The most common obstacles we asked about fell into a few main categories:

Low Understanding of Search

Client Understanding

Peer/Colleague Understanding

Boss Understanding

Prioritization & Buy-In

Low Prioritization of Search Work

External Buy-In from Clients

Internal Buy-In from Peers

Internal Buy-In from Bosses

Past Unsuccessful Projects or Mistakes

Corporate Bureaucracy

Red Tape and Slow Approvals

No Advocate or Champion for Search

Turnover or Personnel Changes (Client-Side)

Difficult or Hostile Client

Resource Limitations

Technical Resources for Developers / Full Backlog

Budget / Scope Too Low to Make Impact

Technical Limitations of Digital Platform

The chart below shows how the obstacles in the survey stacked up. Higher scores mean people reported it as a more frequent or common problem they experience:

Some participants also wrote in additional blocks they’ve encountered – everything from bottlenecks in the workflow to over-complicated processes, lack of ownership to internal politics, shifting budgets to shifting priorities.

Too real? Are you completely bummed out yet? There is clearly no shortage of things that can stand in the way of SEO progress, and likely our work as marketers will never be without challenges.

Playing the Blame Game

When things don’t go our way and our work gets intercepted or lost before it ever goes live, we tend to be quick to blame clients. It’s the client’s fault things are hung up, or if the client had only listened to us, and the client’s business is the problem.

But I don’t buy it.

Don’t get me wrong — this could possibly be true in part in some cases, but rarely is it the whole story and rarely are we completely hopeless to affect change. Sometimes the problem is the system, sometimes the problem is the people, and my friends, sometimes the problem is you.

But fortunately, we are all optimizers — we all inherently believe that things could be just a little bit better.

These are the tools you need in your belt to face many of the common obstacles to implementing your best search work.

7 Techniques to Get Your Search Work Approved & Implemented

When we enter the world of search, we are instantly trained on how to execute the work – not the soft skills needed to sustain and grow the work, break down barriers, get buy-in and get stuff implemented. These soft skills are critical to maximize your search success for clients, and can lead to more fruitful, long-lasting relationships.

Below are seven of the most highly recommended skills and techniques, from the SEO professionals surveyed and my own experience, to learn in order to increase the likelihood your work will get implemented by your clients.

1. How Mature Is Your Client?

Challenges to implementation tend to be organizational, people, integration, and process problems. Conducting a search maturity assessment with your client can be eye-opening to what needs to be solved internally before great search work can be implemented. Pairing a search capabilities model with an organizational maturity model gives you a wealth of knowledge and tools to help your client.

For search, we can think about a maturity model two ways. One may be the actual technical implementation of search best practices — is the client implementing exceptional, advanced SEO, just the basics, nothing at all, or even operating counterproductively? This helps identify what kinds of project make sense to start with for your client. Here is a sample maturity model across several aspects of search that you can use or modify for your purposes:

This SEO capabilities maturity model only starts to solve for what you should implement, but doesn’t get to the heart of why it’s so hard to get your work implemented. The real problems are a lot more nuanced, and aren’t as easy as checking the boxes of “best practices SEO.”

We also need to diagnose the organizational maturity of the client as it pertains to building, using and evolving an organic search practice. We have to understand the assets and obstacles of our client’s organization that either aid or block the implementation of our recommendations in order to move the ball forward.

If, after conducting these maturity model exercises, we find that a client has extremely limited personnel, budget and capacity to complete the work, that’s the first problem we should focus on solving for — helping them allocate proper resources and prioritization to the work.

If we find that they have plenty of personnel, budget, and capacity, but have no discernible, repeatable process for integrating search into their marketing mix, we focus our efforts there. How can we help them define, implement, and continually evolve processes that work for them and with the agency?

Perhaps the maturity assessment finds that they are adequate in most categories, but struggle with being reactive and implementing retrofitted SEO only as an afterthought, we may help them investigate their actionable workflows and connect dots across departments. How can we insert organic search expertise in the right ways at the right moments to have the greatest impact?

2. Speak to CEOs and CMOs, Not SEOs

Because we are subject matter experts in search, we are responsible for educating clients and colleagues on the power of SEO and the impact it can have on brands. If the executives are skeptical or don’t care about search, it won’t happen. If you want to educate and inspire people, you can’t waste time losing them in the details.

Speak Their Language

Tailor your educational content to busy CEOs and CMOs, not SEOs. Make the effort to listen to, read, write, and speak their corporate language. Their jargon is return on investment, earnings per share, operational costs. Yours is canonicalization, HTTPS and SSL encryption, 302 redirects, and 301 redirect chains.

Be mindful that you are coming from different places and meet them in the middle. Use layperson’s terms that anyone can understand, not technical jargon, when explaining search.

Don’t be afraid to use analogies (i.e. instead of “implement permanent 301 redirect rewrite rules in the .htaccess file to correct 404 not found errors,” perhaps “it’s like forwarding your mail when you change addresses.”)

Get Out of the Weeds

Perhaps because we are so passionate about the inner workings of search, we often get deep into the weeds of explaining how every SEO signal works. Even things that seem not-so-technical to us (title tags and meta description tags, for example) can lose your audience’s attention in a heartbeat. Unless you know that the client is a technical mind who loves to get in the weeds or that they have search experience, stay at 30,000 feet.

Another powerful tool here is to show, not tell. Often you can tell a much more effective and hard-hitting story using images or smart data visualization. Your audience being able to see instead of trying to listen and decipher what you’re proposing can allow you to communicate complex information much more succinctly.

Focus on Outcomes

The goal of educating is not teaching peers and clients how to do search. They pay you to know that. Focus on the things that actually matter to your audience. (Come on, we’re inbound marketers — we should know this!) For many brands, that may include benefits like how it will build their brand visibility, how they can conquest competitors, and how they can make more money. Focus on the outcomes and benefits, not the granular, technical steps of how to get there.

What’s In It for Them?

Similarly, if you are doing a roadshow to educate your peers in other disciplines and get their buy-in, don’t focus on teaching them everything you know. Focus on how your work can benefit them (make their work smarter, more visible, make them more money) rather than demanding what other departments need to do for you. Aim to align on when, where, and how your two teams intersect to get greater results together.

3. SEO is Not the Center of the Universe

It was a tough pill for me to swallow when I realized that my clients simply didn’t care as much about organic search as my team and I did. (I mean, honestly, who isn’t passionate about dedicating their careers to understanding human thinking and behavior when we search, then optimizing technical stuff and website content for those humans to find it?!)

Bigger Fish to Fry

While clients may honestly love the sound of things we can do for them with search, rarely is SEO the only thing — or even a sizable thing — on a client’s mind. Rarely is our primary client contact someone who is exclusively dedicated to search, and typically, not even exclusively to digital marketing. We frequently report to digital directors and CMOs who have many more and much bigger fish to fry.

They have to look at the big picture and understand how the entire marketing mix works, and in reality, SEO is only one small part of that. While organic search is typically a client’s biggest source of traffic to their website, we often forget that the website isn’t even at the top of the priorities list for many clients. Our clients are thinking about the whole brand and the entirety of its marketing performance, or the organizational challenges they need to overcome to grow their business. SEO is just one small piece of that.

Acknowledge the Opportunity Cost

The benefits of search are no-brainers for us and it seems so obvious, but we fail to acknowledge that every decision a CMO makes has a risk, time commitment, risks and costs associated with it. Every time they invest in something for search, it is an opportunity cost for another marketing initiative. We fail to take the time to understand all the competing priorities and things that a client has to choose between with a limited budget.

To persuade them to choose an organic search project over something else — like a paid search, creative, paid media, email, or other play — we had better make a damn good case to justify not just the hard cost in dollars, but the opportunity cost to other marketing initiatives. (More on that later.)

Integrated Marketing Efforts

More and more, brands are moving to integrated agency models in hopes of getting more bang for their buck by maximizing the impact of every single campaign across channels working together, side-by-side. Until we start to think more about how SEO ladders up to the big picture and works alongside or supports larger marketing initiatives and brand goals, we will continue to hamstring ourselves when we propose ideas to clients.

It’s our responsibility to seek big-picture perspective and figure out where we fit. We have to understand the realities of a client’s internal and external processes, their larger marketing mix and SEO’s role in that. SEO experts tend to obsess over rankings and website traffic. But we should be making organic search recommendations within the context of their goals and priorities — not what we think their goals and priorities should be.

For example, we have worked on a large CPG food brand for several years. In year one, my colleagues did great discovery works and put together an awesome SEO playbook, and we spent most of the year trying to get integrated and trying to check all these SEO best practices boxes for the client. But no one cared and nothing was getting implemented. It turned out that our “SEO best practices” didn’t seem relevant to the bigger picture initiatives and brand campaigns they had planned for the year, so they were being deprioritized or ignored entirely. In year two, our contract was restructured to focus search efforts primarily on the planned campaigns for the year. Were we doing the search work we thought we would be doing for the client? No. Are we being included more and getting great search work implemented finally? Yes. Because we stopped trying to veer off in our own direction and started pulling the weight alongside everyone else toward a common vision.

4. Don’t Stay in Your Lane, Get Buy-In Across Lanes

Few brands hire only SEO experts and no other marketing services to drive their business. They have to coordinate a lot of moving pieces to drive all of them forward in the same direction as best they can. In order to do that, everyone has to be aligned on where we’re headed and the problems we’re solving for.

Ultimately, for most SEOs, this is about having the wisdom and humility to realize that you’re not in this alone – you can’t be. And even if you don’t get your way 100% of the time, you’re a lot more likely to get your way more of the time when you collaborate with others and ladder your efforts up to the big picture.

One of my survey respondents phrased it beautifully: “Treat all search projects as products that require a complete product team including engineering, project manager, and business-side folks.”

Horizontal Buy-In

You need buy-in across practices in your own agency (or combination of agencies serving the client and internal client team members helping execute the work). We have to stop swimming in entirely separate lanes where SEO is setting goals by themselves and not aligning to the larger business initiatives and marketing channels. We are all in this together to help the client solve for something. We have to learn to better communicate the value of search as it aligns to larger business initiatives, not in a separate swim lane.

Organic Search is uniquely dependent in that we often rely on others to get our work implemented. You can’t operate entirely separately from the analytics experts, developers, user experience designers, social media, paid search, and so on — especially when they’re all working together toward a common goal on behalf of the client.

Vertical Buy-In

To get buy-in for implementing your work, you need buy-in beyond your immediate client contact. You need buy-in top-to-bottom in the client’s organization — it has to support what the C-level executive cares about as much as your day-to-day contacts or their direct reports.

This can be especially helpful when you started within the agency — selling the value of the idea and getting the buy-in of your colleagues first. It forces you to vet and strengthen your idea, helps find blind spots, and craft the pitch for the client. Then, bring those important people to the table with the client — it gives you strength in numbers and expertise to have the developer, user experience designer, client engagement lead, and data analyst on the project in your corner validating the recommendation.

When you get to the client, it is so important to help them understand the benefits and outcomes of doing the project, the cost (and opportunity cost) of doing it, and how this can get them results toward their big picture goals. Understand their role in it and give them a voice, and make them the hero for approving it. If you have to pitch the idea at multiple levels, custom tailor your approach to speak to the client-side team members who will be helping you implement the work differently from how you would speak to the CMO who decides whether your project lives or dies.

5. Build a Bulletproof Plan

Here’s how a typical SEO project is proposed to a client: “You should do this SEO project because SEO.”

This explanation is not good enough, and they don’t care. You need to know what they do care about and are trying to accomplish, and formulate a bullet-proof business plan to sell the idea.

Case Studies as Proof-of-Concept

Case studies serve a few important purposes: they help explain the outcomes and benefits of SEO projects, they prove that you have the chops to get results, and they prove the concept using someone else’s money first, which reduces the perceived risk for your client.

In my experience and in the survey results, case studies come up time and again as the leading way to get client buy-in. Ideally you would use case studies that are your own, very clearly relevant to the project at hand, and created for a client that is similar in nature (like B2B vs. B2C, in a similar vertical, or facing a similar problem).

Even if you don’t have your own case studies to show, do your due diligence and find real examples other companies and practitioners have published. As an added bonus, the results of these case studies can help you forecast the potential high/medium/low impact of your work.

Simplify the Process for Everyone

It is important to bake the process into your business plan to clearly outline the requirements for the project, identify next steps and assign ownership, and take ownership of moving the ball forward. Do your due diligence up front to understand the role that everyone plays and boil it down into a clear step-by-step plan makes it feel easy for others to buy-in and help. Reducing the unknown reduces friction. When you assume that nothing you are capable of doing falls in the “not my job” description, and make it a breeze for everyone to know what they’re responsible for and where they fit in, you lower barriers and resistance.

Forecast the Potential ROI

SEOs are often incredibly hesitant to forecast potential outcomes, ROI, traffic or revenue impact because of the sheer volumes of unknowns. (“But what if the client actually expects us to achieve the forecast?!”) We naturally want to be accurate and right, so it’s understandable we wouldn’t want to commit to something we can’t say for certain we can accomplish.

But to say that forecasting is impossible is patently false. There is a wealth of information out there to help you come up with even conservative estimates of impact with lots of caveats. You need to know why you’re recommending this over other projects. Your clients need some sort of information to weigh one project against the next. A combination of forecasting and your marketer’s experience and intuition can help you define that.

For every project your client invests in, there is an opportunity cost for something else they could be working on. If you can’t articulate the potential benefit to doing the project, how can you expect your client to choose it above dozens of potential other things they could spend their time on?

Show the Impact of Inaction

Sometimes opportunity for growth isn’t enough to light the fire — also demonstrate the negative impact from inaction or incorrect action. The greatest risk I see with most clients is not making a wrong move, but rather making no move at all.

We developed a visual tool that helps us quickly explain to clients that active optimization and expansion can lead to growth (we forecast an estimate of impact based on their budget, their industry, their business goals, the initiatives we plan to prioritize, etc.), small maintenance could at least uphold what we’ve done but the site will likely stagnate, and to do nothing at all could lead to atrophy and decline as their competitors keep optimizing and surpass them.

Remind clients that search success is not only about what they do, it’s about what everyone else in their space is doing, too. If they are not actively monitoring, maintaining and expanding, they are essentially conceding territory to competitors who will fill the space in their absence.

You saw this in my deck at MozCon 2017. We have used it to help clients understand what’s next when we do annual planning with them.

Success Story: Selling AMP

One of my teammates believed that AMP was a key initiative that could have a big impact on one of his B2B automotive clients by making access to their location pages easier, faster, and more streamlined, especially in rural areas where mobile connections are slower and the client’s clients are often found.

He did a brilliant job of due diligence research, finding and dissecting case studies, and using the results of those case studies to forecast conservative, average and ambitious outcomes and calculated the estimated revenue impact for the client. He calculated that even at the most conservative estimate of ROI, it would far outweigh the cost of the project within weeks, and generate significant returns thereafter.

He got the buy-in of our internal developers and experience designers on how they would implement the work, simplified the AMP idea for the client to understand in a non-technical way, and framedin a way that made it clear how low the level of effort was. He was able to confidently propose the idea and get buy-in fast, and the work is now on track for implementation.

6. Headlines, Taglines, and Sound Bytes

You can increase the likelihood that your recommendations will get implemented if you can help the client focus on what’s really important. There are two key ways to accomplish this.

Ask for the Moon, Not the Galaxy

If you’re anything like me, you get a little excited when the to-do of SEO action items for a client is long and actionable. But we do ourselves a disservice when we try to push every recommendation at once – they get overwhelmed and tune out. They have nothing to grab onto, so nothing gets done. It seems counterintuitive that you will get more done by proposing less, but it works.

Prioritize what’s important for your client to care about right now. Don’t push every recommendation — push specific, high-impact recommendations that executives can latch on to, understand and rationalize.

They’re busy and making hard choices. Be their trusted advisor. Give them permission to focus on one thing at a time by communicating what they should care about while other projects stay on the backburner or happen in the background, because this high-impact project is what they should really care about right now.

Give Them Soundbites They Can Sell

It’s easy to forget that our immediate client contact is not always able to make the call to pull the trigger on a project by themselves. They often have to sell it internally to get it prioritized. To help them do this, give them catchy headlines, taglines and sound bites they can sell to their bosses and colleagues. Make them so memorable and repeatable, the clients will shop the ideas around their office clearly and confidently, and may even start to think they came up with the idea themselves.

Success Story: Prioritizing Content

As an example of both of these principles in practice, we have a global client we have worked with for a few years whose greatest chance of gaining ground in search is to improve and increase their website content. Before presenting the annual strategy to the client, we asked ourselves what we really wanted to accomplish with the client if they cut the meeting short or cut their budget for the year, and the answer was unequivocally content.

In our proposal deck, we built up to the big opportunity by reminding the client of the mission we all agreed on, highlighted some of the wins we got in 2017 (including a very sexy voice search win that made our client look like a hero at their office), set the stage with headlines like, “How We’re Going to Break Records in 2018,” then navigated to the section called, “The Big Opportunities.”

Then, we used the headline, “Web Content is the Single Most Important Priority” to kick off the first initiative. There was no mistaking in that room what our point was. We proposed two other initiatives for the year, but we put this one at the very top of the deck and all others fell after. Because this was our number one priority to get approved and implemented, we spent the lion’s share of the meeting focusing on this single point. We backed this slide up verbally and added emphasis by saying things like, “If we did nothing else recommended in this deck, this is the one thing to prioritize, hands down.”

This is the real slide from the real client deck we presented.

The client left that meeting crystal clear, fully understanding our recommendation, and bought in. The best part, though? When we heard different clients who were in the meeting starting to repeat things like, “Content is our number one priority this year.” unprompted on strategy and status calls.

7. Patience, Persistence, & Parallel Paths

Keep Several Irons in the Fire

Where possible, build parallel paths. What time-consuming but high-impact projects can you initiate with the client now that may take time to get approved, while you can concurrently work on lower obstacle tasks alongside? Having multiple irons in the fire increases the likelihood that you will be able to implement SEO recommendations and get measurable results that get people bought in to more work in the future.

Stay Strong

Finally, getting your work implemented is a balance of patience, persistence, communication and follow-up. There are always many things at play, and your empathy and understanding for the situation while bringing a confident point-of-view can ultimately get projects across the finish line.

Special thanks to my VML colleagues Chris, Jeff, Kasey, and Britt, whose real client examples were used in this article.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

If your work involves SEO at some level, you’ve most likely been hearing more and more about JavaScript and the implications it has on crawling and indexing. Frankly, Googlebot struggles with it, and many websites utilize modern-day JavaScript to load in crucial content today. Because of this, we need to be equipped to discuss this topic when it comes up in order to be effective.

The goal of this post is to equip you with the minimum viable knowledge required to do so. This post won’t go into the nitty gritty details, describe the history, or give you extreme detail on specifics. There are a lot of incredible write-ups that already do this — I suggest giving them a read if you are interested in diving deeper (I’ll link out to my favorites at the bottom).

In order to be effective consultants when it comes to the topic of JavaScript and SEO, we need to be able to answer three questions:

Does the domain/page in question rely on client-side JavaScript to load/change on-page content or links?

If yes, is Googlebot seeing the content that’s loaded in via JavaScript properly?

If not, what is the ideal solution?

With some quick searching, I was able to find three examples of landing pages that utilize JavaScript to load in crucial content.

I’m going to be using Sitecore’s Symposium landing page through each of these talking points to illustrate how to answer the questions above.

We’ll cover the “how do I do this” aspect first, and at the end I’ll expand on a few core concepts and link to further resources.

Question 1: Does the domain in question rely on client-side JavaScript to load/change on-page content or links?

The first step to diagnosing any issues involving JavaScript is to check if the domain uses it to load in crucial content that could impact SEO (on-page content or links). Ideally this will happen anytime you get a new client (during the initial technical audit), or whenever your client redesigns/launches new features of the site.

How do we go about doing this?

Ask the client

Ask, and you shall receive! Seriously though, one of the quickest/easiest things you can do as a consultant is contact your POC (or developers on the account) and ask them. After all, these are the people who work on the website day-in and day-out!

“Hi [client], we’re currently doing a technical sweep on the site. One thing we check is if any crucial content (links, on-page content) gets loaded in via JavaScript. We will do some manual testing, but an easy way to confirm this is to ask! Could you (or the team) answer the following, please?

1. Are we using client-side JavaScript to load in important content?

2. If yes, can we get a bulleted list of where/what content is loaded in via JavaScript?”

Check manually

Even on a large e-commerce website with millions of pages, there are usually only a handful of important page templates. In my experience, it should only take an hour max to check manually. I use the Chrome Web Developers plugin, disable JavaScript from there, and manually check the important templates of the site (homepage, category page, product page, blog post, etc.)

In the example above, once we turn off JavaScript and reload the page, we can see that we are looking at a blank page.

As you make progress, jot down notes about content that isn’t being loaded in, is being loaded in wrong, or any internal linking that isn’t working properly.

At the end of this step we should know if the domain in question relies on JavaScript to load/change on-page content or links. If the answer is yes, we should also know where this happens (homepage, category pages, specific modules, etc.)

Crawl

You could also crawl the site (with a tool like Screaming Frog or Sitebulb) with JavaScript rendering turned off, and then run the same crawl with JavaScript turned on, and compare the differences with internal links and on-page elements.

For example, it could be that when you crawl the site with JavaScript rendering turned off, the title tags don’t appear. In my mind this would trigger an action to crawl the site with JavaScript rendering turned on to see if the title tags do appear (as well as checking manually).

Example

For our example, I went ahead and did a manual check. As we can see from the screenshot below, when we disable JavaScript, the content does not load.

In other words, the answer to our first question for this pages is “yes, JavaScript is being used to load in crucial parts of the site.”

If your client is relying on JavaScript on certain parts of their website (in our example they are), it is our job to try and replicate how Google is actually seeing the page(s). We want to answer the question, “Is Google seeing the page/site the way we want it to?”

In order to get a more accurate depiction of what Googlebot is seeing, we need to attempt to mimic how it crawls the page.

How do we do that?

Use Google’s new mobile-friendly testing tool

At the moment, the quickest and most accurate way to try and replicate what Googlebot is seeing on a site is by using Google’s new mobile friendliness tool. My colleague Dom recently wrote an in-depth post comparing Search Console Fetch and Render, Googlebot, and the mobile friendliness tool. His findings were that most of the time, Googlebot and the mobile friendliness tool resulted in the same output.

In Google’s mobile friendliness tool, simply input your URL, hit “run test,” and then once the test is complete, click on “source code” on the right side of the window. You can take that code and search for any on-page content (title tags, canonicals, etc.) or links. If they appear here, Google is most likely seeing the content.

Search for visible content in Google

It’s always good to sense-check. Another quick way to check if GoogleBot has indexed content on your page is by simply selecting visible text on your page, and doing a site:search for it in Google with quotations around said text.

In our example there is visible text on the page that reads…

“Whether you are in marketing, business development, or IT, you feel a sense of urgency. Or maybe opportunity?”

When we do a site:search for this exact phrase, for this exact page, we get nothing. This means Google hasn’t indexed the content.

Crawling with a tool

Most crawling tools have the functionality to crawl JavaScript now. For example, in Screaming Frog you can head to configuration > spider > rendering > then select “JavaScript” from the dropdown and hit save. DeepCrawl and SiteBulb both have this feature as well.

From here you can input your domain/URL and see the rendered page/code once your tool of choice has completed the crawl.

Example:

When attempting to answer this question, my preference is to start by inputting the domain into Google’s mobile friendliness tool, copy the source code, and searching for important on-page elements (think title tag, <h1>, body copy, etc.) It’s also helpful to use a tool like diff checker to compare the rendered HTML with the original HTML (Screaming Frog also has a function where you can do this side by side).

For our example, here is what the output of the mobile friendliness tool shows us.

After a few searches, it becomes clear that important on-page elements are missing here.

We also did the second test and confirmed that Google hasn’t indexed the body content found on this page.

The implication at this point is that Googlebot is not seeing our content the way we want it to, which is a problem.

Now we know that the domain is using JavaScript to load in crucial content and we know that Googlebot is most likely not seeing that content, the final step is to recommend an ideal solution to the client. Key word: recommend, not implement. It’s 100% our job to flag the issue to our client, explain why it’s important (as well as the possible implications), and highlight an ideal solution. It is 100% not our job to try to do the developer’s job of figuring out an ideal solution with their unique stack/resources/etc.

How do we do that?

You want server-side rendering

The main reason why Google is having trouble seeing Sitecore’s landing page right now, is because Sitecore’s landing page is asking the user (us, Googlebot) to do the heavy work of loading the JavaScript on their page. In other words, they’re using client-side JavaScript.

Googlebot is literally landing on the page, trying to execute JavaScript as best as possible, and then needing to leave before it has a chance to see any content.

The fix here is to instead have Sitecore’s landing page load on their server. In other words, we want to take the heavy lifting off of Googlebot, and put it on Sitecore’s servers. This will ensure that when Googlebot comes to the page, it doesn’t have to do any heavy lifting and instead can crawl the rendered HTML.

In this scenario, Googlebot lands on the page and already sees the HTML (and all the content).

There are more specific options (like isomorphic setups)

This is where it gets to be a bit in the weeds, but there are hybrid solutions. The best one at the moment is called isomorphic.

In this model, we’re asking the client to load the first request on their server, and then any future requests are made client-side.

So Googlebot comes to the page, the client’s server has already executed the initial JavaScript needed for the page, sends the rendered HTML down to the browser, and anything after that is done on the client-side.

AJAX crawling = no go

I won’t go into details on this, but just know that Google’s previous AJAX crawling solution for JavaScript has since been discontinued and will eventually not work. We shouldn’t be recommending this method.

(However, I am interested to hear any case studies from anyone who has implemented this solution recently. How has Google responded? Also, here’s a great write-up on this from my colleague Rob.)

Summary

At the risk of severely oversimplifying, here’s what you need to do in order to start working with JavaScript and SEO in 2018:

I’m really interested to hear about any of your experiences with JavaScript and SEO. What are some examples of things that have worked well for you? What about things that haven’t worked so well? If you’ve implemented an isomorphic setup, I’m curious to hear how that’s impacted how Googlebot sees your site.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

Good to see you again! With the Monday Martin Luther King, Jr. holiday, this was a short week on Copyblogger. On Tuesday, Kelton Reid kicked things off with a thoughtful look at impostor syndrome — with clues on how to approach it from different sources, including the famous Turing Test. And on Wednesday, I talked Read More…

We’ve been hearing a lot about mobile-first indexing lately, as the latest development in Google’s ever-continuing efforts to make the web more mobile-friendly and reflect user behavior trends.

But there’s also a lot of confusion around what this means for the average business owner. Do you have to change anything? Everything? If your site is mobile-friendly, will that be good enough?

IS THIS GOING TO BE ANOTHER MOBILEGEDDON?!!

In this post I’ll go over the basics of what “mobile-first indexing” means, and what you may need to do about it. I’ll also answer some frequently asked questions about mobile-first indexing and what it means for our SEO efforts.

What is “mobile-first indexing”?

Mobile-first indexing is exactly what it sounds like. It just means that the mobile version of your website becomes the starting point for what Google includes in their index, and the baseline for how they determine rankings. If you monitor crawlbot traffic to your site, you may see an increase in traffic from Smartphone Googlebot, and the cached versions of pages will usually be the mobile version of the page.

It’s called “mobile-first” because it’s not a mobile-only index: for instance, if a site doesn’t have a mobile-friendly version, the desktop site can still be included in the index. But the lack of a mobile-friendly experience could impact negatively on the rankings of that site, and a site with a better mobile experience would potentially receive a rankings boost even for searchers on a desktop.

You may also want to think of the phrase “mobile-first” as a reference to the fact that the mobile version will be considered the primary version of your website. So if your mobile and desktop versions are equivalent — for instance if you’ve optimized your content for mobile, and/or if you use responsive design — this change should (in theory) not have any significant impact in terms of your site’s performance in search results.

However it does represent a fundamental reversal in the way Google is thinking about your website content and how to prioritize crawling and indexation. Remember that up until now the desktop site was considered the primary version (similar to a canonical URL) and the mobile site was treated as an “alternate” version for a particular use case. This is why Google encouraged webmasters with a separate mobile site (m.domain.com) to implement switchboard tags (which indicated the existence of a mobile URL version with a special rel=alternate tag). Google might not even make the effort to crawl and cache the mobile versions of all of these pages, as they could simply display that mobile URL to mobile searchers.

This view of the desktop version as the primary one often meant in practice that the desktop site would be prioritized by SEOs and marketing teams and was treated as the most comprehensive version of a website, with full content, structured data markup, hreflang (international tags), the majority of backlinks, etc.; while the mobile version might have lighter content, and/or not include the same level of markup and structure, and almost certainly would not receive the bulk of backlinks and external attention.

What should I do about mobile-first indexing?

The first thing to know is that there’s no need to panic. So far this change is only in the very earliest stages of testing, and is being rolled out very gradually only to websites which Google considers to be “ready” enough for this change to have a minimal impact.

According to Google’s own latest guidance on the topic, if your website is responsive or otherwise identical in its desktop and mobile versions, you may not have to do anything differently (assuming you’re happy with your current rankings!).

That said, even with a totally responsive site, you’ll want to ensure that mobile page speed and load time are prioritized and that images and other (potentially) dynamic elements are optimized correctly for the mobile experience. Note that with mobile-first indexing, content which is collapsed or hidden in tabs, etc. due to space limitations will not be treated differently than visible content (as it may have been previously), since this type of screen real estate management is actually a mobile best practice.

If you have a separate mobile site, you’ll want to check the following:

Content: make sure your mobile version has all the high-quality, valuable content that exists on your desktop site. This could include text, videos and images. Make sure the formats used on the mobile version are crawlable and indexable (including alt-attributes for images).

Structured data: you should include the same structured data markup on both the mobile and desktop versions of the site. URLs shown within structured data on mobile pages should be the mobile version of the URL. Avoid adding unnecessary structured data if it isn’t relevant to the specific content of a page.

Metadata: ensure that titles and meta descriptions are equivalent on both versions of all pages.

Note that the official guidance says “equivalent” rather than “identical” – you may still want to optimize your mobile titles for shorter character counts, but make sure the same information and relevant keywords are included.

Hreflang: if you use rel=hreflang for internationalization, your mobile URLs’ hreflang annotations should point to the mobile version of your country or language variants, and desktop URLs should point to the desktop versions.

Social metadata: OpenGraph tags, Twitter cards and other social metadata should be included on the mobile version as well as the desktop version.

XML and media sitemaps: ensure that any links to sitemaps are accessible from the mobile version of the site. This also applies to robots directives (robots.txt and on-page meta-robots tags) and potentially even trust signals, like links to your privacy policy page.

Search Console verification: if you have only verified your desktop site in Google Search Console, make sure you also add and verify the mobile version.

Common questions about mobile-first indexing

With mobile-first indexing, there is only one index (the same one Google uses now). The change to mobile-first indexing does not generate a new “mobile-first” index, nor is it creating a separate “mobile index” with a “desktop index” remaining active. Instead, it simply changes how content is added to the existing index.

Is the mobile-first index live and affecting my site now? If not, when does it go live?

Google has been experimenting with this approach to indexing on a small number of sites, which were selected based on perceived “readiness”. A wider rollout is likely going to take a long time and in June 2017, Gary Illyes stated that it will probably take a few years before “we reach an index that is only mobile-first.”

“We will be evaluating sites independently on their readiness for mobile-first indexing based on the above criteria and transitioning them when ready. This process has already started for a handful of sites and is closely being monitored by the search team.

“We continue to be cautious with rolling out mobile-first indexing. We believe taking this slowly will help webmasters get their sites ready for mobile users, and because of that, we currently don’t have a timeline for when it’s going to be completed.”

Will Google only use my mobile site to determine my rankings?

Mobile-first means that the mobile version will be considered the primary version when it comes to how rankings are determined. However, there may be circumstances where the desktop version could be taken into consideration (for instance, if you don’t have a mobile version of a page).

That being said, you will potentially still see varying ranking results between mobile search results and desktop search results, so you’ll still want to track both. (In the same way that now, Google primarily uses the desktop site to determine rankings but you still want to track mobile rankings as these vary from desktop rankings based on user behavior and other factors).

When might Google use the desktop site to determine rankings vs. the mobile site?

The primary use case I’ve seen referred to so far is that they will use the desktop site to determine rankings when there is no mobile version.

It is possible that for websites where the desktop version has additional ranking information (such as backlinks), that information could also be taken into consideration – but there is no guarantee that they will crawl or index the desktop version once they’ve seen the mobile version, and I haven’t seen any official statements that this would be the case.

Therefore one of the official recommendations is that once the mobile-first indexing rollout happens, if you’re in the process of building your mobile site or have a “placeholder” type mobile version currently live it would actually be better to have no mobile site than a broken or incomplete one. In this case, you should wait to launch your mobile site until it is fully ready.

What if I don’t have a mobile version of my site?

If you don’t have a mobile version of your site and your desktop version is not mobile-friendly, your content can still be indexed; however you may not rank as well in comparison to mobile-friendly websites. This may even negatively impact your overall rankings on desktop search as well as mobile search results because it will be perceived as having a poorer user experience than other sites (since the crawler will be a “mobile” crawler).

What could happen to sites with a large desktop site and a small mobile site? Will content on your desktop site that does not appear on the mobile version be indexed and appear for desktop searches?

The end goal for this rollout is that the index will be based predominantly on crawling mobile content. If you have a heavily indexed desktop version, they’re not going to suddenly purge your desktop content from the existing index and start fresh with just your thin mobile site indexed; but the more you can ensure that your mobile version contains all relevant and valuable content, the more likely it is to continue to rank well, particularly as they cut back on crawling desktop versions of websites.

How does this change ranking factors and strategy going forward?

This may impact a variety of ranking factors and strategy in the future; Cindy Krum at Mobile Moxie has written two excellentarticles on what could be coming in the future around this topic.

Cindy talks about the idea that mobile-first indexing may be “an indication that Google is becoming less dependent on traditional links and HTML URLS for ranking.” It seems that Google is moving away from needing to rely so much on a “URL” system of organizing content, in favor of a more API type approach based on “entities” (thanks, structured data!) rather than URL style links. Check out Cindy’s posts for more explanation of how this could impact the future of search and SEO.

Is there a difference between how responsive sites and separate mobile sites will be treated?

Yes and no. The main difference will be in terms of how much work you have to do to get ready for this change.

If you have a fully responsive site, you should already have everything present on your mobile version that is currently part of the desktop version, and your main challenge will simply be to ensure that the mobile experience is well optimized from a user perspective (e.g. page speed, load time, navigation, etc).

With a separate mobile site, you’ll need to make sure that your mobile version contains everything that your desktop site does, which could be a lot of work depending on your mobile strategy so far.

Will this change how I should serve ads/content/etc. on my mobile site?

If your current approach to ads is creating a slow or otherwise poor user experience you will certainly need to address that.

If you currently opt to hide some of your mobile site content in accordions or tabs to save space, this is actually not an issue as this content will be treated in the same way as if it was loaded fully visible (as long as the content is still crawlable/accessible).

Does this change how I use rel=canonical/switchboard tags?

Has this overview helped you to feel more prepared for the shift to mobile-first indexing? Are there any questions you still have?

I’d love to hear what you’re thinking about in the comments!

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!