π Overview
OTTO generates page-level schema (structured data) to help search engines understand what each page is. Sometimes OTTO labels pages as CollectionPage when you expected BlogPosting. This article explains why that happens, how to check whether the label is wrong, and what to do if many pages are affected, including pages that are not yet deployed.
π€ Why OTTO Might Choose CollectionPage
OTTO first classifies each page's type from signals such as the URL, title, headings, page structure and visible content. It then suggests a default schema type for that page type, and category, portfolio and resource-hub pages default to CollectionPage. A page may be labeled CollectionPage when:
- The page shows a list or grid of other posts or items, such as a blog index, category page, tag page, or archive.
- The URL looks like a category or listing path, even though the page is a single article.
- The page template includes large sections of related posts that outweigh the article content.
- The page has little article-style content, such as a clear author, publish date, or body text.
CollectionPage is the right type for listing pages. Only change it if the page is a single article.
β Check Whether the Schema Type Is Actually Wrong
Before changing anything, review a few of the affected pages:
- Open the page in your browser and confirm whether it is a single blog post or a list of posts.
- Single article with a title, body text and date: OTTO classifies it as a blog page, and Article or BlogPosting are both appropriate schema types. BlogPosting is the more specific choice if you want it.
- Page listing many posts, such as a category or archive: CollectionPage is correct, so leave it as is.
- Note any patterns, such as all affected URLs sharing the same folder or template. Patterns help us find the cause faster.
β³ Why Undeployed Schema Can Be Hard to Change
Schema that has not been deployed yet is a generated draft, and you can open it and edit it before deploying. Editing is done in the schema drawer (Edit icon), for example by changing the @type in the JSON, and then deploying. The exception is the page-level WebPage and FAQPage schemas, whose content is managed from the Semantic Analysis and Knowledge-Based Trust pages. There is no per-page schema type dropdown. Fixing many pages one by one is still slow, so for large batches we recommend contacting support. **
Because of this, we recommend the following for large batches of mislabeled pages:
- Hold off on deploying the affected pages so incorrect schema does not go live on your site.
- Do not regenerate repeatedly. If the page signals have not changed, OTTO will likely produce the same type again.
- Contact support with the details below so our team can review the pages and advise on the best way to correct the type in bulk.
π οΈ Options for Getting BlogPosting Schema
- Ask support to review the batch. This is the best option when dozens or hundreds of pages are affected. Our team can look at why the pages were classified as CollectionPage and recommend a fix.
- Adjust the page itself. If a template shows long lists of related posts or lacks clear article elements, adding a visible title, author, and publish date, and reducing list-style content, can help OTTO recognize the page as an article.
- Edit the schema directly for a few pages. You can change the schema type in the schema drawer by editing the @type in the schema JSON, and you can do this before or after deploying, so you don't need to deploy the wrong type first. This is practical for a small number of pages but not for large batches, where you should ask support to review.
- Use custom schema code. If you prefer to write your own BlogPosting markup, you can replace the generated schema with custom code once the page is deployed and editable.
π What to Include When You Contact Support
Sending complete information the first time helps us resolve your request faster. Please include:
- Your project or domain name.
- The number of affected pages, for example 194.
- Three to five example URLs.
- The current schema type (CollectionPage) and the type you want (BlogPosting).
- Confirmation that these pages are individual blog posts and not category or archive pages.
- Whether the pages are deployed or not yet deployed.
π§ͺ Verify the Result
After the schema is corrected and deployed, check a sample of pages:
- Open the live page and copy its URL.
- Paste it into Google's Rich Results Test or the Schema Markup Validator.
- Confirm that the detected type is BlogPosting and that there are no errors.
π‘ Tips to Avoid This in the Future
- Keep blog posts in a consistent URL structure that is clearly different from category and archive pages.
- Make sure each post shows a clear headline, author, and publish date.
- Review a small sample of generated schema before deploying a large batch.
π¬ 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.