---
title: "SEOCode Rule Engine 1.3.2: Three New Schema Rules for Speakable, IPTC Media Provenance, and Shipping Vocabulary"
date: 2026-06-09
version: 1.3.2
slug: rule-engine-1-3-2
description: "Version 1.3.2 adds three new schema rules covering Google's removal of Speakable rich result support, IPTC digital source type tagging for AI-generated media, and deprecated shipping schema types."
tags: [schema, structured-data, release-notes, ai-content, ecommerce]
---
SEOCode Rule Engine 1.3.2: Three New Schema Rules for Speakable, IPTC Media Provenance, and Shipping Vocabulary
Version 1.3.2 adds three new schema rules that reflect recent changes to schema.org's vocabulary and Google's supported structured data features — covering a removed rich result type, AI-generated media provenance, and deprecated ecommerce shipping types.
New Rules
speakable-schema-deprecated — SpeakableSpecification structured data no longer supported
Severity: Warning | Category: Schema
SpeakableSpecification was introduced in schema.org 3.2 and promoted to core in 3.5. It was designed to mark sections of a document as well-suited for text-to-speech rendering. Google has since removed Speakable from its list of supported rich result types and no longer processes SpeakableSpecification for any Search feature.
Why it matters: Implementing this schema type has no effect on how your content appears in Google Search. It is dead weight in your structured data. The type still exists in the schema.org vocabulary and may be consumed by other platforms, but if your goal is Google Search optimization, this markup does nothing.
What to do: If SEOCode flags this rule, audit whether you have a specific non-Google reason to keep SpeakableSpecification markup. If not, remove it to reduce structured data noise.
schema-org-iptc-digital-source-type — Missing IPTCDigitalSourceEnumeration for AI-generated media
Severity: Info | Category: Schema
Schema.org 24.0 introduced the IPTCDigitalSourceEnumeration vocabulary with 14 coded values describing the origin of digital media. Schema.org 29.4 added further missing enumeration values. The vocabulary is applied via the digitalSourceType property on MediaObject and its subtypes: ImageObject, VideoObject, and AudioObject.
Relevant values include:
-
TrainedAlgorithmicMediaDigitalSource— content generated entirely by a trained algorithm (e.g., an AI image generator) -
CompositeWithTrainedAlgorithmicMediaDigitalSource— content that combines real-world capture with AI-generated elements
Why it matters: Google uses digitalSourceType as a content provenance signal in its "About this image" feature. Correctly tagging AI-generated or AI-assisted media helps search engines and users understand the origin of your content. This also aligns with C2PA metadata standards, which are increasingly relevant for content authenticity. This rule complements the existing c2pa-metadata rule in SEOCode.
What to do: For any ImageObject, VideoObject, or AudioObject in your structured data that represents AI-generated or AI-assisted media, add the digitalSourceType property with the appropriate IPTCDigitalSourceEnumeration value. If the media is fully human-captured with no algorithmic manipulation, tagging it explicitly is still good practice for provenance clarity.
Example:
{
"@type": "ImageObject",
"url": "https://example.com/image.jpg",
"digitalSourceType": "https://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia"
}
schema-org-shipping-vocabulary-updated — Deprecated shipping schema types in use
Severity: Warning | Category: Schema
Schema.org 29.0 deprecated DeliveryTimeSettings and ShippingRateSettings, replacing them with updated shipping vocabulary types.
Why it matters: Google uses shipping structured data to populate shipping information in merchant listings and product rich results. As Google adopts the updated schema.org vocabulary, relying on deprecated types risks your shipping data being misread or ignored in product search features. The impact may not be immediate, but staying on deprecated types creates technical debt that will need to be resolved before it affects your merchant listings.
What to do: If your product structured data uses DeliveryTimeSettings or ShippingRateSettings, migrate to the replacement types introduced in schema.org 29.0. Refer to the schema.org release notes for the specific replacement type names and property mappings.
Sources & References
Catch SEO issues before they ship
SEOCode reviews every pull request against the latest Google SEO rules — automatically. No manual audits. No surprises after deploy.
It checks for missing metadata, broken structured data, hreflang errors, robots.txt issues, and more — right inside your existing GitHub workflow.
Top comments (0)