Avoid Conflicting Article-Type Schemas

Estimated reading: 2 minutes 6 views

Article, BlogPosting, and NewsArticle are related schema types.

If more than one of these is assigned to the same post type, Schema Manager displays a warning.

The warning recommends using only one article-type schema per page and selecting the most specific type for the content:

This helps avoid overlapping article-type configurations for the same content.

Schema Types with Different Configuration Requirements

Not every schema type uses the same configuration.

For example:

Article uses post-type assignment and field mappings.

FAQ uses a post/page selection plus manually configured questions and answers.

Website is configured globally.

Organization uses organization, contact, address, and social information.

Author first requires choosing between Person and Organization.

Product provides product-specific fields such as SKU, price, stock status, category, and offers.

For this reason, always configure the fields displayed for the specific schema type you select.

Schema Manager is part of the Premium plan.

If Schema Manager is not available under the current license, the page displays a Premium Required notice.

The screen provides:

If you have upgraded but Schema Manager still shows the Premium Required screen, use Refresh License Status to refresh the current license state.