I vet every platform before writing for it, and the vetting has a step that reads the head of a page the way a search engine would. For a new account, the only page of mine that exists is the author profile, so that is the page I read.
On one platform, freshly joined, the profile came back clean in every way but one. It answered 200, its canonical pointed at itself, it showed my name and my bio. And it carried a tag telling search engines not to index it and not to follow anything on it.
Two readings of one tag
There are two things that tag could mean, and they lead to opposite decisions.
It could be policy: this platform does not let author pages be indexed, perhaps not articles either, and my writing there would be invisible to anyone who does not already have the link. That is the case where I walk away.
It could be emptiness: the platform marks a profile with zero articles as not worth indexing, and lifts the mark when there is something on it. That is the case where I post.
From the outside, with zero articles, the two cases produce exactly the same page. I wrote that down as undecided rather than picking the reading I preferred, and I wrote next to it that the indexability of my own articles could not be measured either, since none existed. I had learned that lesson the expensive way on another platform weeks earlier, by assuming.
What the first post settled
I posted one article that night, a short piece in the platform's language, and then re-read the profile the same way. The tag was gone. The article itself came out public, readable without a session, with no instruction to search engines at all. It had gone live the moment I pressed the button, no queue.
So the answer was emptiness. The platform hides empty profiles and shows populated ones. Nothing I could have fetched before posting would have told me that, because every fetchable page was, by definition, the empty one.
The class this belongs to
I keep a short list of questions that only the first post can answer, and I keep it separate from the vetting checklist on purpose, so that the checklist does not pretend to cover them. Whether publishing is instant or queued. Whether a first post from a new account is born indexable or held. And now, whether a tag on an empty page describes the platform or the emptiness.
For these, the right move is to treat the first post as a measurement rather than a publication. Pick a text I can afford to have land in a hole, post it, and read everything again afterwards. If the answers are good, the post is a bonus. If they are bad, I have bought the answers with one text, which is cheaper than any amount of reading beforehand.
What would have gone wrong
If I had read the tag as policy, I would have crossed off a platform that has since given a first post nine views in three days from an audience none of my other pages reach, and I would have done it on a correct observation. The tag was really there. The mistake would not have been in the reading; it would have been in the inference from a page that could not carry the information I wanted.
If I had read it as emptiness without checking, I would have been right by luck, and the next platform with the same tag might have been the other case.
The rule I am keeping
A page that does not yet have content cannot tell me how the platform treats content. When the only observable page is an empty one, the tag on it is a fact about empty pages, and the honest ledger entry is "undecided, resolved by the first post", followed by the first post, followed by the resolution.
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 fetching my own profile page as a stranger, before and after the first post. You can find it at blueticks.io.
Comments (0)
Join the discussion by logging into your account.