Profile cover photo
Profile photo
Kazunori Iguchi
55 followers -
hello :)
hello :)

55 followers
About
Posts

Post has attachment

Post has attachment

Post has attachment

Post has attachment

Post has attachment

Post has shared content
I see a bunch of posts about the robotted resources message that we're sending out. I haven't had time to go through & review them all (so include URLs if you can :)), but I'll spend some time double-checking the reports tomorrow. 

Looking back a lot of years, blocking CSS & JS is something that used to make sense when search engines weren't that smart, and ended up indexing & ranking those files in search. For a long time now, that's no longer the case  (happy to get reports if you do see it though), and nowadays it's extremely helpful to be able to access CSS & JS files so that we understand what a page really looks like. Is it mobile-friendly? Is there content that we'd miss without JavaScript? Blocked CSS & JS files are some of the bigger problems that we run across in the meantime.

Search Console gives you tools to find blocked content across your site, to test individual pages to see if all embedded content is accessible, and to test your robots.txt files to find why a specific URL is blocked (and to submit an updated robots.txt so that we can crawl it ASAP). We've also documented this problem in various ways over time, for example in https://developers.google.com/webmasters/mobile-sites/mobile-seo/common-mistakes/blocked-resources 

That said, we hear you that these messages aren't as clear as they could be, and we'll double-check your reports (here on G+, on Twiter, in the forums, etc) to see what we can do to improve that. 
Photo

Post has attachment

Post has attachment

Post has shared content
As previously announced [1], Freebase will be going read-only next Tuesday, March 31st. This means that the website will no longer accept edits and the MQL write API will be retired. 

In that announcement we also promised updates on the Wikidata import review tool and transition plan for the Freebase Search API & Suggest Widget to a Knowledge Graph-based solution.

The Primary Sources tool will have two parts: a front end integrated into the Wikidata User Interface and a back end running on Wikimedia labs to provide data to the front end. Shortly after read-only, we will start with a small set of data in order to get feedback from the community and refine the tool.
- Screenshot and more info: https://www.wikidata.org/wiki/Wikidata:Primary_sources_tool 
- Code will be available by the end of the month here: https://github.com/google/primarysources
- FAQ by the Wikidata community: https://www.wikidata.org/wiki/Help:FAQ/Freebase 
- Discussion: https://www.wikidata.org/wiki/Wikidata:WikiProject_Freebase

The new Knowledge Graph API should be publicly available as a beta sometime during calendar Q2. We will ensure that there are at least three full months between the launch of that beta and the retirement of the current Freebase APIs, so this does mean the original June 30th retirement date will be pushed out. In the meantime, here are a few more details about the new API:
- Enables searching for Knowledge Graph entities by text or MID
- Returns name, subtitle, image, description and URL for candidate matches
- Results can also be restricted to a specific language or type
- Uses schema.org vocabulary in the JSON-LD format
- Companion Freebase Suggest-like Javascript library

[1] https://plus.google.com/109936836907132434202/posts/bu3z2wVqcQc 

Post has attachment
Wait while more posts are being loaded