Research Guides
Small Screen, Same Evidence: A Mobile Content Parity Worksheet
A desktop page can explain an offer clearly while its mobile version leaves out the detail that makes the offer believable. A screenshot comparison may miss this: both screens can look polished even when one has lost the methodology, qualifications or supporting links.
This worksheet audits whether people and search systems can find equivalent information across versions. It is a manual research method, not a claim that Colquhoun.shop currently performs mobile audits automatically.
Start with the information, not the layout
Google uses the mobile version of a site's content for indexing and ranking. Its mobile-first guidance calls for equivalent primary content, meaningful headings and consistent metadata across desktop and mobile versions. Layouts can differ: an accordion is not inherently a problem. The important distinction is between reorganizing content and failing to supply it. Google's mobile-first indexing guidance.
Before opening an audit tool, write down five things the page promises to answer. For a research report, that might be its main finding, sample size, collection period, method and limitations. For a service page, it might be scope, price, exclusions, delivery timing and cancellation information.
These are your evidence units. Compare those units rather than total word counts. Removing a repeated navigation label is different from removing the only sentence that says a price excludes tax.
Choose a small, useful sample
Start with one page from each important template, plus a page that recently changed and one known to contain expandable sections. This is a diagnostic sample, not proof that every URL is correct.
Record each exact URL before testing. Note whether desktop and mobile use the same address or distinct addresses. Also record language, login state, consent state and the time of the test. Otherwise, you may compare different experiences and wrongly attribute the difference to screen size.
Keep private account pages out of screenshots intended for a public report. Do not share session tokens or customer information with a third-party testing service.
Capture three separate views
- Desktop baseline: Record the evidence units and their location on the page.
- Mobile before interaction: Reload in the mobile test configuration and record what arrives before you open controls.
- Mobile after interaction: Open the relevant tabs or accordions and record what changes.
Chrome DevTools device mode can approximate mobile viewport sizes and behavior, but it does not run the page on an actual phone. Label emulation results as such, and reproduce suspicious findings on a real device when possible. Chrome's device-mode documentation.
A screenshot tells you what was visible, not everything present in the document. For a suspected omission, inspect the rendered document as well as the screen. Google distinguishes fetching, rendering and indexing; some JavaScript pages do not include their primary content in the initial HTML response. An empty initial response alone therefore does not settle what the rendered page contains. Google's JavaScript SEO basics.
Use one row per evidence unit
Copy this compact worksheet into your review notes:
| Field | What to record |
|---|---|
| URL and template | Exact address and page type |
| Evidence unit | The answer or qualification being checked |
| Desktop observation | Present, absent or not tested |
| Mobile observation | Present, absent or not tested |
| Interaction dependency | None, reveal existing content, or fetch new content |
| Evidence | Screenshot, relevant document excerpt and timestamp |
| Impact | What a reader could misunderstand |
| Next action | Named owner and specific retest |
Avoid a single “mobile SEO score.” A count of matching elements can disguise the omission that matters most. Instead, distinguish confirmed differences from unanswered questions.
Example: a missing limitation
Imagine a fictional report page whose desktop view explains that its survey covers 40 respondents in one region. On mobile, the same chart appears, but the sample limitation is absent until a visitor opens “More details.”
Do not immediately file this as a search defect. First establish whether the limitation already exists in the rendered document and the control merely reveals it, or whether opening the control initiates a new request that retrieves the text.
That distinction matters because Google warns against loading primary content only after user interaction. Its crawler does not click, swipe or type to retrieve that content. Google's mobile content access guidance.
The finding should name the observation: “The sample limitation is fetched only after opening More details in the tested mobile session.” That is more actionable than “Google cannot understand this page,” which the test has not established.
Verify a repair without promising rankings
For a site you control, Search Console's URL Inspection offers indexed information and a separate live test. Keep those records separate: the indexed report can describe an older version. The live test can expose rendered output and resource issues, but does not guarantee indexing or search appearance. URL Inspection documentation.
Close a finding when the missing evidence unit is available under the agreed test conditions, supporting captures are saved, and the owner has repeated the original failing check. Record remaining uncertainty explicitly.
A good parity report does not claim every screen must look identical. It shows whether the same essential answers survive the move to a smaller screen, and leaves another reviewer enough evidence to check the conclusion.