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 styles
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> wrote:
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
an en.m. version of the pages.
Best,
Jon
---------- Forwarded message ----------
From: Wes Moran <wmoran(a)wikimedia.org>
Date: Fri, May 29, 2015 at 12:47 PM
Subject: Mobile Firendly
To: Jon Katz <jkatz(a)wikimedia.org>
Cc: Adam Baso <abaso(a)wikimedia.org>
Jon,
Google notified us of the followin...
"We recently noticed that there was a change with how you embed CSS & JS
which results in us not being able to use the CSS & JS to recognize what
the page looks like. That's making some of your pages fail the
mobile-friendly-test, for example. You used to load CSS & JS from
bits.wikimedia.org, but now they're loaded through /w/load.php?...
directly 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 test-page at:
https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fe…
Some of the pages still pass the test there (example
<https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FZ%25C3%25BCrich>),
but the CSS is broken there too since it's blocked. "
Any ideas what can be causing this?
Regards,
Wes
_______________________________________________
reading-wmf mailing list
reading-wmf(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/reading-wmf
_______________________________________________
reading-wmf mailing list
reading-wmf(a)lists.wikimedia.org