02-25-2019, 10:17 AM
Just for the benefit of anyone else who runs into this in future and comes across this thread:
I ran into the same "Error-1" problem today and worked out that in my case the cause was that the URLs I had loaded into the Google Mobile Site Tester were from a site that had a global disallow set up in robots.txt
Google's mobile site testing will not run on website's where either robots.txt or meta robots are blocking search engines. Figured this out when I took one of the URLs that was returning an "Error-1" in Scrapebox and manually chucked it into Google's mobile friendly testing tool (their error code is much clearer).
That likely will not be the only thing that produces an "Error-1" in SB, but is definitely one thing you can check.
I ran into the same "Error-1" problem today and worked out that in my case the cause was that the URLs I had loaded into the Google Mobile Site Tester were from a site that had a global disallow set up in robots.txt
Google's mobile site testing will not run on website's where either robots.txt or meta robots are blocking search engines. Figured this out when I took one of the URLs that was returning an "Error-1" in Scrapebox and manually chucked it into Google's mobile friendly testing tool (their error code is much clearer).
That likely will not be the only thing that produces an "Error-1" in SB, but is definitely one thing you can check.