DEV Community: SEOCode

SEOCode Rules Update v1.3.2

SEOCode — Tue, 09 Jun 2026 17:06:26 +0000

---
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

Schema.org Release Notes

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.

Try SEOCode →

SEOCode Rules Update v1.3.0

SEOCode — Tue, 09 Jun 2026 16:29:51 +0000

---
title: "SEOCode Rule Engine 1.3.0: AI Mode preferred sources, hasAdultConsideration schema, and third-party tool guidance"
date: 2026-06-09
version: "1.3.0"
slug: "rule-engine-1-3-0"
description: "Version 1.3.0 adds three new rules covering Google's expanded preferred sources feature, the new hasAdultConsideration merchant listing property, and Google's published guidance on evaluating third-party SEO tools."
tags: ["changelog", "rules", "schema", "technical-seo", "ai-overviews", "structured-data"]
---

SEOCode Rule Engine 1.3.0

Version 1.3.0 adds three rules reflecting changes Google published to its Search Central documentation on 2026-06-09, and updates one existing rule with revised references and fix guidance.

New Rules

`preferred-sources-ai-mode` — Preferred sources not configured for AI Mode and AI Overviews

Severity: Info

Google's preferred sources feature, which previously applied only to standard Google Search, now also applies to AI Overviews and AI Mode. Publishers who qualify and have correctly configured preferred sources can receive increased visibility in AI-generated search results.

What the rule checks:
This rule flags pages where identity signals required for preferred sources eligibility are absent or misconfigured. Specifically, it looks for:

Organization schema with a matching sameAs or url property
Site name schema (WebSite with a name property)
Self-referencing canonical URLs

Why it matters:
AI Overviews and AI Mode are now a significant surface in Google Search. Preferred sources is one of the few explicit mechanisms Google offers publishers to influence how their content is attributed in AI-generated answers. If your identity signals are broken or missing, you cannot benefit from this feature even if your site otherwise qualifies.

What to do:
Check that your site has valid Organization and WebSite structured data on your homepage, and that canonical URLs are correctly set across your pages. Then review Google's eligibility requirements for preferred sources (linked in the references below) to confirm your site qualifies.

`has-adult-consideration-schema` — Missing `hasAdultConsideration` property on adult merchant listings

Severity: Info

Google has added support for the hasAdultConsideration property in merchant listing structured data, aligning it with the existing Merchant Center feed specification.

What the rule checks:
This rule flags Product or Offer structured data on pages that appear to contain adult content but do not include the hasAdultConsideration property.

Why it matters:
Without this property, Google must infer whether a merchant listing contains adult content algorithmically. Incorrect classification can affect where and how your products appear in shopping experiences — either surfacing them in contexts where adult content is filtered out, or failing to apply appropriate filters. Explicit markup removes the ambiguity.

What to do:
If you operate a merchant site with adult product listings, add "hasAdultConsideration": true to the relevant Offer or Product structured data blocks. This is a direct signal to Google rather than leaving classification to inference.

Example:

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Example Product",
  "offers": {
    "@type": "Offer",
    "hasAdultConsideration": true,
    "price": "29.99",
    "priceCurrency": "USD"
  }
}

`third-party-seo-tools-guidance` — Third-party SEO tool recommendations not critically evaluated

Severity: Info

Google has published explicit guidance on how to evaluate recommendations from third-party SEO tools, services, and consultants.

What the rule checks:
This is a process-level rule rather than a markup check. It surfaces as an informational flag when SEOCode detects patterns in your codebase that are commonly associated with outdated or unverified SEO advice — for example, meta tags or structured data patterns that contradict current Google documentation.

Why it matters:
Google's guidance makes four points worth internalizing:

SEO tool recommendations do not necessarily reflect Google's actual ranking signals.
Many recommendations are based on correlation studies, not confirmed causation.
Advice can become outdated as Google's systems evolve.
Google Search Console data and official Search Central documentation should be the primary reference for SEO decisions.

This rule exists to prompt a review when your code contains patterns that may have originated from third-party tool output rather than verified guidance.

What to do:
When this rule fires, cross-reference the flagged pattern against the Google Search Central documentation. If the pattern is not supported or recommended there, treat it as unverified. No code change is automatically required — this rule is informational and intended to prompt a review step.

Updated Rules

`preferred-sources-feature` — Missing preferred sources markup or configuration

The existing rule covering preferred sources configuration has been updated with revised references, an updated description, and a new fix template to reflect Google's expansion of the feature to AI Overviews and AI Mode. The underlying check logic is unchanged; the update ensures the guidance surfaced in pull request comments points to current documentation.

What to do:
No action required unless this rule is already firing on your PRs. If it is, the updated fix template provides more accurate remediation steps than the previous version.

Sources & References

Google Search Central Documentation Changelog

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.

Try SEOCode →

DEV Community: SEOCode

SEOCode Rules Update v1.3.2

SEOCode Rule Engine 1.3.2: Three New Schema Rules for Speakable, IPTC Media Provenance, and Shipping Vocabulary

New Rules

speakable-schema-deprecated — SpeakableSpecification structured data no longer supported

schema-org-iptc-digital-source-type — Missing IPTCDigitalSourceEnumeration for AI-generated media

schema-org-shipping-vocabulary-updated — Deprecated shipping schema types in use

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.3.0

SEOCode Rule Engine 1.3.0

New Rules

preferred-sources-ai-mode — Preferred sources not configured for AI Mode and AI Overviews

has-adult-consideration-schema — Missing hasAdultConsideration property on adult merchant listings

third-party-seo-tools-guidance — Third-party SEO tool recommendations not critically evaluated

Updated Rules

preferred-sources-feature — Missing preferred sources markup or configuration

Sources & References

Catch SEO issues before they ship

`speakable-schema-deprecated` — SpeakableSpecification structured data no longer supported

`schema-org-iptc-digital-source-type` — Missing IPTCDigitalSourceEnumeration for AI-generated media

`schema-org-shipping-vocabulary-updated` — Deprecated shipping schema types in use

`preferred-sources-ai-mode` — Preferred sources not configured for AI Mode and AI Overviews

`has-adult-consideration-schema` — Missing `hasAdultConsideration` property on adult merchant listings

`third-party-seo-tools-guidance` — Third-party SEO tool recommendations not critically evaluated

`preferred-sources-feature` — Missing preferred sources markup or configuration