打造擁有更多 HTTPS 網站的網路環境！
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
2016 年 11 月 4 日，星期五
透過 Google 安全性網誌同步發布。
安全性一直是網路的重要課題，但多年來因網站遷移帶來的難題，導致難以採用 HTTPS。為了打造更安全的上網環境，Google 與其他夥伴針對線上生態系統合作，進一步瞭解並排解面臨的難題，藉此實現真正的變革。廣泛採用 HTTPS 的網路生態並非很遙遠的未來。
目前這個情況正在發生，安全瀏覽也已成為 Chrome 使用者的標準要求。
我們將在資訊公開報告中，為 HTTPS 報告資訊卡新增一個章節，說明根據資料，HTTPS 使用量正隨著時間持續增加。目前有超過半數的載入網頁，以及超過三分之二的 Chrome 電腦版使用者總時間，都是透過 HTTPS 執行，我們期望這項指標會繼續維持這種強勢成長。
隨著網路的其餘部分轉換至 HTTPS，我們將繼續努力，確保遷移至 HTTPS 更加輕鬆，在提升安全性的同時還能帶來業務優勢。HTTPS 目前提供的強大功能可以達到網路能提供的最佳效能，並且有利於提升網站轉換率，其中包括新功能和原有功能，新功能如 Service Worker (支援離線使用)，以及網路推播通知等，原有功能則包括信用卡自動填入功能和 HTML5 geolocation API，這些功能太過強大，無法透過不安全的 HTTP 使用。和所有大型網站遷移作業一樣，網站擁有者應該採取一些步驟，確保系統在改用 HTTPS 時，搜尋排名可以順利進行。為協助解決這個問題，我們張貼了常見問題來協助網站正確轉換，並且會持續改善網頁基礎知識指南。
我們發現有許多網站成功轉換，並對搜尋排名和流量造成小幅影響。Wayfair 大型零售網站 SEO 行銷總監 Brian Wood 表示：「我們已成功將 Wayfair.com 遷移至 HTTPS，對 Google 排名或 Google 自然搜尋流量沒有多少影響。很高興在此宣布，所有 Wayfair 網站現在都採用完整的 HTTPS 技術。」CNET 是大型科技新聞網站，一樣也有類似的經驗：CNET 技術工程部副總裁 John Sherwood 表示，「我們在上個月成功將 CNET.com 遷移至 HTTPS。從那時起，我們的 Google 排名或 Google 自然搜尋流量沒有任何變化。」
如果網站含有廣告，網站擁有者在遷移大量網站時，也應密切監控大型網站遷移時的廣告成效和收益。過去 3 年來，透過 HTTPS 放送的 Google 廣告流量比例大幅提升。來自 Google 來源的所有廣告一律支援 HTTPS，包括 AdWords、AdSense 或 DoubleClick Ad Exchange；直接銷售的廣告 (例如透過 DoubleClick for Publishers 放送的廣告) 仍須設計為支援 HTTPS。這表示遷移至 HTTPS 之後，來自 Google 來源的廣告在網站上的顯示不會有任何變化。許多發布者在成功完成 HTTPS 轉換作業後都發現了這種情況。Washington Post 的程式輔助廣告總監 Jason Tollestrup 表示，「轉換至 SSL 對 ADX 收益沒有任何實質影響。」
隨著遷移至 HTTPS 的作業變得較為簡單，我們會繼續打造安全無虞的網路。歡迎立即開始規劃 HTTPS 遷移作業！
發文者：Chrome 安全性團隊的 Adrienne Porter Felt 和 Emily Schechter
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。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"]]
