The Ultimate DrinkAction
Schema Generator
The act of swallowing liquids.
Magic Build
Paste your URL below and our AI will automatically fill the DrinkAction fields for you.
Configuration
Live GeneratorWhy use DrinkAction?
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is DrinkAction Schema?
The act of swallowing liquids.
Google uses DrinkAction structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add DrinkAction Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement DrinkAction JSON-LD
Generate
Use the form above to fill in your details and generate valid DrinkAction JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
DrinkAction schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| actionAccessibilityRequirement | A set of requirements that must be fulfilled in order to perform an Action. If more than one value is specified, fulfilling one set of requirements will allow the Action to be performed. | ActionAccessSpecification | Optional |
| actionProcess | Description of the process by which the action was performed. | HowTo | Optional |
| actionStatus | Indicates the current disposition of the Action. | ActionStatusType | Optional |
| additionalType | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. | Text, URL | Optional |
| agent | The direct performer or driver of the action (animate or inanimate). E.g. *John* wrote a book. | Organization, Person | Optional |
| alternateName | An alias for the item. | Text | Optional |
| description | A description of the item. | Text, TextObject | Optional |
| disambiguatingDescription | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation. | Text | Optional |
| endTime | The endTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to end. For actions that span a period of time, when the action was performed. E.g. John wrote a book from January to *December*. For media, including audio and video, it's the time offset of the end of a clip within a larger file.\n\nNote that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions. | DateTime, Time | Optional |
| error | For failed actions, more information on the cause of the failure. Consider using the Error type. | Thing | Optional |
| expectsAcceptanceOf | An Offer which must be accepted before the user can perform the Action. For example, the user may need to buy a movie before being able to watch it. | Offer | Optional |
| identifier | The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details. | PropertyValue, Text, URL | Optional |
| image | An image of the item. This can be a URL or a fully described ImageObject. | ImageObject, URL | Recommended |
| instrument | The object that helped the agent perform the action. E.g. John wrote a book with *a pen*. | Thing | Optional |
| location | The location of, for example, where an event is happening, where an organization is located, or where an action takes place. | Place, PostalAddress, Text, VirtualLocation | Optional |
| mainEntityOfPage | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details. | CreativeWork, URL | Optional |
| name | The name of the item. | Text | Required |
| object | The object upon which the action is carried out, whose state is kept intact or changed. Also known as the semantic roles patient, affected or undergoer (which change their state) or theme (which doesn't). E.g. John read *a book*. | Thing | Optional |
| owner | A person or organization who owns this Thing. | Organization, Person | Optional |
| participant | Other co-agents that participated in the action indirectly. E.g. John wrote a book with *Steve*. | Organization, Person | Optional |
Example DrinkAction JSON-LD
Here's what valid DrinkAction structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "DrinkAction",
"name": "Example DrinkAction",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"actionAccessibilityRequirement": {
"@type": "ActionAccessSpecification",
"name": "Example ActionAccessSpecification",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"actionProcess": {
"@type": "HowTo",
"name": "Example HowTo",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"actionStatus": {
"@type": "ActionStatusType",
"name": "Example ActionStatusType",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"additionalType": "Example additionalType",
"agent": {
"@type": "Organization",
"name": "Example Organization",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
}
}Validate Your DrinkAction Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your DrinkAction schema for errors and Rich Result eligibility