package listing not indexed by google?

[theoephraim]

Select Topic Area

Question

Body

How often is google indexing NPM package listings? Do pages ever get accidentally blocked from being indexed?

I'm unclear as to why, but when I search for my package name "varlock" and "npm" it does not come up in the results, although other related packages do, and some packages with similar but not quite matching names. It seems to me that google has blocked indexing of this page for some reason...

This is not a brand new package, and there are plenty of other related hits coming up outside of NPM, so it really seems that indexing has been blocked for some reason.

Thanks!

[theoephraim]

In general we are pretty good about all of these things. We push updates regularly, have backlinks in many places including a proper docs site, etc... I did notice that my main package is missing a description, and thought that maybe packages without a description were excluded from the index, but further digging reveals that is not the case.

We have many packages published from our monorepo including integrations for many frameworks.

Interestingly searching for site:npmjs.com varlock astro does yield the correct result, while site:npmjs.com varlock nextjs does not. The nextjs integration is actually older, more used, and I believe has more backlinks.

So it sure seems like something is blocking these pages from being indexed at all.

[theoephraim]

Following up here - this sure seems like a bug. Our package has been out for many months and is having significant usage, but is still not indexed by google. Would love someone to do a quick check to verify what is blocking it.