Questner: Growth signals and a five-step replication plan

1. What this site is

Questner (questner.ai) is a games-and-interactive-storytelling candidate described publicly as an AI dungeon escape game with interactive storytelling. This report uses only public T0 evidence.

Discovery evidence: Toolify's July 2026 monthly chart, rank 144, with chart growth 1.0467; listing page. The chart was read in a browser at 2026-08-12T10:18:30.072Z. Chart fields only place the site in the candidate pool; they do not prove traffic or revenue.

2. Evidence timeline

Registration point: RDAP records 2026-01-12. Registration is not a launch date; unavailable values remain missing.
Rank point: Tranco returned 449,290 on 2026-08-11. This is a popularity proxy, not visits.
Structure point: the homepage returned HTTP 200; the sitemap exposed 93 URLs; a pricing page was found.
Historical range: one archived month and one distinct content digest were observed. A digest change does not independently prove a redesign.
- 2026-01-31: first archived point, Wayback CDX, high confidence.
- Source: Wayback CDX, collected 2026-08-12T11:25:57+00:00. The wildcard fallback query is retained in the snapshot.
Authority point: OpenPageRank returned 0.37 / 10 and global rank 70,037,355. This is a Common Crawl authority proxy, not traffic.

Questner shows brand-led, content-hub, and subscription signals. They make it worth observing, while the next pass should remain limited to pages, pricing, and Tranco.

3. Playbook breakdown

Site type: brand-led, heuristic and low confidence. Begin with one complete interactive story loop.
SEO direction: content hub, heuristic and low confidence. The 93 discoverable URLs do not prove organic traffic.
Monetization: subscription/plans. No public amount was captured, so do not estimate ARPU.
Technical clues: React, Vercel, and Google Tag Manager; one language. These are low-confidence fingerprints.

4. Five actions to test

Break down the H1, input, output, and CTA on the current Questner homepage, then reproduce one complete interaction loop.
The sitemap contains two blog pages. Start with one page modeled on /about, validate its role, and only then expand.
Use /pricing as the monetization baseline. The captured label is subscription; without amounts, do not infer ARPU or MRR.
Test only the “brand-led + content hub” path, cross-checking the homepage, sitemap, and pricing page.
Use the first Wayback point and this snapshot as the baseline. Next time, compare page categories, pricing entry, and Tranco; keep unavailable fields as missing.

5. Data boundary