Check and improve your shop's agent readiness

An agentic score is a third-party estimate of how easily an AI assistant can find, read, understand, and use a public website. It is a useful way to spot missing shop information, but it is not a KORONA Event setting or a guarantee that an assistant will recommend your offers. This guide uses Is Agentic as an example. Its methodology explains that individual checks and their evidence matter more than the total score.

Your shop already provides public discovery features such as a sitemap, an llms.txt guide, readable page content, and offer data. The quality of the score also depends on the pages and details your team publishes.

Before you start

Use the shop's public, preferred domain and a customer-facing language URL. The shop should be published and accessible without staff sign-in. Scan a preview or temporary test address only to inspect its content; checks for brand recognition, search presence, and domain identity are meaningful on the real public domain.

Prepare accurate organization details, approved legal notices, a short introduction to the shop, and complete information for offers you intend to sell. Keep private or staging shops private; do not enable indexing just to improve a test score.

Check the public report

Open the public shop in a private browser window. Confirm that the home page and at least one offer detail page load without signing in.
Copy the shop's public home-page URL into Is Agentic and start a scan.
Read the Commerce view, then open the evidence for each essential and recommended check. Note the scanned URL and scan time. A failed or partial check can reflect missing content, a temporary network problem, or the scanner's interpretation.
After changing and publishing content, check the public pages again and rescan. A repeat request can show a cached result for up to six hours; use the timestamp to tell whether the report is fresh.

The score is a snapshot from an independent service. Its checks and applicability can change, and automated checks can be wrong. Use the underlying evidence to decide what to change rather than aiming for a fixed number of passing checks.

Improve the information you control

In the back office, open Shops, select the shop, and open SEO. Fill in Site name, Default meta description, and Default social image, including meaningful image alternative text. Add translations for every shop language. These are defaults; a page or offer can have more specific metadata. See Configure search and social sharing for the fields and their fallback order.
In Organization identity on the same tab, check the legal and public names, website URL, address, phone number, logo, and social links. Use the account profile when it represents the shop operator, or enter shop-specific details when it does not. Link to your real organization website and public contact channels.
Open Page Builder, edit Home, and add a Heading block with Level set to H1 for the page's main heading. Add a useful introduction: who runs the shop, what customers can book or buy, where or when it happens, and which offers to explore. Add an Offer List or links to the relevant public offer pages. Use editable blocks for the main heading on custom pages and the Detail Template too; pages edited in Page Builder do not receive an automatic heading. Write for customers; repeating keywords or adding filler text does not make an offer easier to understand. Use Customize shop page content and ordering for the editing and publishing steps.
On Home, expand SEO & Meta if the generated title or description needs a page-specific value. A representative social image is useful for shared links. Keep page text and metadata consistent, and translate both for the languages you publish.
Review each published event, admission, product, or voucher in the back office. Give it a specific name, useful description, suitable image, correct date or location where applicable, and current price and availability. Link from the home page or an offer list to the detail page. The shop presents offer prices from the live offer data; avoid copying changeable prices into static home-page text. Use the offer's SEO tab for an offer-specific title, description, or URL when the defaults are insufficient.
Under Admin > Profile > Legal Notices, maintain the approved privacy policy, imprint, terms, and other documents your shop needs. Provide complete, accurate content or an approved public URL, with the languages your customers use. On the public shop, verify that the legal links open and that customers can find a real way to contact the operator. If useful, create an About or Contact page in Page Builder, enable it, and show it in navigation. A short placeholder page written only for a scanner does not establish trust.
When the shop is ready for public search, review SEO > Indexing and the indexing choice for each page or offer. Index only public content that should appear in search results. A custom shop domain gives customers and search engines a stable address; search presence still takes time and depends on external search engines.

The shop generates its sitemap and llms.txt from public content. You do not need to write or host those files yourself. Checks for external brand mentions, search results, or developer APIs may still be incomplete for an individual shop; only add such material when it serves real customers or developers.

Check the result

Visit the published home page, a representative offer, and the legal and contact links as a customer. Make sure the description, price, organization identity, and language are accurate. Then compare a fresh scan's evidence with the changes you made. If a check still fails, follow the evidence to the affected public page or setting; a high total score does not replace this review.