Choose either example.eu or www.example.eu as your main address, then send the other to it with a permanent (301) redirect, and send HTTP to HTTPS in the same way. Google does not say either form is better: it asks you to pick one canonical URL and use it consistently. For a .eu domain, the choice mainly affects DNS flexibility.

Is www or non-www better?

Google’s guidance on consolidating duplicate URLs lists https://www.example.com and other variants as versions of one page and says to pick one of them as the canonical URL.

The practical difference is in DNS. The bare domain needs an A record, while www can be a CNAME to a host’s target name. DNS record types explained shows why.

How do you set up the redirect?

Both names must resolve, so create the A record and the www record first: see how to point a .eu domain at a website. Then configure the redirect in your web server or hosting control panel, following your host’s documentation.

Use a permanent server-side redirect, 301 or 308. Google says a server-side redirect has the highest chance of being interpreted correctly, and that a permanent one makes the target the canonical URL. A temporary redirect keeps showing the source page in results.

How do you handle HTTP and HTTPS?

Google prefers HTTPS pages as canonical. It suggests redirecting HTTP to HTTPS, and warns that HTTPS-to-HTTP redirects and bad certificates make it prefer HTTP strongly.

The certificate must match the complete URL, so it should cover both example.eu and www.example.eu; otherwise the redirect itself shows a browser warning.

How do you keep the canonical URL consistent?

Use the same form in internal links, the sitemap and rel="canonical" tags. Google says linking consistently to the canonical URL helps it understand your preference, and advises against listing the HTTP version in sitemaps.

What are the common redirect mistakes?

Redirect chains. A request that goes from http://example.eu to https://example.eu and on to https://www.example.eu takes two hops. Send each variant straight to the final address. Google says Googlebot can follow up to 10 hops but recommends keeping chains short, ideally no more than 3 and fewer than 5.

Redirect loops. Two rules that send visitors back and forth, such as one adding www and another removing it, make the browser give up. Keep one rule set.

Using 302 by mistake. A temporary redirect does not tell Google the new address is permanent.

Key facts

  • Google does not rank www above non-www or the reverse: pick one and be consistent.
  • Redirect the other variant, and HTTP to HTTPS, with a permanent server-side redirect.
  • Google prefers HTTPS pages as canonical.
  • The SSL certificate must match the full URL, including www if you use it.
  • Redirect each variant directly to the final URL, not through a chain.
  • The bare domain cannot use a CNAME; www can.

Frequently asked questions

Does www affect my rankings? Google does not say so. It treats the variants as duplicates and chooses one canonical, so consistency matters more than the choice.

Should I use 301 or 308? Both mean permanent. Google lists both as permanent redirects without ranking one above the other.

Do I need to keep the redirect forever? For a site move, Google says generally at least a year. For www, keep it while the domain is used.

Can I leave both versions live? That creates duplicates: redirect one to the other.

Manage the DNS side on the DNS and DNSSEC management page. If you are changing domain, read how to move your website to a .eu domain without losing rankings, and for the underlying cache behaviour, DNS propagation and TTL.