π Overview
Sometimes OTTO generates a schema type that does not match what a page really is. A common example is a group of blog pages marked as CollectionPage when they should use a blog-related type. If this affects dozens or hundreds of pages that are not yet deployed, fixing them one by one is slow and frustrating. This article explains why it happens, how to fix it efficiently, and how to ask our team to review credits used on incorrect output.
π§© Why the Wrong Schema Type Appears
OTTO chooses a schema type by looking at the structure and content of each page. A page can be misread when:
- It shows a list or grid of posts, which looks like a collection or category page.
- The URL structure resembles a category, tag, or archive path.
- The page has little body text, so the layout is the strongest signal.
- Similar pages share the same template, so one misread repeats across the whole group.
Because pages built from the same template usually share the same cause, a wrong type tends to affect many pages at once. That is why the fix is best handled as a batch rather than page by page.
β Confirm the Right Schema Type First
Before changing anything, decide which type is correct for each group of pages. The right answer depends on the page:
- Blog listing or index page: a page that lists many posts. A collection-style type can be correct here, or a Blog type, depending on your goals.
- Individual blog post: a single article. A blog post or article type is normally the right choice.
- Category or tag archive: a collection-style type is usually appropriate.
If you are not sure, spot-check two or three pages from each group. Look at the live page and ask whether it is one article or a list of articles. Settling this first prevents you from correcting the same pages twice.
π οΈ How to Fix Many Pages Efficiently
- Find the affected pages. In the OTTO Schema table, use the Not Deployed filter and search by page URL (for example /blog/). Read the Page Type column to spot the pages that were classified the same way. Note the URLs or the shared URL pattern.
- Group them by template. Pages with the same layout usually need the same correction. Handle each group together.
- Test one page first. Correct a single page in the group, check that the schema type and fields look right, and confirm it is valid before applying the same approach to the rest.
- Apply the fix to the rest of the group. Bulk selection in the Schema table lets you AI Generate (up to 50 at a time), Deploy, Roll back or Delete the selected schemas. It does not change a schema's type. If the type is wrong for many pages, move to the next step instead of editing each page. **
- Ask support to run a bulk correction. For large batches, such as 100 or more pages, send the details to our team in the chat widget so they can review a single correction for the whole set.
- Review before deploying. Check a sample of corrected pages, then deploy. Leaving pages undeployed until they are verified keeps incorrect schema off your live site.
You should not have to rewrite schema code outside the platform and paste it over each page. If you find yourself doing that for a large batch, it is a good sign to contact support instead.
π³ Credits and Incorrect Schema
If OTTO generated schema with the wrong type, you may have used credits on output you could not use. Here is what to know:
- Our team can review the affected pages and the credits used on them.
- Each request is reviewed individually, so include as much detail as you can to speed up the review.
- Do not regenerate the same pages repeatedly while waiting. Regenerating can use additional credits and may produce the same result until the underlying cause is fixed.
Once the team confirms the cause and any eligible credits, they will let you know in the chat what was corrected and what was restored.
π What to Include in Your Chat Message
Sending the right details up front helps our team resolve this in fewer replies. Please include:
- The name of the project or site.
- The number of affected pages, for example 194 not deployed pages.
- The schema type currently shown and the type you expect.
- A few example URLs, plus the shared URL pattern if there is one.
- Whether any of the pages are already deployed.
- An estimate of credits used on the incorrect schema, if you can see it.
π‘ Tips to Avoid This in the Future
- Review before you deploy. Check a small sample from each page group before approving a large batch.
- Start small. When setting up a new site or template, run OTTO on a few pages first to confirm the schema type is right.
- Keep page types separate. Clear URL structures for posts, categories, and listings make the correct type easier to detect.
- Report patterns early. If you see the same wrong type on several pages, tell support before generating more.
β Quick Answers
Do I need to fix each page by hand? No. Group pages by template, test one, and ask support to help with large batches.
Will deploying incorrect schema hurt my site? Wrong schema can send misleading signals to search engines, so it is best to correct pages before deploying them.
Can I get my credits back? Our team can review the pages and credits involved. Share the details above so they can look into it.
π¬ Need 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.