Verb

Docs

The assistant does not show up on my website

You signed up, added the script tag, and the assistant is missing or will not answer on your real website. Five things cause this, and the first two cover nearly every new account. Go down the list in order.

1. The script tag still has the test key

Every site comes with two keys. The test key starts with site_test_ and only answers on localhost, inside your app on your own computer. On any real domain it is refused, by design, so a test key that ends up in production serves nothing.

On your website, use the live key, which starts with site_live_. It is under Keys and API on your site in the dashboard, and in the script tag the Overview gives you for going live.

The live key on your website

html
<script src="https://api.askverb.com/v1/verb.js"
        data-verb-site="site_live_..." defer></script>

2. The domain is not verified yet

The live key only answers on domains you have verified, so a copied script tag on somebody else's site serves nothing. Until yours is verified, the assistant is refused on it too.

  • Open your site in the dashboard and go to Settings, then the domains.
  • If your domain shows seen, the script tag was spotted running there: one click confirms it.
  • If it is not listed, add it, then prove it is yours with a meta tag, a DNS TXT record or a file, and press verify. A DNS record can take a while to show up.
The address has to match exactly. www.yourapp.com and yourapp.com are two different domains, and so are http:// and https://. Add every address your users actually open, such as app.yourapp.com if that is where they sign in.

3. The tag is on one page, or not deployed

Put the script tag in your root layout, the template every page shares, not on a single page. Then check it is in what you deployed: view the page source of your live site and search for verb.js. If it is not there, the change has not shipped.

4. A Content-Security-Policy is blocking it

If your site sends a Content-Security-Policy, the browser can block the script without any visible error on the page. Add api.askverb.com to script-src and connect-src. Many apps only send a policy in production, which is why it can work locally and not on your website. Troubleshooting has the Next.js nonce case.

5. The site is switched off

An archived site answers with "The assistant is switched off on this site." Restore it from the site's Settings. Nothing was deleted while it was off. Archiving

Tell which one in a minute

Open your website, open the browser's developer tools (F12), and look at the Console and Network tabs while the page loads.

  • No request to `verb.js` at all: the tag is not on this page or not deployed (3).
  • `verb.js` blocked, or a CSP error naming askverb.com: the Content-Security-Policy (4).
  • A 403 saying the origin is not allowed: the test key on a real domain (1), or a domain not verified, or verified under a different address (2).
  • It loads and says it is switched off: the site is archived (5).

Still stuck

Write to vishnu.ps@askverb.com with your website's address and your site's name in the dashboard. I will look at it with you.

Stuck on something this does not cover? Write to us and you reach the person who built it.