1
0
Fork 0

feat(onboarding): Docsearch who can apply updated page (#2607)

* feat(v4): Docsearch who can apply updated page

* feat(v4): Includes info about new users

* Remove the messaging

---------

Co-authored-by: NatanTechOfNY <natanyagudayev@gmail.com>
This commit is contained in:
Felipe Bermudez 2025-07-02 10:53:23 -05:00 committed by GitHub
parent 2874789fad
commit 161dcdca00
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -8,38 +8,23 @@ We built DocSearch from the ground up with the idea of improving search on large
We usually turn down applications when they are not production ready or have non-technical content on the website.
## The checklist
## Application process
To have your request validated, well ask that you check all the following points.
To [apply][1] to the DocSearch program, follow the DocSearch onboarding process in the Algolia dashboard where you'll submit your domain for an automated validation check against our requirements. If your domain meets all criteria, you'll be quickly approved to proceed with creating your DocSearch crawler.
- Your website must be a **technical documentation or a technical blog**.
- ✅ Using one of our official integrations will streamline your implementation process after data ingestion.
- You must be the **owner** of the website, or at least have the permissions to update its content. You'll need to [include a JavaScript snippet][1] to your frontend to implement DocSearch.
- ✅ You must verify your domain ownership within 7 days of approval to continue using the crawler.
- Your website must be **publicly available**. We do not host search indices for websites that are only available after authentication or are hosted on a private network.
- Your website must be **production ready**. We won't index empty websites nor those filled with placeholder content. Please, wait until you have written some documentation before applying. We would be happy to help you as soon as you have a steady design.
If in doubt, don't hesitate to [apply][2] and we'll figure it out together.
Even if we cannot accept your request, this does not mean that you cannot enjoy great search on your website. Legacy DocSearch is entirely open source and [you can run it yourself][3], or use any of [our other API clients][4] to take advantage of Algolia's features.
## Priority
We're receiving dozens of requests every day, and while we strive to answer them all as fast as we can, we sometimes give priority to some based on the following criteria:
- 🙂 If you're using one of our [official integrations][5], creating your config will be much faster for us.
- 🙁 If we need to render your website in the browser through JavaScript, it means that we'll have to crawl it through a much slower browser emulation. We highly recommend that you put in place server-side rendering for the useful textual content.
- ✅ Please review [DocSearch Plan Terms and Conditions][2].
## Process duration
As stated in [the priority section](#priority), we receive a lot of requests every day. To ensure they all match [our checklist](#the-checklist), we manually review each of them, which means it can take a bit of time before you get an answer from us.
DocSearch application process includes automated validation for faster processing. However, if we can't automatically determine your eligibility, we'll conduct a manual review that may take 1-2 business days.
The full process (from application to deployment) can take **up to two weeks**, applying multiple times or opening issues **only slows the process**, please be patient 🙏.
Once approved, you can continue the onboarding process to create your DocSearch crawler. After your data is ingested into Algolia, you'll need to implement the search UI using either our provided code snippet or one of our [integrations][3].
[1]: /docs/docsearch-v3
[2]: /apply
[3]: /docs/legacy/run-your-own
[4]: https://www.algolia.com/doc/api-client/getting-started/install/javascript/?client=javascript
[5]: integrations.md
[1]: https://dashboard.algolia.com/users/sign_up?selected_plan=docsearch
[2]: https://www.algolia.com/policies/docsearch-plan-specific-terms
[3]: integrations.md
[4]: https://alg.li/discord