GitHub Community
Replies: 2 comments 2 replies
-
|
Hi @tjtanjin I'm facing a similar problem. Checkout this Stackoverflow Answer Also checkout this Google Support Discussion |
Beta Was this translation helpful? Give feedback.
-
|
Hey @thecodeinfluencer, Thank you for raising that you're facing the same issue. I actually came across that stackoverflow answer before but in this case it's specifically the |
Beta Was this translation helpful? Give feedback.
-
I didn't catch that 😂. I've also scoured the internet looking for a solution although my npm package is just about a month old today. My conclusion is that maybe npm has a hand in this. There's a possibility that they are disabling indexing for packages that do not have many weekly downloads by automatically setting the |
Beta Was this translation helpful? Give feedback.
-
|
I would actually accept the explanation if it was intentionally set based on downloads etc. However, I've found packages with 0 weekly downloads still searchable on google. That seems to make the argument that indexing is based on downloads mute. Having had an extensive email exchange with support, the feeling I'm getting is that they're either ignoring or simply not understanding that At one point, they suggested I rename my package because I had At this point, I've kind of resigned to fate that there's some mysterious reasons for the package not being indexed. I just hope things could have been more transparent but it is what it is. Instead of wasting my time with this, I've moved on to improve my package in other ways and letting its quality speak for itself 🎈 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hey everyone, I understand this may not be the best place to seek help for my issue but I'm genuinely running out of options. Slightly over half a year ago, I published a package on npm. To date, the package has yet to be indexed for google search as can be seen from the results below:
I've reached out to the npm support team, who pointed me to the google community which I have started a discussion here. The helpful peeps in the community then highlighted to me that my package had the
x-robots-tag: noindexset and search engines were thus not indexing my package.I went back to the npm support team with said information, but after numerous back and forth conversations, the team insist that I reach out to search engine providers and that there was nothing they could do on their end. At one point, they suggested it could be due to the fact that my package had "bot" in it and that I should change my package name. I'm a little jaded by the response, as
x-robots-tagis something only the site owner can change.Eventually, the support team said this was out of their scope and insisted I continue to reach out to search engine providers (who are just following the
x-robots-tagset). I've hopped over to look at the npm discussions, but activity there is extremely low and it doesn't feel like I'd be able to receive help there. Seeing as npm is under GitHub, I thought posting here might be worth a try especially since people here are generally more active.If there's anyone who can assist with this matter, or even just point me to the correct team/place to seek help, I'll be very grateful. It's been demoralizing trying to get this issue resolved. Thank you for reading all this way!
Edit: I should surface that if npm has rules in place for packages and intentionally set
x-robots-tagfor my package, I'd definitely accept their reasons. The fact support team could not point out what's wrong and made uncertain suggestions like change package name and continuously lookover thex-robots-tagsuggest otherwise - could be a bug?Beta Was this translation helpful? Give feedback.
All reactions