The locale mistakes that stop an Australian business being recommended, ranked by what each one costs

Seven mistakes account for most of it, ranked here by what each one costs rather than by how technical it sounds. The expensive ones are not the obvious ones. The single most expensive locale defect we have measured anywhere was a page whose prices existed in several currencies and served only one of them to anything that was not a browser, and it was our own.

The seven, in the order worth fixing

1. Currency figures that are not in the served document. If prices are converted by a script, a crawler sends none of the signals a browser sends and gets whatever your fallback is. Put every currency you sell in into the HTML on every request.
2. No service area stated anywhere a machine can read. States, cities, suburbs and travel radius, in plain words. In a country this size an unstated service area is the most expensive omission on the list, because it produces enquiries you cannot fulfil and misses ones you can.
3. GST silence on a price. A figure with no indication of whether tax is included invites a reader to assume the cheaper reading. State it beside the number.
4. American spelling and vocabulary on an Australian page. It tells a reader where the page came from before they have read a sentence of it, and it undermines a local expertise claim instantly.
5. Two domains serving similar content. A com and a com.au both answering for your business splits the signal and neither accumulates. Pick the one buyers type, redirect the other permanently, and leave the redirect alone.
6. Dates and formats that are ambiguous. Write the month in words. A date readable two ways on a page about a deadline is a support ticket waiting to happen.
7. Hreflang that contradicts the content. A tag claiming an Australian page while the copy prices in another currency and names another country's regulator is a signal fighting the page it sits on.

The one we got wrong, with the figures

Our own pricing page is the clearest example of mistake one, and we publish it because the cause is more useful than the fix. Fetched as a crawler, the page returned HTTP 200 and 88KB of which 55KB was script payload, and the visible first response carried rupee figures and no dollar, pound or euro figure at all, because the conversion ran in the browser.

The detector was never broken. 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 the five signals, so the detector reached its last line, which reads we could not tell, so rupees. That default is deliberate and protects a buyer whose phone ships with a foreign locale from being shown a ladder more than twice his own. The defect was that the other currencies were never in the HTML. It was fixed the same day with a server rendered chapter printing every plan in every region on every request, and the page now carries 15 dollar figures, 5 pound, 5 euro and 31 rupee in its visible text.

And our own gate could not see it. We already run a check that fetches a page as each AI crawler and as a browser and fails when a figure a browser sees is missing for a crawler. Run from our own network both got rupees, so there was no difference to find. A comparison between two requests that share a blind spot cannot reveal the blind spot, and the replacement asserts the arithmetic instead.

The residual gap applies directly to an Australian reader. Our pricing page offers six currencies in its selector, INR, USD, GBP, EUR, AUD and CAD, and only the rupee and dollar figures are in the served HTML. The machine readable llms.txt carries those same two. There is no Australian dollar figure in either, so Australia takes the dollar column: read on 22 October 2026, Growth is $199 a month outside the United States and the United Kingdom for 100 buyer questions across all five engines, and SEO Start at $99 reads zero engines.

The Australian source that settles the domain question

auda.org.au, the administrator of the .au domain space, appeared in 4 of our 64 Australian readings. That is the authority the engines reach for on this question, which means a page arguing about com against com.au is competing with the registry's own documentation. Read the registry and follow it rather than guessing, and then stop revisiting the decision.

What a locale mistake costs in an answer

On 22 October 2026 we put 33 batches of buying questions to ChatGPT and Gemini with Australia written into the text of each one, because the search interface we use accepts country, language and location parameters and ignores all three. The snapshot taken that evening holds 64 blind readings, 32 per engine, returning 1,010 distinct hosts of which 435 carry an Australian domain, and reaching 66 distinct Australian government hosts 139 times across 25 readings.

In 28 of the 64 readings the engines named no business at all. A locale defect does not usually produce a wrong answer about you. It produces no answer about you, because a page that cannot be read as an Australian page is not a candidate for an Australian question. That is why the ranking above puts machine readability above tagging.

Questions about locale problems on an Australian site

How do I tell whether my site is being shown to the right country

Fetch it yourself with a plain request sending no cookies, no accept language header and no user agent, and read what comes back. Whatever that response contains is what a machine with no signals gets, and it is the worst case your page has to survive.

Does a currency selector count as having the price on the page

Only if the figures are in the document. A selector converting in the browser means the figures exist for a person and not for a crawler, which is exactly the defect described above.

Should I write Australia into every page

Into every page where the market changes the answer, which is most commercial pages. A generic page serving everybody is quotable for nobody.

Does the service area really need publishing

In Australia more than anywhere. A two hour drive can cross a service boundary, and an engine cannot infer a radius you have not stated. Our page on drawing the service map first and building in waves works through it for one city.

What is the quickest win on this list

The GST line beside your prices and the service area in plain text. Both are an afternoon.

The registry is the authority on the one everybody argues about

Of the seven, the domain question is the one that generates the most opinion and the least evidence, and our reading settles where to look for an answer. auda.org.au, the administrator of the .au domain space, appeared in 4 of 64 blind Australian readings on 22 October 2026. That is an unusual host to find in a marketing answer and it means the engines treat the registry as the authority on this question rather than any vendor. So read the registry, follow it, and stop revisiting the decision, because the cost of holding two domains and serving similar content on both is larger than either choice ever was. Then check the mistake that actually hides: fetch your own pages with a plain request sending no cookies, no accept language header and no user agent, and read what comes back, because that is what a machine with no signals gets. We found our own currency defect exactly that way and published it. What none of the seven fixes tells you is whether an answer moved, and in 28 of those 64 readings there was no answer about any business to move. AI Knows Us keeps the before and after on a fixed question list across ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews, reporting reached and named separately because a locale defect breaks the first and a content problem breaks the second.