HTTPS 类网页越来越多啦！
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
2016 年 11 月 4 日（星期五）
从 Google 安全博客交叉发布。
安全性对于网络来说一直尤为关键，但数年来，网站迁移方面的挑战一直阻碍着 HTTPS 的采用。为了给所有用户营造一个更安全的网络环境，Google 与整个网络生态系统中的许多其他方紧密合作，以便更好地了解和应对这些挑战，并带来真正的改变。实现网络中遍布 HTTPS 网页不会太遥远。随着安全浏览成为 Chrome 用户的标准，这个愿景正在逐步实现。
今天，我们向透明度报告内的“HTTPS 报告”卡片中新增了一个部分，其中包含有关 HTTPS 使用量随时间增加情况的数据。超过一半的网页加载活动以及 Chrome 桌面设备用户所用总时间中三分之二的时间相关的活动是通过 HTTPS 完成的，并且我们预计这些指标将继续保持强劲的上升势头。
随着网络中其余网页转换到 HTTPS，我们将继续努力确保迁移到 HTTPS 的过程轻松便捷，并在提高安全性之外提供业务优势。HTTPS 目前可实现网络提供的绝佳性能以及有助于
促进网站转化的强大功能，后者包括新功能（例如 Service Worker [或称为离线支持] 和
Web 推送通知）和现有功能（如信用卡自动填充和 HTML5 geolocation API），这些强大的功能均无法通过不安全的 HTTP 使用。与所有主要网站迁移一样，网站所有者应采取某些措施，确保在改用 HTTPS 时顺利转换搜索排名。为此，我们发布了常见问题解答来帮助网站正确完成转换，并将继续完善我们的网站开发基础指南。
我们发现，许多网站在成功转换后，其搜索排名和流量所受的影响微乎其微。大型零售网站 Wayfair 的营销搜索引擎优化 (SEO) 总监 Brian Wood 评论说：“我们能够将 Wayfair.com 迁移到 HTTPS，而且对 Google 排名或 Google 自然搜索流量没有任何重大影响。我们可以很高兴地宣布，所有 Wayfair 网站现在都完全采用 HTTPS。”
大型科技新闻网站 CNET 也有类似经历：“上个月，我们成功将 CNET.com 迁移到了 HTTPS，”CNET 的工程和技术副总裁 John Sherwood 表示，“从那时起，我们的 Google 排名或 Google 自然搜索流量没有发生过任何变化。”
如果网站所有者在其网站上展示广告，还应在大型网站迁移期间仔细监控广告效果和收入。过去 3 年，通过 HTTPS 投放的 Google 广告流量所占的比例大幅增加。来自任何 Google 来源（包括 AdWords、AdSense 或 DoubleClick Ad Exchange）的所有广告一律支持 HTTPS；直接销售的广告（例如通过 DoubleClick for Publishers 销售的广告）仍需要设计为支持 HTTPS。这意味着，迁移到 HTTPS 后，网站上展示的来自 Google 的广告不会发生变化。许多发布合作伙伴在成功转换到 HTTPS 后都见证了这一点。《华盛顿邮报》的程序化广告总监 Jason Tollestrup 表示：“转换到 SSL 后，AdX 收入没有受到实质性影响。”
随着迁移到 HTTPS 变得越来越简单，我们将继续努力打造遵循默认安全原则的网络。请立即开始规划您的 HTTPS 迁移，就趁现在！
发布者：Chrome 安全团队的 Adriana Porter Felt 和 Emily Schechter
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
[null,null,[],[[["\u003cp\u003eMore than half of pages loaded by Chrome desktop users are via HTTPS, and Google expects this to increase.\u003c/p\u003e\n"],["\u003cp\u003eGoogle is working to ensure HTTPS migration is easy, provides business benefits, and maintains search ranking.\u003c/p\u003e\n"],["\u003cp\u003eSites like Wayfair and CNET have successfully transitioned to HTTPS with no negative impact on search ranking or traffic.\u003c/p\u003e\n"],["\u003cp\u003eGoogle ads already support HTTPS, so site owners shouldn't see ad revenue changes after migrating.\u003c/p\u003e\n"],["\u003cp\u003eGoogle is actively working towards a web that's secure by default and encourages sites to plan their HTTPS migration.\u003c/p\u003e\n"]]],["Google reports increasing HTTPS usage, with over half of Chrome desktop page loads and two-thirds of time spent being secure. They emphasize transitioning to HTTPS is easier and beneficial, offering improved performance and features like service workers and web push. Sites are encouraged to migrate, with resources provided to ensure smooth search ranking transitions. Google-sourced ads fully support HTTPS. Successful migrations by Wayfair, CNET, and the Washington Post have shown no negative impact on rankings, traffic, or ad revenue.\n"],null,["# Here's to more HTTPS on the web!\n\nFriday, November 04, 2016\n\n\n*Cross-posted from the\n[Google Security Blog](https://security.googleblog.com/2016/11/heres-to-more-https-on-web.html)*.\n\n\nSecurity has always been critical to the web, but challenges involved in site migration have\ninhibited HTTPS adoption for several years. In the interest of a safer web for all, at Google\nwe've worked alongside many others across the online ecosystem to better understand and address\nthese challenges, resulting in real change. A web with ubiquitous HTTPS is not the distant future.\nIt's happening now, with secure browsing becoming standard for users of Chrome.\n\n\nToday, we're adding a\n[new section to the HTTPS Report Card in our Transparency Report](https://www.google.com/transparencyreport/https/metrics/)\nthat includes data about how HTTPS usage has been increasing over time. More than half of pages\nloaded and two-thirds of total time spent by Chrome desktop users occur via HTTPS, and we expect\nthese metrics to continue their strong upward trajectory.\n\n\nAs the remainder of the web transitions to HTTPS, we'll continue working to ensure that migrating\nto HTTPS is a no-brainer, providing business benefit beyond increased security. HTTPS currently\nenables the [best](https://istlsfastyet.com/)\n[performance](https://blog.chromium.org/2013/11/making-web-faster-with-spdy-and-http2.html)\nthe web offers and powerful features that [benefit](/web/showcase)\nsite conversions, including both new features such as\n[service workers](/web/fundamentals/getting-started/primers/service-workers)\nor offline support and\n[web push notifications](https://www.mobify.com/insights/google-web-push-notifications-case-study/),\nand existing features such as\n[credit card autofill](/web/updates/2015/06/checkout-faster-with-autofill)\nand the\n[HTML5 geolocation API](/web/updates/2016/04/geolocation-on-secure-contexts-only)\nthat are\n[too powerful to be used](https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins)\nover non-secure HTTP. As with all major site migrations, there are certain steps that site owners\nshould take to ensure that search ranking transitions are smooth when moving to HTTPS. To help\nwith this, we've posted\n[FAQs](/search/docs/crawling-indexing/site-move-with-url-changes#http-to-https-migration-faqs)\nto help sites transition correctly, and will continue to improve our\n[web fundamentals guidance](/web/fundamentals/security/encrypt-in-transit/why-https).\n\n\nWe've seen many sites successfully transition with negligible effect on their search ranking and\ntraffic. Brian Wood, Director of Marketing SEO at Wayfair, a large retail site, commented: \"We\nwere able to migrate Wayfair.com to HTTPS with no meaningful impact to Google rankings or Google\norganic search traffic. We are very pleased to say that all Wayfair sites are now fully HTTPS.\"\nCNET, a large tech news site, had a similar experience: \"We successfully completed our move of\nCNET.com to HTTPS last month,\" said John Sherwood, Vice President of Engineering and Technology\nat CNET. \"Since then, there has been no change in our Google rankings or Google organic search\ntraffic.\"\n\n\nSite owners that include ads on their sites also should carefully monitor ad performance and\nrevenue during large site migrations. The portion of Google ad traffic served over HTTPS has\n[increased dramatically](https://transparencyreport.google.com/https/overview) over the past 3 years.\nAll ads that come from any Google source always support HTTPS, including AdWords, AdSense, or\nDoubleClick Ad Exchange; ads sold directly, such as those through DoubleClick for Publishers,\nstill need to be designed to be HTTPS-friendly. This means there will be no change to the\nGoogle-sourced ads that appear on a site after migrating to HTTPS. Many publishing partners have\nseen this in practice after a successful HTTPS transition. Jason Tollestrup, Director of\nProgrammatic Advertising for the\n[Washington Post](https://developer.washingtonpost.com/pb/blog/post/2015/12/10/moving-the-washington-post-to-https/),\n\"saw no material impact to AdX revenue with the transition to SSL.\"\n\n\nAs migrating to HTTPS becomes even easier,\n[we'll continue](https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html)\nworking towards a web that's secure by default. Don't hesitate to start planning your HTTPS migration today!\n\nPosted by [Adriana Porter Felt](/search/blog/authors/adriana-porter-felt) and Emily Schechter, Chrome Security Team"]]
