www/non-www redirect is configured

Serving identical content at both www.yourdomain.com and yourdomain.com splits link equity between two URLs, creating duplicate content that Google may rank separately or penalize. Social shares, backlinks, and analytics fragment across hostnames, distorting traffic attribution. Users bookmarking the wrong variant land on an inconsistent canonical, and session cookies scoped to one host break authentication on the other.

Pick one canonical hostname and issue a 301 from the other. In next.config.js, add a redirects() entry with a host match on www.yourdomain.com targeting the root domain with permanent: true. Alternatively, configure the redirect at the hosting layer via vercel.json or Netlify's domain settings — whichever lives closer to DNS.

// next.config.js
async redirects() {
  return [{ source: '/:path*', has: [{ type: 'host', value: 'www.yourdomain.com' }], destination: 'https://yourdomain.com/:path*', permanent: true }]
}