ClaimReview Mulai Dipensiunkan dari Google Search: Apa Artinya buat Schema Strategy

Ada jenis perubahan structured data yang kelihatannya kecil di changelog, tetapi sebenarnya memberi pelajaran besar.

Google sekarang menyatakan bahwa dukungan `ClaimReview` sedang diphase-out dari Google Search.

Bukan rumor.

Bukan prediksi industri.

Dokumentasi resmi Google Search Central current menampilkan notice:

Google sedang memphase-out support untuk ClaimReview markup di Google Search.

Tetapi markup tersebut tetap didukung oleh Factcheck Explorer Tool.

Kalimat kedua sama pentingnya dengan kalimat pertama.

Karena perubahan ini bukan berarti:

ClaimReview “mati”.

Schema.org menghapus tipe tersebut.

Fact-checking tidak lagi penting.

Semua publisher harus buru-buru menghapus markup malam ini.

Yang berubah adalah satu consumer dan satu search experience.

Ini contoh perfect untuk memahami schema strategy 2026:

Schema.org vocabulary, platform support, rich-result presentation, dan editorial value adalah empat layer berbeda.

Kalau selama ini strategy kita bergantung pada satu rich-result feature, perubahan seperti ini terasa seperti kehilangan investasi.

Kalau schema dipakai sebagai semantic infrastructure yang benar, perubahan consumer bisa ditangani lebih tenang.

Apa yang Sebenarnya Dipensiunkan Google?

Google Search documentation mengatakan support ClaimReview markup di Google Search sedang diphase-out.

Pada saat yang sama Google menyatakan markup itu masih supported oleh Factcheck Explorer Tool.

Jadi scope-nya jelas:

Google Search presentation/support berubah.

Factcheck Explorer masih memakai.

Schema.org sendiri masih memiliki `ClaimReview` sebagai type untuk fact-checking review terhadap claim yang dibuat atau dilaporkan di CreativeWork.

Ini distinction penting.

Jangan menulis:

“Google menghapus ClaimReview dari Schema.org.”

Google tidak mengontrol Schema.org sendirian seperti itu, dan type tersebut masih ada.

Jangan juga menulis:

“ClaimReview sudah tidak bisa digunakan sama sekali.”

Tidak sesuai current documentation.

Better:

“Google sedang menghentikan dukungan ClaimReview sebagai Search feature, sementara ClaimReview tetap menjadi Schema.org type dan masih didukung Factcheck Explorer.”

Itu accurate.

Kenapa Google Melakukan Ini?

Google pada 2025 mengumumkan program simplifikasi Search results dan mulai phase-out beberapa structured-data-powered features.

Documentation updates kemudian menandai sejumlah feature yang akan dipensiunkan, termasuk ClaimReview.

Kita tidak perlu mengarang alasan lebih jauh.

Google memberi framing bahwa mereka menyederhanakan Search result page dan secara berkala mengevaluasi usefulness Search features.

Cukup.

Jangan menambah narrative:

“Karena AI Overviews menggantikan fact check.”

Unless Google explicitly says.

Don't infer motive without evidence.

Schema strategy harus membedakan platform statement dari industry speculation.

Ini Lesson Pertama: Rich Result Bukan Schema Itu Sendiri

Banyak tim memperlakukan keduanya sama.

“ClaimReview = Google fact-check rich result.”

Historically closely related.

But Schema.org `ClaimReview` is a semantic type.

Google Search feature is one consumer implementation.

When Google phases out Search support, semantic type can still exist for:

Factcheck Explorer.

Other consumers.

Internal graph.

Data exchange.

Fact-check repositories.

Research.

Future systems.

Whether each consumer actually uses it must be verified separately.

The vocabulary isn't automatically obsolete because one UI changes.

This is why schema governance should track:

Vocabulary status.

Consumer support.

Business use.

Separately.

Kalau Target Anda Hanya Google Search Rich Result

Then practical priority changes.

If only reason for implementing ClaimReview was:

“Get a special Google Search presentation.”

That reason is being removed.

Don't keep engineering budget on legacy enhancement purely from inertia.

Reassess.

Questions:

Does Factcheck Explorer matter to us?

Does another platform consume ClaimReview?

Is our fact-check database using it?

Does internal publishing pipeline rely on it?

Do partners ingest it?

If no:
maybe implementation can be simplified or retired.

But don't delete until dependency audit.

Schema is infrastructure.

Dependencies may be hidden.

Kalau Anda Publisher Fact-Checking

Different.

ClaimReview may still be important because:

Factcheck Explorer remains supported according to Google.

