Invalid object type for field "brand": change Thing to Brand
Your product markup gives brand the wrong type, often Thing. Change it to Brand with a name. It's a non-critical issue, so it doesn't block your product's rich result while you fix it.
- Non-critical
Invalid object type for field "brand"
Shopping > Merchant listings
Non-critical: the item can still show as a rich result.
By Bruno Amorim · ·
Google's help says this message means the object's type is wrong for that property. Google's product examples nest brand as a Brand with one name. Some themes and structured data apps write "@type": "Thing" instead.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Canvas Weekender Bag",
"image": "https://example.com/photos/weekender-bag.jpg",
"brand": {
"@type": "Thing",
"name": "Trailhead Goods"
},
"offers": {
"@type": "Offer",
"price": 89,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}{
"@context": "https://schema.org",
"@type": "Product",
"name": "Canvas Weekender Bag",
"image": "https://example.com/photos/weekender-bag.jpg",
"brand": {
"@type": "Brand",
"name": "Trailhead Goods"
},
"offers": {
"@type": "Offer",
"price": 89,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}Give one brand name only. If the product has no brand, leave brand out instead of filling in a placeholder.
Find the code that writes it
- Shopify: Dawn and Horizon use the
structured_datafilter, which writesBrandcorrectly. If you see this on Shopify, the markup comes from another theme or an app. In the theme editor's code view, search forThing. If it isn't in the theme, check your apps. - WordPress: the theme or a schema plugin writes it. Turn plugins off one at a time on a test copy and rerun the Rich Results Test.
- Custom sites: search your templates for
"brand"and fix the type where it's set.
The same message on other fields
author: Google's Article docs ask forPersonorOrganization, neverThing.itemReviewed: the reviewed item must be one of the types Google supports for review snippets.<parent_node>: the problem is the object the markup hangs from, not a named field.
For the last two, see Invalid object type for field "<parent_node>".
Confirm the fix
Test a product in the Rich Results Test. Then open the report that listed the issue, click it, and click Validate fix. Google rechecks the pages as it crawls them.
Questions
Does "Invalid object type for field brand" hurt rankings?
It's a non-critical issue. The product can still show as a rich result, and the page stays indexed. Fix it when you next touch the template.
Can brand be an Organization instead of a Brand?
Schema.org allows both. Google's product docs and examples use Brand with a name, so that's the safe choice.
Sources
Checked on October 8, 2026. Vendors change their tools and docs, so check the source if something looks different.
See which of your pages Google left out
Prices, stars, and breadcrumbs only show for pages in Google's index. CrawlCoach shows which of your pages Google left out, and the fix for each.
Get my free reportFree for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.
More structured data fixes
- Invalid object type for field "<parent_node>"Google's help doesn't explain <parent_node>. Reports from site owners point to one pattern: the wrong type is on the object the markup hangs from, not on a named field. Test the live page first, then check the types below.
- No global identifier providedGoogle wants a product ID that is the same everywhere the product is sold, such as the barcode number. It's a non-critical issue: add the GTIN if your products have one, and leave the warning if they don't.
- Merchant listings: missing fieldsA missing name, image, or offer price is critical: those products can't show as merchant listings until you fix it. A missing description, shippingDetails, hasMerchantReturnPolicy, or GTIN is non-critical and can wait.