Do AI assistants answer an Australian buying question differently by language, and the locale decision that costs more

Every question in our Australian reading was asked in English, so this page carries no language split and says so before anything else. What it does give you is the locale decision that genuinely costs Australian businesses money, which is not translation. It is service area, spelling and the tax line, and all three are checkable this week.

What our reading covers, stated before anybody over-reads it

On 22 October 2026 we put 33 batches of buying questions to ChatGPT and Gemini with Australia written into the text of each one. The snapshot taken that evening holds 64 blind readings, 32 on each engine. Every question was in English. So this dataset is evidence about English language Australian answers and carries no reading in any other language at all. Anybody quoting a language split from it would be quoting something not in it.

What the English readings do show is worth having. The engines returned 1,010 distinct hosts, 435 of them on Australian domains, and named six Australian agencies: Online Marketing Gurus in 12 readings, Rocket Agency in 8, StudioHawk in 8, Prosperity Media in 8, Sparro in 3 and King Kong in 3. In 28 of the 64 readings they named nobody at all. The open ground in this market is in English.

The Australian locale decisions that do cost money

Decision	What gets it wrong	The fix
Service area	Implying national coverage you do not have, or local coverage when the service travels	Publish the states, cities, suburbs and travel radius explicitly
Spelling and vocabulary	American spellings and American terms on an Australian page	Australian spellings throughout, and local trade nouns rather than imported ones
The GST line	A price with no indication of whether tax is included	State it beside every figure, both ways where you can
Currency in the served document	Prices converted by a script, so a crawler sees only the fallback	Put every currency you sell in into the HTML on every request
Domain shape	Holding both a com and a com.au and serving similar content on both	Pick the one buyers type, redirect the other permanently, and leave it

The domain question, and the source the engines reach for

One host in our Australian set is worth naming because it answers this directly. auda.org.au, the administrator of the .au domain space, appeared in 4 of the 64 readings. That is an unusual source to see in a marketing answer, and it tells you the engines treat the registry as the authority on the domain question rather than any vendor blog. If you are deciding between a com and a com.au, the registry's own documentation is where the answer lives and a page arguing the point is competing with it.

The currency defect we measured in our own product

This is the locale mistake with the sharpest consequences and we made it. Our pricing page offers six currencies in its selector, INR, USD, GBP, EUR, AUD and CAD. Fetched on 22 October 2026, only the rupee and dollar figures are present in the served HTML, 13 and 25 distinct values. The other four conversions run in the browser. The machine readable llms.txt file carries two currencies, the rupee and the US dollar.

The Australian dollar is in the selector and in neither document. So an assistant asked what this costs in Australian dollars cannot answer from our pages. We publish that because it is the same class of defect this site documents on other people's pages, and because an Australian reader deserves to be told the local figure does not exist rather than handed a conversion we invented. For the record, Australia takes the column outside the United States and the United Kingdom, where Growth is $199 a month for 100 buyer questions across all five engines and SEO Start at $99 reads zero engines.

The cause is more useful than the fix. A browser sends a country header, a time zone cookie or an accept language header and gets its own ladder. A crawler sends none of those signals, so the detector reached its last line. The figures existed and they were not in the HTML, and our own gate could not see it because, run from our own network, both the browser request and the crawler request got the same answer. A comparison between two requests that share a blind spot cannot reveal the blind spot.

The one hour test if you do want a language answer

1. Take five of your actual buying questions. The words a buyer uses, not keywords.
2. Ask each in English with Australia in the text, three times, on each engine. Record who gets named and which sources appear.
3. Ask the same five in the second language, written by a native speaker rather than a translation tool. A translated question is a question nobody asks.
4. Compare three things. Whether a business was named at all, whether the names differ, and whether the sources are local or international.
5. Date the file. One run is a snapshot. The second a month later is the measurement.

That is the same method our own reading used and it is reproducible with a browser and an afternoon. The trap to avoid is trusting a language or location setting: the interface we use accepts both, returns HTTP 200, and ignores them, which is why the market goes in the question text.

Questions about language and locale for an Australian business

Do I need pages in languages other than English

Only where your category has real demand in them, and the test above answers that for your own category in an hour rather than by reasoning about it.

Does Australian spelling actually matter

To a reader it does, immediately and unconsciously. An Australian buyer reading optimize and center on a page claiming local expertise has been told something about where the page came from.

Is hreflang worth setting up

Once you have separate pages for Australia and at least one other market, yes. For a single market site it buys very little.

How do I check what a crawler sees on my own site

Fetch your own page with a plain request sending no cookies, no accept language header and no user agent, and read what comes back. Whatever that returns is the worst case your page has to survive, and it is how we found our own currency defect.

What is the quickest locale win

The GST line beside your prices and the service area published in plain words. Both are an afternoon and both remove an ambiguity a reader notices.

The source that answers the question people actually mean

Most Australian businesses asking a language question are really asking a reach question, and the reach question here is geographic rather than linguistic. The source the engines treat as authoritative on the structural half of it is the domain registry itself: auda.org.au appeared in 4 of our 64 blind readings on 22 October 2026, which is an unusual host to find in a marketing answer and a clear signal of where the engines go on the .au question. Read it, decide once, and put the effort into the two locale items that genuinely move money, which are the published service area and the GST line beside every figure. Then check what a signal free request actually receives from your own pages, because that is how we found our own currency defect and published it. The reading underneath all of this is the one that matters: in 28 of those 64 Australian readings the engines named no business at all, in English, which is the language you already publish in. AI Knows Us runs a fixed question list across ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews and reports named and cited separately, because a locale problem and a visibility problem fail differently and a single number hides which one you have.