Walkthrough
- Register the callback from your child theme's functions.php or a small MU-plugin so the hook survives plugin updates.
- Attach at priority 20 so WBP's own defaults have already run — you're modifying, not replacing.
- Return the mutated value; never echo. WBP wraps the output and echoing early breaks JSON-LD, sitemap XML, or REST responses.
- Guard the callback with a context check (post type, current screen, or is_admin) so the change fires only where intended.
- Log the change to the SEO change log so the next audit run can attribute rank movement to the hook.
Pro tips
- If the hook affects sitemap or robots output, purge the WordPress object cache after saving — WBP caches those responses for 12 hours.
- Pair with the AI Visibility tracker: a hook that changes titles or JSON-LD is the exact kind of change that flips whether ChatGPT cites the URL.
- Never call remote APIs synchronously inside a hook that runs on every request — schedule an Action Scheduler task instead.
Where this fits
This is one of 305 developer hooks WBP Omni SEO Pro exposes. If you need to change output at a different point in the request, browse the Developer Hooks category.
