Get started

Getting started.

From signup to first published llms.txt in 10 minutes. We’ll cover the four things that matter: scan, understand, fix, monitor.

1. Run a scan

You don’t need to sign up to scan. From the home page, paste any public URL into the scanner input and hit Enter.

Scans take 1–3 seconds. The scanner fetches the page, parses HTML, looks for AEO/agent-readiness signals (llms.txt, JSON-LD, agent-skills, meta tags, robots, OpenGraph, schema.org markup, and more — 17 checks in total), and computes four scores: Overall, AEO, Agent, and Commerce.

What gets stored?

Public scans are saved (anonymously — we hash any IP). This is so you can come back and view past results, and so we can build better aggregate insight over time. We never sell or share scan data with third parties.

2. Read the report

Each check appears as an expandable card. The summary at the top shows whether the check passed, warned, or failed, plus a score contribution (×weight). Click to expand.

Recommendations are the actionable part — what to add, change, or remove.
Evidence shows exactly what we found on your site, so you can verify our reasoning.
Fix snippets are copy-pasteable. We’ll give you the literal llms.txt contents, the JSON-LD block, the meta tag, etc.

3. Sign up to monitor + alert

A one-off scan tells you where you are today. Signing up unlocks:

Scheduled monitoring — weekly on Free, daily on Plus and Pro.
Regression alerts — email (and Slack on Plus + Pro) when your score drops or a key check fails.
Score history + trend — see whether you’re improving over time.
Citation tracking — see when AI engines cite you for queries you care about (Plus + Pro).

4. Add your site

From the dashboard, click + Add site and paste your URL. We’ll normalise the hostname (we treat example.com and www.example.com as the same site) and create the record.

Verifying ownership (optional)

You don’t need to verify a site to scan it or get alerts. We recommend verification only if you want to:

Use the WordPress plugin to deploy generated files automatically.
Get a verified badge on shared scan reports.
Use the public REST API to act on the site programmatically (Pro).

Three verification methods are supported: DNS TXT record, meta tag in <head>, or the WordPress plugin (which auto-verifies as a side effect of connecting).

5. Ship a fix

For most users the fastest first win is generating an llms.txt. From your site’s page in the dashboard, click Generators → llms.txt. We’ll produce a draft tailored to your site, which you can edit and deploy:

If you use WordPress: install the plugin, click Connect with API key, then Deploy. The file appears at /llms.txt on your site within seconds.
Otherwise: copy the file contents and place them at the root of your site, served as text/plain.

Verify it worked

Visit your-domain.com/llms.txt in a browser — you should see the file. Then run another scan to see the AEO score improve.

CLI shortcut (Pro)

On the Pro plan you can trigger scans from the command line:

bash

# Get an API key from /account/api-keys

curl -X POST https://aiseolab.ai/api/v1/scans \
  -H "Authorization: Bearer $AEO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id": "..."}'

See the API reference for everything else.

What is AEO?

Understand the file standards and signals that make AI engines cite you.