Add the QualityHive script to the
Three ways to add the script
Copy the script from your project's widget setup, then pick one route. The tracking code guide covers the QualityHive side.
Route | Best for | Watch out for |
Child theme | Sites with a code deploy | Edits to a parent theme are lost when it updates |
Snippets plugin | Sites with no file access | Free tiers differ on what they can insert |
Google Tag Manager | Sites already running a container | Nothing is live until you publish the container |
Child theme
Hook wp_head from your child theme'sfunctions.php. The hook works on classic and block themes, so you never need to touch header.php. This version only prints the script on staging:
add_action( 'wp_head', function () { if ( 'staging' !== wp_get_environment_type() ) { return; } ?>
wp_get_environment_type() returns production unless WP_ENVIRONMENT_TYPE is set, so define it in the staging site's wp-config.php or the script will not print.
Snippets plugin
WPCode's free version has a Scripts in Header field, so paste the script there. Code Snippets keeps JavaScript snippets for its Pro version, so on the free version add the PHP above as a snippet.
Google Tag Manager
Add a Custom HTML tag containing the script, set it to fire on all pages, then publish the container. Changes can take a few minutes to appear.
Staging
Check Settings, then Reading. "Discourage search engines" belongs on staging and must come off at launch.
Send a test through every form and confirm staging emails reach you, and never real customers.
After the database moves to live, search menus and page content for the staging URL.
Caching plugins
Purge the page cache after adding the script, or the cached HTML will not include it.
Review in a private window as well, because many caching setups treat logged-in users differently.
WP Rocket's Delay JavaScript execution holds scripts back until someone interacts with the page. If the widget appears late, add the nowprocket attribute to the script tag.
Page builders
Check responsive visibility settings at each device width, since builders can hide a section on mobile.
Raise feedback on a global header or template once, fix it once, then confirm it on another page that uses it.
If styles look out of date, regenerate the builder's CSS. On Elementor the command is wp elementor flush-css --regenerate.
Plugin conflicts
After any plugin update, retest forms, menus and anything built on a shortcode.
Troubleshooting mode in Health Check disables plugins for your session only, so you can isolate a conflict without affecting visitors.
On Mega and above, tasks log JavaScript errors, which can point at the plugin behind a problem. Our guide to console errors and warnings explains how to read them.
Before go-live, work through our WordPress launch checklist.
