How often should I recheck?

After any theme, app, CDN or checkout change, and periodically after that.

Yes. arc-check runs in CI and fails when the UCP profile or WebMCP breaks.

Does claiming my store page cost anything?

No. Claiming a store page does not cost anything.

How do I make sure my store stays agent-ready after changes?

Theme updates, apps and bot settings can quietly break agent access. Recheck your store after every change: ARC's free store page keeps a simple history. Developers can add ARC's arc-check step to their build so it fails when the UCP profile or WebMCP breaks. Claim your store card to keep a contact on file.

Why readiness breaks

A theme update, an app, a CDN rule or a checkout change can turn a working profile into a block or an invalid file. The store page keeps a simple history of the checks ARC stored. A gap in that history is not a failure.

Recheck after changes

Open the store page after the change and read the latest check date. One-off profile validation is how to check a UCP profile. This page is the repeat check.

Automate with arc-check

arc-check fetches /.well-known/ucp and reads the latest HTTP check. It can fail a build when the UCP profile or WebMCP breaks. The commands are on /developers.

Watch the method changelog

Method changes are not store breakage. The changelog records a 7 October 2026 WebMCP correction: checks saved before the detector existed are Not measured, not a no. That is a method note.

Method changelog: MeasuredMeasuredThe changelog is the method record. It is not a count of stores that broke.

Breakage frequency across stores

Breakage frequency across stores: Not measuredNot measuredadoption_history.csv in this snapshot covers 2 weeks. Its metrics are weekly index and rails counts, not a breakage frequency. A missing breakage count is not zero breakages.

Claim your store card

Claiming keeps a contact on file and does not change the measured result. It does not cost anything.

Frequently asked questions

How do I make sure my store stays agent-ready after changes?: Theme updates, apps and bot settings can quietly break agent access. Recheck your store after every change: ARC's free store page keeps a simple history. Developers can add ARC's arc-check step to their build so it fails when the UCP profile or WebMCP breaks. Claim your store card to keep a contact on file.
How often should I recheck?: After any theme, app, CDN or checkout change, and periodically after that.
Can I automate it?: Yes. arc-check runs in CI and fails when the UCP profile or WebMCP breaks.
Does claiming my store page cost anything?: No. Claiming a store page does not cost anything.

On ARC

Cite this: ARC, arcreport.ai, accessed 2026-10-13, CC-BY-4.0. Protocol figures: ARC saved checks, accessed 2026-10-13 (13 October 2026). Index browser figures: ARC open dataset snapshot 2026-10-12. Platform figures: ARC saved checks, accessed 2026-10-13.

Every figure is labelled Measured, Inferred or Not measured. Not measured is not zero. A missing result is not a mark against a store. ARC stops before payment.