Stay organized with collections
Save and categorize content based on your preferences.
Thursday, June 07, 2018
With the eleventh annual Google I/O
wrapped up, it's a great time to reflect on some of the highlights.
What we did at I/O
The event was a wonderful way to meet many great people from various communities across the globe,
exchange ideas, and gather feedback. Besides many great
web sessions,
codelabs,
and office hours, we shared a few things with the community in two
sessions specific to Search:
The sessions included the launch of JavaScript error reporting in the
Mobile Friendly Test tool,
dynamic rendering (we will discuss this in more detail in a future post), and an explanation of
how CMS can use the Indexing and Search Console APIs to provide users with insights. For example,
Wix lets their users
submit their home page to the index
and see it in Search results instantly, and Squarespace created a
Google Search keywords report
to help webmasters understand what prospective users search for.
During the event, we also presented the
new Search Console in the
Sandbox area for people to try and were happy to get a lot of positive feedback, from people being
excited about the
AMP Status report
to others exploring how to improve their content for Search.
Hands-on codelabs, case studies and more
We presented the
Structured Data Codelab
that walks you through adding and
testing structured data.
We were really happy to see that it ended up being one of the top 20 codelabs by completions at
I/O. If you want to learn more about the benefits of using Structured Data, check out our
case studies.
During the in-person office hours we saw a lot of interest around HTTPS,
mobile-first indexing, AMP,
and many other topics. The in-person Office Hours were a wonderful addition to our monthly
Webmaster Office Hours hangout.
The questions and comments will help us adjust our documentation and tools by making them clearer
and easier to use for everyone.
Highlights and key takeaways
We also repeated a few key points that web developers should have an eye on when building
websites, such as:
Indexing and rendering don't happen at the same time. We may defer the rendering to a later
point in time.
Make sure the content you want in Search has metadata, correct HTTP statuses, and the intended
canonical tag.
Hash-based routing (URLs with #) should be deprecated in favour of the JavaScript
History API in Single Page Apps.
Links should have an href attribute pointing to a URL, so Googlebot can follow the links
properly.
Make sure to
watch this talk for
more on indexing, dynamic rendering and troubleshooting your site. If you wanna learn more about
things to do as a CMS developer or theme author or Structured Data,
watch this talk.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eGoogle I/O provided opportunities to share information about Search Console APIs, dynamic rendering, and JavaScript error reporting in the Mobile-Friendly Test tool.\u003c/p\u003e\n"],["\u003cp\u003eWeb developers should ensure their content has correct metadata, HTTP statuses, canonical tags, and crawlable links for optimal indexing.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends using the JavaScript History API instead of hash-based routing for Single Page Apps.\u003c/p\u003e\n"],["\u003cp\u003eIndexing and rendering are separate processes, and Google may defer rendering.\u003c/p\u003e\n"],["\u003cp\u003eStructured data is beneficial, and developers can learn more through Google's codelabs and case studies.\u003c/p\u003e\n"]]],["Google I/O included sessions on search-friendly JavaScript, web presence, and the new Search Console. Key features launched were JavaScript error reporting in the Mobile Friendly Test and dynamic rendering. Presenters highlighted the Structured Data Codelab and discussed indexing, rendering, metadata, HTTP statuses, and canonical tags. They recommended deprecating hash-based routing for the JavaScript History API. Attendees could interact in web and in-person office hours and access case studies, as well as submit feedback on the new updates.\n"],null,["# Google Search at I/O 2018\n\n| It's been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore).\n\nThursday, June 07, 2018\n\n\nWith the eleventh annual [Google I/O](https://events.google.com/io/)\nwrapped up, it's a great time to reflect on some of the highlights.\n\nWhat we did at I/O\n------------------\n\n\nThe event was a wonderful way to meet many great people from various communities across the globe,\nexchange ideas, and gather feedback. Besides many great\n[web sessions](https://www.youtube.com/watch?v=FglWLLA4g-s),\n[codelabs](https://codelabs.developers.google.com/codelabs/structured-data/index.html?index=..%2F..%2Findex#0),\nand office hours, we shared a few things with the community in two\nsessions specific to Search:\n\n- [Deliver search-friendly JavaScript-powered websites](https://www.youtube.com/watch?v=PFwUbgvpdaQ) with John Mueller and Tom Greenaway\n- [Build a successful web presence with Google Search](https://www.youtube.com/watch?v=NO-sdBzb1Hc) with Mariya Moeva and John Mueller\n\n\nThe sessions included the launch of JavaScript error reporting in the\n[Mobile Friendly Test tool](https://search.google.com/test/mobile-friendly),\ndynamic rendering (we will discuss this in more detail in a future post), and an explanation of\nhow CMS can use the Indexing and Search Console APIs to provide users with insights. For example,\nWix lets their users\n[submit their home page to the index](https://youtu.be/FBG3-pwMFxU?t=1m22s)\nand see it in Search results instantly, and Squarespace created a\n[Google Search keywords report](https://support.squarespace.com/hc/en-us/articles/360001014647)\nto help webmasters understand what prospective users search for.\n\n\nDuring the event, we also presented the\n[new Search Console](https://search.google.com/search-console) in the\nSandbox area for people to try and were happy to get a lot of positive feedback, from people being\nexcited about the\n[AMP Status report](https://support.google.com/webmasters/answer/7450883)\nto others exploring how to improve their content for Search.\n\nHands-on codelabs, case studies and more\n----------------------------------------\n\n\nWe presented the\n[Structured Data Codelab](https://codelabs.developers.google.com/codelabs/structured-data/index.html?index=..%2F..%2Findex#0)\nthat walks you through adding and\n[testing structured data](/search/docs/advanced/structured-data).\nWe were really happy to see that it ended up being one of the top 20 codelabs by completions at\nI/O. If you want to learn more about the benefits of using Structured Data, check out our\n[case studies](/search/case-studies).\n\n\nDuring the in-person office hours we saw a lot of interest around HTTPS,\n[mobile-first indexing](/search/blog/2018/03/rolling-out-mobile-first-indexing), AMP,\nand many other topics. The in-person Office Hours were a wonderful addition to our monthly\n[Webmaster Office Hours hangout](/search/events/join-office-hours).\nThe questions and comments will help us adjust our documentation and tools by making them clearer\nand easier to use for everyone.\n\nHighlights and key takeaways\n----------------------------\n\n\nWe also repeated a few key points that web developers should have an eye on when building\nwebsites, such as:\n\n- Indexing and rendering don't happen at the same time. We may defer the rendering to a later point in time.\n- Make sure the content you want in Search has metadata, correct HTTP statuses, and the intended canonical tag.\n- Hash-based routing (URLs with `#`) should be deprecated in favour of the JavaScript History API in Single Page Apps.\n- Links should have an `href` attribute pointing to a URL, so Googlebot can follow the links properly.\n\n\nMake sure to\n[watch this talk](https://www.youtube.com/watch?v=PFwUbgvpdaQ) for\nmore on indexing, dynamic rendering and troubleshooting your site. If you wanna learn more about\nthings to do as a CMS developer or theme author or Structured Data,\n[watch this talk](https://www.youtube.com/watch?v=NO-sdBzb1Hc).\n\n\nWe were excited to meet some of you at I/O as well as the\n[global I/O extended events](https://events.google.com/io/extended/)\nand share the latest developments in Search. To stay in touch, join the\n[Webmaster Forum](https://support.google.com/webmasters/community/)\nor follow us on\n[Twitter](https://twitter.com/googlesearchc),\n[Google+](https://plus.google.com/+googlewebmasters), and\n[YouTube](https://www.youtube.com/@GoogleSearchCentral).\n\nPosted by [Martin Splitt](/search/blog/authors/martin-splitt), Webmaster Trends Analyst"]]