ClaimReview is part of fact-check metadata ecosystem.

Your content can still be syndicated/processed by other systems depending their support.

Internal structured archive can benefit.

So the answer isn't:
“Remove immediately.”

It's:
“Change expectation.”

Don't promise Google Search rich-result benefit.

Keep if there is supported use case.

Monitor official docs.

Track platform dependencies.

This is mature.

Skenario di Ruang Redaksi

Editor:
“Google pensiunkan ClaimReview. Kita hapus semua?”

Developer:
“Tool Factcheck Explorer masih support.”

SEO:
“Search rich result benefit akan hilang.”

Data team:
“Dataset fact-check internal kita pakai ClaimReview.”

Editor:
“Berarti jangan hapus, tapi ubah tujuan?”

Exactly.

Schema strategy moves from:
Search appearance.

To:
semantic/data interoperability + remaining consumer support.

This is what good architecture does.

It adapts without panic.

Don't Let Deprecated Search Feature Break Editorial Workflow

Fact checking should exist because truth verification matters.

Not because rich result exists.

A fact-check page still needs:

Claim.

Who made it.

Source.

Date.

Evidence.

Verdict.

Method.

Reviewer.

Correction policy.

References.

Structured markup can support systems.

But editorial quality remains.

If Google Search stops special presentation, the content doesn't lose public value.

This is key.

Search feature shouldn't determine whether newsroom verifies facts.

Schema is representation.

Editorial process is substance.

What Should Happen to Existing ClaimReview Markup?

Don't mass-delete blindly.

Run inventory.

Which pages?

Which system generates?

Any consumers?

Any API?

Any Factcheck Explorer usage?

Any external syndication?

Then categorize.

A. Still needed:
Keep.

B. Search-only legacy:
Plan retirement.

C. Broken/stale:
Fix or remove.

D. Unknown dependency:
Investigate.

This avoids two bad extremes:

Keep forever because “schema is always good.”

Remove everything because Google UI changed.

Decision based on use.

Version.

Document.

What Should New Pages Do?

If publisher is fact-checking and ClaimReview still supports your intended ecosystem:
use it correctly.

If normal corporate website publishes an article checking industry claim:
don't add ClaimReview just because it sounds authoritative.

Even before phase-out, ClaimReview had specific requirements and purpose.

It is a Review subtype for fact-checking claims.

Not generic “we reviewed our own statement.”

Not “this article is accurate.”

Not “our service claim verified.”

Using ClaimReview as self-certification would be semantically wrong.

Google's phase-out makes that misuse even less justifiable.

Use actual content type.

Article.

Report.

Review.

ClaimReview only when genuinely fact-checking claim.

Schema.org Tidak Sama dengan Google Feature Gallery

This change should reset mindset.

Schema.org:
large vocabulary.

Google:
supports selected structured-data features.

Some features added.

Some removed.

Some restricted.

Some used in other products.

Search Gallery changes.

If your architecture hardcodes:
“If valid Schema.org, Google will show special result,”
wrong.

If architecture assumes:
“If Google removes rich result, Schema.org type useless,”
also wrong.

Need consumer matrix.

Example internal table:

Type:
ClaimReview.

Schema.org:
Active.

Google Search:
Phasing out.

Factcheck Explorer:
Supported.

Other consumer:
Verify separately.

Internal use:
Yes/no.

Now decision explicit.

This is schema governance.

Not folklore.

Could ClaimReview Still Help AI Search?

Unknown in general.

Do not claim:

“ChatGPT reads ClaimReview.”

“Gemini uses it.”

“Perplexity trusts fact checks more if markup exists.”

Unless platform documentation or controlled evidence supports.

Some AI systems may encounter fact-check pages through search indexes or web retrieval.

Whether they directly parse/use ClaimReview metadata is platform-dependent.

So GEO strategy:

Keep semantic correctness if use case exists.

Observe citation/answer behavior.

Don't promise.

Google Search phase-out is actually warning against schema-as-AI-hack thinking.

Platform features change.

Good content and evidence survive.

Factcheck Explorer Remaining Support Shows Consumer-Specific Design

Same markup.

Different consumer status.

Google Search:
phasing out.

Factcheck Explorer:
supported.

This is a useful architecture lesson.

One structured representation can serve multiple systems.

But only if those systems support.

Therefore documentation monitoring should be consumer-by-consumer.

Not:
“Google supports ClaimReview.”

Too broad.

Which Google product?

Search?

Explorer?

This level of precision matters.

Especially when feature status diverges.

Monitoring Documentation Is Part of Schema Operations

In 2026, schema governance can't be “implement once.”

