38 Messages

 • 

840 Points

Saturday, August 19th, 2023

secure website facility lost

'The importance of securing your web site' rightly says how important this is. I totally rebuilt my web site using your latest Web Site Builder on the web. I was promised it would provide a secure web site. At first it did. Now using the https prefix does not work. I looked at how to secure my web site and it says "For SITEBUILDER PLUS ONLY. Do not use if you have Website Builder." So I can't do that. I am blocked. The Bing version of search console does not support http, only https so I cant even submit my web site to it so it is unlikely to find it. Google knocks ranking points off for not being https. You promised this would work, I have put many many long hours into recreating my web site and it is considered inferior by Google and is invisible to Bing. If you want to keep your customers you should stop removing vital facilities or you will lose us all eventually.

The Bing search console says it usually ignores sitemaps with all the last modified dates all set the same. As far as I can see, your software only build sitemaps with them all the same. Can I post edit the sitemap so Bing does not ignore it?

This conversation is no longer open for comments or replies and is no longer visible to community members.

Oldest First
Selected Oldest First
Brand User

11.4K Messages

 • 

148.7K Points

2 years ago

Hello, 

For WebsiteBuilder sites, these are the instructions to apply the SSL if it doesn't work automatically. 

‎WebsiteBuilder: SSL | Homestead Community

38 Messages

 • 

840 Points

When I get to Confirmation of Advanced DNS Changes I get an error message is bold red lettering saying "Changing your 'www' A Record will make your Homestead website or store inaccessible! Please verify that this action is desired before confirming. " I certainly do not want to make my web site inaccessible. What have I done wrong? I think I have followed the guidance to the letter.

Brand User

11.4K Messages

 • 

148.7K Points

You are doing it properly. That warning shows whenever DNS is edited.