AI AGENT READINESS

Can AI agents
use your website?

Audit your website with PageScanner, Ora and Google PageSpeed. Check agent usability, DNS and page delivery, with evidence behind every result.

Scan profile

Scans public pages, discovery endpoints and DNS, and sends the public domain to Ora and Google PageSpeed for separate provider reports.

Try a live scan
SAMPLE REPORT

WEBSITE FOUNDATIONS

northstar.example Website audit
  • Find89
  • Read65
  • Act47

What we check

Agent readiness, domain health and page performance in one audit.

64 checks + Ora + PageSpeed

Find

Can agents reach your pages?

Check crawl rules, HTTPS, your sitemap and the signals that point agents to the right URL.

  • Crawler rules
  • Sitemap
  • Indexing

Read

Can agents understand them?

Inspect the HTML, page metadata, schema, llms.txt and Markdown served to automated readers.

  • Structured data
  • llms.txt
  • Markdown

Act

Can agents take the next step?

Find contact paths, forms, APIs and protocols that let agents do something with what they learn.

  • Forms
  • MCP
  • APIs
  • Commerce

DNS

Is your domain configured correctly?

Inspect addresses, nameservers, DNSSEC, email policies and DNS discovery records.

  • DNSSEC
  • Nameservers
  • Email policies

Delivery

How are your pages delivered?

Check HTTPS redirects, caching, compression, browser headers and observable CDN signals.

  • HTTPS
  • Caching
  • Headers

PageSpeed

How does your page perform?

Google measures mobile and desktop performance, accessibility, best practices, SEO and agentic browsing. Explore every returned Lighthouse audit.

  • Mobile
  • Desktop
  • Lighthouse

Ora AX

Can agents discover and use you?

Ora supplies its own agent readiness report, including brand search, WebMCP and applicable integration checks. Review its evidence, scoring version and estimated fixes.

  • Discovery
  • Usability
  • Protocols

How scoring works

PageScanner, Ora and Google report separate scores with different scopes.

What does PageScanner fetch?

A scan reads the public homepage, up to four relevant internal pages, up to three same-origin llms.txt links, common discovery files and DNS records. HTML sampling is bounded. MCP checks use initialization and tool discovery. The public domain is also sent to Ora and the homepage URL to Google PageSpeed. Ora's saved report is used when available; a missing report starts a quota-limited provider scan.

What changes with each profile?

Website weights common visitor actions, Publisher emphasizes discovery and readable content, and App / API emphasizes API and protocol discovery. The PageScanner foundations score combines Find, Read and Act. DNS and Delivery have their own scores. Optional and unverified checks carry no points, and partial results earn half credit. The foundations score does not include external search visibility or prove functional agent tools.

Why can Ora's score differ?

Ora uses its own rubric for discovery, access, usability and payments, including checks that PageScanner treats as optional. Its report is imported with the scan date and scoring version. Raw layer points are not overall score points. Provider estimates and search observations need verification; a failed brand search can depend on the search index. Neither this report nor a “watch” link proves a live journey was completed. Run a journey on Ora to observe an agent attempting a task.

Why might a result be unverified?

Timeouts, access restrictions, browser challenges and provider quotas can prevent verification. The readiness score requires a reachable homepage and assessment of at least 55% of applicable checks. Emerging discovery and commerce protocols remain informational when their relevance is unverified. A DNS snapshot reports current records. Dynamic DNS update history requires monitoring.