DEV Community: SEOCode

SEOCode Rules Update v1.4.6

SEOCode — Sat, 05 Sep 2026 21:21:23 +0000

---
title: "SEOCode Rule Engine v1.4.6: Agentic Commerce Protocols and IndexNow"
date: 2026-09-05
version: 1.4.6
slug: rule-engine-v1-4-6-agentic-commerce-indexnow
description: "Version 1.4.6 adds two new informational rules: one flagging missing agentic commerce protocol (ACP/UCP) support on ecommerce sites, and one flagging missing IndexNow implementation for faster search engine indexing."
tags:
  - rule-engine
  - changelog
  - technical-seo
  - ecommerce
  - indexnow
  - agentic-commerce
---

SEOCode Rule Engine v1.4.6: Agentic Commerce Protocols and IndexNow

Version 1.4.6 adds two new informational rules that address how search engines and AI agents discover and index your content — one targeting ecommerce sites preparing for AI-driven shopping, and one targeting any site that wants faster indexing after publishing or updating content.

New Rules

`acp-ucp-agentic-commerce-protocols` — Agentic commerce protocols (ACP/UCP) not implemented

Severity: Info

Category: Technical

What it checks

This rule flags ecommerce sites that have not implemented either the Agent Commerce Protocol (ACP) or the Universal Commerce Protocol (UCP).

What ACP and UCP are

ACP and UCP are emerging protocols designed to give AI shopping agents a structured, programmatic interface to ecommerce sites. Instead of parsing HTML or simulating a browser session, an AI agent using these protocols can directly query a site for product data, pricing, availability, and checkout flows through defined endpoints.

Google has referenced UCP in its AI optimization guidance as an emerging standard for Search agents. These protocols extend the broader concept of "agent-friendly" websites — sites that are structured so that AI agents can reliably extract and act on information — into the specific domain of commerce transactions.

Why it matters for SEO

AI-driven shopping experiences are growing. Crawl data from Botify shows that AI bots are meaningfully increasing their crawl volume across the web, and ecommerce sites that structure their product data for agent-driven discovery are better positioned as these experiences mature.

Neither ACP nor UCP is a formal ranking signal today. This rule is flagged at info severity for that reason — it is not a regression that will hurt you now, but it is a gap worth tracking as the ecosystem develops. Sites that adopt early will have a structural advantage when AI agent-driven shopping becomes a mainstream discovery channel.

What you need to do

This rule will not block a PR or trigger a warning. It surfaces as an informational flag on ecommerce repositories so that the relevant teams are aware of the protocols.

If you want to act on it:

Review the UCP specification and Google's AI optimization guidance to understand the endpoint and data structure requirements.
Review the ACP specification for agent transaction interfaces.
Assess whether your product data (pricing, availability, checkout) can be exposed through these interfaces without creating security or business logic risks.

There is no urgency here. The rule exists to make sure the conversation happens before these protocols become table stakes.

`indexnow-protocol` — IndexNow protocol not implemented for faster indexing

Severity: Info

Category: Technical

What it checks

This rule flags sites that have not implemented the IndexNow protocol.

What IndexNow is

IndexNow is an open protocol that lets a website push notifications to participating search engines — currently Bing, Yandex, and others — whenever a URL is published, updated, or deleted. Google is evaluating adoption.

The default model for search engine indexing is pull-based: crawlers visit your site on their own schedule and discover changes when they happen to crawl the relevant URLs. IndexNow flips this to a push-based model. When you publish or update a page, you send a lightweight HTTP request to the IndexNow endpoint, and participating search engines are notified immediately.

Why it matters for SEO

Crawl budget is finite and unevenly distributed. Large, high-authority sites get crawled frequently. Mid-sized sites often wait days or weeks for updated content to be re-crawled and re-indexed. For content types where freshness matters — news articles, ecommerce product pages with price or availability changes, job listings, event pages — that delay has a direct impact on search visibility.

IndexNow does not guarantee faster indexing on Google (which has not yet adopted the protocol), but it meaningfully accelerates indexing on Bing and other participating engines. For sites where Bing drives material traffic, or where content freshness is a competitive factor, the implementation cost is low relative to the benefit.

Bing Webmaster Tools provides native IndexNow integration, which reduces the implementation overhead further.

What you need to do

This rule is flagged at info severity. It will not block a PR.

If you want to implement IndexNow:

