Content update policy

eSIM information ages quickly: prices, OS menus and supported handsets all move. Each content type therefore has its own review cycle.

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.

This is why we split review cycles by content type rather than purely by a page's age. A brand-new page and an older page in the same category are checked at the same frequency.

Prices and plans: the fastest-moving cycle

Plan pricing is checked at every sync with the provider, because it is the figure that most directly affects a buying decision and it moves most often. If a provider changes a price or the data volume in a plan, the relevant product page is updated at the next sync, not held until a calendar-based review comes around.

One thing worth knowing: the price shown on a product page may differ from the one you remember seeing last time, because syncs happen more often than most people expect. 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 are reviewed on a six-month cycle, but if iOS or Android ships a major release that moves the settings menu, we review the affected guide immediately rather than waiting for the six-month mark. 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 every three months on the ordinary cycle, and reviewed sooner as soon as a local operator announces a significant change, such as a network technology shift or a coverage adjustment, because destination-page information affects the buying decision of someone travelling in the next few days.

Travel guides and travel rules

General travel guides — packing advice or preparation tips, say — are reviewed every twelve months, since they age more slowly than technical content. 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, without waiting for the twelve-month mark, because a travel rule affects a reader's entry into a country directly.

Slow-moving reference pages

Basic terms and definitions — 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 scheduled reviews

A scheduled review is not the only chance a page gets to be corrected. If someone reports an error through our corrections policy, we check and fix it immediately rather than waiting for the next scheduled pass. The calendar is a safety net, not the only route to keeping a page accurate.

What a scheduled review actually involves

1. 1Pull the pages due for reviewThe list is pulled according to each content type's cycle stated on this page.
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 latest syncSo no stale figure survives from an earlier sync.
4. 4Fix, or confirm no fix is neededIf something is off, we correct it. If everything still holds, we update the check date 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 an early review

Who actually reviews each content type

The person who checks pricing pages is not the same person who checks install guides or travel rules, because each type calls for familiarity with a different kind of source. Whoever checks pricing needs to be comfortable with the provider's sync system; whoever checks install guides needs to be hands-on with the real menus on both operating systems.

Splitting responsibility this way lets each reviewer go deeper than one person trying to check every page of every type, and it reduces the chance that a point needing specialist knowledge gets skimmed over.

Do heavily visited pages get checked more often

Not directly, no. The review cycle is tied to content type only, as shown in the table above. A low-traffic pricing page is checked just as often 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 an early 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 — a price, 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 — how profile transfer between devices works, say — 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 early-review trigger, alongside the signals table above.

Checklist: is the page you are reading current

• It shows an Updated date, and it is not older than the cycle stated in the table above
• 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 the team