fix(blog): strip query string and hash from SEO canonical and JSON-LD URLs (#1645)

Requests arriving with ?utm_source=..., ?page=2 or a #hash were leaking
those into the canonical link, the BlogPosting/Blog url and
mainEntityOfPage, and the BreadcrumbList items emitted by SeoBlogPost
and SeoBlogPostListing. Normalize in withCanonicalBase so every emitted
URL is origin + pathname only, both with and without a configured
canonicalBaseUrl. Relative URLs without a base still pass through
unchanged.

Co-authored-by: decobot <capy@deco.cx>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: 3 people

blog/utils/jsonLD.ts

@@ -25,15 +25,22 @@ export const toOrganization = (publisher: Publisher) => ({
 });
 
 /**
- * Replaces the origin of a URL, keeping path, query and hash. Relative URLs
- * are resolved against the canonical base.
+ * Normalizes a page URL for SEO use (canonical and JSON-LD): strips the query
+ * string and hash, keeping only origin + pathname, and replaces the origin
+ * with the canonical base's when one is configured. Relative URLs are
+ * resolved against the canonical base; without a base, relative URLs are
+ * returned unchanged.
  */
 export const withCanonicalBase = (url: string, canonicalBaseUrl?: string) => {
   if (!canonicalBaseUrl) {
-    return url;
+    if (!URL.canParse(url)) {
+      return url;
+    }
+    const { origin, pathname } = new URL(url);
+    return origin + pathname;
   }
-  const { pathname, search, hash } = new URL(url, canonicalBaseUrl);
-  return new URL(pathname + search + hash, canonicalBaseUrl).href;
+  const { pathname } = new URL(url, canonicalBaseUrl);
+  return new URL(pathname, canonicalBaseUrl).href;
 };
 
 /**