Install Procora on WordPress

Confirm permission to insert a script

WordPress may remove scripts when the user or configuration does not permit them. Its official Custom HTML documentation describes this restriction. Establish administrator access, hosting conditions and business security policy rather than disabling security filtering.

Source: WordPress: Custom HTML and script permissions

Use code from your own workspace

Open the installation instructions in your Procora workspace. Copy the widget code with your own assistant ID. A widget assistant ID is a public installation reference; an API key or password must never be inserted into page HTML.

Choose a test page and one code location, such as a Custom HTML block where the administrator permits the script. Save and inspect the public page as a logged-out visitor. This manual method does not imply a dedicated Procora plugin or support for every WordPress hosting plan.

Check language and enquiry capture

Use the widget’s documented language setting and test open/close, focus, Danish/English and a routine question. Check receipt of a fictional enquiry in the workspace. A visible chat icon establishes display, not a correct knowledge base or complete booking setup.

Find duplicates and blocking

If two icons appear, remove one installation method. If nothing appears, check whether the script survived saving and whether content or consent rules block it. Review caching and possible script errors with the administrator. Follow the business’s chosen privacy and consent process.

Be able to remove it

Record exactly where the code was inserted. Remove it from that location for rollback, clear relevant cache and check the public page. Removing a widget does not automatically cancel an agreement or delete saved conversations; handle those separately.

Use the worksheet

Version 15 October 2026. Fill in your own facts; illustrative values are not results or an agreed service.

WORDPRESS INSTALLATION
Owner and test page:
Widget code copied from own Procora workspace:
One installation method only:
HTML/script persists without being stripped:
Language and open/close controls checked:
Mobile and keyboard checked:
Consent tooling and privacy information reviewed:
Known question / unknown question / enquiry capture tested:
Rollback location recorded:

Sources and scope of review

First-party documentation reviewed 15 October 2026. Vendor statements are not independent product tests. Recheck your actual package and agreement.

• WordPress: Custom HTML and script permissions