Notifio has fifteen pages about other companies' alert features and five pages comparing itself to direct rivals. That is thirty-ish screens of writing about products I do not own, published on a site that wants you to buy mine.
The lazy version of this page writes itself: their alerts are slow, ours are fast, here is a button. We do not write that, and the reason is not politeness. It is that the lazy claim is the one a reader can disprove in ten seconds, and a page that loses an argument in its first paragraph does not get a chance to make the true one.
So our page about Rightmove alerts opens by telling you to go and change Rightmove's settings:
Credit where it is due: Rightmove lets you set Property Alerts to instantly, daily, every 3 days or every 7 days, and if you have them on daily you should change that today. The instant setting is the right one and it costs nothing.
That is on a page whose job is to sell a competing product. Here is why it is there, and the two type definitions that keep it there.
The doctrine is written at the top of the file holding the UK portal pages, and the last sentence of it is the rule:
That distinction is what these four pages are about, and it is why none of them claims the portals are slow.
"Slow" is a bad claim for us for three separate reasons. It is unfalsifiable in the direction that matters, since any individual reader's last alert probably did arrive quickly. It ages badly, because a company can fix a latency problem in a sprint and then your page is wrong. And it is a claim about someone else's infrastructure made by someone with no access to it.
The claim that survives all three tests is structural. A portal alert is an announcement about an event, and the events are specific: a property being published, or a price being reduced by 2% or more. It is not a view of your search. So anything that changes a property's eligibility after publication reaches you only if the portal decides to re-announce it. A let falls through. An agent takes a property down and puts it back. A price drops by one percent and lands inside your filter.
That claim is checkable, it is about design rather than performance, and it does not get fixed by a faster mail server. It is also, usefully, the actual product difference: comparing a search results page against its previous state every thirty seconds has no concept of "newsworthy", so it catches all of those.
What the page does say about timing is a count of the things between the decision and the inbox, which is the subject of Count the hops: why "instant" notifications are never instant. "Instant" names the moment the portal decides you should hear about a property. It does not name the moment you can read it, and the gap contains a matcher working out whose saved searches match, a bulk mailer sending the same announcement to everybody on that list, and a send queue emptying at its own pace. None of that is a criticism of the portal. Every alert eventually arriving is a perfectly good target. It is just a different target from your alert arriving first.
Every one of those pages is a typed object, and the section that describes a third party's behaviour cannot be constructed without its receipts:
sources: Source[] with no ?. You cannot add a page that describes a competitor's alerts without going and finding the help-centre article that says so. In practice that constraint did most of the editing: a few things I believed about these products turned out to have no citable basis, and they are not on the pages.
And the citation is not a footnote nobody renders. The template prints it with a lead-in that is close to an invitation to catch us out:
"so you can check whether X has changed this since we wrote it" is doing two jobs. For the reader it is a statement that the claim has a shelf life and we know it. For me it is a standing admission that these pages are a maintenance liability, written into the page rather than into a ticket I would not read.
The head-to-head pages have a second type, and one optional field on it carries most of the credibility:
Three possible values, and the only one that earns anything is "them". A comparison table with a tick in every row on one side is not read as information. It is read as an advertisement, by a reader who then stops believing the rows they could not check either.
It runs in the cloud, and that is not a small thing. Rentbird's bots do not care whether your laptop is shut, out of battery, or in a bag on a train. Notifio only monitors while the machine it is installed on is awake and online, so if you do not have a desktop or a laptop you are willing to leave running, Rentbird will catch listings that Notifio sleeps through. That is the single most important difference between the two products and it is the one we lose.