How does it work?If you save / share / copy the URL of a report that gives you the "last 7 days" of traffic on your website, it will now respect the real last 7 days every time you paste that URL or click on it, instead of remembering the date when you actually saved / shared / copied that URL.

ex: if I save a URL I created on January 25th, with a "last 7 days" view, and click on it today, it will give me a report on the last 7 days of traffic on my website, relative to today, rather than to January 25th.

Hope you like it, and if you have any feedback, please use the comments!

Show all 8 comments

David Sottimano: Sorry +Zineb Ait Bahajji , I'm not sure who asked for this, but this is hardly something that deserved immediate attention in GSC. There are lots of things that need attention that are more important than this. For example, 404 errors are bad for users right? We want to correct them too, but for some reason the Crawl error interface forces a click on an individual 404 to find out where it's being linked from - fine, but why isn't the link source at least in the export? Don't get me wrong, I appreciate any improvement, and am thankful, I just wish that there was a public voting system for proposed improvements in GSC.

Zineb Ait Bahajji: Thank you +David Sottimano for this feedback. I will pass it on the the GSC team.

I was very happy to see the Google Dance return last week. So many search marketers never get to see Google in person, even though it dominates so much of what they do. It was a real treat for them, plus it was great that a special meeting was held to gather feedback from SEOs. Thanks especially to webmaster trends analyst +Gary Illyes and search quality analyst +Nathan Johns for making it happen.

Planning on moving to HTTPS? Here are 13 FAQs! What's missing? Let me know in the comments and I'll expand this over time, perhaps it's even worth a blog post or help center article. Note that these are specific to moving an existing site from HTTP to HTTPS on the same hostname. Also remember to check out our help center at https://support.google.com/webmasters/answer/6073543

# Do I need to set something in Search Console? No, just add the HTTPS site there. The change-of-address setting doesn't apply for HTTP -> HTTPS moves.

# Will the rel=canonical guarantee that the HTTP URL is indexed? No, but it's a very strong signal when picking the indexed URL.

# What's the next step after testing? Follow our site-move documentation ( https://support.google.com/webmasters/answer/6033049 ). Use 301 redirects from HTTP to HTTPS, confirm the new version by adding a rel=canonical on the HTTPS page, pointing to itself, and submit sitemaps including both HTTP & HTTPS URLs with new change-dates (in the long run, just keep the HTTPS sitemap).

# What about the robots.txt file? The HTTPS site uses the HTTPS robots.txt file. Check that it's reachable or serves a 404 result code, and check that your HTTP URLs aren't blocked by the HTTP robots.txt file.

# Is it OK to have just some pages on HTTPS? Yes, no problem! Start with a part, test it, add more.

# Should I move everything together, or is it fine to do sections? Moving in sections is fine.

# Will I see a drop in search? Fluctuations can happen with any bigger site change. We can't make any guarantees, but our systems are usually good with HTTP -> HTTPS moves.

# Which certificate do I need? For Google Search, any modern certificate that's accepted by modern browsers is acceptable.

# Do I lose "link juice" from the redirects? No, for 301 or 302 redirects from HTTP to HTTPS no PageRank is lost.

# Will we see search keywords in Google Analytics when we're on HTTPS? This won't change with HTTPS, you can see the search queries in Search Console.

# How can I test how many pages were indexed? Verify HTTP / HTTPS separately in Search Console, use Index Status for a broad look, or the sitemaps indexed counts for sitemap URLs.

# How long will a move from HTTP to HTTPS take? There are no fixed crawl frequencies, it depends on the size of your site, and the speed of crawling that's possible. The move takes place on a per-URL basis.

Hope this helps clarify some of the open questions! Let me know if there's anything missing.

We spent a lot of time making this site right for you. We took our own advice by analyzing visitor behavior and conducting user studies to organize the site into categories you’ll find most useful. The site contains support resources to help you fix issues with your website, SEO learning materials to create a high-quality site and improve search rankings, and connection opportunities to stay up-to-date with our team and webmaster community.

Browse around www.google.com/webmasters and let us know in the comments if you stumble onto something new. Thanks to our awesome community and Top Contributors for the valuable feedback during the process!

A new year’s refresh of Android App-Indexing Crawl Errors data in Search ConsoleWe’re updating and simplifying the app crawl error types we show in Search Console. You’ll now see three error types in the App Crawl Status report: Package not found (unchanged), URI unsupported (unchanged), Removed from index (new).We’ve reset the data in the report, so you’ll see updated stats for these three error types since December 11.

All about the new error typeThese are app pages that don’t meet our technical guidelines — for example, users get redirected to the home page or the app crashes when the user attempts to open the deep link. To fix this, check the example URIs both in Fetch as Google and on an actual device, and make sure your app doesn't crash on opening, the deep pages don't redirect to the homepage, and the content is equivalent. Once you fix the issues and we recrawl your app pages, these deep links from Google search to your app will be reexamined If you’ve got more questions, drop by the help forum: https://productforums.google.com/forum/#!categories/webmasters/app-indexing

A new year’s refresh of Android App-Indexing Crawl Errors data in Search ConsoleWe’re updating and simplifying the app crawl error types we show in Search Console. You’ll now see three error types in the App Crawl Errors report: Package not found (unchanged), URI unsupported (unchanged), Removed from index (new).We’ve reset the data in the report, so you’ll see updated stats for these three error types since December 11.

All about the new error typeThese are app pages that don’t meet our technical guidelines — for example, users get redirected to the home page or the app crashes when the user attempts to open the deep link. To fix this, check the example URIs both in Fetch as Google and on an actual device, and make sure your app doesn't crash on opening, the deep pages don't redirect to the homepage, and the content is equivalent. Once you fix the issues and we recrawl your app pages, these deep links from Google search to your app will be reexamined If you’ve got more questions, drop by the help forum: https://productforums.google.com/forum/#!categories/webmasters/app-indexing