Help!!! About URL 301

[robin222]

Before my website URL is https://domain.com, because Cloudflare routing is not enabled properly in the absence of www. Because I changed the URL to https://www.domain.com without reconsideration and rewritten it.
Since I suddenly thought about changing the URL, the page that caused the index was lost, causing the ranking to drop, so I changed the URL to https://domain.com again without WWW.
This lasted for less than 12 hours, so I wanted to know if I would change the 301 redirect URL back and forth. Will it affect my page index invalidation and the ranking will drop dramatically?

 

[Mr Positive]

Normally it should not effect but ask your host to properly set it up for you and then cache it from web console it shall work just fine

 

[robin222]

Normally it should not effect but ask your host to properly set it up for you and then cache it from web console it shall work just fine

Hi, buddy:This means that I am reverting to my original URL without www, namely: https://domain.com, can it be? No impact? right?

 

[IamNRE]

Don't keep changing it.

You should have just kept it the with www, instead of panicking and going back.

But whatever you do now, stop changing things. Just leave it and don't touch it, and pray to jebus, or buddha or allah or whoever you pray to. Fingers crossed bro.

 

[praetserge]

Stop changing your url's.
google is relatively slow nowadays and of course your ranking will jump up and down and you'll have different pages in search engines. So it's a very bad idea to keep changing the url structure.

 

[robin222]

Stop changing your url's.
google is relatively slow nowadays and of course your ranking will jump up and down and you'll have different pages in search engines. So it's a very bad idea to keep changing the url structure.

In 12 hours, I restored the URL to the original https://domain.com without WWW. And the index URL format of my website on Google is also: https://domain.com
Does this situation mean that there will be no problem?

 

[robin222]

Don't keep changing it.

You should have just kept it the with www, instead of panicking and going back.

But whatever you do now, stop changing things. Just leave it and don't touch it, and pray to jebus, or buddha or allah or whoever you pray to. Fingers crossed bro.

In 12 hours, I restored the URL to the original https://domain.com without WWW. And the index URL format of my website on Google is also: https://domain.com
Is it ok? thanks

 

[praetserge]

In 12 hours, I restored the URL to the original https://domain.com without WWW. And the index URL format of my website on Google is also: https://domain.com
Does this situation mean that there will be no problem?

maybe, google has pages with and without WWW... just give it some time and eventually every single page will be https://domain.com. Just don't change it anymore.

 

[SirLouen]

Stick to one as some others have suggested. It doesn't matter if you go to www or non-www
Get a sc domain profile in Search Console to avoid having to upload multiple sitemaps
And just do the 3 common 301 redirects whatever you choose, all that end in the https version of the www you have chosen.

By the way, your problem with cloudflare is not about www but your own lack of knowledge about its configuration
Read the docs properly. Using www or non-www is completely indiferent for a well done route pattern matching in CF
Some examples: https://developers.cloudflare.com/workers/archive/api/route-matching/

 

[robin222]

Stick to one as some others have suggested. It doesn't matter if you go to www or non-www
Get a sc domain profile in Search Console to avoid having to upload multiple sitemaps
And just do the 3 common 301 redirects whatever you choose, all that end in the https version of the www you have chosen.

By the way, your problem with cloudflare is not about www but your own lack of knowledge about its configuration
Read the docs properly. Using www or non-www is completely indiferent for a well done route pattern matching in CF
Some examples: https://developers.cloudflare.com/workers/archive/api/route-matching/

buddy, many thanks! i'm see it!