Live scanner methodology

One readiness score. Separate technical evidence.

Tracy uses one persisted scanner job for the headline four-pillar score and 14 live technical checks. Both describe the same scan, while their two scores remain visibly separate.

Canonical result

The score is returned by four readiness pillars.

Each result is stored by the scanner under a host and job ID so an exact public result link can be opened again.

01

Extraction

Can the scanner identify useful business facts and content from public pages?

02

Discovery

Can important business information and machine-readable entry points be found?

03

Agentic capability

Are supported customer paths and next actions clear enough to evaluate?

04

Bot accessibility

Can automated systems reach the public site and interpret its access signals?

14 supplemental tools

Technical evidence explains the site. It does not change the score.

Tools can pass, warn, fail, be skipped, or be unavailable. Their composite is a second technical view and is never blended with or substituted for the four-pillar result.

01

Access & transport

DNS and HTTPS, AI-relevant headers, and robots.txt policy.

02

Discovery

llms.txt, sitemaps, well-known files, API discovery, and feed freshness.

03

Business context

Structured data, local identity, pricing transparency, and social metadata.

04

Content quality

Page weight and whether public content is practical to quote and reuse.

How to interpret a result

The action plan orders failed and warning checkpoints by the points actually deducted by the service. It shows available points and returned remediation text, without guessing effort or promising a future score.

What the scanner does not measure

The result does not predict search ranking, AI citations, conversion, security, compliance, or whether a third-party model will be correct. It does not access credentials or submit forms.

Local controls

History and technical summaries stay on this device.

Tracy keeps at most 20 recent result references in browser storage for history and comparison. It does not store fetched page bodies or raw website content there.

Exact shared links restore the persisted four-pillar result and explanation. Live tool evidence, optional profile checks, and single-tool rechecks remain on the device that ran them.

Settings control advanced rechecks and the preferred evidence view. Website captures stay only in the active browser session, while the AI narrative is cached by the scanner service.

Public standards

Useful content and accessible public pages remain the foundation.

Run the scanner

See the readiness score and the evidence behind it.

Run a public-site scan