π Why the schema is not in the page source
Search Atlas adds schema with a script that runs after the page loads. The markup is written into the live page as JSON-LD. It is not stored as static HTML in your theme or page template, so View Source often will not show it.
That is expected. Search engines and schema testers that render JavaScript can still read the markup. To confirm it yourself, open the live page, use your browserβs Inspect tool, and look for a script with type application/ld+json. A raw source check alone is not enough.
βοΈ Why the schema type stops changing
Search Atlas can suggest a type, such as Service, from the page it last analyzed. After you accept or deploy that suggestion, later edits on the site do not always replace it. Changing the page in your CMS from a service page to a collection page updates your content, but it does not automatically rewrite a schema type that is already saved in Search Atlas.
The type can also look stuck when an older deployment, a cached page, or a previous crawl is still what Search Atlas and search engines are reading. The suggestion and the deployed schema are separate. A new suggestion does not overwrite a deployed type until you change it and publish again.
π Where to Find It
UI path: OTTO SEO β Overview β Schema Markup β Preview
π οΈ How to update the schema type
- In Search Atlas, open the page that should use the new type.
- Open its schema settings and change the type from the old suggestion, such as Service, to the correct type, such as CollectionPage.
- Review the fields so they match the current page, then save.
- Deploy or publish the schema from Search Atlas so the live script receives the new type.
- Publish the page in your CMS and clear any site, CDN, or plugin cache.
- Wait for the next crawl, or run a fresh analysis of that URL in Search Atlas.
- Recheck the rendered page, not only the source, and confirm the JSON-LD type changed.
If the page URL, canonical, or template changed, update the URL in Search Atlas first. A schema saved on the old URL will not follow the page on its own.
π How to confirm the new type is live
- Inspect the rendered page and find one JSON-LD block for that URL.
- Check that the @type value matches the type you just deployed.
- Test the live URL in a renderer that executes JavaScript, such as a rich results or schema testing tool.
- Compare the tested URL with the canonical URL. A mismatch can show the old schema.
- Allow time after deployment. A cached copy can keep the previous type visible for a while.
More than one JSON-LD block on the same page can make an old Service type appear even after you add CollectionPage. Keep a single clear type for the page unless you intentionally need more than one.
π‘ If the type still does not update
- Confirm you deployed from Search Atlas after changing the type, not only edited the suggestion.
- Confirm the Search Atlas script is present on the live page and is not blocked by a consent tool, ad blocker, or optimization plugin.
- Remove conflicting schema added by your theme, an SEO plugin, or a tag manager.
- Re-analyze the exact canonical URL after cache is cleared.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.