Generate an IndexNow API key and host the key file at the root of your domain (e.g., https://yourdomain.com/{key}.txt).
Add a call to the IndexNow endpoint (https://api.indexnow.org/indexnow) whenever a URL is published, updated, or deleted. This is typically a one-line addition to your CMS publish hook or deployment pipeline.
Optionally, configure Bing Webmaster Tools for native integration.

The full specification and key generation tool are available at indexnow.org.

Sources & References

Botify Blog — "ACP vs. UCP: The New Protocols Shaping Agentic Commerce"; "UCP: What It Is, Why It Matters, & How to Get Started for E-commerce"; "Why Mid-Sized Brands Should Use IndexNow to Accelerate Organic Search Growth" (scraped 2026-09-05)

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

SEOCode — Fri, 04 Sep 2026 17:17:59 +0000

---
title: "SEOCode Rule Engine v1.4.5: Vacation Rental Schema, Movie Schema, and European Licensing Info"
date: 2026-09-04
version: 1.4.5
slug: rule-engine-v1-4-5
description: "Version 1.4.5 adds three new informational rules covering Vacation Rental structured data, Movie structured data, and the Google European Search Dataset Licensing Program."
tags:
  - changelog
  - structured-data
  - schema
  - technical-seo
  - rich-results
---

Rule Engine v1.4.5: Vacation Rental Schema, Movie Schema, and European Licensing Info

Version 1.4.5 adds three new informational rules that surface structured data opportunities and a publisher licensing program that SEOCode previously had no coverage for.

No rules were updated or deprecated in this release.

New Rules

`vacation-rental-schema` — Missing Vacation Rental structured data

Severity: Info | Category: Schema

What it checks
This rule flags pages that list vacation rental properties but do not include VacationRental structured data.

Why it matters
Google Search supports VacationRental structured data and uses it to generate rich results for vacation property listings. Implementing it gives your listings a chance to appear with enhanced presentation in search results — including property name, description, images, location, rating, and reviews — directly in the SERP. Without it, Google has to infer all of that from unstructured page content, which is less reliable and forfeits the rich result opportunity entirely.

What you need to do
If your site lists vacation rental properties, add VacationRental structured data (JSON-LD recommended) to those pages. Refer to Google's documentation for the required and recommended properties. This rule will fire on any property listing page that SEOCode identifies as a vacation rental listing but finds no corresponding schema markup.

`movie-schema` — Missing Movie structured data for movie listing pages

Severity: Info | Category: Schema

What it checks
This rule flags pages that publish movie listings, movie databases, or editorial movie content but do not include Movie structured data.

Why it matters
Google Search uses Movie structured data to power movie carousel rich results — the kind that appear for queries like "best movies of 2023." If your site publishes movie content and you want it to be eligible for that carousel, structured data is the mechanism that makes it possible. Without it, your content cannot participate in that rich result type regardless of how well it ranks.

What you need to do
Add Movie structured data (JSON-LD recommended) to pages that describe individual movies. At minimum, include the movie title, director, and at least one image. This rule will fire on pages SEOCode identifies as movie content pages that are missing the markup.

`european-search-dataset-licensing` — European Search Dataset Licensing Program eligibility

Severity: Info | Category: Technical

What it checks
This rule surfaces an informational notice for publishers in the European Economic Area (EEA) about the Google European Search Dataset Licensing Program.

Why it matters
Google has updated the program overview, eligibility criteria, and application details for this program. It is a formal licensing arrangement between Google and EEA publishers — separate from standard indexing and crawling. If your organization publishes content in the EEA and you are interested in licensing that content to Google Search under this program, the eligibility criteria have changed and you should review the updated documentation.

What you need to do
This rule does not indicate a technical problem with your site. It is an informational flag for EEA publishers only. If this applies to you, review the updated program page linked in the Sources section below. If you are not an EEA publisher, this rule is not relevant to your situation and can be suppressed in your SEOCode configuration.

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.

Try SEOCode →

SEOCode Rules Update v1.4.4

SEOCode — Sat, 29 Aug 2026 06:45:30 +0000

---
title: "Rule Engine Update: Site Reputation Abuse (EEA), Favicon Checks, and Preferred Sources — v1.4.4"
date: 2026-08-29
version: 1.4.4
slug: rule-engine-update-1-4-4
description: "SEOCode v1.4.4 adds a new warning for Google's EEA-adjusted site reputation abuse policy enforcement and updates rules for favicon validation and preferred sources markup."
tags:
  - rule-engine
  - changelog
  - technical-seo
  - google-search
---

Rule Engine Update v1.4.4 — Site Reputation Abuse (EEA), Favicon Checks, and Preferred Sources

Google's adjusted enforcement of the site reputation abuse policy in the European Economic Area is now flagged in pull requests — along with updated checks for favicons and preferred sources markup.

New Rules

`site-reputation-policy-eea` — Site reputation abuse policy adjusted for EEA

Severity: Warning

What it checks:
This rule flags sites that may be hosting third-party content in a way that could be interpreted as exploiting the site's existing ranking signals — specifically under Google's site reputation abuse policy. The new rule accounts for the fact that Google has adjusted how it enforces this policy within the European Economic Area (EEA), meaning the enforcement approach differs from the global baseline.

The policy itself is unchanged in its intent: hosting third-party content on a site to piggyback on that site's authority — regardless of whether the site owner is directly involved in or overseeing that content — is prohibited. What has changed is the regional enforcement posture for EEA-based sites.

Why it matters for SEO:
A violation of the site reputation abuse policy can result in a manual action against part or all of your site. If your site operates in the EEA, the enforcement path may look different from what Google's global documentation describes, which creates ambiguity that can lead to unintentional non-compliance.

What you need to do:
If your site is based in or serves the EEA and you host any third-party content — sponsored sections, partner-contributed pages, syndicated content, affiliate hubs — review Google's updated site reputation abuse policy documentation for EEA-specific guidance. If SEOCode flags this rule in a PR, it means content or configuration changes in that PR warrant a manual review against the policy before merging.

Updated Rules

`favicon-aspect-ratio` — Favicon incorrect size, aspect ratio, or unsupported file format

What changed: The rule's description, name, fix template, and source reference have all been updated to reflect current Google documentation.

What it checks:
This rule validates that your site's favicon meets Google's requirements for use in Search results — specifically that the image is square (1:1 aspect ratio), meets minimum size requirements, and uses a supported file format.

Why it matters for SEO:
Google displays favicons in mobile search results next to your site name. An incorrectly sized, non-square, or unsupported favicon will be replaced by a generic placeholder. This doesn't affect ranking directly, but it does affect click-through appearance and brand recognition in the SERP.

What you need to do:
If this rule fires in a PR, check the updated fix template in the SEOCode annotation — the guidance has been revised to align with the latest Google documentation. Ensure your favicon is square, at least 48×48px, and served in a supported format (PNG, ICO, SVG, or WebP).

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

What changed: The rule's description, fix template, and source reference have been updated.

What it checks:
This rule checks whether your site has the appropriate markup or configuration in place to signal preferred sources to Google — relevant for sites that want to influence how Google identifies authoritative or preferred versions of their content.

Why it matters for SEO:
Without correct preferred sources configuration, Google may surface versions of your content that you did not intend as canonical or authoritative. This is particularly relevant for publishers, news sites, and any site where content appears in multiple forms or locations.

What you need to do:
Review the updated fix template in the SEOCode PR annotation if this rule fires. The description and recommended implementation steps have been revised — if you previously addressed this rule based on older guidance, it is worth re-checking your implementation against the updated documentation.

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 →

SEOCode Rules Update v1.4.3

SEOCode — Thu, 20 Aug 2026 14:11:59 +0000

---
title: "SEOCode Rule Engine Update: schema.org v30, EU Digital Product Passport, and HTTP QUERY Method"
date: 2026-08-20
version: 1.4.3
slug: rule-engine-update-1-4-3
description: "Version 1.4.3 adds four new informational rules covering schema.org v30 vocabulary changes, EU Digital Product Passport structured data, financial incentive markup, and Google's future support for the HTTP QUERY method."
tags:
  - rule-engine
  - schema-org
  - structured-data
  - technical-seo
  - ecommerce
---

Rule Engine Update 1.4.3: schema.org v30, EU Digital Product Passport, and HTTP QUERY Method

Version 1.4.3 adds four new informational rules that surface emerging structured data vocabulary and a forthcoming web standard — none require immediate action, but all have concrete implications for ecommerce sites and developers building search-facing APIs.

New Rules

`schema-org-v30-equivalence-annotations` — schema.org v30 cross-vocabulary equivalences

What it checks: Whether your site uses schema.org structured data alongside Open Graph tags, GS1 product identifiers, or Dublin Core metadata — and flags that schema.org v30 now formally declares equivalences between its vocabulary and those external systems.

Why it matters for SEO: Schema.org v30 added formally declared equivalence annotations linking schema.org properties to terms in GS1 (used for product identification in retail and supply chains), Dublin Core (widely used in publishing and library metadata), and Open Graph (used for social sharing previews). "Formally declared" means these equivalences are machine-readable and part of the schema.org vocabulary itself, not just informal documentation.

For sites that already implement both schema.org structured data and Open Graph tags — which is common — this alignment means parsers and search engines can more reliably reconcile the two metadata systems. For ecommerce sites using GS1 identifiers (barcodes, GTINs, GLNs), the equivalence annotations improve interoperability with supply chain and merchant data systems.

v30 also extended the credential vocabulary to cover credentials beyond educational credentials, and extended CompoundPriceSpecification to use the more generic UnitPriceSpecification as its base type.

What you need to do: No immediate markup changes are required. If you maintain sites that use GS1 identifiers or Dublin Core metadata alongside schema.org, review the v30 vocabulary to confirm your existing markup aligns with the newly declared equivalences. If you use CompoundPriceSpecification, check whether the updated type hierarchy affects your implementation.

`schema-org-v30-eu-digital-product-passport` — EU Digital Product Passport structured data examples

What it checks: Whether ecommerce sites targeting EU markets are aware that schema.org v30 now provides vocabulary and examples for implementing EU Digital Product Passport (DPP) data in structured data, aligned with UN/CEFACT codes.

Why it matters for SEO: The EU Digital Product Passport is a regulatory requirement under the EU Ecodesign for Sustainable Products Regulation (ESPR). When it comes into force, products sold in the EU will need to carry a digital record covering sustainability, repairability, and lifecycle data. Schema.org now provides the vocabulary to express this data in structured form.

From an SEO perspective, structured data that satisfies regulatory requirements and is machine-readable by search engines creates an opportunity for richer product representations in search results — particularly as search engines expand merchant and product listing features. Getting ahead of the vocabulary now means less retrofit work when DPP requirements become mandatory.

What you need to do: If you sell physical products in EU markets, review the schema.org DPP examples and UN/CEFACT code alignment. No implementation is required today, but understanding the vocabulary now will reduce the cost of compliance when ESPR requirements take effect.

`schema-org-v29-financial-incentives` — Missing financial incentive structured data for eligible offers

What it checks: Whether product offers on ecommerce sites that include sustainability-related incentives, rebates, or government-backed financial incentives are missing the financial incentive structured data vocabulary introduced in schema.org v29.

Why it matters for SEO: Schema.org v29 added new types and enumeration types — including IncentiveQualifiedExpenseType — along with new properties for Offer, including eligibleWithSupplier. This vocabulary lets you express conditions attached to an offer: for example, that a product qualifies for a government energy-efficiency rebate, or that a financial incentive is available when purchased through a specific supplier.

Search engines use Offer structured data to populate merchant listings and product rich results. If your offers have conditions that affect their effective price or eligibility, and those conditions aren't expressed in structured data, search engines may display incomplete or misleading offer information. Financial incentives are increasingly common in sustainability-adjacent product categories (EV chargers, heat pumps, energy-efficient appliances), where the incentive can be a significant part of the purchase decision.

What you need to do: If your product offers include rebates, sustainability incentives, or supplier-conditional pricing, review the schema.org v29 financial incentive vocabulary and add the relevant properties to your Offer markup. At minimum, audit whether your current Offer structured data accurately reflects the conditions under which listed prices apply.

`http-query-method-google-search` — Google Search will eventually support HTTP QUERY method

What it checks: Flags awareness that Google has indicated it will eventually support the HTTP QUERY method in Google Search, and surfaces this for teams building search interfaces or APIs.

Why it matters for SEO: The HTTP QUERY method is an emerging web standard designed to fill a gap between GET and POST. GET requests are safe and cacheable but cannot carry a request body. POST requests can carry a body but are neither safe nor cacheable by default. QUERY is designed to be safe and cacheable while also supporting a request body — making it suitable for expressive search and query interactions that don't fit cleanly into GET's URL-parameter model.

Google's indication that Search will eventually support QUERY is significant because it signals that the method is on a path toward mainstream adoption. For developers building search APIs, faceted search interfaces, or any system where query complexity exceeds what URL parameters can cleanly express, QUERY is worth tracking.

What you need to do: Nothing immediately. Monitor the IETF standardization progress for HTTP QUERY and Google's implementation timeline. If you are designing new search or query APIs, factor QUERY into your architecture planning so you are not locked into patterns that will require significant rework later.

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.

Try SEOCode →

SEOCode Rules Update v1.4.1

SEOCode — Thu, 20 Aug 2026 05:11:31 +0000

---
title: "Rule Engine Update: AI Search Optimization Rules Refreshed (v1.4.1)"
date: 2026-08-20
version: 1.4.1
slug: rule-engine-update-1-4-1
description: "SEOCode v1.4.1 updates two rules covering Google's generative AI search features, reflecting changes to Google's official AI optimization and eligibility documentation."
tags:
  - rule-engine
  - changelog
  - ai-search
  - generative-ai
---

Rule Engine Update: AI Search Optimization Rules Refreshed (v1.4.1)

Two rules covering Google's generative AI search features have been updated to reflect changes in Google's official documentation, scraped on 2026-08-20.

Updated Rules

`generative-ai-optimization` — Content not optimized for generative AI Search features

What it checks

This rule inspects page content for signals that Google's generative AI search features — including AI Overviews and other AI-generated summaries — use to decide whether to surface your content. That includes things like clear, factual prose; well-structured answers to specific questions; and proper use of structured data where applicable.

Why it matters

Google's AI Overviews pull from indexed pages, but not all indexed pages are treated equally. Pages that are structured to answer questions directly, with authoritative and unambiguous language, are more likely to be cited in AI-generated responses. If your content is vague, poorly structured, or relies on formatting that AI systems can't parse well, it may be skipped even when it's topically relevant.

What changed

The rule's description, fix template, and source reference have been updated to align with the current Google AI Optimization Guide. The guidance in that document has evolved, and the rule's recommendations now reflect the latest best practices Google has published.

What you need to do

If this rule is already passing in your PRs, no immediate action is required. If it's flagging issues, review the updated fix suggestions in the SEOCode PR comment — the recommended remediation may have changed from what you saw under v1.4.0.

`ai-features-snippet-eligibility` — Page not eligible for AI features due to snippet, indexing, or Search Console requirements

What it checks

This rule checks whether a page meets the baseline requirements for appearing in Google's AI-powered search features. Eligibility depends on several factors: the page must be indexed, snippet generation must not be blocked (e.g., via nosnippet or max-snippet:0 meta tags), and the site must not have settings in Search Console that restrict AI feature participation.

Why it matters

A page can rank well in traditional search and still be completely excluded from AI Overviews or other AI features if any one of these eligibility gates is closed. Developers often block snippets for legitimate reasons — for example, on thin pages or duplicate content — but those same directives will disqualify a page from AI features. This rule surfaces that trade-off at PR time, before the change ships.

What changed

The rule's name has been updated to more precisely describe the three eligibility axes it covers: snippet settings, indexing status, and Search Console configuration. The description and fix template have also been revised to match the current Google AI Features in Search documentation.

What you need to do

Check whether the rule name change affects any suppression rules or ignore configurations you have in .seocode.yml. If you were suppressing this rule by name, update the identifier to match. The rule ID (ai-features-snippet-eligibility) has not changed, so ID-based suppressions are unaffected.

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.

Try SEOCode →

SEOCode Rules Update v1.4.0

SEOCode — Thu, 20 Aug 2026 04:58:33 +0000

---
title: "SEOCode Rule Engine 1.4.0: Eight New Rules Covering Spam, Schema, AMP, and Canonicalization"
date: 2026-08-20
version: 1.4.0
slug: rule-engine-1-4-0
description: "Version 1.4.0 adds eight new rules responding to Google's August 2026 Spam Update, updated review snippet and product schema guidelines, AMP hosting changes, and canonicalization timing clarifications."
tags:
  - changelog
  - schema
  - technical-seo
  - spam
  - amp
  - canonicalization
  - reviews
  - product-schema
---

SEOCode Rule Engine 1.4.0: Eight New Rules Covering Spam, Schema, AMP, and Canonicalization

Version 1.4.0 adds eight new rules in response to Google documentation updates and the August 2026 Spam Update, covering review integrity, product schema, AMP hosting behavior, canonicalization timing, and more.

New Rules

`google-august-2026-spam-update` — Google August 2026 Spam Update Released

Severity: Warning | Category: Technical

What it checks: This rule flags codebases and configurations that exhibit patterns associated with Google's spam policies: cloaking (serving different content to Googlebot than to users), doorway pages, scaled content abuse, site reputation abuse, back button hijacking, and fake reviews.

Why it matters: Google's spam updates can cause severe ranking drops or complete removal from search results. Unlike broad core updates, spam updates target specific policy violations. If your site is hit, rankings do not recover on their own — you must identify and fix the violation, then submit a reconsideration request if a manual action was applied.

What to do: Review your codebase for any server-side logic that conditionally serves different HTML to known crawler user agents. Audit any programmatically generated content at scale. If you implement review markup, see the fake-incentivized-reviews-policy rule below.

`fake-incentivized-reviews-policy` — Fake or Undisclosed Incentivized Reviews Violate Review Snippet Guidelines

Severity: Critical | Category: Schema

What it checks: This rule detects Review and AggregateRating structured data on pages where reviews may be fake or where incentivized reviews are not disclosed. It flags patterns such as review markup on pages with no visible review content, or review schema on pages that solicit reviews in exchange for discounts or other benefits without disclosure.

Why it matters: Google has added an explicit guideline to its review snippet documentation prohibiting fake reviews and requiring disclosure of incentivized reviews. Violations put your site at risk of losing review rich results eligibility entirely. Depending on severity, a manual spam action may also be applied. This applies to both reviews you collect directly and third-party review markup you implement on your site.

What to do:

Never implement Review schema for reviews that were not genuinely given by real customers.
If you offer incentives (discounts, free products, loyalty points) in exchange for reviews, the review markup and the visible review text must clearly disclose this.
Audit any third-party review widgets you embed — you are responsible for the markup they inject into your pages.

`product-category-schema` — Missing `google_product_category` in Product Structured Data

Severity: Info | Category: Schema

What it checks: This rule checks Product and Offer structured data for the presence of the google_product_category property, which aligns with the Google Merchant Center feed attribute of the same name.

Why it matters: Google's updated product structured data documentation now details how google_product_category can be used within schema.org markup. Providing this property helps Google classify your products accurately in Search and Shopping, improving discoverability in merchant listings.

What to do: If you have Product or Offer schema on your pages, add the google_product_category property using the appropriate Google product taxonomy value. This is the same value you would use in a Merchant Center feed. If you do not run Shopping campaigns, this is informational — the property is not required for basic product rich results.

`sale-price-effective-date-schema` — Missing Sale Price Effective Date in Product Structured Data

Severity: Info | Category: Schema

What it checks: This rule checks Offer structured data on pages with a priceValidUntil or sale price for the presence of sale duration properties that correspond to the Merchant Center sale_price_effective_date attribute.

Why it matters: Google has added a "Sale duration" section to the Merchant listing guide explaining how to express sale price validity windows in schema.org markup. Without effective date information, Google cannot determine when a sale price is valid, which can result in incorrect or missing sale price display in product rich results and merchant listings.

What to do: If you mark up sale prices in your Offer schema, add the relevant schema.org date range properties to define when the sale price is active. Align these values with what you submit in your Merchant Center feed under sale_price_effective_date. Do not leave sale price markup in place after a sale has ended.

`canonicalization-reevaluation-time` — Canonicalization Changes Take Time to Re-Evaluate

Severity: Info | Category: Technical

What it checks: This rule detects pull requests that modify canonical tags (<link rel="canonical">), hreflang annotations, or other canonicalization signals within a short window after a previous change to the same signals on the same URLs.

Why it matters: Google's updated canonicalization troubleshooting guide clarifies that changes to canonical signals are not processed immediately. Re-evaluation can take days to weeks depending on crawl frequency and site size. Making rapid successive changes to canonical signals while waiting for previous changes to take effect creates conflicting signals and can further delay resolution.

What to do: When you change canonical tags or hreflang annotations, allow sufficient time — at minimum several days, potentially weeks for large sites — before making further changes to the same signals. Use Google Search Console's URL Inspection tool to monitor how Google has indexed a URL before modifying its canonicalization signals again.

`amp-direct-publisher-hosting` — AMP Cache and Signed Exchanges No Longer Required for AMP Pages

Severity: Info | Category: Technical

What it checks: This rule flags build configurations, deployment scripts, or documentation comments that reference AMP Cache update steps or signed exchange (SXG) setup as required steps for AMP pages to appear in Google Search.

Why it matters: Google has changed how it serves AMP pages: users are now taken directly to the publisher's AMP host rather than being served from the AMP Cache or via signed exchanges. This removes a maintenance burden. Existing AMP Cache configurations and signed exchange setups will not cause harm, but they are no longer required.

What to do: You do not need to take any action for existing AMP pages to continue appearing in Google Search. If your deployment pipeline includes steps specifically to update the AMP Cache or configure signed exchanges for Google Search purposes, those steps can be removed. AMP content continues to rank on the same basis as any other web page.

`social-video-platform-search-console` — Social and Video Platform Content Not Tracked in Search Console

Severity: Info | Category: Technical

What it checks: This rule surfaces an informational notice for repositories that contain YouTube embeds, social media embeds, or other video platform integrations, flagging that dedicated Search Console reporting is now available for this content type.

Why it matters: Google has published a new guide on analyzing social and video platform content performance in Search Console. If your site publishes or embeds YouTube videos or social platform content, you can now measure how that content performs in Google Search through dedicated reporting — separate from your standard web search performance data.

What to do: No code changes are required. If your site includes YouTube or social platform content, review Google's new Search Console guide to understand what data is available and how to use it to inform content decisions.

`package-tracking-early-adopters-closed` — Package Tracking Early Adopters Program No Longer Accepting New Partners

Severity: Info | Category: Schema

What it checks: This rule flags any pull requests that add package tracking structured data markup on sites that are not already enrolled in Google's package tracking early adopters program.

Why it matters: Google has updated the package tracking documentation to confirm the early adopters program is closed to new applicants. Implementing package tracking schema without program enrollment will not produce rich results in Google Search.

What to do: If your site is not already an accepted partner in the package tracking program, do not implement package tracking structured data — it will have no effect. If you are an existing partner, review the updated eligibility and feature availability sections of the package tracking documentation to confirm your implementation remains compliant.

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.

Try SEOCode →

SEOCode Rules Update v1.3.6

SEOCode — Thu, 18 Jun 2026 20:08:01 +0000

---
title: "Rule Engine Update 1.3.6: HTML Is the SEO Standard, Not Markdown"
date: 2026-06-18
version: 1.3.6
slug: rule-engine-update-1-3-6
description: "SEOCode 1.3.6 adds one new informational rule clarifying that Markdown files served as content carry no SEO advantage over HTML, per Google's own guidance."
tags:
  - rule-engine
  - changelog
  - technical-seo
  - html
  - markdown
---

Rule Engine Update 1.3.6: HTML Is the SEO Standard, Not Markdown

Version 1.3.6 adds one new informational rule based on explicit guidance from Google: serving content as Markdown files provides no SEO advantage over HTML, and HTML remains the canonical document format for Google Search.

New Rules

`html-standard-for-seo` — Markdown files have no SEO advantage over HTML

Severity: Info

Category: Technical

What the rule checks

This rule flags cases where content is being served directly as Markdown files — for example, .md files exposed at a public URL, or llms.txt-style Markdown documents intended to carry indexable content. It surfaces a warning when your repository appears to be routing Markdown files as primary content endpoints rather than rendering them as HTML before serving.

Why it matters for SEO

Google has stated directly that HTML is the standard for SEO, not Markdown. Google's crawlers and ranking systems are built around HTML as the document format of the web. A Markdown file served at a URL is not treated as an equivalent substitute for a properly structured HTML page. If you are publishing content you want to rank — articles, documentation, landing pages — and that content is being delivered as raw Markdown rather than rendered HTML, you are working against how Google's systems are designed to process and evaluate pages.

This rule complements the existing llms-txt-not-required rule. That rule addresses the specific pattern of creating llms.txt files for AI crawlers. This rule addresses the broader question: even setting aside AI-specific files, Markdown as a general content delivery format is not a recommended or advantaged format for SEO.

What you need to do

If this rule fires on your PR, check whether the files being added or modified are:

Served directly as .md files at a public URL — If so, consider whether those files should be rendered to HTML before being served. Most static site generators (Jekyll, Hugo, Eleventy, Next.js, etc.) do this automatically. Verify your build pipeline is not accidentally exposing raw Markdown at canonical URLs.
Intended only as source files — If the .md files are build inputs that get compiled to HTML, and the HTML output is what gets served and indexed, no action is needed. The rule is informational and may not apply to your setup.
Intended as AI-readable documents — See llms-txt-not-required for guidance on that specific pattern.

No code change is required if your Markdown files are already being rendered to HTML by your build process. This rule exists to catch cases where that rendering step is missing or bypassed.

Sources & References

Search Engine Roundtable — "Google: HTML The Standard For SEO, Not Markdown Files" (scraped 2026-06-18)

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

SEOCode — Thu, 18 Jun 2026 19:38:30 +0000

---
title: "SEOCode Rule Engine Update: v1.3.5"
date: 2026-06-18
version: 1.3.5
slug: rule-engine-update-1-3-5
description: "Version 1.3.5 adds two new rules covering domain migration subdomain variant requirements and the final removal of FAQ rich result documentation from Google Search Central."
tags:
  - rule-engine
  - changelog
  - technical-seo
  - schema
  - domain-migration
---

SEOCode Rule Engine Update: v1.3.5

Version 1.3.5 adds two new rules reflecting changes Google made to its Search Central documentation on 2026-06-18: updated site move guidance that now explicitly requires migrating all subdomain variants, and the complete removal of FAQ rich result documentation confirming the feature is dead.

New Rules

`site-move-domain-variants` — Site move guidance: include all domain variants

Severity: Warning
Category: Technical

What it checks

When SEOCode detects a domain migration in progress (based on redirect configurations, canonical changes, or Search Console Change of Address signals in your codebase), this rule verifies that all subdomain variants of the origin domain are accounted for in the migration. Specifically, it flags cases where www and non-www variants are not both being migrated.

For example: migrating example.com → newdomain.com without also migrating www.example.com → www.newdomain.com (or the appropriate canonical target) will trigger this warning.

Why it matters for SEO

Google's Change of Address tool works at the domain level, but ranking signals are associated with specific URLs — including both www and non-www variants. If you only submit a Change of Address for one variant, Google may consolidate signals for that variant but leave the other behind. The result is a slower, incomplete migration where some of your historical ranking authority doesn't transfer to the new domain.

Google updated its site move documentation on 2026-06-18 to make this requirement explicit. This rule encodes that guidance so incomplete migrations are caught at the PR stage rather than weeks later in Search Console.

What you need to do

If this rule fires on your PR:

Confirm that both www.olddomain.com and olddomain.com have redirects pointing to the correct destination on the new domain.
Submit the Change of Address tool in Google Search Console for each variant separately — the tool does not automatically apply to both.
Ensure canonical tags on the new domain are consistent and point to your preferred variant.

If your site only ever served one variant (e.g., you enforced www everywhere and non-www returned a redirect), document that in your migration plan. The rule accepts a configuration override for sites that can confirm only one variant was ever active.

`faq-rich-result-documentation-removed` — FAQ rich result documentation fully removed

Severity: Info
Category: Schema

What it checks

This rule flags any use of FAQPage structured data in your codebase. It does not block merges. It surfaces as an informational notice to ensure developers are aware that FAQPage schema produces no rich result benefit in Google Search as of this update.

Note: The existing rule faq-schema-deprecated already issues actionable guidance on removing or replacing FAQPage markup. This rule adds a milestone marker: Google has now fully removed the FAQ rich result documentation from Search Central, which is the final confirmation that the feature is gone — not deprecated, not limited, gone.

Why it matters for SEO

When Google deprecates a rich result type, there is typically a window where the documentation remains available and some implementations may still render. That window is now closed for FAQ rich results. The documentation removal on 2026-06-18 is the definitive signal that no implementation of FAQPage structured data will produce a visual rich result in Google Search.

Leaving FAQPage markup in your codebase is not harmful — it won't cause a penalty — but it is dead weight. It adds payload to your pages and creates maintenance surface for structured data that returns nothing.

What you need to do

This rule is informational only. No immediate action is required to merge. However, you should plan to:

Remove FAQPage structured data from your templates and components.
If you were using FAQ rich results as a click-through rate strategy, evaluate alternatives such as HowTo (where applicable and still supported) or improving on-page content directly.
Check your structured data testing pipeline — if you have tests that assert FAQPage schema is present, those tests are now asserting the presence of inert markup and should be updated or removed.

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 →

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

SEOCode Rule Engine v1.4.6: Agentic Commerce Protocols and IndexNow

New Rules

acp-ucp-agentic-commerce-protocols — Agentic commerce protocols (ACP/UCP) not implemented

What it checks

What ACP and UCP are

Why it matters for SEO

What you need to do

indexnow-protocol — IndexNow protocol not implemented for faster indexing

What it checks

What IndexNow is

Why it matters for SEO

What you need to do

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.4.5

Rule Engine v1.4.5: Vacation Rental Schema, Movie Schema, and European Licensing Info

New Rules

vacation-rental-schema — Missing Vacation Rental structured data

movie-schema — Missing Movie structured data for movie listing pages

european-search-dataset-licensing — European Search Dataset Licensing Program eligibility

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.4.4

Rule Engine Update v1.4.4 — Site Reputation Abuse (EEA), Favicon Checks, and Preferred Sources

New Rules

site-reputation-policy-eea — Site reputation abuse policy adjusted for EEA

Updated Rules

favicon-aspect-ratio — Favicon incorrect size, aspect ratio, or unsupported file format

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

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.4.3

Rule Engine Update 1.4.3: schema.org v30, EU Digital Product Passport, and HTTP QUERY Method

New Rules

schema-org-v30-equivalence-annotations — schema.org v30 cross-vocabulary equivalences

schema-org-v30-eu-digital-product-passport — EU Digital Product Passport structured data examples

schema-org-v29-financial-incentives — Missing financial incentive structured data for eligible offers

http-query-method-google-search — Google Search will eventually support HTTP QUERY method

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.4.1

Rule Engine Update: AI Search Optimization Rules Refreshed (v1.4.1)

Updated Rules

generative-ai-optimization — Content not optimized for generative AI Search features

ai-features-snippet-eligibility — Page not eligible for AI features due to snippet, indexing, or Search Console requirements

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.4.0

SEOCode Rule Engine 1.4.0: Eight New Rules Covering Spam, Schema, AMP, and Canonicalization

New Rules

google-august-2026-spam-update — Google August 2026 Spam Update Released

fake-incentivized-reviews-policy — Fake or Undisclosed Incentivized Reviews Violate Review Snippet Guidelines

product-category-schema — Missing google_product_category in Product Structured Data

sale-price-effective-date-schema — Missing Sale Price Effective Date in Product Structured Data

canonicalization-reevaluation-time — Canonicalization Changes Take Time to Re-Evaluate

amp-direct-publisher-hosting — AMP Cache and Signed Exchanges No Longer Required for AMP Pages

social-video-platform-search-console — Social and Video Platform Content Not Tracked in Search Console

package-tracking-early-adopters-closed — Package Tracking Early Adopters Program No Longer Accepting New Partners

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.3.6

Rule Engine Update 1.3.6: HTML Is the SEO Standard, Not Markdown

New Rules

html-standard-for-seo — Markdown files have no SEO advantage over HTML

What the rule checks

Why it matters for SEO

What you need to do

Sources & References

Catch SEO issues before they ship

SEOCode Rules Update v1.3.5

SEOCode Rule Engine Update: v1.3.5

New Rules

site-move-domain-variants — Site move guidance: include all domain variants

What it checks

Why it matters for SEO

What you need to do

faq-rich-result-documentation-removed — FAQ rich result documentation fully removed

What it checks

`acp-ucp-agentic-commerce-protocols` — Agentic commerce protocols (ACP/UCP) not implemented

`indexnow-protocol` — IndexNow protocol not implemented for faster indexing

`vacation-rental-schema` — Missing Vacation Rental structured data

`movie-schema` — Missing Movie structured data for movie listing pages

`european-search-dataset-licensing` — European Search Dataset Licensing Program eligibility

`site-reputation-policy-eea` — Site reputation abuse policy adjusted for EEA

`favicon-aspect-ratio` — Favicon incorrect size, aspect ratio, or unsupported file format

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

`schema-org-v30-equivalence-annotations` — schema.org v30 cross-vocabulary equivalences

`schema-org-v30-eu-digital-product-passport` — EU Digital Product Passport structured data examples

`schema-org-v29-financial-incentives` — Missing financial incentive structured data for eligible offers

`http-query-method-google-search` — Google Search will eventually support HTTP QUERY method

`generative-ai-optimization` — Content not optimized for generative AI Search features

`ai-features-snippet-eligibility` — Page not eligible for AI features due to snippet, indexing, or Search Console requirements

`google-august-2026-spam-update` — Google August 2026 Spam Update Released

`fake-incentivized-reviews-policy` — Fake or Undisclosed Incentivized Reviews Violate Review Snippet Guidelines

`product-category-schema` — Missing `google_product_category` in Product Structured Data

`sale-price-effective-date-schema` — Missing Sale Price Effective Date in Product Structured Data

`canonicalization-reevaluation-time` — Canonicalization Changes Take Time to Re-Evaluate

`amp-direct-publisher-hosting` — AMP Cache and Signed Exchanges No Longer Required for AMP Pages

`social-video-platform-search-console` — Social and Video Platform Content Not Tracked in Search Console

`package-tracking-early-adopters-closed` — Package Tracking Early Adopters Program No Longer Accepting New Partners

`html-standard-for-seo` — Markdown files have no SEO advantage over HTML

`site-move-domain-variants` — Site move guidance: include all domain variants

`faq-rich-result-documentation-removed` — FAQ rich result documentation fully removed

`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