Google retired/changed multiple Search structured-data features over recent years.

Teams need changelog monitoring.

At least quarterly.

Better:
event-driven.

Subscribe/read Search documentation updates.

Track:

New type.

Changed requirement.

Deprecation.

Property changes.

Search Console report changes.

Testing-tool support.

When announcement:
impact analysis.

Which templates?

How many pages?

What code?

What UI?

What KPI?

Then change.

No panic.

No stale schema for five years.

Schema Has Lifecycle Like Software

Active.

Deprecated by consumer.

Retired.

Still semantic.

Internal-only.

Unsupported.

Experimental.

Create status registry.

Example:

ClaimReview
Schema.org status: available.
Google Search: phasing out.
Factcheck Explorer: supported.
Owner: editorial data.
Review date: 2026-08.
Decision: keep for fact-check pages, remove Search-rich-result KPI.

This is mature.

Developers know.

SEO knows.

Editors know.

No one asks six months later:
“Why is this still here?”

Documentation is governance.

Search Console Reporting May Change Too

When structured-data Search features retire, associated Search Console enhancement/rich-result reporting can also change or disappear depending feature.

Google has done this with other deprecated features.

For ClaimReview, teams should monitor current Google documentation and Search Console rather than assuming legacy reports remain indefinitely.

Don't build executive KPI around a Search appearance filter that may be removed.

Use content KPIs:

Search traffic.

Factcheck visibility.

Referral.

Citations.

Corrections.

Factcheck Explorer discovery.

But verify available data.

Deprecation is analytics issue too.

Do Not Replace ClaimReview with Random “New AI Schema”

This is predictable market response.

Old feature retired.

Someone invents:

AIClaim.

LLMFactCheck.

GenerativeTruth.

Custom JSON-LD.

Then sells as replacement.

Unless vocabulary and consumers exist:
it's custom metadata.

Could be useful internally.

But don't imply Google or AI platforms recognize.

If you need internal schema:
namespace clearly.

If public:
standards and docs.

Don't substitute a deprecated supported feature with unsupported made-up feature just to feel covered.

Evidence Architecture Matters More

Fact-check page should remain highly usable.

Claim:
short and precise.

Claimant:
who said.

First appearance/source.

Verdict.

Evidence.

Method.

Date.

Reviewer.

Corrections.

References.

Machine-readable markup can mirror.

Even if Search rich result disappears, the page remains retrievable and understandable.

This is a stronger investment.

Content structure survives platform change.

Schema follows.

What Does This Mean for GEO.or.id?

For institutional schema strategy:

1. Don't treat Search-feature schema as permanent.

2. Keep a consumer support matrix.

3. Separate semantic value from rich-result value.

4. Don't promise AI citation benefit from unsupported markup.

5. Track deprecations.

6. Version schema runtime.

7. Remove legacy code when no longer useful.

8. Preserve editorial facts independent of markup.

9. Measure external AI behavior separately.

ClaimReview becomes case study in governance.

Not just fact-check markup.

When Should You Remove It?

Possible decision:

Remove if:

No remaining consumer matters.

No internal dependency.

No syndication.

No Factcheck Explorer use.

Maintenance cost > value.

Keep if:

Factcheck Explorer matters.

Fact-check ecosystem integration exists.

Internal structured archive uses it.

Partner/API relies.

Semantic consistency useful.

But periodically reassess.

There is no universal instruction “everyone remove now.”

Because Google itself says one remaining tool still supports it.

Scope matters.

When Should You Keep It but Stop Talking About SEO Benefit?

Now.

If Google Search support is being phased out, don't market ClaimReview as an enduring Google Search enhancement.

Update docs.

Sales.

SEO checklist.

Training.

Remove outdated screenshots.

Stop telling publishers “implement for Google Search rich result” without current caveat.

Historical articles need update note.

This is editorial currentness.

A deprecation isn't complete until organization stops repeating old advice.

The Bigger Lesson: Schema Strategy Must Survive Platform Churn

Today ClaimReview.

Tomorrow another feature.

If schema strategy is:

“Collect every rich result,”
team will constantly chase.

Better:

Model real content.

Use supported platform enhancements when valuable.

Keep consumer registry.

Measure.

Retire gracefully.

Structured data is a contract between publisher and consumers.

Consumers evolve.

Contracts change.

Semantic truth should remain.

ClaimReview being phased out from Google Search doesn't make structured data less important.

It makes disciplined structured-data governance more important.

Because now we can see clearly:

The markup is not the feature.

The feature is not the meaning.

And a strategy that knows the difference doesn't collapse when one blue box disappears from search results.