Platform guides

How to make your site agent-ready, whatever it's built with. Three things help AI agents most, and each raises your agent-readiness score:

Your own LAWP at /.well-known/lawp.json: your pages and actions, in your words. Make it with the LAWP Generator.
Business details as schema.org data: address, opening hours, phone, prices. Google uses these too.
Actions agents can take: contact, book, order. A booking system like Calendly, OpenTable or Fresha counts; Actuent links straight to it.

Some platforms don't let you put files at /.well-known/. For those, claim your site in Analytics → My sites and edit what agents see in a form. Claimed sites are never overwritten by the crawler.

At a glance WordPress Shopify Squarespace Wix Webflow Static hosts Cloudflare Your own server

At a glance

Platform	Own lawp.json	Business details	Easiest route
WordPress	Yes (plugin)	Your SEO plugin	Actuent plugin
Shopify	No	Theme code	Products are automatic; claim your site
Squarespace	No	Code injection	Claim your site
Wix	No	SEO settings	Claim your site
Webflow	No	Custom code	Claim your site
Netlify, Vercel, Cloudflare Pages, GitHub Pages	Yes	In your HTML	Add the file
Any site on Cloudflare	Yes (Worker)	In your HTML	One-click Worker

WordPress

Install the Actuent LAWP plugin (Plugins → Add New → Upload Plugin). It publishes /.well-known/lawp.json and /llms.txt from your pages, with a search action and a contact action that emails you. WooCommerce products are picked up automatically.

Business details: most SEO plugins (Yoast, Rank Math, All in One SEO) have a "local business" or "organization" setting that outputs schema.org data. Fill in your address, phone and opening hours there.

Shopify

Products: nothing to do. Actuent reads your public catalogue (/products.json) with prices, stock and barcodes, so your products show up in shopping searches and price comparisons.

Your own lawp.json: Shopify doesn't allow files at /.well-known/, and Actuent doesn't follow redirects there (only you should control that address). Instead, claim your site and edit your pages and actions in Analytics → My sites.

Business details

Online Store → Themes → ⋯ → Edit code → theme.liquid, and paste before </head> (edit the values):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Store",
  "name": "{{ shop.name }}",
  "url": "{{ shop.url }}",
  "telephone": "+45 12 34 56 78",
  "address": { "@type": "PostalAddress", "streetAddress": "Street 1", "postalCode": "1000", "addressLocality": "Copenhagen", "addressCountry": "DK" },
  "openingHoursSpecification": [{ "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"], "opens": "10:00", "closes": "18:00" }]
}
</script>

Online-only shop? Use "@type": "OnlineStore" and leave out the address and hours.

Squarespace

Squarespace doesn't allow files at /.well-known/, so claim your site and edit what agents see in Analytics → My sites.

Business details

Fill in Settings → Business information (address, phone, hours). To add more, such as services with prices, go to Settings → Developer tools → Code injection → Header (on plans that include it) and paste a schema.org snippet like the one for Shopify, with "@type" set to your business type (for example "HairSalon" or "Restaurant").

Squarespace Scheduling (Acuity) links on your site are detected as a booking action automatically.

Wix

Wix doesn't allow files at /.well-known/, so claim your site and edit what agents see in Analytics → My sites.

Business details

Fill in your business info in the Wix dashboard (Settings → Business info). For custom structured data, open a page's SEO settings → Advanced SEO → Structured data markup, and add a schema.org snippet like the one for Shopify.

Webflow

Webflow doesn't allow files at /.well-known/, so claim your site, or, if your domain's DNS is on Cloudflare with the proxy on, use the Cloudflare Worker.

Business details

Site settings → Custom code → Head code: paste a schema.org snippet like the one for Shopify.

Static hosts

Make your file with the LAWP Generator, then add it to your site as .well-known/lawp.json (a folder named .well-known at the root of your published site).

Netlify, Vercel, Cloudflare Pages: put it in your publish folder (often public/ or dist/). Done.
GitHub Pages: Jekyll skips folders starting with a dot. Add an empty .nojekyll file to the root, or add include: [".well-known"] to _config.yml.

Add the schema.org snippet (like the one for Shopify) to your homepage's <head>, and optionally an llms.txt at the root.

Any site on Cloudflare

If your domain uses Cloudflare with the proxy (orange cloud) on, deploy the Actuent Worker in one click. It serves /.well-known/lawp.json and /llms.txt built from your pages, without touching your site, and can count AI bot visits for Analytics.

Your own server

Serve the file at /.well-known/lawp.json as JSON, without a redirect.

# nginx
location = /.well-known/lawp.json {
  alias /var/www/lawp.json;
  default_type application/json;
  add_header Access-Control-Allow-Origin *;
}

// Express
app.get("/.well-known/lawp.json", (req, res) => res.set("Access-Control-Allow-Origin", "*").sendFile("/srv/lawp.json"))

Want agents to actually do things, like book or send a message? Add an endpoint to an action: see LAWP Actions.

After any of these, check your site with the LAWP Checker and see your score at https://api.actuent.ai/site/yoursite.com. Changes show up after the next crawl, or right away for claimed sites.