How to Capture Competitor SERP Screenshots for Desktop and Mobile Audits

To capture competitor search engine results pages (SERPs) for a desktop and mobile audit, open the same search query in Chrome, capture it at a consistent desktop viewport, then use DevTools Device Mode to capture it at a consistent mobile viewport. Save both screenshots with the query, capture time, market or locale, device class, and viewport dimensions. Treat each image as evidence of one rendered observation, not a universal or permanent ranking.

1. Decide what the screenshots need to show

Before opening Chrome, write down the exact search query and the market or language context you want to inspect. Treat each query and market as its own audit observation. Search results can vary between sessions, so record the context and avoid presenting a single capture as a definitive ranking for everyone.

Choose the screenshot type based on the question:

Viewport screenshot: shows what fits on screen immediately. Use it to compare the above-the-fold experience, visible results, ads, and SERP features.
Full-size screenshot: captures the rendered page beyond the current viewport. Use it when you need to inspect the page as a whole; a tall image is less useful for judging what appears first.

Decide whether the audit also needs a performance or page-quality report. Lighthouse can provide that separate artifact; it does not replace a saved SERP screenshot.

2. Capture the desktop SERP in Chrome

Open Chrome and navigate to the search page for the query you selected.
Set a consistent desktop browser window and viewport for the audit. Record the viewport width and height in CSS pixels.
Position the page at the top if you are documenting the initial view.
Open Chrome DevTools. In the DevTools menu, choose Run command, search for screenshot, then choose Capture screenshot for the visible viewport or Capture full size screenshot for the full rendered page.
Save the file with a descriptive name, for example best-running-shoes_2026-10-04_us-desktop-1440x900.png.

Chrome documents viewport and full-size screenshot capture in its Device Mode documentation. The exact menu labels can vary with Chrome versions; use the DevTools command menu to find the screenshot actions.

3. Capture the mobile SERP with Device Mode

Keep the same query and market context. In DevTools, turn on Device Mode using the device toolbar toggle.
Select a device preset or enter a specific responsive viewport width and height. Use the same preset or dimensions for every mobile capture in the audit.
Make sure the page is at the top, then capture the visible viewport or full-size page using the DevTools screenshot command.
Save the image separately from the desktop one and include the device class and viewport in its filename.

Device Mode simulates a mobile viewport and device conditions. A device frame may be included in device-specific mode when it helps communicate context, but it is usually clearer to compare the page content without a frame. Emulation is useful for repeatable viewport checks; it does not prove that every device- or browser-specific behavior matches a physical phone.

4. Keep a useful audit record

Store a short observation log next to the raw images. Record at least:

Exact query and language or market.
Capture date and time, including time zone if the team spans regions.
Desktop or mobile, viewport dimensions, and device preset if used.
Whether the capture is viewport-only or full-size.
Whether the browser session was signed in and any unusual personalization state you noticed.
Brief observations, such as visible organic-result count, snippet truncation, paid placements, and SERP features.

These details make the capture easier for another analyst to understand and reproduce as closely as practical. They do not eliminate search variation or guarantee identical results in another session.

5. Compare desktop and mobile captures

With the query and market held as steady as practical, review the images side by side. Compare:

Viewport dimensions and the amount of content visible above the fold.
Number and ordering of visible organic results.
How titles and snippets wrap or truncate.
Paid placements, local results, answer features, and other SERP elements.
Whether a result’s presentation differs between the two captures.

Describe the evidence precisely: for example, “At this viewport, the first organic result appears below the visible ad block.” Avoid turning that observation into a claim about every user or every search. Google says it uses the mobile version of site content, crawled with a smartphone agent, for indexing and ranking. Google also describes responsive design as serving the same HTML and URL across devices while the display can vary by screen size. A visual difference between mobile and desktop alone does not show that the underlying content or URL differs. See Google’s mobile site and mobile-first indexing guidance.

6. Use Lighthouse only for a separate page-quality question

If the audit also needs performance or page-quality diagnostics, run Lighthouse separately and keep its report distinct from the SERP screenshots. Lighthouse defaults to mobile emulation and also has a desktop preset; its configuration includes form factor, screen emulation, and user-agent emulation. See the Lighthouse emulation documentation. Label the report as emulation-based, and do not treat it as proof of the exact experience on a physical device.

7. Troubleshooting common capture problems

Problem	Likely cause	What to do
Screenshot command is hard to find	DevTools menu labels or layout differ across Chrome versions.	Open the DevTools command menu and search for “screenshot”; choose the viewport or full-size action.
Mobile capture looks like desktop content squeezed into a narrow window	Device Mode was not enabled, or the page has not finished responding to the viewport change.	Enable the device toolbar, choose the intended preset or dimensions, and allow the page to render before capturing.
Desktop and mobile images cannot be compared fairly	Query, viewport, market, session, or capture type changed between captures.	Repeat with the same query and market and consistent capture conditions; record unavoidable differences in the log.
Important result or feature is missing from the image	The screenshot captured only the visible viewport, or the page had not settled.	For whole-page inspection, capture full size. For the initial view, keep the viewport capture and note that content below the fold is excluded.
A mobile behavior appears suspicious	Device emulation may not reproduce a particular phone’s browser or hardware behavior.	Verify consequential device-specific findings on a real phone.
A Lighthouse report is being used as the screenshot evidence	The report answers a performance or quality question, not what the saved SERP looked like.	Save a separate Chrome screenshot and retain Lighthouse as its own report.

8. Performance, reliability, and cost

The Chrome workflow uses built-in browser tools and creates local image files. Capture time depends on the page and whether it has finished rendering; allow dynamic content to settle before taking the image, and keep the same approach across comparisons. Device Mode improves consistency of viewport checks, while a physical device is the right follow-up when a consequential result depends on device-specific behavior.

Preserve the original screenshots and observation log so later readers can distinguish recorded evidence from interpretation. A screenshot is a point-in-time record, not a continuously updated rank tracker. This workflow has no screenshot API charge; it does require someone to repeat and label captures. For automated or repeatable API capture, ScreenshotNeo provides a website screenshot API and MCP server.

Or skip the browser setup

ScreenshotNeo can capture a SERP with one GET request. For an API key and the full parameter list, see the ScreenshotNeo documentation.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.google.com/search?q=best+running+shoes -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://www.google.com/search?q=best+running+shoes",
    },
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://www.google.com/search?q=best+running+shoes',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

Add desktop and mobile viewport parameters from the docs to capture both sizes, and use the same query and market context when comparing the outputs. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed; its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Does a mobile SERP screenshot prove what every phone user sees?

No. It records one emulated rendering under the conditions you captured. Check a physical phone when a device-specific behavior matters to the finding.

Should desktop and mobile use the same query?

Yes, if the goal is to compare presentation across viewport classes. Keep the market and language context as consistent as practical and record the conditions.

Does a full-page screenshot replace an above-the-fold capture?

No. A full-size image is useful for page-wide inspection, while a viewport capture makes the immediate searcher experience easier to assess.

Does a desktop/mobile layout difference mean the site has separate content?

No. Responsive design can display the same HTML and URL differently at different screen sizes.