`react-doctor/nextjs-metadata-url-consistency`

Canonical and Open Graph URLs disagree

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: nextjs
Enabled when: nextjs
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/nextjs-metadata-url-consistency. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

export const metadata = {
  alternates: { canonical: "https://example.com/docs" },
  openGraph: { url: "https://example.com/documentation" },
};

Corrected pattern

export const metadata = {
  alternates: { canonical: "https://example.com/docs" },
  openGraph: { url: "https://example.com/docs" },
};

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/nextjs-metadata-url-consistency diagnostic in the current repository. Required change: - Use the same preferred page URL for alternates.canonical and openGraph.url so search and social previews identify one page.

Reference transformation:Before:

export const metadata = {
  alternates: { canonical: "https://example.com/docs" },
  openGraph: { url: "https://example.com/documentation" },
};

After:

export const metadata = {
  alternates: { canonical: "https://example.com/docs" },
  openGraph: { url: "https://example.com/docs" },
};

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. - Confirm this rule is enabled for the project: nextjs. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Bugs rules from the rules reference:

react-doctor/nextjs-missing-metadata: Add `export const metadata = { title: '...', description: '...' }` or `export async function generateMetadata()`
react-doctor/nextjs-no-a-element: `import Link from 'next/link'` — enables client-side navigation, prefetching, and preserves scroll position
react-doctor/nextjs-no-client-fetch-for-server-data: Remove 'use client' and fetch directly in the Server Component — no API round-trip, secrets stay on server
react-doctor/nextjs-no-client-side-redirect: Avoid redirects inside useEffect. Use an event handler, middleware, or server-side redirect (App Router: redirect() from next/navigation; Pages Router: getServerSideProps redirect)
react-doctor/nextjs-no-css-link: Import CSS directly: `import './styles.css'` or use CSS Modules: `import styles from './Button.module.css'`

react-doctor/nextjs-metadata-url-consistency