OPS-007low SeverityProduction Deployment & Launch Hygiene

Canonical URL Configured on All Major Landing Pages

Search engines see duplicate content penalties when both www and non-www or trailing slash versions of URLs are indexed.

1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Canonical URL Configured on All Major Landing Pages" (OPS-007).
Issue: Search engines see duplicate content penalties when both www and non-www or trailing slash versions of URLs are indexed.
Remediation required: Specify metadataBase in layout.tsx and add alternates: { canonical: "./" } to ensure consistent indexing.

Please:
1. Locate any occurrences of this issue across my repository.
2. Refactor the code to follow production standards without breaking existing functionality.
3. Provide a clear command or step to test and verify the fix.

Why AI Assistants Write This Bug

Search engines see duplicate content penalties when both www and non-www or trailing slash versions of URLs are indexed.

AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.

Code Comparison

Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Canonical URL Configured on All Major Landing Pages
// Problematic pattern: Search engines see duplicate content penalties when both www and non-www or trailing slash versions of URLs are indexed.
Launch-Ready Fix
// Production-ready fix for: Canonical URL Configured on All Major Landing Pages
// Recommended remediation: Specify metadataBase in layout.tsx and add alternates: { canonical: "./" } to ensure consistent indexing.

Remediation & Verification Checklist

Remediation: Specify metadataBase in layout.tsx and add alternates: { canonical: "./" } to ensure consistent indexing.
  1. Search your codebase for pattern matching "Canonical URL Configured on All Major Landing Pages".
  2. Apply the recommended remediation: Specify metadataBase in layout.tsx and add alternates: { canonical: "./" } to ensure consistent indexing.
  3. Run local build and test commands to ensure no regressions.
  4. Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click

Checking items one by one takes hours. Let us do it in 2 minutes.

With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.