Errors in `Metadata`: Configured but unable to recogonize it

[coderrshyam (Shyam Verma)]

Metadata is setup correctly in root layout.tsx and did not overwritten by page or any other layout, but there is unable to visualize it by browser, og checker like opengraph.xyz and even vercel itself. The metadata is successfully compiled and able to see them in head tag but unable to reconised.

This is only happens for / page only other remains pages having issue.

Code configuration

// layout.tsx

export const metadata: Metadata = {
  title: {
    default: siteConfig.shortDescription,
    template: `%s | ${siteConfig.name}`,
    absolute: siteConfig.notFoundText,
  },
  metadataBase: new URL(siteConfig.url),
  description: siteConfig.description,
  applicationName: siteConfig.name,
  icons: { icon: "/favicon.ico", apple: "/logo-192x192.png" },
  authors: [{ name: "Shyam Verma", url: siteConfig.url }],
  category: "Information & Technology",
  creator: siteConfig.name,
  keywords: siteConfig.keywords,
  openGraph: {
    locale: "en_US",
    type: "website",
    title: siteConfig.shortDescription,
    url: siteConfig.url,
    siteName: siteConfig.name,
    description: siteConfig.description,
    images: [
      {
        url: `${siteConfig.url}/og.png`,
        width: 1200,
        height: 628,
        alt: siteConfig.shortDescription,
        secureUrl: siteConfig.url,
      },
    ],
  },
  twitter: {
    card: "summary_large_image",
    title: siteConfig.name,
    description: siteConfig.description,
    images: [`${siteConfig.url}/og.png`],
    creator: "@coderrshyam",
    site: siteConfig.url,
  },
  appleWebApp: {
    capable: true,
    statusBarStyle: "black-translucent",
    title: siteConfig.name,
  },
  manifest: "/manifest.json",
};

// site.ts

export const siteURL =
  process.env.NODE_ENV === "production" ? "https://www.coderrshyam.tech" : "http://localhost:3000";
export const notFoundText = "404: This page could not be found.";
export const siteName = "CoderrShyam";
export const siteDescription =
  "I am Shyam Verma, a full stack web developer & a web designer also.";
export const siteShortDescription = "CoderrShyam - A Professional Web Developer";

export const siteConfig = {
  name: siteName,
  description: siteDescription,
  url: siteURL,
  shortDescription: siteShortDescription,
  notFoundText,
  keywords: [
    "coderrshyam",
    "shyam verma",
    "web developer",
    "web designer",
    "full stack developer",
    "next.js",
    "react",
    "node.js",
    "express.js",
    "mongodb",
    "tailwind css",
    "typescript",
    "javascript",
    "html",
    "css",
    "web development",
    "web design",
  ],
};

Framework: Next.js 15.3.1
URL: https://www.coderrshyam.tech
I had also asked this issue from v0 but i am not able to resolve it.

Please help!

Thanku.

[system]

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

If you’re having trouble deploying an Express app, this guide can help.

How to Deploy an Express.js Application to Vercel

You can also ask v0 for suggestions tailored to your own project setup.

[coderrshyam (Shyam Verma)]

Hey! Please help me, I am working on a serious project and this issue doesn’t resolve yet.

[stefathanasoulias-99 (stef.ath)]

I have the same issue. Have we found any solution for this one?

[coderrshyam (Shyam Verma)]

No! Still not. I tried to find solution but not

[stefathanasoulias-99 (stef.ath)]

I tried almost everything. I dont know why the metadata won’t work. Fun fact if you test your metadata on /blog they are working fine. i test them in your website too @coderrshyam

[coderrshyam (Shyam Verma)]

Yes, I know that metadata works fine for all routes except /, /terms-of-service, and /privacy-policy. However, I noticed something: if a layout is used inside a route group (e.g., (abcd)), and the page is also within that group, it seems to cause an error — at least that’s what I think is happening.