Keep the embed maintainable
A WordPress mascot needs a canvas wrapper, a static fallback and a small initialization script. Place those through the site’s existing theme or plugin approach so the integration survives ordinary content edits. Avoid scattering different script copies across individual pages.
For custom theme work, enqueue assets through the supported WordPress APIs. A reusable block or shortcode can provide consistent markup where the mascot is needed. See the WordPress theme asset guidance for the loading model.
Handle the .riv file as a controlled asset
WordPress media uploads may not accept a .riv extension by default. Use a developer-managed static asset location or a narrowly configured upload policy if an editor needs to replace the file. Do not broadly allow arbitrary executable or unknown file types just to make one animation upload work.
If files are served from another origin or a CDN, confirm the browser can fetch them. Keep the runtime and WebAssembly versions matched, and document the exact path expected by the initialization code.
Load only where the character appears
Register the runtime once and enqueue the integration where a mascot is rendered. A site-wide script for a character on a single page adds unnecessary work. Initialize multiple wrappers deliberately if the page genuinely needs more than one character.
The wrapper should reserve space before JavaScript runs. For a fixed corner placement, check the administration bar, consent controls, chat widgets and mobile navigation. A decorative character must not cover essential site controls.
Account for optimization plugins
Caching, script delay and minification tools can change load order. The integration should wait for the official runtime before creating the instance and retain the fallback if a dependency fails. Test the production optimization settings instead of only the editor preview.
After changing the export or input contract, invalidate the relevant cache or use versioned filenames. A new script paired with an old cached rig can fail even when both files individually return successful responses.
Connect site events through a defined adapter
A contact form or commerce plugin may expose its own success event. Confirm which event means the server accepted the operation before mapping it to a character reaction. Do not treat clicking “Place order” as proof of a completed purchase.
Your developer should document the plugin-specific connection, cleanup behavior and fallback. Share the theme, builder and relevant plugins in the brief so integration assistance can be scoped. The same Rive file can serve different stacks, but the surrounding event wiring is site-specific.