Will this create duplicate content problem?

[Axel_inferno09]

so guys the thing is i have a website which is ranked on google.. and its hosting expired and i moved to a new one. and the website was - https://abc.com and after switching hosting, i dont know how it became https://www.abc.com. I was using cloudflare before and now also i'm using cloudflare but i dont know just after switching hosting, 'www' is added when i search 'abc.com'. However, my site is ranked for https://abc.com. Will this cause any issue in ranking and all??
I have heard something like penalizing for duplicate content and all so im quite worried

and guys if you have any knowledge regarding cloudflare, how do i forward, for instance, https://abc.com to https://www.abc.com ?

P.S - abc.com is not my actual site, just an example

 

[Graybeard]

well if it works for us ...
barry@paragon-DS-7:~$ curl -I -L "Affiliate Marketing Forum | AffiliateFix"
HTTP/1.1 301 Moved Permanently
Date: Fri, 19 Apr 2019 16:43:26 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Set-Cookie: __cfduid=d913e14d6acc53eba570d23e65a9d68d91555692206; expires=Sat, 18-Apr-20 16:43:26 GMT; path=/; domain=.affiliatefix.com; HttpOnly
Location: Affiliate Marketing Forum | AffiliateFix
Cache-Control: max-age=600
Expires: Fri, 19 Apr 2019 16:53:26 GMT
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 4ca056625e1d7191-ORD

HTTP/1.1 200 OK
Date: Fri, 19 Apr 2019 16:43:27 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=d99bfc083c2dbcb1a779b28cf10fc065b1555692206; expires=Sat, 18-Apr-20 16:43:26 GMT; path=/; domain=.affiliatefix.com; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-control: private, max-age=0
X-Frame-Options: SAMEORIGIN
X-Xss-Protection: 1
Vary: Accept-Encoding,User-Agent
Set-Cookie: __uzma=5cb9faaeec2c94.48328357; expires=Mon, 16-Apr-2029 16:43:26 GMT; Max-Age=315360000; path=/
Set-Cookie: __uzmb=1555692206; expires=Mon, 16-Apr-2029 16:43:26 GMT; Max-Age=315360000; path=/
Set-Cookie: __uzmc=125521062110; expires=Mon, 16-Apr-2029 16:43:26 GMT; Max-Age=315360000; path=/
Set-Cookie: __uzmd=1555692206; expires=Mon, 16-Apr-2029 16:43:26 GMT; Max-Age=315360000; path=/
Set-Cookie: xf_session=610383362fdde5c0faf8bc2cf1ab6d4e; path=/; domain=.affiliatefix.com; secure; HttpOnly
Last-Modified: Fri, 19 Apr 2019 16:43:27 GMT
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 4ca056649f7dc50e-ORD

AffiliateFix gets a 301 to the www. (that is really a subdomain with an A AAAA >>> abc.com WHO?
A 301 moves the 'juice'

Do you need to make a CNAME in the Cloudflare DNS? @ => www.domain.com IDK?

 

[T J Tutor]

I simply set the redirect option in CPanel. Easy peeeeeeeeeeesy!

As for SEO punishments, I have not suffered any loss when setting the redirect. SEO remained for my sites when I migrated them to new servers. Of course I was able to keep the IP!

 

[MyLead]

The simplest and best solution to this problem is creating is 301 redirect, if you really want to be clear with Google and prevent duplicate, you can prevent it with informing google in Search Console, there is a feature called preferred domain.

 

[Faelmaran]

Graybeard provided way too complicated explanation with a lot more settings which not needed to be changed at all. All that settings located in .htaccess file of your web server, or you could simply ask your webhosting provider to assist you with that. They will help, really

 

[Koramisomi]

Instead of creating a problem second domain consider the simplest one redirect on .htaccess. If you feel not confortable with that, ask hosting provider, probably he'll help you.

 

[Graybeard]

Sorry, I have my own servers and use Nginx.

301 Redirect with mod_rewrite or RedirectMatch

Also read this:Difference between canonical and base tag

really there should be a canonical (base) that would be too easy
in other words you just script an injection into the head of the document;
something like
DO NOT USE
<domain="canonical" href="https://www.example.com" />
^^does not exist -- would be too ez and exact!

 

[Graybeard]

I did see something interesting last week
in the headers of a server reply:
Link: ' h ttp s://ww w.exa mple.c om/ '
Probably more confusing that helpful ...
LinkHeader - W3C Wiki
something else but interesting: https://www.rfc-editor.org/rfc/rfc5988.txt
see page 5 &6 (rather technical)
Maybe not something else altogether as the header Link: overrides any page anchor link (that was followed??)