WordPress knowledge and recovery

What you’ll accomplish

Check what your assistants can use, understand records waiting for capacity and resolve connection interruptions.

Finish with

Useful website knowledge with clear coverage and recovery

The native WordPress integration connects your public website content through the official Chat4U Website Assistant plugin. Start with Install on WordPress.

What enters Knowledge

One WordPress connection creates one shared Knowledge source. Public pages, posts, public custom post types and published language variants are discovered automatically. Content must also be independently readable without signing in. Public fields are included only when their declared schema and anonymous REST values can be verified. Advanced processing is not required for these supplied schemas.

Drafts, future/private/password-protected posts, WordPress users, comments, form submissions and WooCommerce orders are excluded. Shared blocks and templates can cause bounded rechecks of affected rendered content. Bookings, Multisite and headless support remain unsupported. Optional store assistance is described in WooCommerce shopping and privacy and is available only when the approved module is enabled. Orders do not enter public Knowledge.

Each translation has its own stable identity and language URL in the same source. Editing or unpublishing one translation does not overwrite another or create a machine translation. Membership, builder, language, cache and security plugins can change anonymous accessibility. Check coverage and a real answer from each language you use.

How word capacity works

WordPress shares the project's existing indexed-word allowance with all its other Knowledge sources. The effective plan allowance and currently active word add-ons determine available capacity. A future add-on or an unfinished checkout does not grant space yet; an explicit unlimited allowance remains unlimited.

Usage is based on the text actually stored in the shared index, calculated as characters divided by five. Raw HTML size and the lexical word count shown by WordPress are different measurements. Translations each occupy space. Assigning one shared source to additional assistants does not create additional indexed copies; retaining a separate URL import of the same page does.

Chat4U imports whole records that fit and clearly reports partial coverage. Records that do not fit wait; a record is never silently truncated to fit. Existing eligible knowledge remains usable while updates wait for capacity. Adding effective capacity or freeing indexed storage automatically resumes waiting records. A newer version can require more room than the version already stored.

Pausing updates, disconnecting or losing plan access does not by itself delete stored knowledge or free its capacity. Remove/archive records through Knowledge when you want to release storage. Read the connection's current status as well as its usage; word add-ons do not independently grant website-integration access.

Updates and temporary interruptions

Ordinary WordPress saves record a change hint. Signed delivery and periodic reconciliation update the native source through Chat4U's indexing workers. You do not need to run a manual job after each edit. Unchanged text reuses its existing vectors. Coverage shows imported records, exclusions, waiting records and updates that could not be verified.

During a temporary connection outage, eligible previously verified content can remain usable for up to 72 hours from the last verified synchronization. A connection heartbeat alone does not renew unverified content. A received removal, disconnect, plugin deactivation/uninstall, identity revocation or loss of integration access blocks affected use immediately. An unreachable host cannot send an immediate notice; reconciliation and the outage deadline still apply.

Healthy owner pause and capacity waiting are separate from an outage. Reconnecting does not override another active blocker, and content must catch up canonically before an expired source is restored.

Manage the connection

Each project has one website-platform connection across providers. Members can view status; a workspace owner or admin manages the connection. New customers can create an account, workspace and project from the WordPress connection journey. Existing customers can select their current workspace and project.

With plugin 0.3.0 or later, choose your assistant and website display in the initial connection setup. The same action attaches this source to the selected assistant and applies the display choice. Other knowledge and other assistants stay as they are. If no assistant exists yet, connect the content first and continue to assistant setup.

WordPress content does not need to finish importing before an existing eligible assistant can appear using its other knowledge. An assistant load report confirms a page load, not the quality of its answers or every visitor's experience. Check imported facts and languages separately.

Deliberately removing the source's attachment shows an impact warning and stops its source-backed answers and shopping help. An ordinary save does not attach it again; explicitly confirm adding the source back when wanted. A newer Off choice saved in WordPress also wins over an older setup request. An older plugin or connection may need an update and one renewed confirmation from WordPress before Chat4U can apply display changes.

Removing the WordPress source in Knowledge deletes its indexed records and assignments while retaining the connection. Automatic updates do not recreate the removed source. Restore it deliberately from Website platforms when wanted.

Disconnecting stops native access and releases the project's website slot; it does not cancel or transfer a Chat4U subscription. WordPress plugin deactivation or deletion also revokes access. Reinstallation requires a fresh connection. Old signed requests and unfinished work cannot restore a retired binding.

Moving or copying a site requires explicit confirmation in Chat4U. Verified language hosts belong to the declared site; a copied database does not grant a new site access to the original connection.

Last updated on