How to screenshot Google Discover competitor results for SEO research

To screenshot Google Discover competitor results, open Discover in the Google app or on google.com on an Android phone, record the conditions around the feed, then use the phone’s screenshot controls. Treat each image as a dated observation of one personalized feed—not a universal ranking or a view into a competitor’s impressions.

This workflow preserves what appeared and makes repeated observations easier to compare. It cannot establish why a card appeared or how often other people saw it.

1. Open Discover and record the context

Google says Discover is available in the Google app, on google.com on Android, and on some devices by swiping from the home screen. Availability and settings can vary by country and language. Confirm that you are looking at Discover before capturing; app or menu layouts may differ.

Before opening the feed, create a log entry for the capture. Google describes Discover as personalized using device and Google-product information, with account data and location among relevant inputs. The fields below are a recommended research protocol based on that disclosure, not a Google-mandated form.

Log field	What to record
Capture date and time	Include the time zone if captures will be compared across locations.
Device and software	Phone model if known, Android version, and Google app or browser surface.
Language and region	Record the language shown and the region or location context you know.
Account state	Signed in, signed out, or unknown. Do not assume account settings are identical between captures.
Feed context	How you reached Discover and any topic or query context relevant to the observation.
Image identifier	Use a filename or log ID that connects the original screenshot to this entry.

Keep conditions as consistent as practical for a time series. If they change, note the change instead of silently treating the images as directly comparable.

2. Capture the feed on Android

1. Open the Google app, visit google.com in a browser on Android, or use a supported home-screen swipe route.
2. Verify that the visible cards are in Discover and note the capture time.
3. On most Android devices, press Power and Volume Down together. Some devices also offer a Screenshot control after a long press of Power. Button behavior varies by manufacturer.
4. On Android 12 and newer, after taking a screenshot, tap Capture more to extend it on most screens that allow scrolling. Adjust the crop guides and save. If the option does not appear for this feed or device, take multiple ordinary screenshots and log their order.
5. Review the saved image. Preserve the unaltered original; make a separate cropped or annotated copy if needed for analysis.

Android’s scrolling capture is not available on every device or every scrollable screen. Do not assume a single extended image captures the entire feed. Google Photos can be used to view, edit, and share screenshots.

3. Compare captures as observations

For each dated image, record the publisher or page shown, the card headline and image, the card’s visible position, and the capture time. These are useful observation fields proposed for analysis; they are not metrics Google identifies as its ranking system.

• Compare captures made under similar language, region, account, device, and surface conditions where possible.
• Report the number of captures and the time span. A small sample should be described as a small sample.
• Distinguish “this card appeared in this feed at this time” from claims about general visibility, ordering, eligibility, or impressions.
• Keep originals so later annotations do not obscure what the feed actually showed.

Discover is interest-based and personalized, so another person may see different cards. Google also says content can be eligible when it is indexed and complies with Discover policies; eligibility does not guarantee appearance. Google states that special tags or structured data are not required. A screenshot does not show that markup or any particular SEO change caused a placement.

4. Use Search Console for your own measured performance

For a property you control, Search Console’s Discover performance report can show clicks, impressions, and click-through rate when the property meets Google’s minimum impression threshold. It can group data by page, country, appearance type, and day. Google says the report covers content that appeared in Discover during the last 16 months, subject to that threshold.

This report is for the verified property; the cited Google documentation does not describe it as a way to retrieve competitors’ private Discover performance. Google also cautions that Discover traffic is less predictable than Search traffic. Use screenshots for qualitative, time-stamped observations and Search Console for eligible first-party performance data.

5. Or skip the browser setup

For ordinary web pages, ScreenshotNeo is a website screenshot API and MCP server. A normal website URL can be captured with one request; its API is not a way to access a personalized Google Discover feed inside your Android account. Use the phone workflow above when the research question is specifically what appeared in your own Discover feed.

For a web page you can access by URL, this cURL request returns an image. See the ScreenshotNeo API documentation for options and response details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Equivalent Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Equivalent Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. These web-page captures complement the Discover workflow; they do not reproduce your personalized mobile feed.

Sign up for 1,000 free screenshots a month with no card.

Troubleshooting

Problem	Likely cause	What to do
Discover is not visible	The route or feature may not be available in the same way for your device, country, or language.	Try the Google app or google.com on Android, and note which surface you used. Do not assume menus match another user’s device.
Power + Volume Down does nothing	Button behavior differs across manufacturers or the buttons were not pressed together.	Try again, or use the device’s Screenshot control if available from a long press of Power.
Capture more is missing	The device may not run Android 12 or newer, or this particular feed screen may not support scrolling capture.	Take successive standard screenshots and record their order and overlap.
Two captures show different cards	Discover is personalized and can vary with context and time.	Check the log fields and report the variation as an observation, not proof of a ranking change.
A competitor card appears only once	A single capture is a narrow sample; it does not establish stable visibility or eligibility.	Repeat observations under recorded conditions and report sample size and dates.
Search Console has no Discover report	The property may not meet the minimum impression threshold, or there may be no reportable data.	Check again when eligible. Do not use the absence of a report as evidence about competitor performance.

Reliability, time, and cost

• Reliability: Native screenshots preserve the feed as rendered on the device. Scrolling capture support varies, so multiple images may be needed. Context logs make the evidence interpretable later.
• Time: Preparing a log and taking repeated observations adds manual work, but avoids losing the conditions that explain differences. Search Console is better suited to aggregating your own eligible property data.
• Cost: The workflow uses a phone and Google surfaces; no special SEO tool is required by the documented method. Use a phone you already have. ScreenshotNeo’s web API has a free tier and paid tiers, but it captures URL-accessible web pages rather than a signed-in personal Discover feed.

FAQ

Can a Discover screenshot prove a competitor ranks above mine?

No. It documents one personalized feed at a particular time. It does not prove a universal order or provide the competitor’s impressions.

Does a publisher need special markup to appear in Discover?

Google says no special tags or structured data are required. Content must meet eligibility guidance, and eligibility is not a promise of appearance.

Can I see a competitor’s Discover clicks in Search Console?

The documented Discover report provides performance data for a property you can access, not competitors’ private figures.

Sources

• Google Search Central: Get on Discover
• Google Search Console Help: Performance report (Discover)
• Google Search Help: Customize what you find in Discover (Android)
• Android Help: Take a screenshot or record your screen