How to cite a pricing page when the limits keep changing

When a pricing page keeps changing, cite the current link plus the exact field, check date, and decision that depends on it.

A SaaS pricing page can change seat limits, storage caps, API quotas, trial rules, currency, tax wording, and discount eligibility without creating a new URL. If a team only saves the link, the later reader cannot tell whether the old decision was based on the same plan table they see today. That becomes risky in procurement notes, migration comparisons, renewal checklists, and public tool roundups.

A reusable citation should include four pieces: the page URL, the field quoted, the date checked, and the action affected. For example: “Pro plan API limit, checked 2026-06-24, used for migration estimate.” If the value is central to the decision, quote a short phrase or number and keep a screenshot privately where policy allows. Do not publish private account screenshots or invoices just to prove a public price.

Separate stable and volatile parts. The plan name may stay stable while the usage cap changes. The feature description may be stable while annual billing terms change. Write the note so the next reader knows which part needs rechecking. “Link current, limits volatile” is better than treating the whole page as equally reliable.

If two pricing pages disagree, prefer the source closest to purchase: checkout, official pricing table, contract, or account billing page. Public comparisons and blog posts can help find context, but they should not override the primary page. The final note should say which source won and why.

The test is whether someone can reopen the note during renewal season and know exactly which number must be verified before money is committed.

How to cite a pricing page when the limits keep changing

// COMMENTS

ON THIS PAGE