XooCode(){

DeactivateAction

DeactivateAction is a ControlAction subtype. The act of stopping or deactivating a device or application (e.g. stopping a timer or turning off a flashlight).

Full example of schema.org/DeactivateAction json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/DeactivateAction
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DeactivateAction",
  "name": "Example DeactivateAction"
}
</script>

Minimal valid version

The smallest markup that still produces a valid DeactivateAction entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/DeactivateAction (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DeactivateAction",
  "name": "Example"
}
</script>

Google rich results this unlocks

DeactivateAction is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). DeactivateAction becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common DeactivateAction mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Using bare ControlAction instead of the specific DeactivateAction subtype

    Wrong
    "@type": "ControlAction"
    Right
    "@type": "DeactivateAction"

    Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...

Leave a comment