How we work

Four steps, run the same way on every website. The reason to read this page: it answers whether a partner is going to publish wrong prices about your product.

Process

From an unverified figure to a published page

  • Step oneFact lock

    Every number (pricing, plan limits, credits, feature caps) is locked to a verified facts file sourced from the vendor’s own documentation before writing starts. That file is the single source for every page in the cluster, so two of our pages cannot quote two different prices for the same plan.

  • Step twoIntent-mapped content

    Each URL targets exactly one search intent, decided before the outline exists. Pages therefore do not compete with each other, which is what keeps a cluster ranking instead of splitting its own signal.

  • Step threePublished with disclosure

    Affiliate links carry rel="sponsored nofollow" and open in a new tab. The disclosure sits above the first affiliate link, in plain language, visible without expanding anything.

  • Step fourMeasured and refreshed

    Tracked after publication and updated when the vendor changes pricing. A wrong price is treated as a defect, not a detail: it misleads a reader and it costs the program a sale it should have had.

Prices do not go stale here

If your pricing changes, our pages change. Stale prices on affiliate pages are a recurring problem for brand teams, and the brand carries the complaint, not the publisher. Tell us about a change at contact@arinet.io and the pages carrying that figure are corrected. We also re-check pricing on our own schedule rather than waiting to be told.

Editorial

What gets cut

The part of a verification process that matters is what it throws away. Four things that do not make it onto a page.

A figure with no primary source

If a number appears only in another publisher’s article, it does not go in. Secondhand pricing is how a stale figure survives for two years.

A claim the documentation does not support

“Unlimited” that turns out to be fair-use capped gets written as the cap, with the cap cited.

A test we did not run

We do not write “in our testing” unless there is a test behind it. Where there is no first-hand data, the page names its source instead.

A comparison we cannot verify on both sides

If one product’s figures are verifiable and the other’s are not, the comparison is cut rather than published half-sourced.

Who checks what before it publishes

AI drives research, drafting and on-page optimization. Verification and the decision to publish are not. Every page is read by a person against the facts file before it goes live, and that person is accountable for the numbers in it.

Automation is how a focused team publishes at scale and refreshes a page the day a price changes. Human review is why those pages can be trusted. A partner program gets both: the speed of AI and an accountable check before anything is published.

The same standard governs corrections. A brand team that finds an error can write to contact@arinet.io and we act on it within 48 hours, as set out in our compliance policy.

See it on the pages themselves

The Media Kit has the website URLs, so you can read the output of this process rather than take our description of it. Sent within one business day, under NDA if you prefer.