# ClawdPub SOP

ClawdPub = Clawdbot Publishing — iterative workflows for client/public websites, sales pages, ebooks, and other publishable artifacts.

## Design and Iteration Guidelines

This guideline is intended to keep iteration objective. It captures the intentions and questions a:
- professional **designer**
- professional **content writer**
- real **website visitor**

…would bring to a page.

### How to use (the loop)
1) Pick the page + the single conversion goal.
2) Answer the questions below with a **1–5 rating**.
3) Fix the lowest-scoring items first (highest leverage).
4) Publish a new version with a short changelog.

### Rating rubric (use consistently)
- **1 = Broken / confusing / missing**
- **2 = Weak / unclear / incomplete**
- **3 = Adequate / understandable**
- **4 = Strong / clear / credible**
- **5 = Excellent / effortless / persuasive**

---

## A) Professional Designer Intentions (and scored questions)

### A1. First impression & clarity (5-second test)
1. **Can a first-time visitor tell what this is within 5 seconds?** (1–5)
2. **Can they tell who it’s for (persona) within 5 seconds?** (1–5)
3. **Is the primary action visually dominant (one obvious CTA)?** (1–5)
4. **Is there a clear information hierarchy (H1 → supporting copy → proof → CTA)?** (1–5)
5. **Is above-the-fold content scannable (no walls of text; good spacing)?** (1–5)

### A2. Layout, navigation, and wayfinding
6. **Is the page structured to match user scanning patterns (F/Z patterns)?** (1–5)
7. **Are section headings descriptive enough to guide skimming?** (1–5)
8. **Is navigation minimal and aligned to the conversion goal (no distracting detours)?** (1–5)
9. **Does the page provide a clear “safe harbor” (home / top / consistent brand anchor)?** (1–5)

### A3. Visual system & accessibility
10. **Is the brand system consistent (type, spacing, colors, components)?** (1–5)
11. **Is contrast sufficient for text and controls (AA-ish)?** (1–5)
12. **Is the page usable on mobile (no tiny tap targets; no broken layouts)?** (1–5)
13. **Are interactive elements obviously interactive (buttons look like buttons)?** (1–5)
14. **Are states clear (hover/focus/disabled/loading)?** (1–5)

### A4. Trust & risk reduction (design signals)
15. **Does the page look legitimate (not like a template scam page)?** (1–5)
16. **Are security/privacy expectations signaled appropriately (especially for admin tools)?** (1–5)
17. **Are external links safe-looking (consistent, no sketchy redirects)?** (1–5)

### A5. Performance & technical experience
18. **Does it load fast enough to feel instant?** (1–5)
19. **Is the page resilient (no layout shift; stable elements during load)?** (1–5)

---

## B) Professional Content Writer Intentions (and scored questions)

### B1. Audience, goal, and positioning
1. **Is the single conversion goal explicit (what do we want them to do)?** (1–5)
2. **Is the primary persona explicit (who is this page written for)?** (1–5)
3. **Is the value proposition concrete (outcome + for whom + why now)?** (1–5)
4. **Is the differentiation clear vs alternatives (“do nothing”, “build your own”, competitors)?** (1–5)

### B2. Message structure (AIDA / Rule of One)
5. **Headline: does it say something real (not vibe-only)?** (1–5)
6. **Subhead: does it explain how/why and remove ambiguity?** (1–5)
7. **Body copy: is it scannable with short paragraphs + subheads?** (1–5)
8. **CTA copy: does the button text match the user’s intent?** (1–5)

### B3. Proof and credibility
9. **Do we show proof (screenshots, demo, metrics, testimonials, logos) instead of claims?** (1–5)
10. **Are claims specific and verifiable (avoid empty superlatives)?** (1–5)
11. **Is pricing framed fairly (what’s free, what’s paid, what happens after trial)?** (1–5)

### B4. Objections (explicitly addressed)
12. **Does the page answer “Is it safe?” for an operator console?** (1–5)
13. **Does it answer “How hard is setup?” with steps/time?** (1–5)
14. **Does it answer “What happens if I stop paying?” clearly?** (1–5)
15. **Does it answer “What data is sent / stored?”** (1–5)

### B5. Language & tone
16. **Does it sound like a real product, not generic AI text?** (1–5)
17. **Does it use visitor language (VoC) more than internal jargon?** (1–5)
18. **Is jargon introduced only after clarity (define terms like DEL, Moltbot, etc.)?** (1–5)

---

## C) Website Visitor Intentions (and scored questions)

### C1. Visitor reality (they are busy)
1. **Can I tell what this is without knowing your ecosystem?** (1–5)
2. **Can I tell if it fits my situation in under 30 seconds?** (1–5)
3. **Do I know what to do next (one obvious next step)?** (1–5)

### C2. Risk & trust
4. **Do I trust this with credentials / channels / automation?** (1–5)
5. **Do I understand what’s local vs hosted?** (1–5)
6. **Do I know what data leaves my machine?** (1–5)

### C3. Fit & payoff
7. **Do I understand the main benefits (time saved / errors reduced / visibility gained)?** (1–5)
8. **Can I see the product (screenshots/demo) before I commit?** (1–5)
9. **Is the pricing “worth it” relative to the pain?** (1–5)

### C4. Friction
10. **Is “Get started” actionable right now (not a dead button)?** (1–5)
11. **If I self-host: is it clear how long it takes + what I need?** (1–5)
12. **If I want hosted: is there a simple path (waitlist) that sets expectations?** (1–5)

---

## Appendix: Suggested evaluation artifacts
- 5-second test notes (3 people if possible)
- Before/after changelog per version
- Screenshot diff (hero + pricing + CTA sections)
- Top objections observed in DMs/support

## Sources / inspiration (high-signal)
- Nielsen Norman Group: Homepage design principles + usability guidelines
- Landing page copy frameworks: AIDA + Rule of One (common CRO practice)