What Is valueAddedTaxIncluded Schema?

valueAddedTaxIncluded is a Boolean Schema.org property that states whether the price in a PriceSpecification includes value-added tax. Use true when VAT is already included in the stated price and false when VAT is excluded and will be added under the applicable terms.

Primary definition: Schema.org valueAddedTaxIncluded. Apply it only when the visible commercial terms support the Boolean value.

The property removes a specific kind of price ambiguity. A number such as €120 may represent the final VAT-inclusive price or a net price before tax. The Boolean helps machine-readable data preserve the same tax treatment the page communicates to the buyer.

1. Frame the decision raised by What Is valueAddedTaxIncluded Schema.
2. Read the primary property definition and expected value type.
3. Compare markup with the visible price and commercial terms.
4. Correct the source catalog or template without inventing a value.
5. Validate the rendered page and recheck it after pricing changes.

• Attach it to the price specification it actually describes.
• Use a real Boolean, not the strings “yes” or “included.”
• Match visible price labels, checkout, and invoice treatment.

The definition is binary but consequential: valueAddedTaxIncluded says whether VAT is already inside the marked-up price.

valueAddedTaxIncluded qualifies the price inside a PriceSpecification by declaring its VAT treatment. The price and currency identify the amount; the Boolean identifies whether that amount is gross of VAT or net of VAT.

The property does not calculate a tax rate, choose a customer’s jurisdiction, or replace checkout tax logic. It describes the commercial meaning of one price specification at the time and context in which it applies.

• Evidence for How Does valueAddedTaxIncluded Work in PriceSpecification must come from the exact page and pricing context.
• Locate the Offer or PriceSpecification node that contains the property.
• Confirm the currency, price boundaries, tax treatment and eligibility context that apply.
• Compare rendered structured data with catalog, checkout and visible page terms.
• Retain a fresh validation result and the URL where the value was observed.

1. Identify the exact visible price being marked up.
2. Determine whether that amount includes VAT.
3. Set the Boolean on the same price specification.
4. Confirm the buyer sees identical treatment at checkout.

Review the parent structure in PriceSpecification Schema.

The relationship is descriptive: the property explains the tax status of the specific price, not the customer’s eventual tax liability.

Use valueAddedTaxIncluded when VAT treatment is applicable to the price and the page can state truthfully whether VAT is included. It is most relevant to ecommerce, services, subscriptions, tickets, rentals, and cross-border offers shown in VAT jurisdictions.

A US-only offer subject to sales tax rather than VAT may not benefit from the property. Do not treat it as a generic “all taxes included” flag. US sales tax can depend on destination, nexus, product taxability, and checkout data, so a VAT-specific Boolean should not be repurposed.

1. Frame the decision raised by When Should You Use valueAddedTaxIncluded.
2. Read the primary property definition and expected value type.
3. Compare markup with the visible price and commercial terms.
4. Correct the source catalog or template without inventing a value.
5. Validate the rendered page and recheck it after pricing changes.

• Use it only where VAT is a real part of the pricing model.
• Separate B2C gross prices from B2B net prices when both exist.
• Do not guess treatment before region or customer type is known.

Applicability comes first: use the VAT flag only for a price whose VAT treatment is knowable and visible.

Set valueAddedTaxIncluded to true when the marked-up amount already contains VAT and false when the amount is shown before VAT. Decide from the price’s commercial meaning, not from whether the seller eventually remits tax.

The same product can require different values across regional, customer-type, or channel-specific offers. A consumer storefront may publish VAT-inclusive prices, while a wholesale portal publishes net prices. Each structured price must follow its own visible terms.

• Evidence for Should valueAddedTaxIncluded Be true or false must come from the exact page and pricing context.
• Locate the Offer or PriceSpecification node that contains the property.
• Confirm the currency, price boundaries, tax treatment and eligibility context that apply.
• Compare rendered structured data with catalog, checkout and visible page terms.
• Retain a fresh validation result and the URL where the value was observed.

1. Read the exact price label.
2. Inspect tax settings for that market and customer segment.
3. Run a representative checkout.
4. Compare the invoice subtotal, VAT line, and total.
5. Set the Boolean only after the evidence agrees.

The invoice is the strongest check: true means VAT is already within the specified amount; false means it is not.

Add valueAddedTaxIncluded as a JSON Boolean inside the relevant PriceSpecification or compatible subtype. Do not quote true or false, and keep the object connected to the exact Offer whose price appears on the page.

