I wrote the standard for making websites AI-operable. Learn More
Tools · OARS for WordPress
Agents are a new kind of visitor to your site. Most WordPress sites aren't ready for them — not because anything's broken, but because nothing on the page yet tells an AI agent what your business is, who it serves, or how to reach it. This plugin adds that layer. The free version takes a WordPress site to OARS Level 1 the day you activate it. Pro keeps you continuously scored against the standard, monitors the site weekly, generates the schema Level 2 needs, supports multisite, and submits your site to the public Knov.ai directory in one click — $49 a year per site.
Free version
These six pieces are what OARS Level 1 requires. The free plugin produces and maintains them — none of them need configuration, and the settings page lets you override any default if you want to.
/oars.json file an agent can actually readThe file an AI agent looks for to learn what your business is, who it serves, and what it sells. Pulled from your site title, tagline, contact details, and category taxonomy. Updates itself whenever you change site settings or publish a post.
robots.txtGPTBot, ClaudeBot, PerplexityBot, Google-Extended, and the rest each get explicit allow or disallow directives — written into your existing robots.txt without touching the rules you've already set.
Organization JSON-LD on your homepage — name, URL, logo, contact info, social profiles — so any AI parsing your page knows who you are. If your SEO plugin already emits Organization markup, this defers to it instead of fighting.
The response header that tells AI systems whether they can use your content for search results, model inputs, or training. Three toggles in the settings page; same answer applied to every page on your site.
llms.txt that mirrors your siteThe text-format index AI systems use to navigate your site — generated from your page and post structure and rebuilt every time you publish.
A single score in the WordPress dashboard with every failing check listed alongside the exact fix. Most sites pass Level 1 on activation; the rest get a short punch list.
Pro · $49 per site per year
The free version takes a site to Level 1 once. Pro keeps it there as the standard moves, takes it to Level 2, and runs the same checks the OARS Scanner runs — continuously, against your own site.
Every check the OARS Scanner runs, run against your site weekly. Each failing check comes with the specific fix — same model, just running on a schedule instead of on demand.
A WP-Cron job re-scores the site every week. You only hear from the plugin when something changes — a regression to investigate, or a long-broken check that finally passes.
Service, Product, and FAQPage schema generated from your pages — and from WooCommerce products if you run a store. The markup Level 2 needs, without anyone writing JSON-LD by hand.
oars.json that's never staleHooks into every save_post and option update — and every WooCommerce product change — so your oars.json reflects your site as it is, not as it was last Tuesday.
Network admin sees every site's score in one place. Settings inherit by default; override what needs overriding on a per-site basis.
Submit your site to the public OARS directory without leaving the dashboard. The verification ID comes back into your settings and gets written into your oars.json automatically.
Drop [oars-badge] into a page or template and render a live badge that reflects your current declared level. Updates as your score moves.
Setup
The plugin is built so the free version is useful the moment activation finishes — no settings page to fill in before anything turns on.
1
Upload the zip from Plugins → Add New → Upload, or — once the WordPress.org listing goes live — search the plugin directory for "OARS for WordPress".
2
Activation is enough. /oars.json, llms.txt, the robots directives, the Organization schema, and the Content-Signal headers all come online — nothing to configure first.
3
The dashboard shows your OARS Level 1 score the moment activation finishes. Most sites pass. The rest get a short list of fixes, usually a missing logo or an unset social profile.
4
Paste a key into Settings → OARS → Pro and the weekly scoring, expanded schema, multisite controls, and directory submission turn on. Free keeps working if you don't.
Get a Pro key · $49 / site / year
One year of OARS for WordPress Pro for one site. Stripe handles the charge. Your key is shown on the next screen and emailed to you the moment Stripe confirms — usually under thirty seconds.
Need to move the key to a different site later? Reply to the activation email. Need keys for multiple sites? Buy one per site.
No. Activate the plugin and the Level 1 work happens without any configuration. The dashboard tells you your current score and explains any gaps in plain English. If you want the broader picture of what OARS is, /standard is the right place to start.
No. SEO plugins own page meta and sitemaps — things AI agents barely read. This plugin owns a separate layer: oars.json, AI crawler rules in robots.txt, the Schema.org identity on your homepage, Content-Signal headers, and llms.txt. If your SEO plugin already emits Organization schema on the homepage, OARS for WordPress sees it and gets out of the way.
Free does OARS Level 1. Pro extends scoring to Levels 0 and 2, runs the score weekly, generates schema for your services / products / FAQs, supports multisite, submits your site to the Knov.ai directory, and ships a badge shortcode. Same upgrade decision as the rest of WordPress — free does the work, paid does the work and tells you when something changes.
One year of Pro for one site. The key activates the site you used at signup. To move it to a different site, reply to the activation email and I'll release the seat. For multiple sites, buy one key per site.
As soon as Stripe confirms the charge — typically under thirty seconds. The key is shown on the next screen and emailed to the address you entered.
I wrote OARS. The standard is open and free and lives at knov.ai. This plugin is one implementation path — the easiest one if your site is on WordPress. Other CMSes and custom stacks need their own approach; that's what /consulting/implementation is for.
No measurable impact. oars.json and llms.txt are regenerated on save and served as static files. The Schema.org JSON-LD is one small script tag in the head. Content-Signal headers are added at response time. Pro's weekly re-scoring runs through WP-Cron, off the request path.
Yes, within 14 days of purchase, no questions asked. Reply to the activation email.
If your site isn't on WordPress
This plugin is the WordPress path. Shopify, Webflow, custom CMSes, headless front ends — they all need the same agent-readiness layer, just built in their own way. The free OARS Scanner works on any URL, and the audit is the next step for sites that aren't on WordPress.