π Understand the schema setting
Domain-level schema describes your website or organization as a whole. Page-level schema describes an individual page, such as a blog post or service page. Changing the domain-level setting is not the same as correcting a single page.
If OTTO detects a blog post as a Service page and you only see a domain-level dropdown, do not change that dropdown to fix the individual page.
π οΈ Check the affected page
- Open the affected URL and confirm that it is the blog post you want to correct.
- In OTTO, review the schema information shown for that specific page. Note the detected Service type and any available page-specific editing or deployment options.
- Check the pageβs existing schema in your website editor, SEO plugin, or other tool that adds structured data. The Service type may already be present in the pageβs source.
- If you find incorrect Service schema, update or remove it at its source. Add the appropriate article schema for the blog post using the tool you normally use to manage page schema.
- Publish your page changes, then review the page in OTTO. Do not assume that publishing or a normal recrawl will change an existing detected page type. If the type remains incorrect, contact Support for help.
In Schema Markup β Page-Level Schemas, review the schema for the URL and use the available schema editing or deployment options as appropriate. These controls do not change the detected Page Type. Do not change the domain-level setting as a workaround; contact Support if the page type is incorrect. **Source notes:** The schema drawer displays Page Type as text and provides a βDeploy this Schemaβ action (customer-frontend/src/modules/otto/v3/overview/body/issuesTable/baseModels/schema/components/schemaDrawer/index.tsx:664β665, 1071). The normal reprocessing path selects pages for type detection only when their existing page type is empty (content-assistant/app/ca/pipelines/reprocess\_pages\_helpers.py:260β263). The backend also contains a separate project-wide regeneration endpoint, but its presence alone does not establish that a customer-facing control is available (content-assistant/app/ca/api/v2/views/otto\_page\_type\_regen.py:1β7).
β Verify the result
Check the published pageβs structured data to confirm that it describes the blog post and that an unwanted Service type is no longer present. Also check for duplicate or conflicting schema added by different tools.
If Service is still detected, note the page URL, where you see the detection in OTTO, and what you have already changed. This information will help the support team investigate.
π¬ Get 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.