u/Jazzlike_Repair5017

Issues with indexing after moving from WordPress to Next.js

Hey everyone,

I’m working on a project that was migrated from WordPress to Next.js a few months ago, and I’ve been running into an issue since then.

After the migration, only the homepage is showing up in search results, while the rest of the pages aren’t getting picked up at all.

Before the migration, multiple pages were indexed and working fine.

The site has a lot of dynamic pages, and everything seems accessible when opened normally. Basic checks like sitemap, robots.txt, and meta tags look okay.

One thing I noticed is that some pages seem to fall back to client-side rendering instead of being fully rendered on the server.

<div hidden="">
        <!--$-->
        <!--/$-->
        </div>
        <!--$!-->
        <template data-dgst="BAILOUT_TO_CLIENT_SIDE_RENDERING"></template>
        <!--/$-->
        <!--$?-->
        <template id="B:0"></template>
        <div class="page-loader-overlay" aria-hidden="true">
            <div class="page-loader-spinner"></div>
        </div>
        <!--/$-->
        <script>
            requestAnimationFrame(function() {
                $RT = performance.now()
            });
        </script>

So I wanted to ask:

  • Has anyone faced indexing issues after moving to Next.js?
  • Does client-side rendering fallback affect how pages get picked up?
  • Do you usually force SSR/SSG for better crawlability?
  • Any practical way to verify what bots are actually seeing?

Would appreciate hearing how others are handling this in real projects.

Thanks!

reddit.com
u/Jazzlike_Repair5017 — 3 days ago