Several high-traffic packages not indexed by Google

[ealmansi]

🏷️ Discussion Type

Bug

Body

Hi,

I’ve noticed that a number of long-published, actively maintained packages with millions of weekly downloads don’t show up in Google searches. A site:npmjs.com search for the exact package name returns nothing. Other packages, including ones from the same publishers, are indexed fine, so this doesn’t look like a problem with the packages themselves.

Not indexed:

postcss-font-variant (~2.5M weekly downloads)
https://www.google.com/search?q=site:npmjs.com%20%22postcss-font-variant%22
https://www.npmjs.com/package/postcss-font-variant

@appium/schema (~1.2M weekly downloads)
https://www.google.com/search?q=site:npmjs.com%20%22%40appium%2Fschema%22
https://www.npmjs.com/package/@appium/schema

set-interval-async (~600k weekly downloads)
https://www.google.com/search?q=site:npmjs.com%20%22set-interval-async%22
https://www.npmjs.com/package/set-interval-async

A few more I found: math-interval-parser, es-content-type, @tinyhttp/cors

Indexed, same publishers as the above:

postcss-calc
https://www.google.com/search?q=site:npmjs.com%20%22postcss-calc%22
https://www.npmjs.com/package/postcss-calc

@appium/base-plugin
https://www.google.com/search?q=site%3Anpmjs.com%20%22%40appium%2Fbase-plugin%22
https://www.npmjs.com/package/@appium/base-plugin

elen
https://www.google.com/search?q=site:npmjs.com%20%22elen%22
https://www.npmjs.com/package/elen

I understand that npm doesn’t control Google’s indexing. But since this seems widespread, and it’s hitting packages with very large download counts, I suspect it’s related to how npmjs.com is configured (CDN or bot-protection rules, rate limiting, headers, etc.) rather than anything on the package side. This may be related, though I can’t say whether it applies to you: https://www.searchenginejournal.com/report-that-cloudflare-ai-bot-blocking-prevents-googlebot-from-indexing-sites/584673/

I’m the publisher of set-interval-async listed above, so if it would help to test something on an affected package (a readme change, for example), I’m happy to do that.

I’m reaching out since I can't really troubleshoot from the outside - e.g. internal request logs for Googlebot or use Search Console’s URL Inspection tool would be helpful to understand the issue.

Thanks for taking a look,
Emilio
https://www.npmjs.com/~ealmansi

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ronitgupta138]

You're spot on suspecting bot-management and crawl budget changes.

Over the past year, Cloudflare bot-management updates and anti-scraping protections rolled out on high-traffic npm registry paths have intermittently challenged Googlebot requests with JS execution challenges or 403s on certain package endpoints.

Because npm uses client-side rendering for package pages, if Googlebot's headless renderer gets blocked by an edge challenge or hits a timeout during peak crawl bursts, Google drops the URL from the index.

If you have access to Google Search Console for any domain linking to your packages, running 'URL Inspection > Test Live URL' can confirm whether Googlebot is getting blocked by a WAF challenge or if it's receiving a clean 200 HTML snapshot.