Quick Answer
Google’s Mobile-Friendly Test and API were retired in December 2023. An old checklist or script that can no longer obtain a result should record an unavailable check, not a pass. Define the current mobile task and evidence required, distinguishing desktop emulation from observations on an actual device.
A recurring report can keep displaying an old “mobile friendly” label after its original test disappears. Review what the entry actually means before relying on it for a release decision.
Remove the retired dependency from the decision
Google’s original API announcement now carries a retirement notice for December 2023. Read that notice before following the historical setup instructions below it. The old article does not describe a current supported testing endpoint.
Inventory where the old check appears: a release checklist, a scheduled script, a dashboard or a customer report. Identify whether it is returning old data, an error or no result. Do not silently translate any of those states into “passed.”
Give the replacement check explicit states
| State | Meaning to preserve |
|---|---|
| Observed pass | The defined task met its stated criteria under the recorded conditions. |
| Observed failure | A reproducible problem occurred in that task. |
| Unavailable | The required tool or observation could not provide evidence. |
| Not performed | The planned check has not yet been completed. |
For a hypothetical inquiry page, the new task might be opening the navigation, reading service information and completing an authorized test inquiry on a relevant phone. Define the expected behavior and required evidence before marking the check complete. This example is a proposed QA task, not a test we ran.
Keep emulation and device evidence separate
Chrome’s Device Mode guide calls its simulation a first-order approximation. It explains that code is running on the desktop rather than a mobile device and identifies limitations such as different CPU architecture.
Emulation can help investigate a narrow layout or reproduce a viewport condition. Label it accurately. An image inside a phone-shaped frame does not establish that a real phone’s keyboard, scrolling, browser controls and interaction behavior were tested.
Update the handoff as well as the tool
Have the responsible developer revise the obsolete automation through the approved project process. Keep the previous behavior and recovery requirements documented. This article does not provide replacement code or authorize changes to a running system.
The report should identify the URL, task, device or emulation conditions, date and observed result. Keep remaining gaps visible. A single check does not certify every page, accessibility requirement or customer journey.
Our website speed-test workflow covers a different evidence set: field and laboratory performance. The Core Web Vitals guide explains slow-page diagnosis, while the ranking-factor explanation keeps technical results separate from promised search positions.
Key Takeaways
- Retire the obsolete API dependency in the QA decision.
- Keep unavailable and unperformed checks separate from passes.
- Label emulation and actual-device observations accurately.
Frequently Asked Questions
Does an API error mean the page failed a mobile check?
It means the attempted check did not provide the required result. Investigate the tool and define the appropriate current test separately.
Does Device Mode prove the real phone experience?
No. Chrome documents its simulation limits. Use actual-device observations where the task requires them.

