Google isn’t indexing my dynamically generated pages :/
I set up a Next.js application and submitted my sitemap to Google for indexing. Although the indexing process seemed to go through, none of the 555 pages have been indexed yet.
I’ve checked the search console, but there are no specific error messages, and it’s been almost a month since I submitted the sitemap. I did find an issue on my main page where the ‘noindex’ meta tag was present, but after changing it to ‘index,’ I’ve waited a week without any results. I even consulted an SEO expert from Twitter, but their attempts didn’t yield any success either :/
Could anyone provide guidance on how to ensure that my dynamically generated pages are indexed by Google? Thank you!
One response to “Google Isn’t indexing my pages generated through dynamic sitemap :/”
It sounds frustrating to deal with indexing issues after your efforts to optimize your Next.js application. Here are several steps you can take to troubleshoot and resolve the problem:
Verify Robots.txt: Check your
robots.txtfile to ensure it doesn’t block Googlebot from crawling your pages. You can do this by visitingyourdomain.com/robots.txtand looking for any disallow directives that may affect your pages.Check Sitemap Structure: Ensure that your dynamic sitemap is correctly formatted and adheres to the sitemap XML protocol. Each URL should include the proper XML tags, and URLs should be crawlable.
Test with URL Inspection Tool: Use the URL Inspection Tool in Google Search Console to check individual pages. This can provide insights on whether the pages can be crawled and indexed. It may also reveal issues like blocked resources or other indexing problems.
Check for Console Errors: Since you’ve mentioned the ‘noindex’ tag was removed, ensure that there are no errors in the console that may be causing issues. Use the browser’s Developer Tools to check for 404 errors or blocked resources.
Ensure Content Quality: Google values quality content. Make sure your pages have unique, valuable content. Low-quality or duplicate content can lead to not being indexed.
Use Server-Side Rendering: Since you’re using Next.js, ensure that your pages are being server-side rendered correctly. Google can have difficulty crawling pages that require excessive JavaScript to render content.
Monitor for Crawling Activity: Check the “Coverage” section in Google Search Console to see if your pages are appearing as “Crawled but currently not indexed.” This can provide further insights into the reason they’re not being indexed.
Fetch as Google: Use the “Fetch as Google” feature to test how Google sees your pages. If your pages aren’t rendering correctly, it might indicate an issue with your server-side rendering or routing.
Check Server Health: Ensure your server responds quickly and reliably. Excessive downtime or slow response times can hinder Google’s ability to crawl your site.
Build Backlinks: Consider promoting your pages through social media or aiming to get backlinks from other reputable sites. This can help Google discover and prioritize your pages.
Patience and Re-index Requests: After making changes, you can ask Google to re-crawl specific URLs through the Search Console. However, patience is key, as indexing can still take time.
If you’ve followed these steps and are still having issues, it might be worth seeking a second opinion from another SEO expert who specializes in technical SEO, particularly with Next.js applications. Good luck!