"Unclear mobile billing": charges users cannot see before they pay

Google has detected that your site "is not sufficiently informing users about mobile charges," and Chrome may show a warning before loading a page that incurs them. This issue is about subscription and carrier billing flows, where a tap on a phone can add a charge to the visitor's mobile bill, often on a recurring basis.

Most WordPress sites never see it; normal WooCommerce checkouts with card or wallet payments are not what it targets. It shows up on sites selling mobile content, ringtone or game subscriptions, premium SMS services, and landing pages built for carrier billing partners. If you do run such pages, the fix is to make the cost impossible to miss before the user agrees.

The issue details list example URLs, a short description and the date the problem was first detected. Google's instruction is to visit those examples, review its mobile billing guidelines, and fix the pages to match them. Because billing landing pages are usually built from one template and duplicated per campaign, expect the same fault on pages that are not in the sample list, and fix the template rather than each copy.

What Google's billing best practices require

Google's guidance on announcing mobile billing charges comes down to three points:

  1. Billing information is visible and obvious. Do not hide or obscure it, and make sure it shows on every type of device, not just desktop.
  2. Users know before they are charged. Tell them which actions will cost money before those actions happen.
  3. The fee structure is easy to understand. State the amount and how often it is charged, for example daily, weekly or monthly.

Pages that fail these typically put the price in small grey text under the button, below the fold on phones, or only in linked terms and conditions, or use a button labelled "Continue" or "Play now" that actually starts a subscription.

Auditing the billing flow on WordPress

Carrier billing pages on WordPress are usually landing pages built with a page builder, plus a script or redirect supplied by the billing partner. Walk through each flagged URL on a real phone, over mobile data, the way a customer would:

  • Is the price, currency and billing frequency visible without scrolling, next to the button that triggers the charge?
  • Does the button text say what it does, such as "Subscribe for $4.99 per week"?
  • Is anything important only in an image, a popup or a linked terms page?
  • Does the page look the same on narrow screens, in dark mode and with larger text settings?
  • Does a partner script change the page after it loads, for example by hiding the price once the user arrives from an ad?

Record each check with a screenshot from a phone. Those screenshots are useful later, both for your own before-and-after comparison and to show a billing partner exactly what needs to change on their side. Check both your template and the partner's embedded elements. If the partner's script is responsible, the page is still yours for the purposes of this issue.

Rewriting the page

A compliant billing section is short and plain:

html
<p class="billing">Subscription: <strong>$4.99 per week</strong>, charged to your
mobile bill until you cancel. Cancel any time by texting STOP to 12345.</p>
<button>Subscribe for $4.99/week</button>

Keep that text near the button, in a readable size and color, and keep it in HTML rather than an image. Remove countdown timers or "you have won" framing around billing buttons; they point in the opposite direction to the guidance. Hydrogen SEO's titles and meta descriptions have no bearing on this issue, but a matching meta description that mentions the price is a small consistency win once the page itself is fixed.

Getting the Chrome warning lifted

When every flagged page, and every page built on the same template, shows the charge clearly before the user acts, select Request Review in the Security issues report:

text
Our subscription landing pages showed the weekly price only in the
terms link. All 12 pages now show the price, billing frequency and how
to cancel next to the subscribe button, visible without scrolling on
mobile. Button text now states the price.

Google says a review can take from a few days to a few weeks, and Chrome's warning stays until it passes. If your billing partner provides the page, share Google's best practices with them and confirm the changes on their side too, because a partner update can reintroduce the problem.

Common questions

Does this issue apply to normal WooCommerce checkouts?

It targets pages that add charges to a visitor's mobile bill without clear information, such as carrier billing subscriptions. A standard checkout that shows prices and takes card payments is not the usual subject.

What must a mobile billing page show?

Google's best practices ask that billing information be visible and obvious on all devices, that users be told which actions cost money before they are charged, and that the fee amount and frequency be easy to understand.

Does this issue affect my Google rankings?

Google describes the effect as a Chrome warning before the page loads. That warning alone can stop most visitors, so fixing the page is worth doing quickly.