Fresh daily crosswords with AI-written clues at three difficulty tiers. Solve in your browser.
No blockers — but 3 fixes would strengthen the launch.
No pricing model declared (form field required for closed-source submissions)
Set pricing_model on the submission form. If TBD, declare 'free during beta' explicitly on the landing page.
Visitors need to know up front: free / freemium / paid / source-available. Hiding pricing creates trust friction.
Site appears to be JS-rendered (SPA) — static-HTML scanners and social previews can't see your content
Add server-side rendering (SSR), static site generation (SSG), or at minimum pre-rendered HTML for the head section (og tags, h1, hero copy). Frameworks: Next.js/Remix (SSR), Astro (SSG), or a custom prerender step.
Social-preview crawlers (Twitter, Slack, Discord, Mastodon, search engines without JS execution) only read the static HTML response. Your content lives in JS that they don't run. This kills link previews, hurts SEO, and makes the audit unable to verify your hero/copy.
No contact path found (no Issues, no email, no contact page)
Enable GitHub Issues, OR add a contact email on the landing page, OR a /contact page.
If a reviewer or first user wants to ask a question or report a bug, they need a way to reach you. No contact path = no follow-up.
No roadmap, changelog, or 'what's next' section found
Add a `## Roadmap` or `## Changelog` section to your README, even briefly.
Visitors evaluating a new project look for signals it will be maintained. A roadmap shows momentum; a changelog shows history; either reduces 'dead-on-arrival' anxiety.
Partial AI discoverability — has structured data (JSON-LD), missing llms.txt
Add a /llms.txt describing the project (llmstxt.org).
AI answer engines (ChatGPT, Perplexity, Google AI Overviews) and coding agents increasingly summarize and recommend tools to people who never visit your page. With no machine-readable description, they fall back to guessing from raw HTML — and are likelier to describe you vaguely or wrongly. Your robots.txt has no explicit AI-crawler policy — optional, but worth a deliberate decision.
Visitors will compare you to The New York Times Crossword, Spelling Bee (NYT), Crosswordle, Waffle (puzzle game) — your copy doesn't say how you differ
Add a short "how we're different" note (a sentence, or a small comparison) addressing: The New York Times Crossword, Spelling Bee (NYT), Crosswordle, Waffle (puzzle game).
Alternatives a visitor would weigh, and an angle for each: - The New York Times Crossword — AI-written clues with instant post-solve explanations vs. hand-crafted clues; free and always accessible vs. paywall-gated premium content - Spelling Bee (NYT) — Dedicated crossword focus with three explicit difficulty tiers and streaks vs. word-puzzle variant with single difficulty; AI-driven clue consistency vs. human editorial variation - Crosswordle — Traditional forward-solving with AI clue explanations vs. reverse-engineering variant; daily fresh puzzles with curated difficulty tiers vs. single dynamic puzzle type - Waffle (puzzle game) — Grid-based word puzzle with AI editorial pipeline vs. grid-based variant; focused on clue quality and explanation depth vs. primary emphasis on grid mechanics WordFuzz clearly claims AI clues and explanations as core features, but never explicitly names or contrasts itself against NYT Crossword, Crosswordle, or other daily puzzle incumbents.
Likely audience Daily crossword enthusiasts who want fresh puzzles with modern AI-written clues and enjoy tracking solving streaks and difficulty progression.
Core audience of active crossword solvers who regularly discuss puzzles, share solving tips, and try new daily puzzle sources.
How to show up Share a sample puzzle with a screenshot showing the difficulty tiers and post-solve explanations; ask for feedback on clue quality rather than promoting directly.
Technical audience interested in the engineering side (Rust constraint solver, AI editorial pipeline) and indie web projects with polish.
How to show up Lead with the technical architecture (solver, clue pipeline) and post-launch metrics; frame as 'built this daily puzzle generator' rather than a marketing push.
Audience actively seeking new indie projects and daily-use web apps; strong fit for a polished, launch-ready puzzle product.
How to show up Prepare a concise product launch post highlighting the daily streak mechanic and AI clue quality; include a live playable demo.
Broader gaming audience that includes casual puzzle game players and daily game enthusiasts.
How to show up Post as a casual 'I built a daily puzzle game' thread with a playable link; expect questions about gameplay loops and monetization.
Community dedicated to browser-based games and casual gaming experiences that fit the daily-play model.
How to show up Share as a new daily web puzzle with a direct link; include a brief note on how the difficulty tiers add replay value.
Strong technical and daily-game-player audience; lead with engineering story on HN and community-first approach on crossword forums, then expand to indie product platforms.
Suggestions, not gospel — confirm each community still fits and read its self-promotion rules. Lead with something useful; don't drop a link and run.