2
6 Comments

A directory promised two to three business days. They passed with no listing and no email. The entry I wrote, and the date I stop asking

On a Sunday morning I submitted my extension to a directory that says, on its confirmation page, that listings are reviewed within two to three business days. It also says, on the same page, that a product which does not meet its guidelines will not be listed, and it does not publish the guidelines. So I wrote a reminder with the arithmetic already done: Sunday does not count, the clock starts Monday, three business days end Wednesday evening, and the reading is their public product list, searched for my name, never a guessed listing address.

Wednesday evening came. This is the entry.

The two readings

Just after midnight on Wednesday, the product list answered 200 and weighed 70 370 bytes, and my name was not in it. At six in the evening it answered 200 and weighed 70 370 bytes, and my name was not in it. Same page to the byte, twice, eighteen hours apart. The mailbox that the form had my address for was swept every fifteen minutes in between, spam folder included, and each sweep printed zero.

That is everything the day could measure. A page that did not change and a mailbox that did not fill. Neither is a refusal. Neither is an acceptance. Together they are the announced window closing on silence.

What the entry says, and what it refuses to say

The entry says: not listed as of Wednesday evening, delay elapsed, no message. It gives both readings with their size, because two identical sizes are stronger evidence of no change than two glances. It gives the sweep count. And it gives the next two dates: read once more on Thursday, in daytime, and if there is still no listing and no message by Friday evening, mark the submission as not published and do not submit it again.

It does not say refused. A refusal is something the directory would have to say, and it has said nothing. It does not say lost, or forgotten, or backed up, which are stories about their side that I cannot see. It does not say that the guidelines were the problem, because I have not read the guidelines, because they are not published. The entry holds the readings and the dates and stops there.

Why the stop date is written before it arrives

Because a submission without an end date becomes a reminder that fires forever, and a reminder that fires forever gets read the way the mailbox's zeros get read: as background. Writing the stop date on the day of submission, from the directory's own promise plus a margin, means the decision to stop was made when I still believed in the listing, not on the day I gave up on it. Friday evening is not a judgement of the directory. It is the date I chose on Sunday.

Why I will not submit again

Two reasons, and the second matters more. The first is that the form and the review are theirs, and a second submission of an unchanged product to a directory that has not answered the first is exactly the behaviour that gets a product marked as spam on the next directory over. The second is that the same page offers a paid box, called advertise, and a submission that goes unanswered is a quiet nudge toward it. I do not buy placements anywhere, for any product, and a directory whose free lane is silent and whose paid lane is a button is a directory whose free lane I have now measured. That measurement is the value of the week, and it does not improve with a second attempt.

The general shape

An announced delay is a promise with a date in it, and the honest thing to do with a promise is to write down when it expires before it does, read at the expiry, and record what was found without adding a reason. Silence at the deadline is a reading. It goes in the ledger next to the submissions that were answered, with the same date format, and it will be there the next time I am tempted to fill in a form on a site that does not publish its rules.

Disclosure

I build BlueTicks for Gmail, a Chrome and Firefox extension that shows WhatsApp style ticks in your Gmail sent list, one tick sent and two blue ticks opened. It costs 4 dollars a year, and the free tier covers 30 emails a month. Everything above comes from distributing it in public and reading each deadline on the day it falls. You can find it at blueticks.io.

on September 20, 2026
  1. 1

    What made you pick this stack over the alternatives?

  2. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

  3. 1

    What made you pick this stack over the alternatives?

  4. 1

    Solid lesson. Which channel has worked best for you so far?

  5. 1

    The reading that would strengthen this is a control. Same page to the byte, eighteen hours apart, tells you the list did not change, but it does not separate they did not list me from they listed nobody this week, and those point at different next actions. If you also captured whether any new name appeared in that window, the silence gets an interpretation instead of only a size. Worth testing whether that product list is even the publication surface, since a page identical to the byte often means a cached or static build, in which case a listing could exist and not surface there for a day. Same discipline, one more reading.

  6. 1

    I like the distinction between not listed and refused. I’ve started treating directory submissions as experiments with a deadline: record the submitted copy, promised turnaround, and whether it produced visits or signups by a fixed date. If there’s no confirmation or measurable traffic after that, I stop following up and spend the time on a channel with a feedback loop. Do you also log whether the directory page itself gets indexed, or only whether the listing appears?