Troubleshooting Javascript for SEO Part 2

JavaScript Troubleshooting

In our first guide on troubleshooting JavaScript, we showed you how to perform the tests needed and walked you through the process of grabbing code from Google Search Console and emulating it. In this article, we’ll show you real examples of this in action. Let’s dive in.

Example 1

In this first example, we’re going to show you how code can differ based on the user-agent. This is a very slight change, but slight changes can be important.

If you head over to, you’ll see slight differences between a default user-agent (your browser) and a Googlebot user-agent. This isn’t a major change, but you can see that a script will load on the default browser that will not show up for Googlebot. We’ve highlighted it in the images below. This is a fairly banal change, but you’d be surprised at what simple changes may do, especially if you fail to load the one script that injects all of your content.

Example 2

Now that you’ve seen a smaller example of this in play, let’s look at a full code swap. We’ve headed over to to see this in action. We’ve also saved the code in case they swap methods.

This time, let’s walk through the steps on how we would approach this. We recommend you follow along and perform the same steps so that it sets in. Remember, this should be familiar if you’ve read the first part of this article.

  • Head over to a category on
  • Load the source code of the site. CTRL+U on Chrome/brave or right click and select view-source.
  • Review the source code and copy/paste it into or emulate it in a new tab.
  • Use a user-agent switcher extension (I used this) and swap to Googlebot (pull the user-agent from Google’s list of crawlers.
  • Revisit the source code as Googlebot, and copy/paste it into or emulate it in a new tab.

Here’s a couple of gifs so that you can quickly see the difference between the two. We’ve also included the actual source code so you can review it yourself.

Browser User-Agent Source Code

Googlebot User-Agent Source Code

Source Code

If you followed those steps, you’ll notice that the default source code for your browser’s user-agent is blank when it emulates. If you look into the code, you’ll see a message about a lack of JavaScript, and it’ll be fairly light in code.

Now, when you emulate the Googlebot user agent source code, you’ll have a completely different story. While it doesn’t look pretty, you’ll be able to see content.

In this case, Wegman’s is using a dynamic rendering solution in order to make sure that Googlebot get’s all of the content it needs, whereas user’s load the regular version of the site. One thing to keep in mind is that Wegman’s is not using any form of verification when it comes to Googlebot, which means anyone who changes their user-agent can get this.

If a site is using verification, you’ll likely experience something like this when you try and spoof Googlebot. 

We usually find this is the case with bigger websites, such as the Stubhub example here. This is also why you should always try and emulate code that’s pulled from GSC’s URL Inspection tool.


As you can see, it does take a little work to fully analyze whether a page is working properly when a JavaScript framework is used, but it’s not out of your reach. Every time a client uses a JavaScript framework, I run these same tests. You may find everything is fine, but that’s not always the case. By fully reviewing the code to make sure everything is loading properly for Google, you’ll be able to identify if issues and get them fixed before it becomes an issue.

Similar Posts