Private beta · Adaptive SEO and GEO

A scan that knows what it can prove.

YAST confirms the job, site and coverage first, then runs an exact Page scan or a durable Site/Scale sample. Business-impact claims remain gated until first-party evidence is connected.

Context before crawlCoverage before claimsUnknown stays unknown
Start a private scanExplore audit examples
Private beta · controlled scan

Build the scan brief

Choose explicitly. YAST will not guess from the URL, size or platform.

1/3
Scope
Audit job
Context

Nothing is fetched, saved or published.

How much of the site should this audit cover?

Choose the claim boundary, not a page-count guess. You can keep it undecided.

No crawlPrivate by defaultNo published report

Adaptive scope

The site and audit job shape the scanner.

Evidence ledger

Every claim points back to inspected evidence.

Private by default

Reports are protected and noindex unless changed deliberately.

Adaptive protocol

Same engine. Not the same audit.

Scope controls breadth. The audit job, site model and available evidence change what the protocol must inspect and what it may conclude.

Choose an example to see the contract change.

Protocol examples

Page opportunity

Landing page

Example · not executable

One exact page, judged against a confirmed audience, offer and action.

Audit job
Improve one conversion page
Coverage
Page · exact URL only
Site model
Landing · page role confirmed
Status
Inputs required before execution

Evidence still needed

  • Audience and offer
  • Primary conversion action
  • Market and language

Proposed focus

Not activated
Source + rendered factsIntent evidenceIndexability inputs

Claim boundary

URL-level evidence only. No sitewide, ranking or conversion claim.

Evidence model

Evidence earns the conclusion.

YAST is designed to show what was inspected, what remains unknown and why an action is allowed. A clean score is not the product.

  1. 01ProfileSeparate observed, confirmed and unknown.
  2. 02CoverageRecord inspected URLs, templates and exclusions.
  3. 03ReceiptsShow which scanners actually executed.
  4. 04DecisionPrioritize only what policy and evidence allow.

Coverage modes

Breadth changes the evidence.

Coverage controls what gets inspected and how far a conclusion may travel. URL thresholds remain product hypotheses.

Page

One exact URL

Page facts only. No sitewide claims from a single document.

Site

Proposed: 10-250 URLs

Lightweight source SEO checks across the confirmed inventory, plus a deeper owner-confirmed structural sample.

Scale

Proposed: 251-2,000 URLs

Inventory-wide technical source checks, then a budgeted deep sample with explicit failures, exclusions and claim limits.

Unsupported

Escalate, do not guess

Authenticated, high-risk or unclear sites stay blocked until the contract is safe.

Product readiness

Three bounded scopes. Honest boundaries.

The private beta executes exact Page scans and durable Site or Scale audits with lightweight inventory-wide source checks plus a confirmed deep sample. Every result keeps its failures, exclusions and claim depth visible.

Private beta · Page, Site and Scale runtime available

Executable today

Available in the private beta

  • Live exact-Page scan

    Fetch one public page and discovery files through the safe network boundary, then compare six critical source/rendered signals in controlled Chromium.

  • Durable Site and Scale scans

    Confirm coverage, retain lightweight technical SEO evidence across the selected inventory, deeply audit an owner-confirmed structural sample, resume bounded work and recheck exact population drift.

  • Evidence-first report

    Inspect public observations plus bounded Page and Site/Scale Indexing, Search Console, analytics, SERP, authority, AI citation and field p75 evidence—without a synthetic score.

  • Private report boundary

    Raw remote documents are not retained. Reports are owner-bound, noindex, expiring, deletable and recoverable after email verification.

  • Verified access + entitlements

    Single-use magic links bind browser sessions to a protected email identity; Site and Scale authorization is checked by the server.

Next product milestone

Turn the accepted private beta into a self-serve service.

PostgreSQL, distributed Redis controls, Vercel Queue, retention cron, private reports, verified recovery, manual server entitlements, bounded Page/Site/Scale evidence imports and owner-bound rechecks passed implementation acceptance. Public release still needs operational ownership, a YAST sending domain, automated billing if self-serve and automated evidence synchronization where manual imports are not enough.

Monitoring + incident ownershipYAST sender domainAutomated billing + webhooksAutomated first-party evidence sync