Search Atlas Help Center

🧩 Schema Markup Layering: Deploy OTTO on Existing Markup

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

OTTO can deploy schema markup automatically across your site, but if you already have custom, hand-crafted schema on specific pages, you need a clear strategy before activating OTTO's schema. This article explains how to layer OTTO schema safely, when to hold back, and how to protect the unique structured data you have already built. It also covers how to remediate broken image tags that can interfere with your structured data and page quality signals.

📋 Understanding the Two Types of Schema on Your Site

Before making any changes, identify what schema you currently have and what OTTO is proposing to add:

  • Existing unique per-page schema: Custom structured data you or your developer wrote specifically for individual pages — for example, a detailed Product schema with specific offers, reviews, and SKUs, or a FAQPage schema tied to that page's exact content.
  • OTTO-generated schema: Structured data OTTO recommends and deploys based on page type, content signals, and SEO best practices. OTTO typically covers site-wide or category-level patterns such as Organization, BreadcrumbList, WebSite, and basic Article or WebPage types.

✅ When It Is Safe to Layer OTTO Schema on Top of Existing Markup

Layering is safe and beneficial when the schema types do not overlap. If your existing markup covers a specific type — such as Product — and OTTO is adding a complementary type — such as BreadcrumbList or Organization — there is no conflict. Google reads multiple JSON-LD blocks on the same page without issue as long as they describe different entities or schema types.

Deploy OTTO schema on top of your existing markup when:

  • OTTO is adding a different schema type than what is already present on the page.
  • Your existing schema covers highly specific data — pricing, inventory, custom review aggregations — that OTTO cannot replicate from its configuration.
  • You want site-wide consistency for secondary schema types without manually maintaining them on every page.

⚠️ When to Hold Back OTTO Schema Deployment

Do not deploy OTTO schema on top of existing markup when the types overlap or conflict. Deploying two Product schemas or two FAQPage schemas on the same page can create contradictory signals that confuse search engine crawlers and may result in neither being used for rich results.

Hold back or customise OTTO's schema deployment when:

  • OTTO is recommending the same schema type already present in your existing markup.
  • Your existing schema contains precise data — such as exact aggregateRating values or structured HowTo steps — that OTTO's version would overwrite or dilute with generic content.
  • Your developer has implemented schema tied to dynamic data pulled from a CMS or database that OTTO cannot access or replicate accurately.

🖼️ Broken Image Tag Remediation

Broken image tags on your pages can affect both user experience and structured data quality. When schema markup references images — for example, an ImageObject within a Product or Article schema — a broken or missing image URL can cause validation errors in Google's Rich Results Test and reduce eligibility for rich results.

To identify and remediate broken image tags:

  1. Audit your pages for broken images. Use your site audit tool within Search Atlas to surface pages with broken image URLs (typically flagged as 4xx errors on image assets).
  2. Check whether broken images are referenced in schema. If a broken image URL appears inside a JSON-LD block — for example, as the image property of a schema type — that schema block may fail validation.
  3. Replace or remove the broken image reference. Update the image URL to a valid, publicly accessible asset, or remove the image property from the schema block temporarily until a valid image is available.
  4. Re-validate your schema. After making corrections, use Google's Rich Results Test to confirm that the schema block is now valid and the image reference resolves correctly.
  5. Redeploy or re-save the affected schema. If the schema is managed through OTTO, trigger a redeployment after fixing the underlying image so that the corrected reference is pushed live.

Addressing broken image tags before or alongside schema deployment ensures that your structured data is both syntactically valid and pointing to accessible resources, which improves the likelihood of rich result eligibility.

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.