Install the widget on WordPress

WordPress gives you several ways to add site-wide code, and the right one depends on how your theme and plugins are managed. Whichever method you use, the goal is the same: load the Zeltino script once in the global document head so the widget is available across the public site.

This guide will help you copy the correct script, choose a durable WordPress installation method, and verify the published result after caches are cleared.

In this article, you'll learn:

• How to copy the project script
• Where to add it in WordPress
• How to clear caches and verify the widget

Copy the script#

Begin in Zeltino with the project and domain you are preparing. This makes sure the installation code belongs to the correct visitor experience.

1. In Zeltino, open Settings > Chat widget > Installation.
2. Add or select your WordPress website domain.
3. Select WordPress.
4. Select Copy script.

Add it to WordPress#

WordPress installations can be managed very differently. Use the site-wide method supported by your setup:

• a trusted header and footer code plugin;
• your site builder's global custom-code or head-code setting; or
• Appearance > Theme File Editor when your theme and administration policy support direct editing.

Paste the copied code in the global head, before the closing </head> tag. Save the setting and publish any pending site-builder changes. A page-level code block is not enough when visitors need the widget throughout the website.

Clear caches and verify#

WordPress sites often have more than one cache between the editor and the visitor. Clear every cache that applies before asking Zeltino to check the installation.

1. Clear the WordPress, hosting, and CDN caches that apply to the site.
2. Open the public site in a private browser window.
3. Return to Zeltino Installation.
4. Wait for the domain to change from Verifying to Active, or select Refresh check.
5. Turn on Enable chat widget on this website.
6. Test more than one public page and a mobile-width view.

If the widget loads only on some pages, the code was probably added to a page-specific template instead of the global head. Move it to the site-wide location, publish again, and follow Troubleshoot widget installation and verification if the problem continues.