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
AI AGENT READINESS
Audit your website with PageScanner, Ora and Google PageSpeed. Check agent usability, DNS and page delivery, with evidence behind every result.
WEBSITE FOUNDATIONS
northstar.example Website auditAgent readiness, domain health and page performance in one audit.
Can agents reach your pages?
Check crawl rules, HTTPS, your sitemap and the signals that point agents to the right URL.
Can agents understand them?
Inspect the HTML, page metadata, schema, llms.txt and Markdown served to automated readers.
Can agents take the next step?
Find contact paths, forms, APIs and protocols that let agents do something with what they learn.
Is your domain configured correctly?
Inspect addresses, nameservers, DNSSEC, email policies and DNS discovery records.
How are your pages delivered?
Check HTTPS redirects, caching, compression, browser headers and observable CDN signals.
How does your page perform?
Google measures mobile and desktop performance, accessibility, best practices, SEO and agentic browsing. Explore every returned Lighthouse audit.
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.
PageScanner, Ora and Google report separate scores with different scopes.
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.
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.
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.
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.