AEO yang Bagus Mengurangi Halusinasi, Bukan Memanipulasi Jawaban

Ada dua cara memandang AEO.

Cara pertama:

“Bagaimana membuat AI mengatakan apa yang kita mau?”

Cara kedua:

“Bagaimana membuat public information cukup jelas sehingga AI tidak perlu banyak menebak?”

Yang kedua lebih sehat.

Dan jauh lebih tahan lama.

Generative systems bisa salah.

Mencampur source.

Menggabungkan entity.

Mengisi detail yang tidak ada.

Menggunakan informasi stale.

Memberi answer terlalu confident.

Kita tidak bisa menghilangkan halusinasi dari internet hanya dengan mengedit website.

Tetapi website bisa memperkecil beberapa sumber ambiguity.

Itulah AEO yang bagus.

Bukan manipulasi output.

Information hygiene.

Mulai dari entity

AI salah menyebut:

owner.

CEO.

brand.

product.

location.

Sebelum membuat 50 FAQ, cek identity.

Canonical About.

Legal entity.

Brand relation.

Product.

Person.

Location.

Alias.

Jika public web sendiri bertentangan, mesin punya bahan yang buruk.

AEO mengurangi conflict.

Tidak menjamin model selalu benar.

Tetapi kita memperbaiki input environment.

Harga adalah contoh paling sederhana

Website A:
Rp1 juta.

Blog lama:
Rp800 ribu.

Marketplace:
Rp900 ribu.

Sales PDF:
Rp1,2 juta.

AI harus memilih.

Mungkin salah.

AEO solution bukan:

buat answer block “harga terbaik”.

Solution:

canonical pricing.

date.

offer.

update stale pages.

Source of truth.

Again, not guarantee.

Less ambiguity.

Product feature juga

Article 2024:
“Fitur SSO akan datang.”

Product 2026:
“SSO tersedia Enterprise.”

Review lama:
“Belum ada SSO.”

AI synthesis bisa campur.

Fix temporal status.

Planned.

Available.

Deprecated.

Current.

Version.

AEO is status discipline.

FAQ bagus juga membantu, tetapi only after canonical fact.

There is a darker path: manipulation

Some people imagine AEO as:

repeat claim everywhere.

create fake forums.

seed fake review.

publish fabricated statistics.

make near-duplicate pages.

hide instructions.

stuff prompts.

invent expert quotes.

Goal:
make model absorb narrative.

This is not answer optimization.

It's information pollution.

Google's generative Search guidance explicitly warns against inauthentic mentions and low-value tactics, while its spam policies target scaled content abuse.

OpenAI search relies on public web sources and offers crawler controls.

If brands pollute web, answer ecosystem gets worse.

AEO should not participate.

What does “reduce hallucination” mean practically?

It means reducing opportunities for wrong inference in areas we control.

1. Entity is explicit.

2. Critical fact has canonical source.

3. Volatile fact has date/version.

4. Claim has evidence.

5. Scope and limitation are visible.

6. Old information is marked historical.

7. Structured data matches visible content.

8. Crawler can access intended public source.

9. Duplicate conflicting pages are fixed.

10. Corrections are documented.

These are boring.

Good.

Safety often looks boring.

AEO that promises “make AI say X” is selling control it doesn't have.

Platforms choose retrieval and generation.

User context changes.

Model changes.

Source selection changes.

We can influence public source quality.

We cannot guarantee final sentence.

This distinction should be non-negotiable.

Answer block should reduce ambiguity

Question:
“Does Product X support SSO?”

Bad:
“Product X supports modern security.”

AI may infer yes.

Good:
“Product X supports SAML-based SSO on Enterprise plan.”

If true.

If not:
“Product X does not currently support SSO.”

Clear.

Negative fact is useful.

Don't hide because marketing dislikes.

Hallucination risk grows in silence.

If feature absent but page is vague, machine may fill.

Transparency is AEO.

Source must match claim

AI says:
“Company has 20 offices.”

Citation:
About page.

About page doesn't say.

Maybe source misalignment.

Brand can create location page with exact current list.

Now there is a source.

Does AI use it next time?

Unknown.

But source ecosystem improved.

AEO should measure answer accuracy, not only citation.

If AI cites us for a wrong answer, that's failure.

Actually worse.

Our domain appears to support misinformation.

Audit:

Citation accuracy.

Claim alignment.

Entity.

Do not celebrate domain presence alone.

Brand manipulation can create hallucination against competitors too

Fake comparison.

Outdated competitor feature.

Strawman.

“Competitor doesn't support X.”

They do.

AI picks our page.

Now misinformation.

Ethically bad.

Legally risky in some contexts.

Strategically fragile.

Comparison must be current, sourced, fair.

If uncertain:
don't claim.

AEO that improves our visibility by degrading information quality is not good AEO.

Human safety matters most in regulated industries

Tax.

Legal.

Health.

Finance.

Security.

Here hallucination can cause consequential harm.

Source must be authoritative.

Jurisdiction.

Date.

Review.

Limit.

Escalation.

Do not write individual advice as universal fact.

AEO's role:
help user understand.

Not replace professional judgment where context is required.

WHO has repeatedly warned that generative AI in health requires caution because convincing output can still be inaccurate or harmful.

