Implemented dynamic sitemap, still facing indexing issues?

Author
Aarti Yadav Author
|
23 hours ago Asked
|
3 Views
|
2 Replies
0

hi everyone,

  • just wanted to follow up on the dynamic sitemap discussion from before. i got it working for my laravel app, really helpful!
  • now, i'm checking google search console and it seems like i'm still seeing some weird indexing issues. some pages are "crawled - currently not indexed" even though they're in the sitemap. it's making me scratch my head about my overall Google indexing efforts.
  • i'm not sure if i missed something in the implementation or if it's something else entirely. maybe a setting i overlooked?
  • here's a snippet from my search console, it looks a bit confusing:
    Page indexing\nNot indexed: 15\n    Crawled - currently not indexed: 10\n    Discovered - currently not indexed: 5\nIndexed: 30
  • is there like a common mistake noobs make after setting up a dynamic sitemap that causes this? what should i check next for these `indexing issues`?
  • anyone faced this before?

2 Answers

0
Iman Ndiaye
Answered 10 hours ago
  • The distinction between "Crawled - currently not indexed" and "Discovered - currently not indexed" is critical for troubleshooting your Google indexing issues. They indicate different stages in Google's processing pipeline and require distinct approaches.

    • "Crawled - currently not indexed" means Google has visited the page, processed its content, but decided not to add it to its index. This usually points to issues with the page's quality, value, or perceived uniqueness.
    • "Discovered - currently not indexed" means Google knows about the page (likely from your sitemap or internal links) but hasn't yet crawled it. This often relates to crawl budget, internal linking structure, or Google not perceiving the page as high priority for immediate crawling.
  • Hereโ€™s what to check next for these specific indexing issues after implementing your dynamic sitemap:

    • For "Crawled - currently not indexed" pages:
      • Content Quality and Value: Google prioritizes high-quality, unique, and valuable content. Review these pages for thin content, duplicate content (even internal duplication), or content that offers little to no unique value to users. Ensure your Laravel application generates rich, user-centric content.
      • On-Page SEO Factors: While not a direct indexing blocker, poor on-page SEO factors like missing or poorly optimized title tags, meta descriptions, and headings (H1, H2) can signal lower quality to Google.
      • User Experience (UX): Pages with a poor user experience (e.g., slow loading, intrusive ads, broken layouts, mobile unfriendliness) can be de-prioritized for indexing.
      • Canonicalization: Double-check that your canonical tags are correctly implemented, especially for pages that might have multiple URLs (e.g., pagination, filtered results). Incorrect canonicalization can lead Google to ignore the intended version.
    • For "Discovered - currently not indexed" pages:
      • Internal Linking: Strengthen the internal link structure to these pages. If Google isn't crawling them, it might be because they are deep within your site's architecture and not receiving enough internal link equity. Ensure important pages are easily reachable within a few clicks from the homepage.
      • Crawl Budget Optimization: For larger sites, Google's crawl budget can be a factor. Ensure your robots.txt isn't blocking essential resources, and that pages you don't want indexed (e.g., admin pages, search results pages) are properly disallowed or noindexed to conserve crawl budget for important content.
      • Server Response Times: Slow server response times can reduce Google's ability to crawl many pages efficiently. Optimize your Laravel application's performance and server configuration.
      • Sitemap Accuracy and Freshness: While you have a dynamic sitemap, confirm it's always up-to-date, contains only canonical URLs you want indexed, and doesn't contain any 404 or redirected URLs.
    • General Checks for both statuses:
      • noindex Tag: Verify that none of these problematic pages accidentally have a <meta name="robots" content="noindex"> tag or an X-Robots-Tag: noindex HTTP header. This is a common oversight.
      • robots.txt File: Ensure your robots.txt file is not disallowing Googlebot from crawling these pages or any critical CSS/JS resources they rely on.
      • Manual Action / Security Issues: Check the "Manual actions" and "Security issues" sections in Search Console. While less common for general indexing, these can severely impact your site's visibility.
  • The snippet from your Search Console is fairly standard. The key is to address the underlying reasons Google isn't indexing those specific URLs. Use the URL Inspection Tool in Search Console for individual problematic URLs to get more specific details on why they might not be indexed.

Have you specifically checked the "Page experience" report in Search Console for these non-indexed pages?

0
Aarti Yadav
Answered 7 hours ago

Oh nice, this breakdown between crawled/discovered is super helpful! ngl, I think a lot of times for the 'crawled but not indexed' stuff, it just comes down to Google deciding the page isn't valuable enough for actual users, even if all the technicals are fine.

Your Answer

You must Log In to post an answer and earn reputation.