From the Had A Farm tool shed

Grown in a real browser.

Lighthouse parses static HTML. eiSEO renders every page in a real Chromium browser with Playwright and axe-core, catching the JavaScript-rendered ARIA failures and missing keyboard paths a parser never sees. WCAG 2.2 AA. Page-level results. Under 2 minutes.

Scan my site free → See the engines

50 pages free · No credit card · Results in under 2 minutes

Playwright + axe-core engine · WCAG 2.2 AA · Built by a chief web architect and digital accessibility practitioner

001 / The Method

Rendered, not parsed.

Most scanners read your HTML the way a machine reads a seed catalog: the words are there, but nothing has grown yet. Your site is not static HTML. Menus open, modals mount, ARIA states change, and entire components exist only after JavaScript runs. eiSEO drives a real Chromium browser with Playwright, waits for your page to become what your visitors actually see, then runs its engines against the rendered DOM.

Real browser. Real results. Not a static HTML parse.

Prepare

eiSEO reads your sitemap and normalizes your domain, so the whole field gets scanned, not one corner of it.

Plant

Every page is queued, up to your plan's page limit. Site-wide coverage, not a one-page spot check.

Tend

Each page renders in real Chromium. Scripts execute, components mount, and the page becomes what your visitors see.

Harvest

Four engines run against the rendered DOM: accessibility, policy, SEO, and AI search visibility.

Sustain

Re-scan as your site changes. New violations surface before your visitors, or your auditors, find them.

Share

Export page-level findings: evidence for a board, a handoff for a client, or a punch list for a developer.

002 / The Engines

Four engines. One scan.

Every engine reads the same rendered page, so a single scan covers compliance, your own standards, search, and how AI systems see you.

Accessibility Engine

WCAG 2.2 AA, tested where your users actually are: the rendered page. Playwright drives a real Chromium browser, axe-core runs after your JavaScript executes, and the violations that never appear in static HTML get caught and documented, page by page.

WCAG 2.2 AA axe-core 4 Rendered DOM ARIA states Keyboard paths Color contrast
axe-scan results
$ eiseo scan --engine=axe https://example.com
✓ Color contrast ratio 4.5:1 met (127 elements)
✓ All images have alt attributes
✓ Heading hierarchy is sequential
⚠ Focus indicator missing on 3 elements
✗ aria-label empty on navigation
Scanned 42 pages in 18.3s | 3 issues found

Policy Engine

Your own HTML rules, enforced across every page in your sitemap. CSS selectors and regex patterns, severity levels, remediation hints. Your standards, checked automatically.

Content matching Attribute validation Regex patterns Team rules Severity levels Remediation hints
policy-check results
$ eiseo scan --engine=policy https://example.com
✓ All links have descriptive text (no "click here")
✓ Phone numbers match E.164 format
⚠ Copyright year outdated on /about (2024)
✗ Missing privacy link in footer on 3 pages
✗ Brand name misspelled on /careers
8 policies checked across 42 pages | 5 violations

SEO Engine

On-page checks for every URL in your sitemap: title tags, meta descriptions, heading structure, canonicals, Open Graph, image attributes. Run against the rendered page, not the source file. Every unique link found during the scan gets checked too: dead internal links are flagged high priority, dead external links medium, and ambiguous responses (rate limits, login walls) are never false-flagged as broken.

Title tags Meta descriptions H1 structure Image optimization Canonical tags Open Graph Broken links
seo-scan results
$ eiseo scan --engine=seo https://example.com
✓ Title tags present and under 60 chars (42/42)
✓ Canonical tags set correctly
⚠ Meta description too long on /pricing (172 chars)
⚠ 4 images missing width/height attributes
✗ Duplicate H1 on /blog/seo-guide
✗ Broken internal link on /resources (404)
42 pages analyzed | SEO score: 87/100

AI Search Engine

Track how AI systems see your content, and what they can extract. Structured data, FAQ blocks, author attribution, freshness signals, bot directives: the new search frontier, measured.

