# Sample Workflow Receipt — Website Readiness Audit

**Example status:** Public sample. Not a customer claim.
**Tool:** Ori8 Website Readiness Audit actor on Apify
**Mode:** Read-only public website review

## Business problem

A small business owner wants to know whether their website clearly explains what they offer, gives prospects a usable contact path, and exposes obvious trust or technical gaps before investing in advertising or a redesign.

## Input

- Public website URL supplied by the owner
- No login credentials
- No private analytics
- No customer records

## Allowed actions

- Fetch public pages
- Review visible copy and page structure
- Identify likely conversion, trust, SEO, and technical-verification issues
- Produce an owner-readable Markdown-style report

## Not allowed

- No website edits
- No DNS, hosting, analytics, or Search Console changes
- No form submissions using real leads
- No private/admin crawling
- No security testing beyond passive public checks

## Human gate

A person reviews the report before treating findings as final. Any implementation, admin access, or production change requires a separate written scope.

## Evidence produced

- Findings grouped by priority
- Page/title/contact/trust observations
- Known limits and required verification tasks
- Recommended next actions

## Known limits

- Public-page review only
- Search-indexing and analytics claims require account access
- Privacy/legal/security conclusions require a scoped review
- Automated output can miss visual, mobile, accessibility, and business-context details

## Decision receipt

```text
input: public URL only
risk: low / read-only
production changes: none
private data: not requested
recommended next step: review findings with owner, choose one bounded fix or paid audit scope
```