Viewing 3 replies - 1 through 3 (of 3 total)
  • Some Thing

    (@jeffdrichardsongmailcom)

    Me too.
    Here’s how it looks like in my case:

    404 URL:
    //pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
    Referred by (this is my own site):
    https://domain.com//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js

    But I can’t tell for sure I was getting these before (since I had many others at the time). Now that I cleaned those I’ve beeen seeing these.
    But like I said, I am not necessarily blaming this plugin. I disabled plugin for now and I’ll watch the logs for few more days.

    Thread Starter Doug

    (@nicoblog)

    If it helps i stopped using this plugin some time ago (i decided it was meaningless) and the errors no longer come up.

    Plugin Author Jason Penney

    (@jczorkmid)

    Looks like those are errors from browsers that don’t support protocol relative URLS (which are now used by WordPress core itself, but you’re more likely to see them with UGL activated, since you’ll have at least on in just about every page).

    Have you actually been able to generate any of these 404 errors yourself, or are they just showing up in logs. I’d guess they are from bots, not users.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘404 errors’ is closed to new replies.