Structured data FAQ blocks Author attribution Freshness signals AI bot directives Content extractability
ai-seo results
$ eiseo scan --engine=ai-seo https://example.com
✓ JSON-LD structured data on all key pages
✓ FAQ schema detected on 8 pages
⚠ No author attribution on /blog pages
⚠ GPTBot blocked in robots.txt
✗ Content readability score below threshold
AI visibility score: 72/100 | 3 quick wins available
Learn more about the AI SEO Engine →
003 / The Harvest

Evidence you can hand to your board.

For the compliance officer

The ADA Title II deadline arrived April 24, 2026. Public universities, cities, and county agencies need documented WCAG findings, site-wide, that hold up in front of a board. That is what a scan produces: page-level evidence, not a score.

For the agency developer

You already run Lighthouse. eiSEO catches what it misses, because your client's site renders JavaScript and Lighthouse doesn't wait for it. Page-level export makes the client handoff a report, not a conversation.

For whoever got handed this

Legal or IT put accessibility on your desk. eiSEO gives you plain-language results you can forward to a developer without translation, and a record that the work is underway.

eiSEO was built by Brent Passmore, the digital accessibility practitioner managing large-scale WCAG audits and PDF remediation programs at a large academic medical center. It's the tool he needed and couldn't find.

, Founder of Had A Farm
004 / Pricing

Start free. Grow when your site does.

Monthly Yearly Save 20%

Free

$0 forever

Try the basics. No card required.

  • 1 site, 50 pages
  • 3 scans/month
  • WCAG AA scanning
  • SEO scanning
  • No AI SEO
  • No exports
Scan 50 pages free →

Starter

$39 / mo $26 / mo, billed yearly

For solo developers and small projects.

  • 2 users
  • 3 sites, 200 pages each
  • 15 scans/month
  • WCAG AA + SEO scanning
  • Scheduled scans (weekly)
  • CSV export
Start scanning 3 sites → Start scanning 3 sites →

Pro AI visibility

$79 / mo $63 / mo, billed yearly

For teams ready for AI-powered SEO.

  • 5 users
  • 10 sites, 750 pages each
  • 50 scans/month
  • Full WCAG + AI SEO
  • AI Visibility (Perplexity)
  • 2 competitors tracked
  • CSV + XLSX export
Unlock AI visibility → Unlock AI visibility →

Business

$199 / mo $159 / mo, billed yearly

For teams that need everything, unlimited.

  • 15 users
  • 25 sites, 2,500 pages each
  • Unlimited scans
  • Full WCAG + AI SEO
  • AI Visibility (all platforms)
  • 10 competitors + all exports
  • API access
Scale to 25 sites → Scale to 25 sites →

Enterprise

Custom

For large organizations with complex needs.

  • Unlimited users
  • Unlimited sites and pages
  • Unlimited scans
  • All engines + all formats
  • Multi-team management
  • API access + SSO
  • White-label available
Contact us →
005 / Common Questions

Asked before you got here.

I already use Lighthouse. Why would I need eiSEO?

Lighthouse parses HTML. eiSEO renders pages in a real browser. This matters because your site renders JavaScript: menus, modals, ARIA states, and entire components that only exist after scripts run. eiSEO runs axe-core against the rendered DOM in real Chromium, so it catches violations a static parse structurally cannot see.

What do I get on the free plan?

One site, 50 pages, three scans a month. No credit card. Results in under 2 minutes.

What standard does the accessibility engine test against?

WCAG 2.2 AA, using axe-core running in a real Chromium browser driven by Playwright. Every finding is documented page by page, so you can present it as compliance evidence.

Can I export results?

Yes. Findings export at page level, so an agency can hand a client a report and a compliance officer can file evidence with their board.

Does eiSEO check for broken links?

Yes. The SEO engine checks every unique link it finds across your scanned pages. Dead internal links are flagged as high priority and dead external links as medium, each with fix guidance. The checker is conservative by design: rate-limited or login-protected pages are never reported as broken.

Is eiSEO itself accessible?

It has to be. An accessibility tool that fails its own scan has no business selling one. We run axe-core on eiSEO before every significant change ships.

006 / Start

Ready when your site is.

Point eiSEO at your sitemap and see what a real browser sees.

Scan my site free →

50 pages free · No credit card · Results in under 2 minutes