Content update policy

eSIM information ages quickly: prices, OS menus and supported handsets all move. We therefore review each content type when its own kind of source changes.

This table sums up who answers for each content type, what it is checked against, and what triggers a review. Every article is written by one of our two co-founders and reviewed by the other.

When we retire a page

• The plan is discontinued with no replacement.
• The content is merged into a more complete page.
• The page is too outdated to fix, in which case we redirect to the closest useful page.

Why content ages at different speeds

eSIM information does not age uniformly. Plan prices can move week to week as providers adjust them, while an explanation of what eSIM actually is barely changes across several years. Setting one review cycle for every page would not make sense: fast-moving pages would go stale while waiting their turn, and slow-moving pages would be reviewed far more often than they need.

So rather than one fixed schedule, we review a page when its primary source changes, when a reader reports a problem, or when we notice something no longer matches. A brand-new page and an older one in the same category follow the same rule.

Prices and plans: the fastest-moving content

Plan prices on a product page come from the supplier catalogue, because price is the figure that most directly affects a buying decision and it moves most often. When we refresh the catalogue, any price or data-volume change the provider made carries through to the relevant product page, and the updated date on a destination page moves with that refresh.

One thing worth knowing: the price shown on a product page may differ from the one you remember seeing last time, because the catalogue may have been refreshed in between. The price that actually binds is the one shown at the moment you check out, not the one you recall from an earlier visit.

Install guides and OS releases

Install guides follow the help pages that handset manufacturers publish. When iOS or Android ships a major release that moves the settings menu, we review the affected guide against the manufacturer's updated documentation. A guide that points to the wrong menu location loses the reader at the very first step.

Device tables and new handsets

Device compatibility tables are reviewed when a manufacturer announces a new model, not on a fixed schedule, because new releases do not arrive evenly across the year; some months bring several, others bring none. We follow manufacturer announcements instead of a rigid calendar.

A new model is added to the table only once official specifications confirm eSIM support. If a page does not yet list a new model, that does not mean it fails; it may mean we have not found confirming specifications yet, or the model is new enough that it has not reached the front of the review queue.

Destination pages and local networks

Each destination page is reviewed when a local operator announces a significant change, such as a network technology shift or a coverage adjustment, and when the supplier catalogue for that country changes, with the updated date moving to match, because destination-page information affects the buying decision of someone travelling in the next few days.

Travel guides and travel rules

General travel guides, such as packing advice or preparation tips, age more slowly than technical content, so we review them when a source on the page changes or a reader writes in. But where an article references a visa or customs rule that a government agency has since changed, we correct it as soon as we know, because a travel rule affects a reader's entry into a country directly.

Slow-moving reference pages

Basic terms and definitions, such as what eSIM is or how an eUICC differs from a physical SIM, barely change meaning across years. This kind of page is reviewed less often than others, but that does not mean it is left untouched forever. We recheck it when the underlying technical standard changes, or when a reader points out that the existing wording is genuinely misleading.

What the dates on a page mean

What happens between reviews

A source changing is not the only reason a page gets corrected. If someone reports an error through our corrections policy, we check and fix it straight away. Reader reports are a second safety net alongside our own checks, not a replacement for them.

What a review actually involves

1. 1Pick the pages to reviewPages whose source changed, pages a reader reported, and pages where the supplier catalogue changed.
2. 2Compare content against the primary sourceWe check whether what is written still matches the manufacturer, provider, or agency documentation.
3. 3Check the displayed price against the supplier catalogueSo no stale figure survives from an earlier catalogue.
4. 4Fix, or confirm no fix is neededIf something is off, we correct it. If everything still holds, the date beside each source we opened moves to today.
5. 5Update the on-page date to match what actually happenedThe updated date only changes when content genuinely changed, not simply because someone opened and closed the page.

When we retire or merge a page

A page describing a discontinued plan with no replacement, or a page whose content has become duplicated by another and should be merged, gets retired or folded into the more complete page. When a page is retired or merged, we always set up a redirect to the closest relevant page, so a link you saved earlier does not land you on something that no longer exists.

Signals that trigger a review

Who actually reviews each content type

Every article is written by one of our two co-founders, Bob Kanokphon Thongdee or Porsch Kunnipat Siramanakul, and reviewed by the other, whose name appears on the page under Reviewed by. Each content type is checked against a different kind of source: pricing against the supplier catalogue, install guides against handset manufacturers' documentation, and travel rules against official government pages.

Having the co-founder who did not write the page do the review makes it easier to catch what the writer missed, and means two named people answer for every published page.

Do heavily visited pages get checked more often

Not directly, no. We review a page when its source or the catalogue changes, or when a reader writes in. A low-traffic pricing page follows the same rule as a high-traffic one, because the risk of stale information harming a reader depends on how fast that type of information moves, not on how many people happen to visit that particular page.

That said, if a high-traffic page collects several problem reports in a short span, that is usually a trigger for a review as described in the signals table above, driven by the number of reports rising, not by the visit count itself.

What stays the same even after a page is reviewed

A review does not mean a page's tone or position shifts. What gets adjusted is whatever fact has gone stale, such as a price or a model list. Warnings about device limitations, or the disclosure of how we earn, stay exactly as they were no matter how many times a page gets reviewed, because those are not facts that expire; they are principles we hold to throughout.

When the GSMA standard itself changes

The technical definition of eSIM we cite from GSMA barely changes across years. But if the standard itself is genuinely revised, for example in how profile transfer between devices works, every related reference and glossary page is reviewed together, not one at a time, because these definitions are linked to each other and need to stay consistent as a set.

Standard-level changes are rare, but when they happen they usually touch several basic explanations at once, so we treat this as another kind of review trigger, alongside the signals table above.

Checklist: is the page you are reading current

• It shows an Updated date, and its Sources list gives each source's publisher and last-checked date
• The displayed price matches what appears at actual checkout
• The device table includes a model close to yours, not one several generations older
• There is no flag warning that a section is awaiting review
• If unsure, open the page directly rather than reading only the search-result snippet

Report something that looks wrong or outdated

Contact us