Profile cover photo
Profile photo
Giacomo Gnecchi Ruscone
3,475 followers -
Making the web a great and safer place for users :)
Making the web a great and safer place for users :)

3,475 followers
About
Giacomo's posts

Post has shared content
Para mis amigos espanholes :)
ATENCION SEOS, PRIMER GOOGLE Q&A EN ESPAÑOL!

En nuestros 5 episodios de Google Q&A hemos tenido invitados de lujo como +John Mueller y +Andrey Lipattsev de Google y reconocidos expertos #SEO como Rand Fishkin o Bill Slawski y otros.

Ahora por primera vez EN ESPAÑOL, se viene Google P&R este 27 de Octubre con +Juan Felipe Rincón líder del equipo global de soporte a webmasters de GOOGLE(Dublin, Irelanda) y expertos como +Aleyda Solis, +Gianluca Fiorelli, +Fernando Maciá Domene y +Cristian Sepulveda.

Post has attachment
Wanna join Google? My team is hiring: contact me if you match the profile :) (Russian also available) https://www.google.com/about/careers/search#!t=jo&jid=218335001&

Post has attachment
Stiamo reclutando specialisti nel mio team (tedesco / russo) qui a Dublino: https://www.google.com/about/careers/search#!t=jo&jid=218335001&
Fatevi avanti e contattatemi se conoscete profili giusti.

Post has attachment
Penguin fa ora parte del nostro algoritmo di base, l'annuncio in Italiano nel Forum di assistenza.

Post has attachment
Grandi cambiamenti lato interstitial su siti mobile ;)

Post has shared content
We collected a few questions from news publishers related to HTTP to HTTPS site moves, but some of the answers are relevant to all webmasters who are considering going secure.
If you have more questions you'd like to see answered, we're listening!

Q: Should I move my site all at once to HTTPS, or bit by bit?
A: We recommend initially moving just a piece of the site to test any effects on traffic and search indexing. After that you can move the rest of your site all at once or in chunks.
When choosing the initial test section of the site, pick a section that changes less frequently and isn't significantly affected by frequent or unpredictable events.
Also keep in mind that while moving just one section is a great way to test your move, it's not necessarily representative of a whole site move when it comes to search. The more pages that you move, the more likely you'll encounter additional problems to solve. Careful planning can minimize problems.

Q: How long should I run my trial?
A: Plan for a few weeks to allow for crawling and indexing to pick up changes, plus time to monitor traffic.

Q: Even though we are starting with only a section, we plan to make the entire site available on HTTPS. To avoid indexing of the HTTPS content early, should we use redirects or rel=canonicals?
A: With redirects in place, you won't be able to test those pages from a technical point of view, so we'd recommend using rel=canonical.

Q: We reference our HTTP sitemaps in robots.txt. Should we update the robots.txt to include our new HTTPS sitemaps?
A: We recommend separate robots.txt files for HTTP and HTTPS, pointing to separate sitemap files for HTTP and HTTPS. We also recommend listing a specific URL in only one sitemap file.

Q: Which sitemap should map the section in the HTTPS trial?
A: You can create a separate sitemap just for the updated section of your site. This will enable you to track indexing of the trial section more precisely. Be sure not to duplicate these URLs in any other sitemaps, though.

Q: Are there any other specific things we need to add to the robots.txt for the HTTPS version?
A: No.

Q: Our HTTPS site redirects non-migrated pages back to HTTP. What should our sitemaps list? Should we list in our sitemaps both the HTTP and HTTPS URLs? What if in the test section the HTTP URLs redirect to HTTPS?
A: List all HTTP URLs in your HTTP sitemap, and all HTTPS URLs in your HTTPS sitemap, regardless of redirects when the user visits the page. Having pages listed in your sitemap regardless of redirects will help search engines discover the new URLs faster.

Q: If we set includeSubDomains in our HSTS header, which domains will that affect?
A: After you migrate your entire site to HTTPS, you can support HSTS preloading for extra security. To enable this, you must set the includeSubDomains directive in the HSTS header.
If the site www.example.com serves an HSTS header with includeSubdomains set, then it will apply to www.example.com and foo.www.example.com, but not example.com or foo.example.com.
Keep in mind however that HSTS adds complexity to your rollback strategy. Our recommendation is this:
1. Roll out HTTPS without HSTS first.
2. Start sending HSTS headers with a short max-age. Monitor your traffic both from users and other clients, and also dependants' performance, such as ads.
3. Slowly increase the HSTS max-age.
If HSTS doesn't affect your users and search engines negatively, you can, if you wish, ask your site to be added to the Chrome HSTS preload list (https://hstspreload.appspot.com/).

Q: We use a single Google News sitemap for our entire site. What do we do if we're migrating our site piece by piece?
A: If you want to use a Google News sitemap for the new HTTPS section, you will have to contact the News team (https://support.google.com/news/publisher/contact/update_domain) to let them know about the protocol change, and then in your HTTPS property in Search Console you can submit a new Google News sitemap (https://support.google.com/news/publisher/answer/74288) for each migrated HTTPS section of the site.

Q: Are there any specific recommendations for Google News Publisher Center (https://partnerdash.google.com/) with HTTPS migration?
A: Google News Publisher Center handles the HTTP->HTTPS moves transparently. In general you don't have to do anything from Google News perspective, unless you're also making use of News sitemaps. In that case, please get in touch with the News team and let them know about the change, https://support.google.com/news/publisher/contact/update_domain. You can also let the team know about changing sections, for example in case you're moving to HTTPS, you can specify that you're moving http://example.com/section to https://example.com/section .

Post has shared content
Starting now!
Our next #mSiteLab site clinic will take place on July 20th at 16:30 Central European Time. During this mobile websites laboratory the webmaster relations team will consider individual websites and provide practical tips.

Registration for the mSite Lab is open until July 18th. Please specify in the registration form (https://goo.gl/VzWXF8) whether you want your website to be audited live during the hangout. Due to the large number of websites submitted we will select several sites at random and notify you if your website is picked.

Please note that hangout will be recorded and hosted on our YouTube channel, so you may come back to watch it anytime.

Playlist with past hangouts: https://www.youtube.com/playlist?list=PLKoqnv2vTMUMqH8IyzOMBc_Z8i-S6-tVJ
Webmaster events calendar: https://www.google.com/webmasters/connect/

Post has shared content
You'll soon be getting alerts in Google Analytics if your site is hacked for spam. Head over to the Webmaster Blog to read more about what that means and what to do if your site is hacked.

Post has shared content
Google Anti-abuse & Security Lead +Elie Bursztein talks about research that helps 600,000 webmasters re-secure their hacked sites every year. Check out his blog, linked below. 

Post has shared content
Financial Times says ...
"both in terms of user experience and financial impact, that there are clear and highly valued benefits in making the site even faster"

http://engineroom.ft.com/2016/04/04/a-faster-ft-com/

(Alas no apology given if you were in the test group that had everything slowed down :))
Wait while more posts are being loaded