# Search Device Comparison Worksheet

Canonical page: https://waitlist.crany.ai/marketing-templates/organic-device-performance-comparison

By Tangenix. Published 2026-10-24. Category: Search operations.

Compare organic search observations across mobile and desktop with consistent scope, then investigate the actual experience before naming a device problem.

## Task

Investigate a device performance difference without confusing audience mix with a broken page.

## When to use

Use this when mobile and desktop search results appear different for the same relevant page or page group. Keep date, country and search-type scope consistent, then inspect the actual journeys.

## Choose another approach when

The samples are too sparse to interpret, filters differ between exports, or the comparison is being used to claim a controlled experiment occurred.

## Inputs

- Comparable Search Console views for the selected devices.
- The page group, period, search type and any country filters.
- A safe way to inspect the page and task on each relevant device class.

## Template

    Question: [which device difference needs explanation?]
    Shared scope: [property, dates, pages, country, search type]
    Group A / Group B: [device classes]
    Clicks, impressions, CTR and position: [same metrics for both]
    Query or audience mix checked: [observations / unknown]
    Actual journey checks: [layout, readability, action, errors]
    Hypothesis: [technical issue or other explanation]
    Evidence against that hypothesis: [record]
    Next diagnostic: [specific check, owner]
    Conclusion strength: observed difference / supported issue / unresolved
    Do not label this an experiment.

## Illustrative example

This is not a Crany customer result. Replace example details with verified facts.

    Fictional comparison shows lower mobile CTR on a client-handoff resource. Both views use the same country, dates and page filter.
    The founder initially suspects a signup defect, but no mobile journey has been tested. Review finds different visible query mixes and asks for a device usability check before editing the offer.
    If that check finds a clipped button, it establishes a page defect worth fixing. It still does not prove that the defect caused the earlier search-result CTR difference.

## How to use

1. Build comparable device views and record the exact filters applied.
2. Inspect mix differences and test the relevant page task on actual device classes.
3. Separate observed report differences, confirmed interface defects and unresolved causal explanations.

## Checks

- The report windows and search types match.
- Mobile CTR is not confused with the rate of completing a task after arrival.
- A device-specific fix is supported by direct evidence of a defect.

## What to measure

Track resolved journey defects and later consistent device-level observations. Interpret before/after changes cautiously because search visibility and audience composition can change independently of the fix.

## Research and sources

Google supports dimensional comparisons and warns that filters affect data interpretation. The mix review and journey checks are original diagnostic planning, not proof of a causal device effect.

- [Google Search Console: Advanced filtering and comparison](https://support.google.com/webmasters/answer/17011165?hl=en) — checked 2026-10-24. Comparable device, country, page and time scopes; filters and aggregation affect interpretation.

Prepared with AI assistance. Sources support the stated principles; they do not endorse Crany or guarantee performance.

## About Crany

Crany is an AI marketing co-founder in development for software founders and vibe coders. It is designed to strategize, execute approved marketing and improve based on results. These free resources are usable independently of app access. The public waitlist is at https://waitlist.crany.ai/.