Common reasons for failure
Website could not be reached
Website could not be reached
Okara tries to fetch your site at the URL you entered. If the site is unreachable, the setup will fail with a message like:
“That website could not be reached.”What to try:
- Make sure the site is publicly accessible (not behind a login, VPN, or maintenance page)
- Confirm the domain is live and your DNS is resolving correctly
- If your site is hosted behind a WAF or CDN (Cloudflare, Fastly, etc.), it may be blocking OkaraBot — see Whitelisting OkaraBot below
Invalid URL format
Invalid URL format
Okara only accepts top-level domains or one level of path. Deep paths are not supported.
Do not include
| Accepted | Not accepted |
|---|---|
okara.ai | www.okara.ai |
okara.ai/product | okara.ai/blog/post/123 |
https://, query strings (?ref=...), or fragments (#section).Content could not be extracted
Content could not be extracted
Okara reads your page’s HTML to understand your business. If we can’t extract enough content, setup will fail.What to try:
- Check that your homepage has readable text in its page source (right-click → View Page Source)
- Check your
robots.txt— if it blocks all crawlers, OkaraBot won’t be able to read the page
Plan or slot limit reached
Plan or slot limit reached
- Your first website is included on all plans
- Adding a second website requires an active Max plan
- Additional slots beyond that require purchasing an add-on
Whitelisting OkaraBot
If your site sits behind a WAF (Web Application Firewall) or CDN, it may be blocking OkaraBot’s requests. Whitelist the following user agent string to allow it through:Cloudflare
Cloudflare
- Go to your Cloudflare dashboard and select your domain
- Navigate to Security > WAF > Custom Rules
- Create a rule with:
- Field: User Agent
- Operator: contains
- Value:
OkaraBot
- Set the action to Allow
- Save and deploy the rule
AWS WAF
AWS WAF
- Open the AWS WAF console and select your Web ACL
- Add a rule with a string match condition on the
User-Agentheader containingOkaraBot - Set the rule action to Allow and place it before any block rules
Sucuri / other WAFs
Sucuri / other WAFs
Look for a Whitelist or Allowlist section in your WAF dashboard. Add
OkaraBot as an allowed user agent string. Refer to your WAF provider’s documentation for exact steps.robots.txt
robots.txt
If your
robots.txt blocks all bots, add an explicit allow for OkaraBot:If you need IP ranges to whitelist or have questions, email support@okara.ai with your domain name.
Onboarding failed after the website was accepted
Sometimes the initial URL check passes but onboarding fails during analysis. Okara retries automatically up to 3 times. If it’s still failing:- Wait about an hour — a Retry button will appear on your dashboard
- Click Retry to resume from where it left off
- If retrying doesn’t help, contact support@okara.ai with your agent ID
Learn more about OkaraBot
See the OkaraBot info page for full details on how the crawler works and what it accesses.