When OTTO deploys schema markup to your site, it should be visible in Google's Rich Results Test tool within a short time. If your schema is marked as published in the OTTO dashboard and the OTTO Pixel is confirmed active, but the schema still does not appear in the Rich Results Test, this may indicate a service-level deployment problem that requires engineering review.
This article explains what to check first, how to identify a backend issue, and exactly when to escalate to our team.
Log in to your Search Atlas account and open your OTTO dashboard for the site in question.
Confirm that the OTTO Pixel is active for the site.
Verify that the relevant schema type is in a published state — not pending or draft.
Note the approximate date and time the schema was published so you can reference it during escalation.
The Rich Results Test tool reads the page as Google sees it. Before assuming a rendering issue, verify that the schema is actually present in your page's HTML source:
Open the target URL in a browser.
View the page's HTML source (the method varies by browser, but most browsers allow this from the browser menu or a keyboard shortcut).
Search the source for application/ld+json.
If no schema block appears, the markup is not reaching the page — this confirms a deployment-level failure, not a Google indexing delay.
Important: If the schema is absent from the page source even though OTTO shows it as published, do not continue with further client-side troubleshooting. Proceed directly to the escalation step below.
If the schema block is present in the page source, run a live test to check how Google interprets it:
Go to Google Rich Results Test.
Enter the full URL of the page and run the test.
Review the results for detected schema types and any reported errors or warnings.
If Google detects the schema here but it still does not appear in search results, this is a normal indexing delay and may take several days. No action is needed beyond monitoring.
Stop troubleshooting and escalate right away if any of the following conditions are true:
The schema is marked as published in OTTO but is completely absent from the live page source.
The OTTO Pixel is active and schema is published, yet the schema does not appear after an extended period.
You are seeing inconsistent behavior across pages or schema types that you cannot explain through indexing delays alone.
To help our team investigate as quickly as possible, please have the following information ready:
The name of the project or site affected.
The specific URL(s) where schema is not appearing.
The schema type(s) that should be deployed (e.g., Article, FAQ, Product).
The date and time the schema was marked as published in OTTO.
Confirmation of whether the schema block is present or absent in the live page source.
Any error messages or unexpected results from the Rich Results Test.
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.