# **🔍 What Is Schema Markup and How Does OTTO Deploy It?**

Schema markup is structured data added to your page's HTML code. It communicates information about your content directly to search engines — without displaying anything visible to your website visitors. When OTTO deploys schema, it injects this code into the background of your page, not into the visible text or layout.

This means that after OTTO successfully deploys FAQ schema, Article schema, or any other schema type, **you will not see any new text or elements appear on your page**. That is expected and correct behaviour.

# **❓ Why Isn't FAQ Schema Visible on My Homepage?**

FAQ schema deployed by OTTO is intentionally invisible. It exists as structured data in your page's source code, which search engines like Google read to understand your content and potentially display rich results (such as expandable FAQ dropdowns in search listings).

The schema tells search engines *about* your FAQ content — it does not create or display that content on the page itself. Think of it as a label on the back of a product: shoppers do not see it, but the warehouse system reads it perfectly.

# **✅ Should I Add Visible FAQs Manually to My Homepage?**

Whether you add visible FAQ content to your homepage is a separate editorial decision from schema deployment. Here is how to think about it:

- **If your homepage already has FAQ content:** OTTO's FAQ schema references that existing content. No manual addition is needed.
- **If your homepage has no visible FAQ content:** You may choose to add an FAQ section for user experience and SEO value. This is entirely optional and based on your content strategy.
- **Duplicate content concern:** Adding visible FAQs to your homepage will **not** create duplicate content issues. Schema markup and visible page content serve different purposes and are read differently by search engines. They complement each other rather than conflict.

# **📄 Why Is OTTO Suggesting Article Schema for My Homepage?**

Article schema is a widely used schema type that helps search engines understand the primary topic, author, publication date, and editorial nature of a page. OTTO may suggest Article schema for your homepage when it detects that the page contains editorial or informational content that fits this structure.

This suggestion does not mean your homepage must be a blog post. It means OTTO has identified that Article schema can help search engines better interpret and index the content already present on your homepage. Applying it provides context — particularly useful for brand authority and AI-driven search visibility.

# **🗂️ What Does "Page-Level Schema" Mean?**

Page-level schema refers to structured data that describes the page as a whole, rather than a specific element within it. Examples include:

- **Article schema** — describes the overall editorial content of the page
- **WebPage schema** — identifies the page type and its role on the site
- **FAQPage schema** — signals that the page contains question-and-answer content

When OTTO deploys page-level schema, it is adding a structured summary of your entire page for search engines to process. This is different from element-level suggestions, such as heading or image optimisations, which target specific parts of the page.

# **🏷️ Are H2 Suggestions Deployed as Invisible Elements?**

No. H2 heading suggestions are **not** deployed as invisible elements. H2 suggestions are structural recommendations that affect the visible headings on your page. When OTTO suggests or deploys an H2, it is modifying or adding a heading that will appear in your page content.

Here is a quick reference for what is visible versus invisible after OTTO deployment:

- **Schema markup (FAQ, Article, WebPage, etc.):** Invisible — exists in source code only
- **H2 heading suggestions:** Visible — appear as on-page headings
- **Meta title and description updates:** Invisible on the page — visible in search engine results
- **Image alt text:** Invisible to visitors — read by screen readers and search engines

# **🚀 How to Check What OTTO Has Deployed**

To review the schema and structural changes OTTO has made to a specific page, follow these steps:

1. Go to **OTTO SEO** in the left sidebar, then open **SEO Automation** (or navigate to **/seo-automation-v3**).
2. Select the relevant project and locate the page you want to inspect.
3. Open the page's task list to see a full breakdown of deployed and pending optimisations, including all schema types that have been applied.
4. To verify schema in your page source, right-click your page in a browser, select **View Page Source**, and search for `application/ld+json` — this is where deployed schema will appear.

You can also use Google's **Rich Results Test** (search.google.com/test/rich-results) to confirm that deployed schema is valid and being read correctly by Google.

# **💡 Key Takeaways**

- Schema deployed by OTTO is always invisible to page visitors — this is correct and intentional.
- Adding visible FAQ content alongside FAQ schema will not cause duplicate content issues.
- Article schema on a homepage is a valid and helpful signal for search engines, not a mismatch.
- H2 suggestions are visible heading changes, not hidden code injections.
- You can verify all deployed schema in your page source or through Google's 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.