Our brand launches in the US next quarter. What should we do before launch?
On this page
A brand that has not launched has no wrong answer to correct. It has a missing one to create, and that is a better position to start from than it sounds — every item below is work that gets more expensive once something has been published.
Why is entity work cheaper before launch?
Because nothing has been published under the wrong spelling yet. Decide one form of the brand name — the romanisation, the legal entity, the social handles, the retailer-facing name — and use that one form everywhere from the first page.
After launch, a brand written several ways has its evidence divided between those spellings, and each one looks too thin to cite. Consolidating means correcting your own site, the marketplace listing, the retailer page and whatever copied them. Entity resolution describes what that split does to an answer.
Who writes your product facts if you don’t?
Whichever source an assistant retrieves first. For a cross-border brand that is usually a marketplace listing or a retailer page, written by a distributor working from a translated spec sheet.
Publishing the specification in English on your own domain before launch is the cheapest way to be the source that gets copied, rather than the one issuing a correction six months later. The same mechanism, after the fact, is the subject of Amazon listings vs your own site. Availability, sellers and shipping origin follow the same rule, and why AI says an imported brand isn’t sold in the US shows which of those records the brand writes itself.
Can crawler access be checked before there is traffic?
Yes, and it is the check least likely to be done. A robots.txt that allows a crawler proves nothing if a bot-management rule challenges it at the edge, and a page that renders its specification client-side reads as empty whatever robots.txt says.
Both are testable on a staging or soft-launch URL with no visitors at all. Run the crawler check against the English site, and read the raw HTML rather than the rendered page.
What does a pre-launch baseline actually record?
Which brands get named instead of you. Ask the buyer questions in English now, before the launch changes anything, and write down the answer each engine gives.
That zero is the comparator every later number is read against, and it exists only before launch. It also names the competitors occupying the answer and the sources those answers come from, which is the work queue. The method is in how to check if ChatGPT mentions your brand.
What is not worth buying before launch?
Correction work, and anything priced on results. There is no published claim to correct, no review corpus to build on, and no measurement history to show movement against. An agency selling a correction retainer to a pre-launch brand is selling a remedy for a problem that has not happened yet.
The honest pre-launch scope is these four items. They are cheap, they are entirely under the brand’s control, and every one of them costs more after the first English page goes live.
| Item | Why it is cheaper before launch |
|---|---|
| One form of the brand name | Nothing has been published under the wrong spelling yet, so there is nothing to consolidate |
| The specification, in English, on your own domain | You become the source that gets copied rather than the one issuing a correction six months later |
| Crawler access | Testable on a staging or soft-launch URL with no visitors at all |
| A baseline reading | The zero exists only before launch, and it names the competitors occupying the answer |
What is not worth buying is correction work, and anything priced on results.
