lans.cloud is a collection of ~65 free, single-purpose web tools — a classroom timer, a random name picker, a granny-square calculator, a Dragon Ball power-level generator. The domain is only a few months old, which means most of the growth work is unglamorous: rank for specific long-tail queries, and get listed on the directories where our audience actually browses.
So we submitted the site to AlternativeTo, the big "find an alternative to X" catalog. A day later, two messages came back:
Your app Lans Cloud - Free Tools was declined by our automated review system. This decision may be reverted after manual review. You cannot reply to this message.
Sorry, Lans Cloud - Free Tools can't be approved because it doesn't meet the quality and benefits we require at AlternativeTo for software, applications and online services.
Generic, final, no reply channel. The kind of email that's easy to either rage at or ignore. Both would have been mistakes.
The rejection was correct
Before assuming a platform is wrong, I read its rules. AlternativeTo's FAQ has a section on why submissions get declined, and it's blunt about what it doesn't want:
Basic AI tools, simple converters, calculators, resizers… Collections of online tools, AI wrappers for LLMs.
Read that middle phrase again. "Collections of online tools." That is a precise, unflattering description of what we submitted: a homepage that links to 65 tools. The automated filter didn't misfire — it did exactly its job. We handed a catalog to a service that explicitly rejects catalogs.
That reframes everything. This isn't a quality bug I can patch on the homepage. There is no headline I can rewrite, no screenshot I can swap, that turns a collection into "not a collection." And the "may be reverted after manual review" line? It fires automatically, there's no way to make a case (no reply channel), and a human looking at the homepage sees the same collection the bot did. The odds of a reversal are low, and there's nothing I can do to improve them. Chasing it would be motion, not progress.
We'd seen this exact wall before, from a different directory (Uneed), which rejected us as an "online tool collection" too. Two independent gatekeepers drawing the same line is a signal, not a coincidence.
Two paths out of the same wall
Here's the thing I almost missed: AlternativeTo has two ways to get listed, and they're judged completely differently.
- List your whole site as an app. This is what we did, and what got rejected. It screens out collections wholesale.
- Add your product as an "alternative" on a specific competitor's page. This accepts single-purpose apps.
Our actual value on AlternativeTo was never the umbrella listing anyway — it was the second path. Our spin-the-wheel is a legitimate, focused alternative to Wheel of Names. Our classroom timer is a real alternative to Online-Stopwatch. Our classroom screen is a direct alternative to Classroomscreen.
The fix wasn't to argue with the rejection — it was to stop submitting the collection and start submitting the individual tools, each pointed at its own deep URL (lans.cloud/spin-the-wheel, not lans.cloud). Each one presents as a single-purpose app, which is the shape the platform rewards. Same site, different unit of submission, opposite outcome.
The same lesson, an hour later
What makes this a good story rather than just a support ticket is that the identical decision came up again the same afternoon — from the product side, completely unprompted by the rejection.
We had a new tool idea: a scratch pad. A place where a teacher (or anyone) can free-write and draw. The obvious move is to build it as a new page — lans.cloud/online-scratch-pad or similar — and rank for it.
But lans.cloud runs on a strict doctrine: we only target specific long-tail queries a young domain can realistically win, and we never chase head terms. "Online notepad," "scratch pad," "online whiteboard" are head terms owned by decade-old exact-match domains. So before writing a line of code, I ran the keyword vet: brainstorm the candidate queries, then look at who actually ranks for each.
The results were unanimous and a little grim:
- "type and draw whiteboard for teaching" → owned by OnlineWhiteboard.org, which even runs a dedicated
/online-whiteboard-for-teachers/sub-page marketing the exact "fullscreen on smartboards, no login" angle we'd chase. They got there first, with an exact-match domain. - "digital scratch paper for students" → owned top-to-bottom by ClassPad (a Casio property) and established education blogs.
- "online notepad no login," "temporary scratch pad no account" → a dense carpet of exact-match domains (notepadly, usethisnotepad, online-notepad.io, and a dozen more).
Every candidate was either a head term, a hardware-intent SERP, or already staked by a domain built precisely for that phrase. And the tighter I made the qualifier to find open space, the more the actual search volume drained away. There was no "specific but real" sweet spot to lead a title with.
Verdict: widget, not page. A standalone scratch-pad page would chase a keyword it can't win and overlap our existing classroom cluster. So the scratch pad shipped as a freehand Sketch pad widget inside the classroom screen — one more tile on a board that already ranks — rather than a lonely page fighting OnlineWhiteboard.org for scraps.
(For the curious: the strokes are stored as normalized 0–1 vector coordinates rather than a canvas PNG, so a drawing is tiny in localStorage and scales crisply from a small grid tile to a fullscreen smartboard. The persistence layer sanitizes unknown data on load, so it's forward- and backward-compatible without any version field. But that's a different post.)
Why the widget was strictly better
The neat part is that building the widget didn't just avoid the standalone-page mistake — it paid off twice.
Classroomscreen — the competitor we're submitting our classroom screen against on AlternativeTo — has draw-and-annotate as one of its signature widgets. By adding a sketch pad to our board, we made the "alternative to Classroomscreen" claim more true on the exact day we were pursuing that listing. The doctrine-driven "don't build the page" decision and the "get listed on the competitor's page" decision reinforced each other. We didn't plan that. The discipline just tends to point the same direction.
The takeaway
Both halves of the day were the same lesson wearing two costumes:
- Directory: don't submit the shape you have (a collection); submit the shape the platform rewards (single-purpose apps).
- Product: don't build the shape you want (a standalone page); build the shape you can actually win with (a widget in a ranking cluster).
When a gatekeeper — Google's SERP or a directory's filter — tells you no, the useful response is rarely "argue" or "quit." It's "what shape were they actually asking for?" A rejection is often just a very blunt spec.
The umbrella listing is dead. The per-tool submissions are in review. And the tool we didn't build as a page is live as a widget, quietly making a competitor comparison more honest. That's a good afternoon.
Update — 15 July 2026: the suspicion held. The day after I submitted our classroom screen as an alternative on Classroomscreen's page — one focused tool at its deep URL, not the whole collection — AlternativeTo approved it. Same site, same platform, opposite verdict, decided entirely by what unit I submitted. The rejection really was a spec, not a wall. Next up: the same move for the other competitor pages, one a day.