🧭 Overview
Yoast author schema can intermittently appear to be missing when MetaSync OTTO or another external sync updates the page’s JSON-LD. In affected cases, the Yoast graph may be replaced with "@graph": false, or imported schema blocks may be dropped. This can prevent the expected Person entity for the author from appearing.
⚠️ Known causes
- Yoast conflict handling: A known MetaSync conflict could produce invalid JSON-LD with "@graph": false on OTTO-covered pages.
- External schema imports: Schema blocks that were not eligible for import could be silently skipped.
- Sync timing: A page may briefly show older or incomplete markup while an external sync is processing.
- Caching: WordPress, plugin, CDN, or browser caches can continue serving an earlier version after the schema is corrected.
- Author data: Missing or incomplete author details in WordPress can prevent Yoast from creating a Person node.
✅ What Search Atlas has addressed
Search Atlas has completed fixes for the MetaSync Yoast conflict handler and OTTO persistence across Yoast, Rank Math, and AIOSEO. These changes address invalid graph output and improve schema synchronization. Schema import eligibility and result reporting are also being improved, so unsupported or skipped blocks can be identified more accurately.
🔎 How to verify the issue
- Open the affected page in an incognito browser window.
- View the page source and search for application/ld+json, "@graph", and "@type":"Person".
- Check whether the page contains "@graph": false, an empty graph, or a Person node without the expected author information.
- Compare the page source with the rendered DOM. If they differ, a plugin, theme, or client-side script may be changing the markup.
- Clear WordPress, SEO plugin, server, CDN, and browser caches, then check the page again.
🛠️ Recommended checks
- Confirm the author has a valid WordPress user profile and display name.
- Check that Yoast is enabled for the post type and that the page is not excluded from search or schema output.
- Review whether OTTO or MetaSync is covering the page and whether an external schema sync recently ran.
- Do not add a second manual Person graph until the existing Yoast and OTTO output has been reviewed. Duplicate entities can create new validation issues.
- After changes, allow the sync to finish and purge all relevant caches before testing again.
📊 Expected result
The page source should contain valid JSON-LD with an @graph array. That graph should include the article or webpage entities and, where author data is available, a linked Person entity. A temporary absence immediately after a sync can be cache-related, but repeated output of "@graph": false indicates a conflict or failed schema update.
💬 Get help
When contacting the team, include the affected URL, WordPress and SEO plugin versions, whether OTTO or MetaSync covers the page, the time of the latest sync, and a page-source excerpt showing the JSON-LD. 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.