The Internet Marketing Driver

  • GSQi Home
  • About Glenn Gabe
  • SEO Services
    • Algorithm Update Recovery
    • Technical SEO Audits
    • Website Redesigns and Site Migrations
    • SEO Training
  • Blog
  • Contact GSQi

How To Use Facebook Pixel Reporting To Identify Who Is Secretly Using Fetch And Render In GSC On Your Site

August 3, 2017 By Glenn Gabe Leave a Comment

Share
Tweet
Share
Email
544 Shares

Using Facebook pixel reporting to surface fetch and render.

I can see you, and now you can see me. :)

A few months ago, Dan Sharp from Screaming Frog wrote a killer post about how to use fetch and render in Google Search Console (GSC) on almost any site. Fetch and render in GSC enables you see how Googlebot is rendering any page on your site (since it fetches all necessary resources to render the page at hand, including JavaScript, CSS, images, etc.) It enables you to detect differences in how Googlebot is viewing your page versus the average user.

It’s an awesome tool and can help identify blocked resources, trouble with rendering content, etc. If you want to learn more about what you can find using fetch and render, you can check out my Search Engine Land column titled Fetch and Horror.

Dan’s global fetch and render approach was to iframe urls from another unverified website on your own domain and then use fetch and render in GSC. It works, and pretty darn well. I’ve set this up and tested it myself, and it does indeed work.

For example, here’s a third party fetch of the Big Green Egg homepage (one of my favorite grills btw):

Using Global Fetch and Render

That’s cool, but let’s face it, rendering a site that you don’t own and control does give you a creepy feeling. You aren’t really authorized to use fetch and render in GSC on any site other than your own verified site(s). So rendering another person’s site is like virtually trying on their clothes from the comfort of your own home. Yes, that sounds creepy and it’s a good analogy. You are basically “fetching around”. You might feel like this:

Global Fetch and Render is creepy.

And for those on the opposite end (being fetched), they can feel violated when someone is fetching and rendering their urls in order to see if there are any render problems. Again, it’s all a bit creepy.

But Are You Really Invisible?… No, Everything Is Trackable
As I was testing this out via my own setup, I started wondering how easily sites being rendered without consent could tell a third party was doing this. And if they could check that easily, it could lead to some uncomfortable situations. Which leads me to my next point…

Facebook Pixel Insights, With A Twist.
I was recently checking out Facebook’s pixel reporting and noticed an interesting finding. If you’re not familiar with the Facebook pixel, it enables you to cookie any visitor to your site and then retarget them back on Facebook. It’s a powerful approach that I’ve written about several times before (especially for boosting content to various custom audiences).

As I was reviewing the pixel reporting in Facebook Business Manager, I checked the domains tab. And clicking that tab just might blow your fetch-and-rendered mind. It will show you any domain where your pixel has fired. And I mean any domain.

Mind blown.

In theory, most sites should only see their own domain listed… so if you see others listed, then something funny could be going on (like another site scraping your pages). And of course, this would show any site that is iframing your content. And that’s exactly what you need to do in order to fetch and render another site’s urls. Do you see where this is leading?

How To Access Pixel Reporting in Facebook Business Manager
In order to view your Facebook pixel reporting, first access Facebook Business Manager. Once you do, click the hamburger menu in the upper left corner. You’ll see several options in the menu, including Pixels. Click that link in the menu and you’ll be taken to a screen that shows all of your “pixel fires”.

Pixel reporting in Facebook Business Manager

Once you are viewing your pixel reporting, you’ll see four tabs, including Events, URLs, Domains, and Devices. The Domains tab is the one you should check out.

The Domains Tab in Facebook's Pixel Reporting

When checking the list of domains in my reporting, I noticed the test domain I was using to set up global fetch and render using Dan’s approach.

Here’s what I saw:

Facebook pixel reporting for domains.

So my own domain is listed, which is correct, but there are several others there that shouldn’t be. And one is the domain I’m using for global fetch and render. Uh oh, I caught myself. :)

Caught fetching around.

Beware, Your Digital Camouflage Isn’t Perfect:
OK, this means any site using the Facebook pixel could easily see that you have been fetch and rendering their urls. Cue creepy music. Remember, everything is trackable on the web (ok, almost anything). So, before you fire up your new global fetch and render setup, just know that websites have an easy way to identify who is fetching around. And by the way, who would think that Facebook would be the one helping SEOs uncover this? Ironic, don’t you think? :)

Big Recommendation: Set up FB’s tracking pixel (for more than this reason!)
When Dan’s global fetch and render approach was published, many were thrilled to try it out (myself included). But there were some concerns about who might be fetching your own site. Now with the Facebook pixel reporting, you can easily check the domains where your pixel is firing. And if any of those domains aren’t your own, then they just might be “fetching around”.

So definitely set up the Facebook pixel, and for more than just this reason. Boosting content to custom audiences is an amazing way to help get your content in front of a very targeted audience. And now that you can see who is rendering your own content, there’s yet another benefit to installing the Facebook pixel. So do it today. It should only take you a few minutes to set up.

In closing, fetch and render is powerful, but be careful if you’re “fetching around”. Facebook apparently has the back of site owners, and those site owners just might see you poking around. See what I did there? :)

GG

 

Share
Tweet
Share
Email
544 Shares

Filed Under: facebook, google, seo, social-advertising, social-media, tools

Connect with Glenn Gabe today!

Latest Blog Posts

  • Google’s December 2020 Broad Core Algorithm Update Part 2: Three Case Studies That Underscore The Complexity and Nuance of Broad Core Updates
  • Google’s December 2020 Broad Core Algorithm Update: Analysis, Observations, Tremors and Reversals, and More Key Points for Site Owners [Part 1 of 2]
  • Exit The Black Hole Of Web Story Tracking – How To Track User Progress In Web Stories Via Event Tracking In Google Analytics
  • Image Packs in Google Web Search – A reason you might be seeing high impressions and rankings in GSC but insanely low click-through rate (CTR)
  • Google’s “Found on the Web” Mobile SERP Feature – A Knowledge Graph and Carousel Frankenstein That’s Hard To Ignore
  • Image Migrations and Lost Signals – How long before images lose signals after a flawed url migration?
  • Web Stories Powered by AMP – 12 Tips and Recommendations For Creating Your First Story
  • Visualizing The SEO Engagement Trap – How To Use Behavior Flow In Google Analytics To View User Frustration [Case Study]
  • The May 2020 Google Core Update – 4 Case Studies That Emphasize The Complexity Of Broad Core Algorithm Updates
  • How To Remove An Image From Google Search Using The Outdated Content Tool (When The Image Was Published On Another Site)

Web Stories

  • Google’s Disqus Indexing Bug
  • Google’s New Page Experience Signal

Archives

  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • GSQi Home
  • About Glenn Gabe
  • SEO Services
  • Blog
  • Contact GSQi
Copyright © 2021 G-Squared Interactive LLC. All Rights Reserved. | Privacy Policy

We are using cookies to give you the best experience on our website.

You can find out more about which cookies we are using or switch them off in settings.

The Internet Marketing Driver
Powered by  GDPR Cookie Compliance
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.

3rd Party Cookies

This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

This site also uses pixels from Facebook, Twitter, and LinkedIn so we publish content that reaches you on those social networks.

Please enable Strictly Necessary Cookies first so that we can save your preferences!