Skip to content
Docs
API reference Go to dashboard
DocsWordPress & WooCommerce

WordPress & WooCommerce

WooCommerce runs on WordPress — and to Alpheris, WooCommerce is exactly that: a WordPress site. You have two ways to add the widget: the one-click connection via the dashboard, or the standard script snippet. Here you'll learn how both work and what gets synced automatically when you connect.

WooCommerce is a WordPress plugin. That's why there is no separate "WooCommerce connector" — you connect your WordPress site, and your shop is covered along with it. If you don't run a WordPress site but use Shopify instead, read the Shopify page instead.

Two Ways to Integrate

Both paths lead to the same result: the Alpheris widget appears in the bottom right of your site and answers customer questions grounded in your knowledge base. Pick whichever is more convenient:

Path 1 — One-Click Connect

The fastest way. You enter your website URL in the dashboard, get briefly redirected, and you're connected. Your domain is automatically marked as verified, a unique install ID is generated, and the knowledge base sync is kicked off.

1
Open the install page
In the dashboard, under Integration, choose the WordPress method.
2
Enter your website URL
Enter your shop's address, e.g. https://your-shop.com. With or without www both work — the www. variant is created automatically as well.
3
Confirm the connection
Click "Connect with WordPress". You'll be briefly redirected; if you're not logged in yet, Alpheris asks for your login first and then returns automatically.
4
Done
Domain verified, install ID generated, knowledge base sync started. The widget is active on your site as soon as the script line loads (see Path 2 for placement).
With the one-click flow, your domain is marked as verified without any additional DNS or file proof, because the connection is made from your logged-in dashboard. The install ID is permanently bound to this domain.

Path 2 — Script Snippet

The snippet is the universal way and works on any WordPress installation, regardless of the theme or page builder. You'll find your personal code in the dashboard under Integration → Code. It looks like this:

HTML
<!-- Alpheris Chat Widget -->
<script src="https://alpheris.com/widget.js" data-alpheris-key="INSTALL_ID" crossorigin="anonymous" async></script>
<!-- End Alpheris Chat Widget -->

Don't replace INSTALL_ID by hand — copy the ready-made code from the dashboard, where your real install ID is already filled in. The attribute is called data-alpheris-key and connects the widget to your shop.

Where the snippet belongs on WordPress

The snippet must load on every page — so the safest place is just before the closing </body> or in the global header. Common ways to do this in WordPress:

  • Theme customizer / header-&-footer plugin: Many themes and plugins (e.g. "Insert Headers and Footers"-style extensions) offer a field for global footer or header code. Paste the snippet there and save.
  • Theme file footer.php: In a child theme, insert the snippet directly before </body>. Only recommended if you're comfortable with child themes, otherwise the change is lost on the next theme update.
  • Block editor / custom HTML block: Not recommended for site-wide integration — the snippet would only load on that particular page.
WordPress and WooCommerce sites cache aggressively (caching plugins, server cache, CDN). If the widget doesn't appear after you insert it, clear the page cache and reload the page. More on this on the Troubleshooting page.

What gets synced

The first time the widget actually loads on your site (not preview mode, valid install ID), Alpheris triggers an embed sync for a WordPress connection. It pulls in your site's public content via the WordPress REST API:

SourceEndpointWhat gets imported
Pages/wp-json/wp/v2/pagesTitle and text content of every published page
Posts/wp-json/wp/v2/postsTitle and text content of every published post

The content is processed into searchable knowledge and stored in your knowledge base as a source of type wordpress_api_full. The chatbot then answers customer questions grounded in this knowledge. Which content ends up there, how you add to it, and how to upload files is covered under Data Sources & Knowledge Base.

Requirement: a reachable REST API

The sync only works if your WordPress REST API is publicly reachable. Alpheris checks this in advance via /wp-json/. If your site returns 401, 403 or 404 here (e.g. because a security plugin blocks the REST API), the embed sync is aborted with a corresponding error.

Is your site behind Cloudflare or a firewall that blocks bots? Then the Crawl Behind Cloudflare page helps. If knowledge building fails entirely, Crawl Failed is the right place to start.

WooCommerce products

Important to understand: the embed sync pulls in pages and posts via the WordPress REST API — it does not read the WooCommerce product catalog through a separate WooCommerce API. There is no native, bidirectional WooCommerce product or order connector like there is for Shopify.

Your WooCommerce product pages are still captured — as perfectly ordinary content pages of your website. So the chatbot can absolutely provide information about products based on the text, descriptions and FAQ content on those pages. What it doesn't do: pull live stock levels, real-time prices or order status from the WooCommerce database.

With WooCommerce, don't rely on real-time stock or prices in the chat. Anything that isn't written as text on a public page is unknown to the chatbot. Keep product-relevant info up to date in your page content — or upload product lists as a file (see Data Sources).

Domain & Security

When you connect, Alpheris binds the install ID to your site's verified domain. By default, strict domain mode is active: widget and chat requests are checked against the host of the embed. This means your key can't simply be misused on someone else's domain.

  • The www. variant of your domain is verified automatically as well.
  • You can add more domains in the dashboard — details under Domains.
  • You configure the privacy notice and optional per-shop consent under Security & Privacy.

Quick test after integration

1
Open your site in a private window
An incognito/private window bypasses the browser cache. The widget should appear in the bottom right.
2
Ask a real question
Ask something that's written on your pages (e.g. shipping, returns, a product). If you get a relevant answer, the knowledge base is populated.
3
No widget? Clear the cache
Clear the caching plugin, server cache and CDN, then check again. If it stays empty, Troubleshooting helps.
Is the widget still answering thinly or inaccurately? Knowledge building runs in the background on the first embed and takes some time depending on the size of your site. You fine-tune the tone and answer length under AI Agent.