Re: Shopify Bug - Web Pixels Manager Sandbox
Shopify has a new bug - they are indexing tons of useless pages in Google again. Is there any way to stop this from happening? The code seems to only be editable by shopify since it's in the content_for_header.
Do a google search for:
inurl:/web-pixels-manager@
(https://www.google.com/search?q=inurl%3A%2Fweb-pixels-manager%40)
Each site has multiple versions of this page indexed. Peets.com for example has 20.
The pages look blank, but include something like this in the code:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Web Pixels Manager Sandbox</title>
<script id="web-pixels-manager-setup">(function e(e,n,a,o,t){e&&(window.Shopify=window.Shopify||{},window.Shopify.analytics=window.Shopify.analytics||{},window.Shopify.analytics.replayQueue=[],window.Shopify.analytics.publish=function(e,n,a){window.Shopify.analytics.replayQueue.push([e,n,a])});var r,i,s,l,d,c,p,u,f=a+"/"+o+"."+function(){var e="legacy",n="unknown",a=null,o=navigator.userAgent.match(/(Firefox|Chrome)\/(\d+)/i),t=navigator.userAgent.match(/(Edg)\/(\d+)/i),r=navigator.userAgent.match(/(Version)\/(\d+)(.+)(Safari)\/(\d+)/i);r?(n="safari",a=parseInt(r[2],10)):t?(n="edge",a=parseInt(t[2],10)):o&&(n=o[1].toLocaleLowerCase(),a=parseInt(o[2],10));var i={chrome:60,firefox:55,safari:11,edge:80}[n];return void 0!==i&&null!==a&&i<=a&&(e="modern"),e}()+".js";r={src:f,async:!0,onload:function(){if(e){var a=window.webPixelsManager.init(e);n(a),window.Shopify.analytics.replayQueue.forEach((function(e){a.publishCustomEvent(e[0],e[1],e[2])})),window.Shopify.analytics.replayQueue=[],window.Shopify.analytics.publish=a.publishCustomEvent}},onerror:function(){var n=(e.storefrontBaseUrl?e.storefrontBaseUrl.replace(/\/$/,""):self.location.origin)+"/.well-known/shopify/monorail/unstable/produce_batch",a=JSON.stringify({metadata:{event_sent_at_ms:(new Date).getTime()},events:[{schema_id:"web_pixels_manager_load/2.0",payload:{version:t||"latest",page_url:self.location.href,status:"failed",error_msg:f+" has failed to load"},metadata:{event_created_at_ms:(new Date).getTime()}}]});try{if(self.navigator.sendBeacon.bind(self.navigator)(n,a))return!0}catch(e){}const o=new XMLHttpRequest;try{return o.open("POST",n,!0),o.setRequestHeader("Content-Type","text/plain"),o.send(a),!0}catch(e){console&&console.warn&&console.warn("[Web Pixels Manager] Got an unhandled error while logging a load error.")}return!1}},i=document.createElement("script"),s=r.src,l=r.async||!0,d=r.onload,c=r.onerror,p=document.head,u=document.body,i.async=l,i.src=s,d&&i.addEventListener("load",d),c&&i.addEventListener("error",c),p?p.appendChild(i):u?u.appendChild(i):console.error("Did not find a head or body element to append the script")})(null,null,"https://cdn.shopify.com/shopifycloud/web-pixels-manager/0.0.186","sandbox","0.0.186");</script>
</head>
<body></body>
</html>
On top of that the vendors?q= is back for me?
When will this damn nightmare end!
that's indeed a sad case. Additionally, some SEO experts told me that if we have a lot of 404 pages, it will draw our SEO traffic down. Here's what I have and 90% of them belongs to "WPM" links.
Greg,
I have tried to keep calm and balanced re this topic - that has been going for 8 months or so.
My "Not found (404)" and "Crawled - currently not indexed" both doubled with the last GCS report:
I am tired of wasting hours trying different things to clean up my GSC .... NOTHING works. My ask that you get Google to do a reset of all the Shopify urls so that the buffer was cleared was ignored.
Now I am back to seeing lots and lots of junk in my GSC - again.
I really wish I hadn't migrated to Shopify (which I did in ~ Oct 2022 - talk about bad timing, as I had thought they would look after me as a small fish!).... and had stayed with another Provider / Wordpress.
Given Shopify has decided NOT to ask Google to clear the buffer, and we just have to wait (for how long ..... who knows, no number of months is provided .... it might be 10000 months for all we know).
I am soooooo annoyed. I will now actively let all my startups colleagues to NOT use Shopify.
How high did you escalate this up in Google ..... CEO to CEO? Of course Google doesn't "want" to do this - it is a negotiation!!!
Yes, there are about 10 WPM's and a few other nasties in there.
I am soooo tired of spending time on this issue.
I am just about to launch, and it looks like I need to find another provider and ditch Shopify ..... sheezzz. That is a lot of work for me.
Greg,
Have you considered that the problem is coming in through http:// (and not https://)
I ran the following reports on GSC Under "URL inspection", for http://www.XYZ.com and http://XYZ.com (as examples) and as you can see there are referrers who are not mine:
Why / who are these referrers? It being http:// perhaps hackers are exploiting it .... how about just shutting down http:// and just leave https:// operational.
Thoughts?
It looks like robots.txt was blocking nothing for a few days. Are you seeing something similar?
Yup …. spam back too
Did your "Blocked by robots.txt" drop to zero?
UPDATE:
Looks like robots.txt was either offline or served a nearly blank file for a few days. Glad to see that there's absolute turmoil on the back end.
"Incorrect use of the [robots.txt] feature can result in loss of all traffic."
Community Blog Articles
Hey Community! As the holiday season unfolds, we want to extend heartfelt thanks to a...
By JasonH Dec 6, 2024
Dropshipping, a high-growth, $226 billion-dollar industry, remains a highly dynamic bus...
By JasonH Nov 27, 2024
Hey Community! It’s time to share some appreciation and celebrate what we have accomplis...
By JasonH Nov 14, 2024