\n initially launched<\/a>
\n with just four reports more than a decade ago. Today, the product includes more than two dozen
\n reports and tools covering AMP, structured data, and live testing tools, all designed to help
\n improve your site’s performance on Google Search.\n<\/p>\n
\n Now we have decided to embark on an extensive redesign to better serve you, our users. Our hope is
\n that this redesign will provide you with:\n<\/p>\n
- \n
- \n More actionable insights<\/strong> – We will now group the identified issues by what we
\n suspect is the common “root-cause” to help you find where you should fix your code. We organize
\n these issues into tasks that have a state (similar to bug tracking systems) so you can easily
\n see whether the issue is still open, whether Google has detected your fix, and track the
\n progress of re-processing the affected pages.\n <\/li>\n- \n Better support of your organizational workflow<\/strong> – As we talked to many
\n organizations, we’ve learned that multiple people are typically involved in implementing,
\n diagnosing, and fixing issues. This is why we are introducing sharing functionality that allows
\n you to pick-up an action item and share it with other people in your group, like developers who
\n will get references to the code in question.\n <\/li>\n- \n Faster feedback loops between you and Google<\/strong> – We’ve built a mechanism to allow
\n you to iterate quickly on your fixes, and not waste time waiting for Google to recrawl your
\n site, only to tell you later that it’s not fixed yet. Rather, we’ll provide on-the-spot testing
\n of fixes and are automatically speeding up crawling once we see things are ok. Similarly, the
\n testing tools will include code snippets and a search preview – so you can quickly see where
\n your issues are, confirm you’ve fixed them, and see how the pages will look on Search.\n <\/li>\n<\/ul>\n\n In the next few weeks, we’re releasing two exciting BETA features from the new Search Console to a
\n small set of users—Index Coverage report and AMP fixing flow.\n<\/p>\n\n The new Index Coverage report shows the count of indexed pages, information about why some pages
\n could not be indexed, along with example pages and tips on how to fix indexing issues. It also
\n enables a simple sitemap submission flow, and the capability to filter all Index Coverage data to
\n any of the submitted sitemaps.\n<\/p>\n\n Here’s a peek of our new Index Coverage report:\n<\/p>\n
![](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-63f2c9dcd29a.png\")
<\/p>\nThe new AMP fixing flow<\/h2>\n
\n The new AMP fixing experience starts with the AMP Issues report. This report shows the current AMP
\n issues affecting your site, grouped by the underlying error. Drill down into an issue to get more
\n details, including sample affected pages. After you fix the underlying issue, click a button to
\n verify your fix, and have Google recrawl the pages affected by that issue. Google will notify you
\n of the progress of the recrawl, and will update the report as your fixes are validated.\n<\/p>\n![](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-b1f2fe900209.png\")
<\/p>\n\n As we start to experiment with these new features, some users will be introduced to the new
\n redesign through the coming weeks.\n<\/p>\n - \n Better support of your organizational workflow<\/strong> – As we talked to many