Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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
-
Breadcrumbs and internal links
Hello, I use to move up my site structure with links in content. I have now installed breadcrumbs, is it is useful to still keep the links in content or isn't there a need to duplicate those links ? and are the breadcrumbs links enough. Thank you,
Intermediate & Advanced SEO | | seoanalytics1 -
Should I use https schema markup after http-https migration?
Dear Moz community, Noticed that several groups of websites after HTTP -> HTTPS migration update their schema markup from, example : {
Intermediate & Advanced SEO | | admiral99
"@context": "http://schema.org",
"@type": "WebSite",
"name": "Your WebSite Name",
"alternateName": "An alternative name for your WebSite",
"url": "http://www.your-site.com"
} becomes {
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Your WebSite Name",
"alternateName": "An alternative name for your WebSite",
"url": "https://www.example.com"
} Interesting to know, because Moz website is on https protocol but uses http version of markup. Looking forward for answers 🙂0 -
Too many on page links
Hi I know previously it was recommended to stick to under 100 links on the page, but I've run a crawl and mine are over this now with 130+ How important is this now? I've read a few articles to say it's not as crucial as before. Thanks!
Intermediate & Advanced SEO | | BeckyKey1 -
What is best practice for "Sorting" URLs to prevent indexing and for best link juice ?
We are now introducing 5 links in all our category pages for different sorting options of category listings.
Intermediate & Advanced SEO | | lcourse
The site has about 100.000 pages and with this change the number of URLs may go up to over 350.000 pages.
Until now google is indexing well our site but I would like to prevent the "sorting URLS" leading to less complete crawling of our core pages, especially since we are planning further huge expansion of pages soon. Apart from blocking the paramter in the search console (which did not really work well for me in the past to prevent indexing) what do you suggest to minimize indexing of these URLs also taking into consideration link juice optimization? On a technical level the sorting is implemented in a way that the whole page is reloaded, for which may be better options as well.0 -
Number of images on Google?
Hello here, In the past I was able to find out pretty easily how many images from my website are indexed by Google and inside the Google image search index. But as today looks like Google is not giving you any numbers, it just lists the indexed images. I use the advanced image search, by defining my domain name for the "site or domain" field: http://www.google.com/advanced_image_search and then Google returns all the images coming from my website. Is there any way to know the actual number of images indexed? Any ideas are very welcome! Thank you in advance.
Intermediate & Advanced SEO | | fablau1 -
Do 404 Pages from Broken Links Still Pass Link Equity?
Hi everyone, I've searched the Q&A section, and also Google, for about the past hour and couldn't find a clear answer on this. When inbound links point to a page that no longer exists, thus producing a 404 Error Page, is link equity/domain authority lost? We are migrating a large eCommerce website and have hundreds of pages with little to no traffic that have legacy 301 redirects pointing to their URLs. I'm trying to decide how necessary it is to keep these redirects. I'm not concerned about the page authority of the pages with little traffic...I'm concerned about overall domain authority of the site since that certainly plays a role in how the site ranks overall in Google (especially pages with no links pointing to them...perfect example is Amazon...thousands of pages with no external links that rank #1 in Google for their product name). Anyone have a clear answer? Thanks!
Intermediate & Advanced SEO | | M_D_Golden_Peak0 -
Site wide footer links vs. single link for websites we design
I’ve been running a web design business for the past 5 years, 90% or more of the websites we build have a “web design by” link in the footer which links back to us using just our brand name or the full “web design by brand name” anchor text. I’m fully aware that site-wide footer links arent doing me much good in terms of SEO, but what Im curious to know is could they be hurting me? More specifically I’m wondering if I should do anything about the existing links or change my ways for all new projects, currently we’re still rolling them out with the site-wide footer links. I know that all other things being equal (1 link from 10 domains > 10 links from 1 domain) but is (1 link from 10 domains > 100 links from 10 domains)? I’ve got a lot of branded anchor text, which balances out my exact match and partial match keyword anchors from other link building nicely. Another thing to consider is that we host many of our clients which means there are quite a few on the same server with a shared IP. Should I? 1.) Go back into as many of the sites as I can and remove the link from all pages except the home page or a decent PA sub page- keeping a single link from the domain. 2.) Leave all the old stuff alone but start using the single link method on new sites. 3.) Scratch the site credit and just insert an exact-match anchor link in the body of the home page and hide with with CSS like my top competitor seems to be doing quite successfully. (kidding of course.... but my competitor really is doing this.)
Intermediate & Advanced SEO | | nbeske0 -
Blocking Pages Via Robots, Can Images On Those Pages Be Included In Image Search
Hi! I have pages within my forum where visitors can upload photos. When they upload photos they provide a simple statement about the photo but no real information about the image,definitely not enough for the page to be deemed worthy of being indexed. The industry however is one that really leans on images and having the images in Google Image search is important to us. The url structure is like such: domain.com/community/photos/~username~/picture111111.aspx I wish to block the whole folder from Googlebot to prevent these low quality pages from being added to Google's main SERP results. This would be something like this: User-agent: googlebot Disallow: /community/photos/ Can I disallow Googlebot specifically rather than just using User-agent: * which would then allow googlebot-image to pick up the photos? I plan on configuring a way to add meaningful alt attributes and image names to assist in visibility, but the actual act of blocking the pages and getting the images picked up... Is this possible? Thanks! Leona
Intermediate & Advanced SEO | | HD_Leona0