--- title: "Agentic Web Optimization: SI Agent Readiness | Webtures" description: "Can SI agents find your brand" source_url: "https://www.webtures.com/agentic-web-optimization/" lang: "en" --- # Is your brand usable by SI agents? AWO is a consulting service that makes a brand's information and transactions on the web usable by SI agents. Visibility alone is not enough: once an agent has found and understood the information, **can it complete a task**? That is the real question. 0 assessment stages Discovery · Understanding · Trust · Action 0 maturity tiers From Invisible to Agent-native 0 implementation tasks 8 foundational tasks + 6 transaction links ## GEO is being in the answer. AWO is being part of the task . The two do not replace each other; they stack. GEO gets the brand cited in the answer. AWO makes the transaction that follows that answer possible. One produces visibility, the other a completed task. ### GEO Goal: appear in the answer Brand information is found It is understood correctly It is used as a source It is recommended in answers **Outcome:** visibility, citation and an accurate brand narrative. ### AWO Goal: become part of a task The need is assessed Options are compared A transaction is started The outcome is measured **Outcome:** a completed task and commercial value. ## Usability is assessed in four stages An agent working with your brand passes through these four gates in order. The weakest link decides the outcome: information that is not understood does not count as found, and information that is not trusted never becomes a transaction. STAGE 1 Discovery Access to the site, services and help resources. → STAGE 2 Understanding Interpreting the service, audience, differentiators and terms. → STAGE 3 Trust Freshness, consistency, sourcing and evidence. → STAGE 4 Action Comparison, quote, booking or support. ## Every brand lands in one of four tiers ### Tiers 0 → 3 0 · Invisibleinformation not found 1 · Accessiblereadable, not trusted 2 · Feed-readyusable in a task 3 · Agent-nativetransaction capable The bars show tier order, not a measured success rate. ### What each tier delivers deliverable 0 · InvisibleBasic access and a single source of truth 1 · AccessibleStructured, current, verifiable information 2 · Feed-readyTask flow, permission limits, approval tests 3 · Agent-nativeLive task flow, permission matrix, transaction logs Tier 2 uses the data; tier 3 moves the transaction into the system. The difference is not what the SI knows, but which transaction the brand has opened. ## Same question, two different endings ### Tier 2 · Feed-ready store without a system link 1 Finds the product 2 Compares stores 3 Opens the purchase page **Outcome:** the user finishes the transaction in the store themselves. ### Tier 3 · Agent-native store with a system link 1 Finds the product 2 Confirms the details 3 Sends the order into the store system **Outcome:** the transaction proceeds through the store connection. ChatGPT Instant Checkout Agentic Commerce Protocol Model Context Protocol product feed permission matrix transaction id ## Scoring runs on a real customer task Not an abstract score: the chosen task is attempted end to end and the point where it stops is recorded. Four criteria say where the task breaks; the fifth says whether that can be measured at all. 0 criteria Access%25 Information quality%25 Task%20 Permission and approval%20 Measurement%10 The weights belong to the Webtures assessment framework; they are not an industry standard. ### What each criterion asks 01 · ACCESS Can the agent reach the information it needs? 02 · INFORMATION QUALITY Is the information current, consistent and verifiable? 03 · TASK Can the information be used in a real customer task? 04 · PERMISSION AND APPROVAL What may the agent do, and where is human approval required? 05 · MEASUREMENT Can the outcome be verified against a record? ## The audit runs on priority customer tasks STEP 1 ### Choose the task High business value, clear boundary, measurable. *What are we testing?* STEP 2 ### Map the sources Service pages, help content, required systems. *What will the agent reach?* STEP 3 ### Test with an agent Discovery and understanding, trust and action, failure cases. *Where does the task stop?* STEP 4 ### Find the blocker Finding and screen recording, risk and commercial impact, owning team. *What gets fixed first?* ## Eight foundational tasks make product information usable The order is fixed: access → data structure → feed → freshness control. Breaking the order makes the next step impossible to measure. ACCESS AND PAGE STRUCTURE 01 Set bot access rules Declare allowed and blocked crawlers explicitly in robots.txt. 02 Fix the sitemap and URL flow Add product pages to a current sitemap; clear broken links and redirect chains. MACHINE READABILITY 03 Complete the structured data Mark up product, offer, organization, breadcrumb and genuine review fields consistently. 04 Make critical product data reachable Do not leave price, stock, variant and specs only in images or behind user interaction. PRODUCT DATA AND FEED 05 Prepare the product feed Standardise id, title, price, stock, image, category and link fields. 06 Fix identity and variant structure Complete SKU, GTIN/MPN, size, colour and item-group relationships. FRESHNESS AND QUALITY CONTROL 07 Set up price and stock synchronisation Keep the values identical across site, feed and transaction system. 08 Set up feed validation and freshness checks Catch missing fields, invalid values and stale records on a schedule. ## If the agent will transact, six build tasks open These six items are the technical shape of tier 3. The first three build the data and transaction link; the last three make completion safe. 01 · DATA AND TRANSACTION LINK ### Product query API A service returning product, variant, price and live stock to the agent. 02 · DATA AND TRANSACTION LINK ### Add-to-cart API Updates the cart by product id, variant and quantity, and returns the current cart. 03 · DATA AND TRANSACTION LINK ### User authentication link Limits access to address and order data to a verified session. 04 · SAFE COMPLETION ### Pre-transaction confirmation Shows product, price, delivery and total; does not proceed without explicit approval. 05 · SAFE COMPLETION ### Duplicate-transaction guard Prevents a second cart, order or booking from the same request id. 06 · SAFE COMPLETION ### Order result callback Reports success, failure or pending to the agent and the tracking system. ## Onboarding builds it, monthly consulting runs it AWO is not a one-off audit but a monthly management service. The onboarding work builds the system; the monthly service runs performance and decisions. ### Onboarding what we will manage, and how 01Priority customer tasks 02Baseline assessment 03Permission and approval framework 04Measurement and attribution structure **Deliverable:** a shared working baseline. ### Monthly cycle what works, what must change 1 Measure → 2 Re-test → 3 Prioritise → 4 Decide The decision is one of three: continue, fix or expand. ## We show return through completed transactions , not profit Without asking the client for profit or cost data, we track which transaction the SI-referred user completed. What we measure is not "how many people SI brought" but **how many customer tasks it carried to an outcome**. 01 ### Traceable referral store.com/running-shoes?ai_source=chatgpt Where consented, the source is kept for the session and matched to the resulting order or booking. **Evidence:** a transaction completed via an SI referral. 02 ### Direct system link SI-Txn-1842 → Order-45821 The transaction starts with an id. If the same id appears in the outcome record, attribution is verified directly. **Evidence:** a transaction matched in the system record. 03 ### Platform and partnership report 18 reported → 16 verified Transactions reported by the platform are reconciled against the client's records; cancelled and unmatched results are separated out. **Evidence:** a transaction matched in two independent records. ### What the monthly report shows illustrative view 0 tasks started 0 transactions completed 0 completion rate 0 verification methods The figures illustrate the report format; they are not a measured client result. ## The monthly report answers four questions 01 ### What happened? Tasks started, completed and handed off. 02 ### Where did it stop? Errors, blockers and human intervention. 03 ### What got fixed? Last month's actions and the re-test result. 04 ### What value did it create? Verified transactions, time and cost impact. ## What the service does not include Webtures owns the consulting. Software development and live operations sit outside the scope. Technical implementation is carried out by the client's team or their delivery partner, against requirements Webtures writes. IMPLEMENTATION REQUIRING A SEPARATE QUOTE Custom agent developmentAgent software, model infrastructure, live product build Backend and API integrationWriting code into order, booking, appointment and customer systems Cart, payment and transaction infrastructureCreating live transactions, taking payment and financial liability Code changes in client systemsProduct, stock, database and application development Continuous technical operationsLive agent operations, incident response and ongoing support ## Common questions Tier differences, verification methods and scope boundaries come up most often. If yours is missing, tell us and we will add it. 01 ### What is the difference between AWO and GEO? GEO aims to get the brand into SI answers: being found, understood correctly, used as a source and recommended. AWO aims at the transaction that follows the answer: assessing the need, comparing options, starting the transaction and measuring the outcome. GEO produces visibility; AWO produces a completed task. 02 ### How do we find out which tier we are in? A real customer task is chosen and attempted end to end with an agent. If information cannot be found or contradicts itself, tier 0. If it is readable but not trustworthy, tier 1. If it is structured and current enough to use in a task, tier 2. If the agent can transact within its permissions, tier 3. 03 ### Does tier 3 always require building APIs? Yes. Tier 3 means moving the transaction into the system: without product query, add-to-cart, user authentication, a confirmation step, duplicate protection and a result callback, an agent cannot complete a task. These six build tasks sit outside the consulting scope and are implemented by the client's team or delivery partner. 04 ### How do you verify results? Through three independent records: a traceable referral link, a transaction-id match on the direct system link, and reconciliation of the platform report against the client's own records. We do not estimate sales or bookings; we classify by the technical evidence at hand. 05 ### Does this apply to brands outside e-commerce? Yes. The task does not have to be a purchase: booking an appointment, requesting a quote, opening a support ticket or making a reservation all pass through the same four stages. The feed and product-data items are e-commerce specific; in other sectors service, capacity and availability data take their place. 06 ### How long before we see results? The baseline assessment and priority-task selection finish in the first month. Access and data-structure fixes usually produce a measurable difference within two months. Tier 3 work that needs a transaction link depends on the client's own development schedule.