Get the correct site configuration
Open the website in your Porchlight workspace and find its installation instructions. Confirm the public domain and use the site identifier from that website. A staging domain may need its own allowed-domain configuration before the widget can load there.
Plan the installation on a staging copy when your site has a complex theme or several optimisation plugins. Keep your existing theme and plugin configuration available so you can reverse the installation change if needed. Never place an account password, private API token or identity-signing secret in WordPress page content.
Use the workspace-provided plugin
Download the WordPress plugin from the installation instructions in your Porchlight workspace. In WordPress administration, open Plugins, choose Add New and Upload Plugin, then select the provided ZIP. Install and activate it, then use the plugin's configuration to enter the site identifier from the same workspace.
Use the controls in the installed plugin as the authority for the exact field labels. After saving its configuration, inspect a public page to confirm the loader appears once. If your host restricts plugin installation, ask the site administrator to handle it or use the alternative below.
Or add the HTML snippet once
If your site already has a trusted way to insert footer scripts, place the workspace's HTML snippet there. You do not need both a plugin and a manual script. Avoid editing a parent theme file directly: a theme update may overwrite the change.
<script async src="https://porchlight.1001toolbox.com/l.js" data-site="YOUR_SITE_ID"></script>Replace YOUR_SITE_ID with your own identifier. Follow the HTML installation guide for placement and the visitor checklist.
Check caching, consent and phone placement
Clear the caches that serve your public pages and open the site while logged out of WordPress. Confirm the launcher is visible where intended and does not overlap a cookie banner or a sticky mobile action. Test the pages that use different templates, including a post and a normal page.
If the snippet is present but the widget is missing, check the browser console, your content security policy and any consent or script-delay rule. Keep your consent requirements in place. Once you deliberately test a conversation, check that the message arrives in the intended Front Desk and that somebody owns the follow-up.