\n Top Contributors<\/a> in our
\n help forums<\/a>
\n have been very helpful in bringing up topics seen in the forums. They communicate regularly with
\n Google’s Search teams, and help the large community of Search Console users.\n <\/li>\n
\n and identified the top requests coming in. Open feedback can be sent via the ‘Submit feedback’
\n button in Search Console. This open feedback helped us get more context around one of the top
\n requests from the last years: more than 90 days of data in the Search Analytics (Performance)
\n report. We learned of the need to compare to a similar period in the previous year, which
\n confirmed that our decision to include 16 months of data might be on the right track.\n <\/li>\n
\n enlisting a group of four hundred randomly selected Search Console users, representing websites
\n of all sizes. The panel members took part in almost every design iteration we had throughout the
\n year, from explorations of new concepts through surveys, interviews and usability tests. The
\n Search Console panel members have been providing valuable feedback which helped us test our
\n assumptions and improve designs.\n <\/li>\n<\/ul>\n
\n In one of these rounds we tested the new suggested design for the Performance report. Specifically
\n we wanted to see whether it was clear how to use the ‘compare’ and ‘filter’ functionalities. To
\n create an experience that felt as real as possible, we used a high fidelity prototype connected to
\n real data. The prototype allowed study participants to interact with the user interface before
\n even one row of production code had been written.\n<\/p>\n
![\"an](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-5ae0141c488f.gif\")
<\/p>\n
\n In this study we learned that the ‘compare’ functionality was often overlooked. We consequently
\n changed the design with ‘filter’ and ‘compare’ appearing in a unified dialogue box, triggered
\n when the ‘Add new’ chip is clicked. We continue to test this design and others to optimize its
\n usability and usefulness.\n<\/p>\n
\n ![\"A](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-fbf8adfd5b7c.png\")
\n<\/p>\n
\n We incorporated user feedback not only in practical design details, but also in architectural
\n decisions. For example, user feedback led us to make major changes in the product’s core
\n information architecture influencing the navigation and product structure of the new Search
\n Console. The error and coverage reports were originally separated which could lead to multiple
\n views of the same error. As a result of user feedback we united the error and coverage reporting
\n offering one holistic view.\n<\/p>\n
\n As the launch date grew closer, we performed several larger scale experiments. We A\/B tested some
\n of the new Search Console reports against the existing reports with 30,000 users. We tracked issue
\n fix rates to verify new Search Console drives better results and sent out follow-up surveys to
\n learn about their experience. This most recent feedback confirmed that export functionality was
\n not a nice-to-have, but rather a requirement for many users and helped us tune detailed help pages
\n in the initial release.\n<\/p>\n
\n We are happy to announce that the new Search Console is now available to all sites. Whether it is
\n through Search Console’s feedback button or through the user panel, we truly value a collaborative
\n design process, where all of our users can help us build the best product.\n<\/p>\n