Google Search Console and Next.js caching - "_rsc=" issue

[Antonio112009]

Summary

I have noticed an increasing number of errors in my Google Search Console related to caching in Next.js. Specifically, the error is 'Alternative page with proper canonical tag' and 98% of occurrences are related to the caching issue. I would like to know how to prevent Google from indexing pages with a URL query '_rsc='.

I tried excluding these pages from indexing by adding them to the robots.txt file, but as they are necessary pages, that approach did not work. Can someone please advise me on what I should do?

Additional information

No response

Example

No response

[nykula]

I'd also appreciate someone familiar with Next.js internals hypothesizing why Google considers the _rsc AJAX calls worthy of being compared to their equivalent public URLs despite _rsc never explicitly appearing in anyone's address bar, and whether anything can or should be done about that by developers who use the Next.js App Router and Link component or by developers of Next.js itself.

[Refrezsh]

These pages do not present any new content. The solution for myself was to add a line in Robots.txt.

Disallow: /*?_rsc=*

[Johrten]

Is this still the solution you have implemented? I added this but Google just moved to "Indexed, though blocked by robots.txt"

[Midnight-Knight]

I came across a similar issue regarding Google and Google Search Console. For some reason, Google is massively crawling pages with "_rsc" parameters in the URL, which leads to errors in identifying canonical pages, despite the fact that they are set for each one. It can also cause incorrect indexing of pages. As a result, our site has stopped being indexed in Google, although everything is fine in other search engines.

We tried to solve this problem using a file robots.txt but it had no effect.

We also tried to fix this by checking the URL parameters and using a redirect in middleware.ts, but the NextRequest does not have such a parameter, since Next removes it from the fields. For example, if the URL states "http://localhost:3000 /?__rsc=1ld0r", then in middleware the request: Next Request parameters are as follows:

{
  href: 'http://localhost:3000/',
  origin: 'http://localhost:3000',
  protocol: 'http:',
  username: ''password: '',
  host: 'localhost:3000',
  hostname: 'localhost',
  port: '3000',
  pathname: '/',
  search: '',
  searchParams: URLSearchParams {  },
  hash: ''
}

Thus, Next.for some reason, js clears these parameters. Perhaps someone has encountered a similar situation?

[dennzimm]

Have you already found a solution? Or how did you proceed with this?

[Midnight-Knight]

Hi, at the moment, it has not been possible to completely fix the problem, but there is a feeling that we are moving in the right direction. It turned out that the _rsc query parameter is not available in any way for manipulation in middleware.ts, however, you can work with it in next.config.js . The following code allows you to configure traffic redirection if the _rsc query parameter is present in the URL.

module.exports = {
  async redirects() {
    return [
      {
        source: '/',
        destination: '/',
        has: [
          {
            type: 'query',
            key: '_rsc',
          }
        ],
        permanent: true,
      },
      {
        source: '/:path*',
        destination: '/:path*',
        has: [
          {
            type: 'query',
            key: '_rsc',
          }
        ],
        permanent: true,
      }
    ]
  },
  ...
}

As a result, from 1300+ original errors related to _rsc only 402 remain at the moment. Google started indexing some pages, but they are still not showing up in the search results, so the problem hasn't been fully resolved yet.

The version is next.js - 15.1.4

[Midnight-Knight]

https://nextjs.org/docs/app/api-reference/config/next-config-js/redirects

[dennzimm]

Thanks for the info :) let's see if that helps us too. I have only seen that it is probably due to prefetch from NextLink. If I set it to false, I no longer have these requests

[kstroka]

Hello there... do you have some solution for this? I have same issue, have thousants of ?rsc= in GSC ... what is best solution from SEO point of view for us?