🔍 Why OTTO changes may not appear
OTTO updates may not appear immediately in the WordPress editor or on the live page. OTTO can apply changes through the WordPress integration, Google Tag Manager, or site code, so some updates are rendered dynamically rather than saved as visible WordPress fields.
For example, schema markup, meta titles, and meta descriptions may be active on the live page without appearing in the standard WordPress post editor. Conversely, a deployment can show as successful while caching, integration settings, or theme behavior prevents the change from rendering.
✅ Confirm the deployment status
- In Search Atlas, open OTTO SEO from the left sidebar.
- Open the relevant project or site audit area and locate the affected URL.
- Check whether the recommendation or fix is marked Deployed, Fixed, or still pending.
- Confirm that the URL is canonical, publicly accessible, and included in the latest crawl.
🔄 Run a fresh sync and recrawl
If the deployment is complete but the page is unchanged, refresh the connection between Search Atlas and WordPress.
- Open OTTO SEO → Site Audit → Installation Guide and confirm the WordPress integration is installed and active.
- Verify that the connected WordPress site is the same site and environment as the affected URL.
- Use the available CMS sync or redeploy action for the affected page.
- Start a new crawl from OTTO SEO → Site Audit after the sync finishes.
🌐 Check the live page
Do not rely only on the WordPress backend. Open the published URL in a private browser window and inspect the page source or rendered HTML.
- For meta titles and descriptions, check the page source for the title element and meta description.
- For schema, use a structured-data testing tool or inspect the JSON-LD in the rendered page source.
- For headings and image alt text, view the live page and confirm the rendered content.
If the change appears on the live page but not in WordPress, this is expected for dynamically applied OTTO updates. WordPress fields may remain unchanged even though search engines can read the deployed output.
🧹 Clear caching and integration conflicts
Cached pages, CDN layers, optimization plugins, and duplicate SEO tools can display older content or overwrite OTTO changes.
- Clear the WordPress cache, CDN cache, and any server-side cache.
- Temporarily check whether an optimization or SEO plugin is generating competing titles, descriptions, schema, headings, or alt text.
- If using Google Tag Manager, confirm the container is published and loading on the affected page.
- Check that consent settings or security tools are not blocking the OTTO script.
- Test the page without a browser cache by using a private window or a hard refresh.
📋 When to review deployment details
Review the deployment details when several pages are affected, changes repeatedly revert, or the live page differs from the deployment preview. Record the affected URL, deployment status, integration type, and the exact change that is missing. This information helps identify whether the issue is related to WordPress, GTM, caching, or the page template.
💬 Get help from our team
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.