Switching from Http to Https, but what about images and image link juice?
-
Hi Ya'll.
I'm transitioning our http version website to https. Important question:
Do images have to have 301 redirects? If so, how and where?
Please send me a link or explain best practices.
Best,
Shawn
-
Shawn124, whenever you move from HTTP to HTTPs, you'll need to set up the 301 permanent redirects for pages on the site only. The other elements, such as images, JavaScript (if they're external files), and .CSS files will need to be changed only in the code so that they reference the new HTTPs URLs, and not HTTP.
If you load an HTTP element (such as an image that uses the full URL in it's reference rather than the image filename only) on an HTTPs URL, then the browser will give you an error. So generally you need to do two things:
-
set up 301 Permanent Redirect for the page URLs.
-
search the entire website for all references to HTTP and change them to HTTPs (unless you're linking out to an external site).
If the site is in WordPress, you can use the Search and Replace plugin to replace it all at once in the database.
-
-
If you 301 redirect all HTTP URLs to HTTPS On the origin server,
To Move the origin server the HTTP to HTTPS On the origin server your redirects on your images will follow
#1
NGINX
Add the following to your Nginx config.
server { listen 80; server_name domain.com www.domain.com; return 301 https://domain.com$request_uri; }
Apache
Add the following to your
.htaccess
file.RewriteEngine On RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
(TOOL Apache htaccess to NGINX config tool https://winginx.com/en/htaccess)
#2
Search and replace the old HTTP:// URLs to New HTTPS://
http://mydomain.com
tohttps://mydomain.com
http://www.mydomain.com
tohttps://www.mydomain.com
Use CLI or https://interconnectit.com/products/search-and-replace-for-wordpress-databases/
#3
Alert Google that you are migrating to HTTPS https://www.google.com/webmasters/tools/home?hl=en
You will have no issue with your images.
Your link juice will flow as it did before because Google is no longer penalizing multiple redirects (So they SAY BUT don't over use redirects) keep them to a minimum, please.
https://www.deepcrawl.com/knowledge/best-practice/the-zen-guide-to-https-configuration/
https://www.deepcrawl.com/knowledge/best-practice/https-dilemma-security-seo/
#4
If on WordPress using proxy or just have insecure content use
Really Simple SSL: https://wordpress.org/plugins/really-simple-ssl/
Your insecure content is fixed by replacing all HTTP:// URLs with HTTPS://, except links to other external domains. Everything is done dynamically.
If using a Photos on a WAF or Pull CDN Force HTTPS
Connections#5
For example, if you're using a CloudFlare for Photos? You would use page rules to force a 301 redirect HTTPS
https://tools.keycdn.com/curl see #9 in https://www.maxcdn.com/one/tutorial/edge-rules-recipes/
#6
301's will not lose link juice see:
https://moz.com/blog/301-redirection-rules-for-seo
#7
Test using https://www.deepcrawl.com/ & or https://www.screamingfrog.co.uk/seo-spider/
(For a larger picture of the image below about redirect rule changing and link juice click on this URL http://i.imgur.com/vqyT6gm.jpg )
#8
If still needing tips or help read below.
Do images have to have 301 redirects? Yes
Citing:
http://searchengineland.com/http-https-seos-guide-securing-website-246940
"Making the switch from HTTP to HTTPS
- Start with a test server. This is important because it lets you get everything right and test without screwing it up in real time. Even if you are doing the switch without a test server, there’s almost nothing you can do that you can’t recover from, but it’s still best practice to have a plan and have everything tested ahead of time.
- Crawl the current website so that you know the current state of the site and for comparison purposes.
- Read any documentation regarding your server or CDN for HTTPS. I run into lots of fun CDN issues, but it can also be straightforward.
- Get a security certificate and install on the server. This will vary depending on your hosting environment and server setup too much for me to go into details, but the process is usually well-documented.
- Update references in content. This can usually be done with a search-and-replace in the database. You’ll want to update all references to internal links to use HTTPS or relative paths.
- Update references in templates. Again, depending on how you deploy, this might be done with Git or simply Notepad++, but you’ll want to make sure references to scripts, images, links and so on are either using HTTPS or relative paths.
- Update canonical tags. Most CMS systems will take care of this for you when you make the switch, but double-check, because that’s not always the case.
- **Update hreflang tags **if your website uses them, or any other tags such as OG tags for that matter. Again, most CMS systems will take care of this, but it’s best to QA it just in case.
- Update any plugins/modules/add-ons to make sure nothing breaks and that nothing contains insecure content. I commonly see internal site search and forms missed.
- CMS-specific settings may need to be changed. For major CMS systems, these are usually well-documented in migration guides.
- Crawl the site to make sure you didn’t miss any links and nothing is broken. You can export any insecure content in one of the Screaming Frog reports if this is the crawler you are using.
- Make sure any external scripts that are called support HTTPS.
- Force HTTPS with redirects. This will depend on your server and configuration but is well-documented for Apache, Nginx, and IIS.
- Update old redirects currently in place (and while you’re at it, take back your lost links from redirects that haven’t been done over the years). I mentioned during the Q&A portion of the Technical SEO Panel at SMX West that I’ve never had a site drop in rankings or traffic when switching to HTTPS, and a lot of people questioned me on this. Due diligence on redirects and redirect, chains are likely the difference, as this is what I see messed up the most when troubleshooting migrations.
- Crawl the old URLs for any broken redirects or any redirect chains, which you can find in a report with Screaming Frog.
- **Update sitemaps **to use HTTPS versions of the URLs.
- **Update your robots.txt file **to include your new sitemap.
- Enable HSTS. This tells the browser always to use HTTPS, which eliminates a server-side check and makes your website load faster. This can also cause confusion at times, since the redirect will show as 307. It could have a 301 or a 302 behind it, though, and you may need to clear your browser cache to see which.
- Enable OCSP stapling. This enables a server to check if a security certificate is revoked instead of a browser, which keeps the browser from having to download or cross-reference with the issuing certificate authority.
- Add HTTP/2 support.
- Add the HTTPS version of your site to all the search engine versions of webmaster tools that you use and load the new sitemap with HTTPS to them. This is important, as I’ve seen traffic drops misdiagnosed because they saw the traffic in the HTTP profile drop, when the traffic in reality moved to the HTTPS profile. Another note for this is that you do not need to use the Change of Address Tool when switching from HTTP to HTTPS.
- Update your disavow file if you had one for the HTTPS version.
- Update your URL parameter settings if you had these configured.
- Go live!
- In your analytics platform, make sure you update the default URL if one is required to ensure that you are tracking HTTPS properly, and add notes about the change so that you know when it occurred for future reference.
- Update your social share counts. There’s a lot of gotchas to this, in that some of the networks will transfer the counts through their APIs, while others will not. There are already guides for this around if you are interested in keeping your share counts.
- Update any paid media, email or marketing automation campaigns to use the HTTPS versions of the URLs.
- Update any other tools such as A/B testing software, heat maps and keyword tracking to use the HTTPS versions of the URLs.
- Monitor everything during the migration and check, double-check and triple-check to make sure everything is going smoothly. There are so many places where things can go wrong, and it seems like there are usually several issues that come up in any switch to HTTPS.
One question I’m often asked is if incoming links should be cleaned up. This is a tremendous amount of outreach and effort. If you have time, then sure; but most likely you’re busy with other things, and I don’t feel it’s necessary. However, you should update the links on any properties that you control, such as social profiles."
** you asked for the best links here are what you need**
- https://yoast.com/dev-blog/move-website-https-ssl/
- https://www.semrush.com/blog/how-to-survive-a-website-migration-semrushchat/?l=en
- https://www.digitalocean.com/community/questions/how-to-redirect-all-traffic-to-https-non-www
- https://moz.com/community/q/301-redirect-all-pictures-when-moving-to-a-new-site
- Link juice
** examplesI have put a lot more below**
- https://www.digitalocean.com/community/questions/how-to-redirect-all-traffic-to-https-non-www
- https://kinsta.com/knowledgebase/redirect-http-to-https/
- https://bjornjohansen.no/redirect-to-https-with-nginx
Unless you have to modify whatever system it is powering them, do you have a CDN? Or using something like AWS S3?
If so your images should move with the rest of the site. If you're posting them on a content delivery network or an AWS S3 whatever it is you must redirect that as well.
- https://yoast.com/dev-blog/move-website-https-ssl/
- https://support.google.com/webmasters/answer/83106?hl=en&ref_topic=6029673
- **https://moz.com/learn/seo/redirection **
- https://moz.com/community/q/301-redirect-all-pictures-when-moving-to-a-new-site
juice will not be lost long is you tell Google your moving the site see the URL below for how to redirect
Some of the systems will have buttons where you'd just click HTTPS others will require you to put the code into the system. I have posted the code below for Nginx as well as Apache.
Redirect from HTTP to https
This last bit will help you tremendously when you’ve not updated every single link on your site yet. You can just add a straight server level redirect from HTTP to https. In NGINX, we do this by having two servers defined in our config, the “right” one; that listens on port 443 and a simple one that listens on port 80 (standard HTTP) and has just this:
server {
listen 80;
server_name yoursite.com www.yoursite.com;
return 301 https://yoursite.com$request_uri;
}This seems to be the fastest way of doing this in NGINX, in Apache you’d do something like this:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]- Tools
- http://www.aleydasolis.com/htaccess-redirects-generator/nonwww-to-www/
- https://yoast.com/research/permalink-helper.php
- http://www.contentforest.com/seo-tools/url-redirect-generator
- https://donatstudios.com/RewriteRule_Generator
- http://www.rapidtables.com/web/tools/redirect-generator.htm
How to force SSL with. htaccess
If you want to force your entire website to go through https, you can add these rules to your .htaccess file:
| |
RewriteEngineOnRewriteCond%{SERVER_PORT}80RewriteRule^(.*)$https://yourdomain.com/$1 [R,L]
|
If your site is in a subfolder, use this code:
| |
RewriteEngineOnRewriteCond%{SERVER_PORT}80RewriteCond%{REQUEST_URI}folderRewriteRule^(.*)$https://yourdomain.com/folder/$1 [R,L]
|
Only replace yourdomain.com with your actual domain name.
Test with
- https://varvy.com/tools/redirects/
- https://varvy.com/pagespeed/hsts.html
- https://varvy.com/mobile/mobile-redirects.html
- http://searchengineland.com/http-https-seos-guide-securing-website-246940
Hope this helps,
Thomas
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
If you do 302 redirect then change to 301 redirect do you lose all link juice?
Hello everyone, I was wondering if you could help me with understanding the following story: A website has been moved from its HTTP version to a HTTPS version. The SEO manager has advised developers that they needed to do 301 redirects. However, in the end, 302 redirects have been put in place instead. Now, 301s should be put in place ASAP. The million dollar question is: has the website lost all of its link juice already given the nature of the redirects? Also, does it depend on whether Google has indexed the new 302 pages or does it depend on something else? Many thanks!
Intermediate & Advanced SEO | | MarketingGH0 -
Faulty title, meta description and version (https instead of http) on homepage
Hi there, I am working on a client (http://minibusshuttle.com/) whose homepage is not indexed correctly by Google. In details, the title & meta description are taken from another website (http://planet55.co.uk/). In addition, homepage is indexed as https instead of http. The rest of the URIs are correctly indexed (titles, meta descriptions, http etc). planet55.co.uk used to be hosted on the same server as minibusshuttle.com and an SSL certificate was activated for that domain. I have tried several times to manually "fetch by Google" the homepage, to no avail. The rest of the pages are indexed/refreshed normally and Google responds very fast when I perform any kind of changes there. Any suggestions would be highly appreciated. Kind regards, George
Intermediate & Advanced SEO | | gpapatheodorou0 -
Do 404s really 'lose' link juice?
It doesn't make sense to me that a 404 causes a loss in link juice, although that is what I've read. What if you have a page that is legitimate -- think of a merchant oriented page where you sell an item for a given merchant --, and then the merchant closes his doors. It makes little sense 5 years later to still have their merchant page so why would removing them from your site in any way hurt your site? I could redirect forever but that makes little sense. What makes sense to me is keeping the page for a while with an explanation and options for 'similar' products, and then eventually putting in a 404. I would think the eventual dropping out of the index actually REDUCES the overall link juice (ie less pages), so there is no harm in using a 404 in this way. It also is a way to avoid the site just getting bigger and bigger and having more and more 'bad' user experiences over time. Am I looking at it wrong? ps I've included this in 'link building' because it is related in a sense -- link 'paring'.
Intermediate & Advanced SEO | | friendoffood0 -
Http, https and link juice
I'm working on a site that is built on DNN. For some reason the client has set all pages to convert to HTTPS (although this is not perfect as some don't when landing on them). All pages indexed in Google are straight HTTP, but when you click on the Google result a temp 302 header response to the corresponding HTTPS page for many. I want it changed to a 301 but unfortunately is an issue for DNN. Is there another way around this in IIS that won't break DNN as it seems to be a bit flaky? I want to have the homepage link juice pass through for all links made to non HTTPS homepage. Removing HTTPS does not seem to be an option for them.
Intermediate & Advanced SEO | | MickEdwards0 -
Redirect ruined domain to new domain without passing link juice
A new client has a domain which has been hammered by bad links, updates etc and it's basically on its arse because of previous SEO guys. They have various domains for their business (brand.com, brand.co.uk) and want to use a fresh domain and take it from there. Their current domain is brand.com (the ruined one). They're not bothered about the rankings for brand.com but they want to redirect brand.com to brand.co.uk so that previous clients can find them easily. Would a 302 redirect work for this? I don't want to set up a 301 redirect as I don't want any of the crappy links pointing across. Thanks!
Intermediate & Advanced SEO | | jasonwdexter0 -
Links from new sites with no link juice
Hi Guys, Do backlinks from a bunch of new sites pass any value to our site? I've heard a lot from some "SEO experts" say that it is an effective link building strategy to build a bunch of new sites and link them to our main site. I highly doubt that... To me, a new site is a new site, which means it won't have any backlinks in the beginning (most likely), so a backlink from this site won't pass too much link juice. Right? In my humble opinion this is not a good strategy any more...if you build new sites for the sake of getting links. This is just wrong. But, if you do have some unique content and you want to share with others on that particular topic, then you can definitely create a blog and write content and start getting links. And over time, the domain authority will increase, then a backlink from this site will become more valuable? I am not a SEO expert myself, so I am eager to hear your thoughts. Thanks.
Intermediate & Advanced SEO | | witmartmarketing0 -
HTTP Status Bad Request - 404, but also, add a 400 HTTP Status in certain circumstances?
We currently have a custom 404 page set up for our clients, but the developer has it returning a HTTP 200 for the status code. Big no, no. I'm having that fixed right now. My question is, currently, the custom 404 page is only returned for urls with the extension .aspx: For example : ilovepizza.com/pepperni.aspx would return a 404 page because the correct page is ilovepizza.com/pepperoni.aspx Any other format of URL without the extension (example ilovepizza.com/thumbtack) does not trigger the custom 404 page we've created, but it does trigger a server error with a 404 HTTP status page. I want to change this so this type of error also triggers the custom 404 page because it's more user-friendly and would return them to the website. My question: Is there any benefit to making the /thumbtack errors return the custom 404 page but with a 400 Bad Request HTTP Status? Kind of a novice here in those aspects, but does the 400 Bad Request status indicate that it was a user mistake and not a mistake created on the website? Other suggestions?
Intermediate & Advanced SEO | | EEE30 -
Strategy After Switching To HTTPS
So we made a big mistake with our website last month. Without thinking things through, our entire website was switched to using a SSL certificate and https urls on all pages of the site. I know it is recommended that SSL is only used on sensitive pages, but we have a lead form on all pages. Of course Google is taking some time to adjust to all of our urls changing. A week later we lost all of our Google search rankings. It has now been about 3 weeks and our site is showing some signs of recovery, but obviously we'd like a quicker recovery. We have done proper 301 redirects throughout the site, but unfortunately our CMS has been a little buggy creating some other problems to fix along the way. So my main question is, how can we speed up the process? I do understand that we stand to lose 5-10% value of our old links due to the redirects. Is there anything else we should be doing to recover quicker though? Also, at this point, would it make any sense to switch back to http urls? Or would that just delay things further? Thanks!
Intermediate & Advanced SEO | | BorisD0