Before you share your prediction market site in a newsletter, community, or social post, open it as a first-time visitor. Ask: Can I tell whose site this is, find a relevant market, and know where to go next?
This is a final review of the visitor experience. For a full installation walkthrough, use the Kuest owner guide. You can make this review with a focused shared catalog; creating a market is optional.
1. Complete the site setup before judging the page
The guided Kuest launch flow moves through Site + Admin wallet, Connections, and Deploy. It asks for a site name, valid contact email, and admin-wallet signature. Before deployment, you connect a GitHub repository, Vercel, Reown, and Supabase. Follow the owner guide for the setup details.
After deployment, open the resulting URL. A custom domain is optional; add whichever domain you use to your Reown project’s allowed domains in the final setup step. Then sign in with the admin wallet and check that the Admin area is accessible.
Operator check: Write down the public URL you intend to share. If the page, wallet connection, or admin access fails there, pause distribution and fix that path first.
2. Make the first screen answer three questions
Whose site is this? In Admin, set the public name and logo, then inspect the page outside Admin. The brand settings also allow a short description. A visitor arriving from your channel should recognize the same identity on the site.
What should I explore first? Choose a small set of markets that fits the audience you are inviting. The Admin controls allow featured-market selection, while Categories controls which categories appear in discovery. Open the actual market pages and check titles, status, rules, and the path back.
Where do I go next? Check the links to your community and support destination. If a visitor arrives from a specific story or discussion, send them to a relevant market page when possible, then give them a clear way to return to your channel. The destination should feel connected to the conversation that brought them there.
3. Use the Admin checklist as a prompt, not a certificate
The current Admin onboarding widget lists five tasks: site name and logo; wallet to receive fees; OpenRouter for AI; translations; and custom endpoints (optional). It is a useful reminder, but the checkboxes can also be marked manually. A completed widget is not proof that the visitor path works.
Review each item against your plan. Confirm your fee-recipient wallet. Configure translations for languages you intend to serve, and read the result on the public site. Connect OpenRouter if you intend to use AI features. Custom endpoints are optional. Separately, review your terms, access settings, and support path for the audience you plan to invite.
4. Run one real first-visit test
Use a phone or narrow browser window and follow the same path a visitor will follow:
- Open the exact URL from your planned post or message. Check the name, logo, description, and first visible markets.
- Choose one relevant market. Check that its page loads, the question and rules are understandable, and the market’s current state matches what you plan to say about it.
- Follow the community or support link and return. If a wallet step is part of your invitation, test the connection on the intended domain without placing a trade.
Have someone unfamiliar with the setup repeat the path. Ask where they hesitated. That is more useful than counting how many configuration boxes are checked.
Site readiness is not audience activity
Passing this checklist means a visitor can understand and navigate the destination you prepared. It does not prove traffic, trading activity, fee revenue, or liquidity in every market. Start with the audience and channels you already have. Watch the signals you can actually observe, such as return visits and which markets people explore, then adjust the first-screen selection.
Want to see the current public experience before reviewing your own? Explore the Kuest demo.