Membership is FREE – with unlimited access to all features, tools, and discussions. Premium accounts get benefits like banner ads and newsletter exposure. ✅ Signature links are now free for all. Share your own thoughts and experience, accounts may be terminated for violations.
  • Welcome to AcornDomains.co.uk, a friendly community for UK domain investors, developers and anyone interested in domain names.

    Whether you're looking to buy or sell domains, learn more about the UK domain market, get feedback on your names, or simply chat with other domainers, you're in the right place. AcornDomains has been bringing together people from across the UK domain industry for many years, from complete beginners to experienced investors.

    Have a look around, join the discussions and, if you haven't already, create a free account and introduce yourself.

Serving The Whole Site Over HTTPS

Status
Not open for further replies.
Joined
Nov 5, 2014
Posts
221
Reaction score
40
I am about to move an entire site so that it is served securely, but want to make sure I'm not affecting any current links to the site.

Previously I have used a Response.Redirect (the site is in ASP.NET) if a page is attempt to be loaded over http rather than https, but as there are many current links to the site, I wonder if I should in fact be returning a 301 to the secure page via Response.Status instead?

Or does Google simply ignore http vs https when looking at links?
 
Or does Google simply ignore http vs https when looking at links?

The https is technically a different site so you should do a proper redirect.

Also ensure all your internal links and assets (images, etc) are https - this avoids any confusion and mixed content warnings.

Register both sites on webmaster tools (or google search console as it's now called)
 
Status
Not open for further replies.
Top Bottom