Https vs http two different domains?

[GardenBeet]

If i visit mywebsite.com.au, www.mywebsite.com.au and http://www.mywebsite.com.au - i get one website

BUT if I visit https://www.mywebsite.com.au  I get a different website - I also get a untrusted website warning

The logo in the bottom right of the https: website is the name of the webdesigner  where the website is hosted.

Is this a normal practice?

[eglove]

No, it's not. Without an example I'd say you just don't have HTTPS set up properly.

[GardenBeet]

if you go to

ryanyoungdesign.com.au

you will see it is different from

https://www.ryanyoungdesign.com.au

[Alick300]

Hi,

In my limited understanding I think you haven't taken SSL. Not only your site you can check for any other website who haven't taken SSL you will get same errors so you don't need to worry about it.

(In below paragraph I'm not trying to promote my website . It is just an example to explain. If I'm violating any guideline by doing so moz staff can edit/delete this post)

I'm giving example of my website signwaves.co.uk  if you open this website it will redirected to https version.

Now coming to second part of your question though I'm not seeing any logo but I understand your concern.

"The logo in the bottom right of the https: website is the name of the webdesigner  where the website is hosted.

Is this a normal practice?"

Yes web designer/development company put their logo on usually every site designed /developed by company . You can ask them to remove or if they don't It won't affect too much to you as far as SEO is concern but It does affect to webdesign company because they are getting loads of backlink on same anchor text and getting links from every page of website.

I hope it helps you.

Thanks

[Bob_van_Biezen]

Dear Felicity,

From what I'm seeing on https://www.ryanyoungdesign.com.au the 443 port isn't configured correctly. This is the standard HTTPS port. There are either two options:

1. The 443 port is set up, but is requesting the wrong files.

2. The 443 port isn't configured at all and picks up the first files it finds.

Either way you will have to ask your webdevelopment company to fix this and make sure they set up the 443 port to process the right files.

Hope this helps!

[GardenBeet]

Hi Bob

Thank you! Can I ask another question?

I have since found that the url https://www.ryanyoungdesign.com.au has been indexed by the Moz bot and has a Moz score of 30. The url https://ryanyoungdesign.com.au has also been indexed and has a score of 28.  The page http://ryanyoungdesign.com.au also has a score of 30. Please refer to attachment

We recently moved the website from one server provider to another - the latest server provider never set up a https for the website. Given the https has its own MOZ ranking does this mean the original server provider set up a https version?

FYI - this was the reply of our new current server host when I pointed out the redirect

'Yes, this is a known issues with Nginx. We are looking at a resolution.There should be no backlinks linking to the SSL version of the site - this would cause an error anyway'

they also stated that ...You don't want to be ranking the https. Not sure why it would be ranked - I would disallow it in your robots.txt if it's an issue.'

EpjMw7U

[Bob_van_Biezen]

Ofcourse!

I think your website isn't ranking on HTTPS at the moment. I couldn't find any HTTPS urls when I used the site:https://ryanyoungdesign.com.au command in Google.

Also, I don't think you have any backlinks pointing at the HTTPS domain. When I check your backlinks MOZ is automaticly showing the results of the HTTP version (see notice in Open Site Explorer on top). When I manualy ask for the links of the HTTPS domain I still get links that point to the normal HTTP domain (I checked a few manualy). So I think there isn't much of a problem there. Althrough I'm curious, were did you get the list that you included? I Couldn't replicate it through Open Site Explorer.

Your latest server provider is right about not setting up HTTPS. That's exaclty were the problem is. Every website has a 443 port and if the server provider doesn't do anything with it it will automaticly search the first configured 443 port. In this case it found the port of a other website on the server that does has HTTPS set up.

Disallowing it in the robots.txt file won't solve the issue of showing a different website. Your server provider should configure this by either showing a blank page (404) or by requesting the HTTP folder through the 443 port. I would prefer the second option since it's the most user friendly.

Hope this helps!

[GardenBeet]

ahh...thank you for your time

I track the website in MOZ tools - that is where the list came from - it is a screen shot.

Perhaps a MOZ staff member can shed some light on the issue?

I could not replicate it either.

Confused ?!?