Getting started

This page walks you from reading the spec to a live site that serves AOM: site policy at a fixed URL plus per-page JSON-LD in the document head, checked with the validator on aom.tools.

Before you begin (no jargon)

You will publish two kinds of JSON:

  1. Site policy — One file for your whole site, served at https://your-domain/.well-known/aom-policy.json. It tells agents the default rules for your domain (including automation).
  2. Page AOM — For each page you care about, a JSON object embedded in HTML as <script type="application/ld+aom+json">…</script> in <head>. That is the “surface” agents read for that screen.

The browser extension helps you see and export JSON from pages; it does not add AOM to your site by itself. You wire policy and page JSON using a plugin or your own templates, then deploy. After deploy, use Validate on real URLs.

Full field definitions and examples are only on the spec site: agentobjectmodel.org. How automation_policy behaves is summarized on Automation modes.

For site owners (any stack)

  1. Read the spec. Skim structure first, then deep-link into sections you need. Understand site policy and page surfaces on agentobjectmodel.org. For forbidden, allowed (with guardrails), and open, see Automation modes.
  2. Install AOM Surface Explorer. Add the browser extension from the Chrome Web Store or from Downloads for surface owners (zip for unpacked load). Details: Browser extension.
  3. Explore pages with the extension. Open your site in Chrome or Edge (local, staging, or production). Click the AOM Surface Explorer icon: the popup reads the page and shows generated or existing AOM JSON. Use Copy or Save AOM as file to draft or review surfaces. The extension does not write AOM into your HTML—publishing happens in the next step.
  4. Publish AOM on your site. Serve site policy at /.well-known/aom-policy.json and add per-page <script type="application/ld+aom+json"> in <head>, as defined in the spec. Use a plugin for your stack, or static snippets for plain HTML, and deploy those changes.
  5. Validate. At aom.tools/validate, run Site policy against your policy URL and Page AOM against real page URLs (or paste JSON). Fix any reported issues.
  6. Go live. After deploy, re-check validation on your production policy and page URLs so agents see the same surfaces you tested.
  7. Tag us on X when you ship.

For Next.js, Nuxt, Gatsby, WordPress, and Shopify

  1. Read the spec and Automation modes so your policy and pages match how you want automation to behave.
  2. Download the plugin for your stack from Downloads for surface owners (versioned zip).
  3. Integrate per README. Unzip and follow that folder’s README—copy middleware/components (Next.js), wire Nuxt/Gatsby, install the WordPress plugin, or add the Shopify Liquid snippet. There is no single npm package such as npm i aom-next; integration is copy-and-wire—see Plugins.
  4. Ship policy and JSON-LD. Confirm your app serves /.well-known/aom-policy.json and emits page-level AOM in <head> as the plugin documents, then deploy.
  5. Optional check: On a live page, open AOM Surface Explorer—if you wired JSON-LD correctly, the popup can show your native page AOM (not only a generated draft).
  6. Validate policy and page URLs at aom.tools/validate on staging and again on production.
  7. Tag us on X when you’re live.

Also useful

Browser extension (full detail) · Badge usage

Documentation · Downloads · Surface owners · Agent owners

Validate your AOM surfaces