Focused sample deliverable

See the evidence.
Keep the paid fix valuable.

This fictional sample shows the structure and decision discipline of a Digital Dominator AI Access Audit. It demonstrates how declared policy, observed DD access and assessment limits remain separate. The complete 21-identity matrix, exact configuration changes and implementation instructions are deliberately withheld.

Run my AI Access CheckView pricing
DIGITAL DOMINATOR · HUMAN-REVIEWED TECHNICAL REPORT

AI Access Audit

How crawler policy and access infrastructure affect retrieval of your website

Prepared forExample Property Group (fictional)
Audited targethttps://example-property.test
Assessment scopeOrigin root (/)
PanelDD-AI-CRAWLERS-v1.0 · 21 identities
Evidence classesDeclared policy + observed DD access
Review statusHuman QA complete
Illustrative public sample. The organisation, domain and evidence below are fictional. The layout represents the focused access product, not a visibility score or competitor audit.
Executive finding

Declared policy and observed access disagree

The origin-root robots policy permits some discovery identities and disallows others. Separately, Digital Dominator’s identified audit crawler received an edge challenge. The report does not attribute that response to OpenAI, Anthropic, Perplexity or any other provider.

Declared policy

SELECTIVE

12 identities DISALLOWED; 9 ALLOWED at path /.

Observed DD access

CHALLENGE OBSERVED

The exact requested URL, final URL, status and retained response signals are recorded separately.

Scope and limits

What this Tier 1 result does—and does not—say

Robots.txt was retrieved from the origin and its rules were evaluated against the root path (/). If a subpath was submitted, it is retained as provenance only; the submitted page was not fetched or assessed.

This audit establishes declared policy for the frozen panel and the response received by our own identified crawler. Access is a prerequisite for retrieval and citation, not a guarantee. Where evidence cannot establish a state, the report says COULD_NOT_ASSESS rather than converting uncertainty into a clean result.

Representative matrix

Selected identities from the 21-identity panel

IdentityPurposeState at /Basis
OAI-SearchBotSearch/discoveryALLOWEDApplicable group permits root
GPTBotTraining-associatedDISALLOWEDMatched Disallow directive
Claude-SearchBotSearch/discoveryDISALLOWEDMatched Disallow directive
Claude-UserUser-triggeredALLOWEDApplicable group permits root
Google-ExtendedData-use controlDISALLOWEDControl directive; not an HTTP crawler
ApplebotSearch/discoveryALLOWEDApplicable group permits root

Six representative rows shown. A paid report includes all 21 identities, their classifications, evaluated path and retained evidence basis.

Retained evidence

Every finding points back to an observation

Requested: https://example-property.test/ Final URL: https://example-property.test/ Declared policy path: / Observed DD result: challenge response Assessment: declared rules readable; live DD retrieval restricted Attribution limit: no claim about a named vendor crawler
Prioritised action

One problem, made straightforward for a developer

Priority 1 — reconcile intended discovery access with policy and edge enforcement

Why it matters: selected search/discovery identities are declared disallowed, while the separate DD observation shows an infrastructure challenge. These are different controls and require different checks.

Owner: website developer or infrastructure administrator.

Paid-report boundary: the exact robots directives, affected evidence lines, edge rule checks, validation commands and re-test procedure are intentionally omitted from this public sample.
Human QA

Automation gathers evidence; a person signs off the report

Before delivery, a human reviewer checks target attribution, scope, state vocabulary, evidence links, contradictions and overclaims. Confirmed findings remain distinct from assessment limits. Paid reports are delivered within five business days.