DocAccessible
Checking account
Documentation
All documentation

Website monitoring

Install the website script on WordPress

Add the DocAccessible script across a WordPress site using a managed code area or a child-theme hook, then clear caches and verify the public HTML.

For
WordPress administrators, developers, and managed-host teams
Typical time
10-25 minutes
Copy your website script

Before you start

  • Administrator or deployment access to the WordPress site
  • The generated installation code for this exact domain
  • A current backup or staging environment before editing theme code

Procedure

Step by step

  1. Copy the generated installation code

    Open the connected website in DocAccessible, choose Installation, and copy the complete tag. Keep the site key unchanged.

  2. Use the site's supported global-code method

    If your managed host or active theme provides a site-wide footer or body-end code area, use that supported tool. Configure it for the public front end and every page.

  3. Use a child theme when code is required

    Ask a WordPress developer to add the tag through a child theme or a small site-owned plugin. Do not edit the parent theme because an update can erase the change.

  4. Publish and clear every cache layer

    Save the change, deploy it, and purge WordPress page caches, optimization plugins, managed-host caches, and the CDN when present.

  5. Check a logged-out public page

    Open a normal page in a private window, use View page source, and search for the exact data-site-key. Admin previews can differ from cached visitor HTML.

  6. Confirm Script connected

    Reload the public page once, then return to the website Installation tab. If verification fails, compare the page-source key before changing anything else.

Choose the safest WordPress method

WordPress core does not provide one universal site-wide script field. Managed hosts, commercial themes, and governance plugins expose different labels, so prefer the installation mechanism already approved for that site.

  • Best for site admins: an existing site-wide Footer or Body - end code area.
  • Best for development teams: a child theme or small site-owned plugin under version control.
  • Avoid: editing footer.php or functions.php in the parent theme.
  • Avoid: adding a Custom HTML block to one page, because monitoring should cover the shared template.

Optional child-theme hook

A developer can add the exact generated tag from the child theme's functions.php. Replace the placeholder tag below with the installation code copied from DocAccessible, then review it through the normal deployment process.

Child theme functions.php example
function docaccessible_add_site_script() {
    ?>
    <script async src="https://docaccessible.com/site/v1.js" data-site-key="YOUR_SITE_KEY"></script>
    <?php
}
add_action( 'wp_footer', 'docaccessible_add_site_script', 100 );

WordPress cache checklist

A saved admin change can be correct while visitors still receive old HTML. Confirm the public source after clearing each cache your stack uses.

  • Page-cache or performance plugin
  • Managed WordPress host cache
  • Reverse proxy or full-page cache
  • CDN cache
  • Browser cache or service worker

Official WordPress references

Use WordPress's theme documentation when your team owns the implementation. Theme and host-specific global-code screens can have different names.

Related guides