SEO: No HTTP-to-HTTPS redirect or www-to-non-www canonical redirect #127

New Issue

Closed

opened 2026-05-17 21:27:44 -05:00 by null · 0 comments

null commented

2026-05-17 21:27:44 -05:00

Owner

Problem

The Express server does not redirect http:// to https:// or www.queuenorth.com to queuenorth.com. This means:

http://queuenorth.com serves the same content as https://queuenorth.com — duplicate content for SEO
www.queuenorth.com serves the same content as queuenorth.com — another duplicate

Search engines may treat these as separate sites, diluting page rank.

Fix

This should typically be handled at the reverse proxy/CDN level (Nginx, Cloudflare, etc.), not in Express. But if Express is directly exposed:

Add middleware to redirect http to https in production
Add middleware to redirect www to non-www (or vice versa)

If using Cloudflare or Nginx as a reverse proxy, configure redirects there instead.

Files

server/index.js — or configure at reverse proxy level

Severity

Medium — SEO impact from duplicate content; canonical URLs not enforced

## Problem The Express server does not redirect http:// to https:// or www.queuenorth.com to queuenorth.com. This means: 1. http://queuenorth.com serves the same content as https://queuenorth.com — duplicate content for SEO 2. www.queuenorth.com serves the same content as queuenorth.com — another duplicate Search engines may treat these as separate sites, diluting page rank. ## Fix This should typically be handled at the reverse proxy/CDN level (Nginx, Cloudflare, etc.), not in Express. But if Express is directly exposed: 1. Add middleware to redirect http to https in production 2. Add middleware to redirect www to non-www (or vice versa) If using Cloudflare or Nginx as a reverse proxy, configure redirects there instead. ## Files - server/index.js — or configure at reverse proxy level ## Severity Medium — SEO impact from duplicate content; canonical URLs not enforced