Next.js Discord

Discord Forum

[SEO] noindex issue with CSR

Unanswered
Silky ant posted this in #help-forum
Open in Discord
Silky antOP
Hi
Several of my pages are considered 'noindex' by Google. They all have in common that they are 'use client' pages. Could 'use client' (client-side rendering) be the cause of an indexing issue in a Next.js project?

14 Replies

Silky antOP
The meta tags seem to be correctly injected on each page, and the HTML files in the build show this: <meta name="robots" content="index"/><meta name="googlebot" content="index"/> in each of the problematic pages
@Silky ant The meta tags seem to be correctly injected on each page, and the HTML files in the build show this: <meta name="robots" content="index"/><meta name="googlebot" content="index"/> in each of the problematic pages
atalay
Hello are you sure to checked everything correclty? Maybe your layouts look like this:
Silky antOP
I don't have any layout except in app/(group)/layout, and it looks like this: 
export const metadata: Metadata = {

 robots: {
    index: true,
    googleBot: {
      index: true,
    },
  },

//...
}
@atalay Hello are you sure to checked everything correclty? Maybe your layouts look like this:
Silky antOP
sorry for late reponse I was afk
Silky antOP
every noindex pages ar in app/(group)/page_name
Silky antOP
How can I check if it's working? I only see 'noindex' in Google Search Console, and it takes a long time to update
ok i will try to remove robots object in Metadata
Silky antOP
Okay, I'll do all that. Why do you think it's because of the robots object in the metadata, by the way?
@atalay you can send report to google for update their data as I know
Silky antOP
Thank you so much for your help, really. I'm just starting out, and I don't quite know what I'm doing at the moment :heartwhite:
@Silky ant Okay, I'll do all that. Why do you think it's because of the robots object in the metadata, by the way?
atalay
cuz all pages should be indexed by default no need to specify again