On Friday, May 29, 2015, Brandon Black <bblack(a)wikimedia.org> wrote:
We've merged up
this, and I've purged the caches to ensure the update is fully live
already. It should address the issue, assuming that the block on RL's
/w/load.php entry point was the only part of the problem.
On Fri, May 29, 2015 at 8:43 PM, Jon Robson <jrobson(a)wikimedia.org
Yup what brandon said.
On 29 May 2015 1:35 pm, "Jon Robson" <jrobson(a)wikimedia.org
> It's all in the report. We block w/ in robots.txt always have.
> There have been a bunch of changes to improve performance of the site
> overall which might have led to that. Mailing this to the public mailing
> list wikitech would give you a better idea.
> Our site /is/ mobile friendly it's just we tell google not to load
> from w/load.php so no need to panic.
> The question is what is the penalty of us failing this tool? Does it
> impact our google search rankings?
> Fix is trivial.. Update robots.txt but first the question is why are we
> blocking scripts and styles on that url?
> On 29 May 2015 1:17 pm, "Jon Katz" <jkatz(a)wikimedia.org
>> Hi Readership team and broader community,
>> Any changes we might have recently made to cause this warning to appear
>> about googlebot not being able to access our site?
>> I consider this to be a very serious issue.
>> The examples below are not mobile, but same issue applies when you try
>> en.m. version of the pages.
>> ---------- Forwarded message ----------
>> Date: Fri, May 29, 2015 at 12:47 PM
>> Subject: Mobile Firendly
>> Google notified us of the followin...
>> "We recently noticed that there was a change with how you embed CSS &
>> which results in us not being able to use
the CSS & JS to recognize
>> page looks like. That's making some
of your pages fail the
>> mobile-friendly-test, for example. You used to load CSS & JS from
, but now they're loaded through /w/load.php?...
>> from the Wikipedia host, where that path
is blocked by robots.txt.
>> You can see how we render the pages with Fetch as Google in Webmaster
>> Tools / Search Console, you can also see most of that with the
>>> Some of the pages still pass the test there (example), but the CSS is
>>> broken there too since it's blocked. "
>>> Any ideas what can be causing this?
>>> reading-wmf mailing list
> Ops mailing list
Ops mailing list