π Overview
OTTO automatically chooses a schema type for each page based on what it detects on that page. Sometimes the choice is not the best fit. A common example is a blog post that OTTO labels as Service schema when it should be Article or BlogPosting. This article explains how to correct that and answers a common question: do you have to write the schema yourself?
β Do I Need to Write the Schema Manually?
In most cases you don't have to write the schema from scratch. Open the page's schema, edit the JSON-LD so its @type is Article or BlogPosting, and adjust the fields to match that type. The Regenerate button asks OTTO to generate the schema again, but if the page signals haven't changed it may produce the same type.
- Most customers: adjust the schema type for the page and review the generated details.
- Advanced users: supply your own custom structured data if you want to define every property yourself.
π Article vs. BlogPosting: Which Should I Choose?
Both are valid for written content. BlogPosting is a more specific version of Article, so neither is wrong for a blog post.
- BlogPosting: best for blog posts, opinion pieces, and personal or company updates.
- Article: best for guides, how-to content, news, and longer editorial pages.
- Service: best for pages that describe a service you sell, such as a service landing page. Keep this type for those pages only.
π§ Before You Start
- Confirm the page is really informational content and not a service page.
- Make sure the page is part of your OTTO project and OTTO is installed and active on your site.
- Check whether your theme or an SEO plugin also adds schema to the same page. Two sources can create duplicate or conflicting markup.
βοΈ How to Change the Schema Type for a Page
The exact labels in your dashboard may differ slightly, but the process follows these steps.
- Log in to Search Atlas and open your OTTO project for the site.
- Find the page that has the wrong schema type. Use the search or filter options to locate it by URL.
- Open the page's schema details and review what OTTO has currently set (for example, Service).
- In the schema drawer, click the pencil icon (Edit schema). Switch to the "Raw JSON" tab, change the "@type" value (for example from "Service" to "BlogPosting"), and edit the other fields to match. This doesn't work for WebPage or FAQPage schemas, which are managed by Semantic Analysis and Knowledge-Based Trust.
- In the JSON-LD, review and fix fields such as headline, description, author, datePublished and image. If the drawer shows "Schema Validation Warning β Review Required", expand "Expected Format (Example)" to see the expected structure and fix the highlighted fields.
- Click "Save edit". Then click "Deploy this Schema", or "Deploy as-is" if validation warnings remain. If the schema is already deployed, saving the edit updates what the live page serves. The time it takes to appear on the live site wasn't checked.
If you have several blog pages with the same issue, repeat the steps for each page and keep the schema type consistent across similar content.
βοΈ If You Want to Use Custom Schema
If you prefer to provide your own structured data, you can use JSON-LD, which is the format Google recommends. A basic BlogPosting should include these properties:
- headline: the title of the post.
- description: a short summary of the post.
- author: the name of the person or organization that wrote it.
- datePublished and dateModified: the publish and last update dates.
- image: the main image of the post.
- mainEntityOfPage: the URL of the page.
Make sure the information in the schema matches what visitors can see on the page. Schema that does not match the visible content can be ignored by search engines.
β How to Verify the Change
- Wait a few minutes after saving, then open the live page in your browser.
- Run the URL through Google's Rich Results Test or the Schema Markup Validator.
- Confirm the page now shows Article or BlogPosting and no longer shows Service.
- Check that there are no errors or duplicate schema blocks for the same page.
If you recently changed the schema, clear your site cache or CDN cache so the updated version appears.
π οΈ Troubleshooting
- The old schema type still appears: clear your site, plugin, and CDN caches, then test the page again.
- Two schema types appear on the page: your theme or another plugin may be adding its own schema. Disable the duplicate source or keep only one.
- The type reverts after a while: confirm your change was saved and deployed, and that no other tool is overwriting it.
- Validation warnings about missing fields: add the missing details, such as author, image, or dates, so the markup is complete.
- You cannot find the schema option for a page: make sure the page is included in your OTTO project and that OTTO is connected to your site.
π‘ Best Practices
- Use one schema type per page purpose. Do not mark a blog post as a Service.
- Keep schema details accurate and up to date, especially dates and authors.
- Apply changes to a single page first, test it, and then roll the same approach out to similar pages.
- Re-test after major site updates, theme changes, or plugin changes.
π¬ Need More Help?
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. To help us resolve it faster, include the page URL, the schema type you see now, and the type you want.