Newly published npm package is not appearing in npm search results

[Farimah71]

🏷️ Discussion Type

Question

Body

Hello npm community,

I recently published a new package to npm, but I noticed that it is not appearing in npm search results.

Package:
https://www.npmjs.com/package/seo-engine

The package is available directly, and installation works correctly:

npm install seo-engine

I can also retrieve package information successfully:

npm view seo-engine

However, searching for the package does not return any results:

https://www.npmjs.com/search?q=seo-engine

The package was published successfully, so I am wondering if this is expected behavior for newly published packages or if there is any additional configuration required for npm search indexing.

Has anyone experienced a similar issue? Is there usually a delay before a new package becomes searchable?

Thanks in advance for any guidance.

[v-ember]

Hi @EnzoSCH1 , thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

We’ll be hiding this post for now. Any repeat and future violations may result in a temporary or indefinite block from the Community.

We appreciate your understanding.

[Arpitha2697]

Hi @[Username],

Yes, this is completely expected behavior!

When you publish a new package, it is immediately uploaded to the main npm registry (which is why npm install and npm view work right away), but the search index is updated asynchronously on a separate pipeline.

Here is why it happens and what to expect:

1. Indexing Delay: The npm search index usually takes anywhere from a few hours up to 24–48 hours to process and reflect newly published packages.
2. Quality Checks: npm runs automated scans (checking for spam, typosquatting, and basic metadata like description and keywords in your package.json) before listing packages in public search.
3. No Action Needed: You don't need any special configuration. As long as your package.json includes clear keywords and a description, it will automatically appear in search results once the indexer catches up.

Give it a little time, and it should show up soon!

[v-ember]

Hi @Arpitha2697 , thanks for participating in GitHub Discussions!

Please note: we’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team. 

You can read our updated Code of Conduct and the announcement for more details.

Please feel encouraged to continue engaging in Discussions as your authentic self though. We appreciate you being a part of the Community 🌟

[initial-d]

Yes, this can happen for a newly published npm package.

npm install seo-engine and npm view seo-engine hitting the package successfully means the package exists in the npm registry. The website search page is backed by a separate search index, so it can lag behind the registry after a new publish.

I would not keep unpublishing/re-publishing or changing versions just to force it. I would check these instead:

• make sure the package is public
• make sure package.json has a clear description and keywords
• try npm search seo-engine as well as the website search
• wait for the search index to catch up

If it is still missing after 24-48 hours while npm view seo-engine continues to work, then it is probably an npm search-indexing issue rather than a package configuration issue, and I would contact npm support with the package URL and publish time.