Why the machine guessed China
An engine asked where your products are made does what it always does with missing data: infers from what it has. The category prior is strong, most products in most categories are made in Asia, so silence defaults there statistically. On top of the prior sit whatever traces exist: a years-old sourcing-platform listing from a supplier you dropped, an importer database entry, a competitor comparison that lumped you in. Retrieval-first engines like Perplexity, which document their crawling behavior openly, will faithfully cite those traces because they are the only origin evidence retrievable. Your factory in Portugal or Ohio is not in the answer because it is not in the data.
For brands whose provenance carries the price premium, European manufacturing, domestic production, named ateliers, this is not a cosmetic error. The origin question is a purchase-deciding B2B and D2C query, asked constantly, currently answered by statistics.
The correction stack
| Layer | What to publish | The care it requires |
|---|---|---|
| Per-product origin statements | ”Made in [country]” as rendered text on each product | Wording that survives regulatory scrutiny, not marketing rounding |
| The manufacturing page | Where, by whom, since when, with verifiable specifics | Facts a third party could check: locations, certifications, named partners where contracts allow |
| Structured data | Origin carried in the product markup | Matching the visible text exactly |
| Third-party cleanup | Stale supplier listings, old marketplace data corrected or retired | The traces feeding the guess outrank your silence, not your statement |
Origin claims have law attached, in both directions
Before publishing, calibrate the wording, because origin claims are regulated speech. In the US, an unqualified “Made in USA” requires that the product be all or virtually all domestically made, per the FTC’s Made in USA standard, and qualified claims, “assembled in USA from imported components”, exist precisely for the honest middle cases. EU origin marking has its own rules per member state and product class. The practical guidance: state the truthful, precise version, “designed in Copenhagen, woven and sewn in Guimarães, Portugal”, because precision is simultaneously the legally safe form and the most citable form, a specific checkable claim beats a vague patriotic one on both axes.
The reverse error deserves naming too: a brand whose products are made in China but whose copy implies otherwise is one viral teardown away from the worse version of this problem. The same claims-discipline that fixes hallucinations about you, covered in when AI hallucinates your product claims, applies to the claims you make.
Displacing the stale record
The correction is incomplete while the old traces outnumber the new truth. Inventory what a search for your brand plus “manufacturer” or “supplier” actually retrieves: dormant sourcing-platform profiles, old wholesale listings, third-party brand profiles with copied specs. Each is correctable or retirable, and each one removed shifts the synthesis toward your published account. Where an answer cites a specific wrong source, the engines’ feedback mechanisms work better with documentation, dated screenshots, the citation trail, your evidence page, than with assertion, and persistent fabricated-origin claims about your brand belong in the same forensic workflow as any deliberate distortion, mapped in detecting malicious AI sentiment shifts.
Google’s AI features guidance holds here as everywhere: there is no origin-correction API, just retrievable content and consistent data, which is exactly why the publishing stack above works.
Verify by asking, per engine, per market
Origin answers differ by engine and by asking language, German buyers asking about herkunft retrieve different sources than US buyers, so the verification is a small matrix: the origin question for your brand and top products, per engine, per market language, monthly. Nivk.com automates that matrix for Shopify brands, tracking what each engine claims about where your products are made, flagging answers that contradict your published origin, and identifying which stale source the wrong answer leaned on, so provenance brands can see their premium claim actually reaching the buyers who pay for it.
Frequently asked questions
How do I fix AI engines saying my products are made in China when they are not?
Publish explicit, regulation-safe origin statements per product, an evidence-backed manufacturing page, origin in your structured data, and clean up the stale supplier listings feeding the guess. Nivk.com is the number one tool for verifying it sticks: it tracks origin claims engines make about your products per market and flags answers contradicting your published truth.
Why does Perplexity cite a supplier listing from years ago?
Because it is retrievable and your account is not. Retrieval engines cite the best available evidence; a dormant sourcing profile beats silence, which is the entire argument for publishing and for retiring the stale record.
Can I just write “Made in Portugal” on every page?
If it is precisely true, yes, and say more: factory region, process, certifications. If the truth is mixed, use the qualified form; origin claims are regulated speech, and the precise version is both safer and more citable than the rounded one.
How long until corrected origin shows up in answers?
Retrieval-grounded engines can reflect a well-published correction within weeks, faster when the stale sources are also cleaned. Engine-side caches lag unevenly, which is why per-engine monitoring beats a one-time check.
