Request quality

Good Request Examples

Better issue inputs produce better previews and faster full teardowns. Use these examples to see the level of detail that helps most without posting confidential information.

What makes a strong request

  • One public landing page URL, not a multi-page review.
  • A plain explanation of what the page sells in one or two sentences.
  • The single main action the page should drive.
  • The audience segment that matters most right now.
  • The one weakness you want weighted most heavily in the review.

Keep it public-safe. Do not post private metrics, private URLs, revenue screenshots, or internal strategy notes in the GitHub issue.

Fast checklist before you open the issue

  • The page loads without login.
  • The page has one primary conversion goal.
  • You want text, structure, CTA, clarity, or trust feedback.
  • You do not need implementation work or outcome guarantees.
  • You are comfortable with public issue intake and an AI-assisted deliverable.
Example 1

Developer tool request

This is the level of detail that makes a preview useful without turning the issue into a long brief.

URL

https://example.devtool.com

What The Page Sells

A hosted API testing tool for backend teams that want faster regression checks before deploys.

Primary Goal

Start a free trial.

Intended Audience

Engineering leads and senior backend developers at small SaaS teams.

Main Constraint Or Concern

The hero feels too technical and I think visitors miss the practical payoff too fast.

Example 2

Service business request

URL

https://example-b2bservice.com

What The Page Sells

A done-for-you outbound appointment-setting service for B2B cybersecurity companies.

Primary Goal

Book a discovery call.

Intended Audience

Founders and growth leads at early-stage cybersecurity vendors.

Main Constraint Or Concern

The page sounds too broad and does not make the niche fit obvious enough near the top.