{
  "@context": "https://schema.org",
  "@type": "Offer",
  "priceSpecification": {
    "@type": "PriceSpecification",
    "price": "120.00",
    "priceCurrency": "EUR",
    "valueAddedTaxIncluded": true
  }
}

• Evidence for How Do You Add valueAddedTaxIncluded in JSON-LD must come from the exact page and pricing context.
• Locate the Offer or PriceSpecification node that contains the property.
• Confirm the currency, price boundaries, tax treatment and eligibility context that apply.
• Compare rendered structured data with catalog, checkout and visible page terms.
• Retain a fresh validation result and the URL where the value was observed.

1. Frame the decision raised by How Do You Add valueAddedTaxIncluded in JSON-LD.
2. Read the primary property definition and expected value type.
3. Compare markup with the visible price and commercial terms.
4. Correct the source catalog or template without inventing a value.
5. Validate the rendered page and recheck it after pricing changes.

Inspect deployed templates with Novaverb Site Audit rather than validating only a copied code sample.

The correct JSON-LD mirrors one real offer: its amount, currency, market, and VAT Boolean must describe the same transaction.

valueAddedTaxIncluded is specifically about VAT in the stated price; it is not a universal flag for US sales tax, use tax, excise tax, or every checkout fee. VAT and US sales tax differ in legal structure, collection method, and common price-display conventions.

Many US ecommerce pages show a pre-tax price and calculate sales tax after the shipping destination is known. Marking valueAddedTaxIncluded false does not necessarily communicate that scenario accurately because the property names VAT, not generic tax exclusion.

• Evidence for valueAddedTaxIncluded vs Sales Tax: What Is the Difference must come from the exact page and pricing context.
• Locate the Offer or PriceSpecification node that contains the property.
• Confirm the currency, price boundaries, tax treatment and eligibility context that apply.
• Compare rendered structured data with catalog, checkout and visible page terms.
• Retain a fresh validation result and the URL where the value was observed.

1. Frame the decision raised by valueAddedTaxIncluded vs Sales Tax: What Is the Difference.
2. Read the primary property definition and expected value type.
3. Compare markup with the visible price and commercial terms.
4. Correct the source catalog or template without inventing a value.
5. Validate the rendered page and recheck it after pricing changes.

For the currency dimension, see priceCurrency in Product Schema.

Do not generalize the label: a VAT Boolean should make a VAT claim, not stand in for every tax a buyer might owe.

Regional and B2B prices should be modeled as distinct offers or price specifications whenever their amount, currency, customer eligibility, or VAT treatment differs. One global Boolean cannot truthfully describe a gross consumer price and a net wholesale price at the same time.

Generate each structured object from the same regional catalog and customer-segment rules used to render the page. If geolocation or account status changes the price, ensure crawlers and visitors receive a coherent default rather than contradictory hidden objects.

• Evidence for How Should Regional and B2B Prices Be Modeled must come from the exact page and pricing context.
• Locate the Offer or PriceSpecification node that contains the property.
• Confirm the currency, price boundaries, tax treatment and eligibility context that apply.
• Compare rendered structured data with catalog, checkout and visible page terms.
• Retain a fresh validation result and the URL where the value was observed.

1. Choose the page’s canonical market and audience.
2. Render the corresponding visible price.
3. Build structured data from that same offer record.
4. Prevent alternate-market objects from contradicting the page.
5. Test logged-out, business-account, and location states.

Segment before marking up: every VAT flag should belong to one identifiable price, market, and customer context.

Validate valueAddedTaxIncluded by checking its Boolean type, entity placement, visible tax label, regional context, checkout calculation, and invoice result. Syntax validation is necessary, but the decisive question is whether the stated price truly contains VAT.

1. Frame the decision raised by How Do You Validate valueAddedTaxIncluded Markup.
2. Read the primary property definition and expected value type.
3. Compare markup with the visible price and commercial terms.
4. Correct the source catalog or template without inventing a value.
5. Validate the rendered page and recheck it after pricing changes.

• Test consumer and business purchasing states.
• Test representative VAT jurisdictions.
• Check promotions, subscription renewals, and sale prices.
• Re-crawl after tax-engine or catalog changes.

Use the wider Novaverb SEO tools system to connect markup findings with crawl, indexability, content, and internal-link evidence.

Check the rendered page with the free website SEO checker, keep recurring evidence in Site Audit, and compare ongoing Novaverb plans when manual review no longer scales.

Validation must reach the commercial record: the Boolean is correct only when page, checkout, and invoice agree.