Ask the person who sent the phone screenshot to provide the query, city, and time of the search. reChecker checks desktop results, so a mobile position cannot be compared directly with a desktop position. Save both results along with the conditions under which they were obtained.
If the phone shows a different page or an inconvenient form, open that URL and check it separately. Search position and mobile page usability require different actions: the former calls for measurement settings, while the latter calls for the screen, browser, and specific defect.
Record the conditions of the manual search
The context for each row should be clear: search engine, query, region, device, and date. If the device is not recorded, any discussion of position differences starts with missing data. Reconstruct the source conditions before assigning work to a developer.
Label the manual mobile search as a separate observation. Save the visible URL, query text, and time. Do not present a phone screen as proof that the desktop data collected in the account is wrong: that conclusion requires comparable conditions and a repeatable check.
If the client sent an image without a date or settings, first clarify the context. This is a normal diagnostic step. Based on it, you can decide which comparisons are valid and which observations do not yet support a numerical conclusion.
Separate the sources in the report
| Source | What is known | What is needed for comparison |
|---|---|---|
| reChecker account | Desktop, query, region, date | Check that the available snapshot is current |
| Employee’s phone | Visible page and manual query | Clarify the time and location of the observation |
| Search Console | Metrics for a period and selected segment | Specify the filters and measurement method |
| Service page audit | URL condition on the check date | Compare the URL and the scope of the technical data |
If different sources show different service pages, start by looking at the purpose of each page. One page may answer an informational question, while another describes an offering. Requiring the positions to match does not explain what is useful to visitors.
Open the same page on a phone
Open the same URL on desktop and on a phone. Make sure important information is not missing in either version of the interface. Users should be able to see the service terms, key product details, and an available way to get in touch.
Check the content and technical constraints on the actual page. Google describes the specifics of mobile-first indexing. For website work, this is a reason to check that important data is accessible, not an explanation for every position difference based on a single factor.
For a display check, use the responsive testing guide. Record specific defects: a heading is cut off, a button is inaccessible, or a table extends beyond the screen. These issues can be fixed and checked independently of position.
Keep separate metrics
Use the desktop series to track changes in the selected search queries in the subscription. Use the mobile interface check to assess page usability and element functionality. Use visitor statistics by device to understand your audience from your analytics sources.
Do not treat one metric as another. An average position in period-based statistics is not the same as a single manual position. The number of mobile visits does not establish the cause of a desktop decline. For every figure, identify its source and the question it answers.
The rank tracking guide helps document the conditions of a search check. It is useful to include these conditions in the internal report so colleagues do not try to compare unrelated observations just because the query text is the same.
Assign a task for the mobile page
For a search observation, specify the query, region, desktop results, and dates being compared. For a mobile page, specify the URL, screen size, and the action the visitor is expected to take. This separation gives implementers a clear scope of work.
For example, a form partly extends beyond the screen on a phone, and the desktop position differs from the manual mobile search. The developer gets a task to fix the form and checks it after the change. The search specialist separately clarifies the conditions of the two observations. Neither of them has to prove that two different positions will become identical.
After checking the result, ask a colleague to repeat the mobile scenario and open the saved desktop result. They should understand which problem was fixed and which metric is simply still being monitored. If the final text mixes these two parts, rewrite the conclusion before sending it to the client.
Check results are available in the site monitoring dashboard.