That is a broader lesson for answer optimization:

confidence is not accuracy.

Our website should not contribute false confidence.

Evidence labels help

Fact.

Observation.

Interpretation.

Hypothesis.

Recommendation.

These categories don't need to appear as metadata on every sentence.

But writing should signal.

“Google states…”

Official fact.

“In our testing…”

Observation.

“This suggests…”

Interpretation.

“We recommend…”

Advice.

“May…”

Uncertainty.

This language prevents epistemic blur.

AEO content should teach the model and reader what kind of statement they're seeing.

Not literally train model.

Provide clear source semantics.

Canonical page reduces version conflict

One truth home.

Pricing.

Product.

Policy.

Identity.

Security.

Methodology.

When update:
change there.

Then dependent articles link.

If old article is historical, label.

Don't silently mutate history.

This is information architecture.

Less conflict.

No magic.

Structured data has a role, but not superpower

Google uses structured data to help understand page information and support certain features.

It should match visible content.

If structured data says one thing and page another, we have made error more machine-readable.

So AEO doesn't mean “add more schema.”

It means data consistency.

Only relevant types.

Valid.

Current.

No hidden fake facts.

Machine-readable truth should equal human-readable truth.

There is also crawler governance

If we want public source eligible for search surfaces, intentional access matters.

OAI-SearchBot exists for ChatGPT search features.

Google uses its crawling/indexing systems for Search and generative features.

But opening crawler access is not enough.

Page quality.

Relevance.

Source selection.

All external.

AEO should say:

“accessible.”

Not:

“guaranteed citation.”

Words matter.

How do we test hallucination reduction?

Create critical fact set.

20 facts.

Company.

Product.

Price.

Location.

Policy.

Limitation.

Ask platforms repeatedly.

Before intervention.

After cleanup.

Measure:

Correct.

Incorrect.

Unknown.

Source.

Citation alignment.

If errors drop, good evidence.

Still not proof of general model improvement.

But site-specific representation may have improved in test.

Label scope.

This is much better than asking:

“Are we more authoritative?”

Test actual facts.

Include negative facts

This is important.

“Does Product X have offline mode?”

Correct:
no.

“Is service available in Bali?”

Maybe no.

“Does company have branch Y?”

No.

If AI says yes, that's hallucination.

Negative facts reveal gaps.

Brands often publish only positive capabilities.

Then absence is ambiguous.

For critical limitations, explicit no can help.

Not every absent feature needs public page.

Use business relevance.

But buyer-critical:
yes.

There's a human conversation behind this.

Marketing:
“Don't write that feature isn't available.”

Product:
“But customers keep asking.”

Marketing:
“Looks negative.”

AEO:
“Ambiguity is worse.”

If you don't support it, say so.

Right customer qualifies.

AI has correct source.

Trust.

Good AEO sometimes reduces visibility

Interesting.

If brand isn't fit for query, accurate content may make AI less likely to recommend.

That's okay.

Example:
service only enterprise.

User asks:
“Cheap option for freelancer.”

Website says:
“Designed for enterprise.”

AI doesn't recommend.

Success in accuracy.

Not failure.

This is why “maximize recommendation” is dangerous north-star.

Right recommendation > more recommendation.

The same applies to medical/legal advice.

Sometimes best answer is:

“Need professional assessment.”

AEO doesn't always close query with brand.

It routes safely.

What about hallucination caused outside our control?

Third-party stale.

Model internal knowledge.

User typo.

Platform bug.

We cannot fix all.

AEO should have correction loop.

Monitor.

Identify source.

Correct owned page.

Request legitimate third-party correction if factually wrong.

Publish clarification.

Re-test.

Don't spam.

Don't threaten search with duplicate pages.

Information correction takes time.

Accept limits.

There's an editorial principle worth keeping:

Never publish a sentence solely because you hope an AI will repeat it.

Publish because it is useful and defensible if an AI does repeat it.

This flips incentive.

If AI quotes:
are we comfortable?

If journalist quotes:
comfortable?

If regulator reads:
comfortable?

If customer acts on it:
comfortable?

If answer is no, source isn't ready.

That is the strongest AEO quality gate.

It also protects brand.

In a world where sentences can be synthesized into contexts we don't control, every public claim has longer legs.

Evidence matters.

Scope matters.

Dates matter.

AEO is not just visibility optimization.

It's public knowledge engineering.

Manipulation is tempting because it promises speed.

Fake mentions.

Fake authority.

Prompt-shaped pages.

Mass content.

Maybe some tactics appear to work briefly.

But they create two debts:

reputation debt.

information debt.

Eventually someone has to clean them.

Better to build truth infrastructure.

Canonical facts.

Evidence.

Real reputation.

Clear limitations.

Current data.

Human-readable explanation.

At 100 articles into this GEO.or.id series, that is probably the most important conclusion.

The future of AEO should not be a contest to see who can manipulate machines most effectively.

Machines will change.

Policies will change.

Interfaces will change.

One principle survives:

Make the public information good enough that a person or system can reach the right conclusion with less guessing.

That's not glamorous.

It's durable.

AEO yang bagus bukan membuat AI “menurut”.

AEO yang bagus membuat website berhenti menjadi sumber kebingungan.