How to screenshot product pages with crossed-out list prices visible

To screenshot a product page with a crossed-out list price visible, open the exact product page, select the intended variant or sale state, and wait for the price area to finish rendering. Move both the current price and crossed-out price into the visible screen area, close anything covering them, take a screenshot using your device’s capture controls, then open the saved image and confirm both amounts and the strikethrough are legible.

A screenshot records what the page actually rendered at that moment. It does not establish that a reference price is universally valid, that the offer applies in every market, or that the same prices will appear later.

1. What the crossed-out price means

On a product page, the active sale price is generally the amount the customer pays, while the crossed-out amount represents an original or comparison price. Google Merchant Center describes the original price as less prominent than the active sale price; merchants may distinguish it by striking it through, graying it out, or otherwise showing it as inactive. Google’s guidance concerns its merchant data and sale annotations, not every store’s product page. Google Merchant Center: About sale price annotations.

The reference amount may be absent. Merchants submit a base price and can submit a sale_price; whether a sale annotation appears on Google surfaces depends on destination-specific and country-specific conditions, and Google says display is not guaranteed even when its criteria are met. Those rules do not create a universal requirement that every storefront show a crossed-out price. Google’s sale price annotation guidance and eligibility requirements.

Store configuration can also matter. As one Shopify-specific example, Omega’s support documentation describes using a Compare-at price higher than the current Price to display the former crossed out, while noting that apps and themes may affect the result. Omega: Show crossed-out prices on a Shopify product page. Adobe Commerce documents another configuration: minimum advertised price settings can hide the selling price behind a “Click for Price” action or show a crossed-out list or market price. Adobe Commerce: Minimum advertised price.

So capture the rendered page rather than assuming what the merchant intended to display. Describe only what the image shows. The struck-through amount alone does not prove a universally valid reference price or a discount available to every shopper.

2. Prepare the product page

Open the exact product page. Check the product name and relevant details so the screenshot can be identified later.
Set the intended state. If the price depends on a region, size, color, quantity, account state, or promotion selector, choose the state relevant to your screenshot and allow the page to update.
Wait for the price area to render. Do not capture while a loading indicator, placeholder, or price update is still in progress.
Fit both amounts into the screen. Scroll until the current price and its crossed-out comparison price appear together. Include the product name or another identifying detail if the image might be shared out of context.
Clear obstructions. Dismiss pop-ups or banners that cover either amount. Close menus, tooltips, and browser overlays if they obscure the page.
Capture with your device’s screenshot control. The exact key combination and full-page options depend on the device, operating system, and browser. This guide stays platform-neutral rather than guessing at a shortcut that may not work for your setup.
Inspect the saved image. Open it and check that both amounts, the currency, the product identity, and the strikethrough are readable and not cropped or blurred.

3. Choose a capture that preserves context

Visible-area screenshot

Use a visible-area screenshot when the product identity and both prices fit together on screen. It is the simplest choice for a single price record. Confirm that the saved image includes the whole price block and enough surrounding page context to identify what it belongs to.

Full-page screenshot

A full-page capture can help when relevant details span a long page, but support and behavior vary by platform and browser. Before relying on one, confirm that the method you choose retains the rendered price styling and includes any content loaded while scrolling. A full-page image can also make the price block too small to read, so inspect it at its actual size.

If the prices are far apart, consider whether a single readable screenshot is possible by changing the page zoom or capture method available in your browser. Verify the result rather than assuming the tool preserved the styling. Do not edit the saved original to make a price look crossed out or more prominent. If you need annotations, add them to a separate copy and distinguish them from page content.

4. Keep useful context with the image

When the screenshot is meant to document an offer, note the capture date and the market or region separately from the image. Prices and promotions can change, and Google’s sale annotation conditions vary by geography. The cited sources do not prescribe an evidence-retention standard; recording context is practical guidance, not a legal rule.

Before sharing, check these details:

The product name or another reliable identifier is visible.
The active price and the crossed-out price appear together.
The currency and any selected variant or quantity are clear when relevant.
The crossed-out treatment is visible in the saved image, not merely on the live page.
No cursor, tooltip, sticky banner, browser chrome, or compression blur obscures a key detail.
The screenshot is an unaltered record, or any marked-up copy is clearly identified as annotated.

5. Capture the page with ScreenshotNeo

If you need a repeatable capture without setting up browser automation, ScreenshotNeo provides a website screenshot API. Pass the exact product page URL; the API returns an image or PDF. Review the result to ensure the variant and price state you need actually rendered.

See the ScreenshotNeo API documentation for request options. This minimal cURL example saves the response as a WebP image:

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

Replace the example URL with the product page and set your API key. The returned capture reflects the page state ScreenshotNeo can render; it cannot guarantee that a merchant displays a crossed-out price or that the page has a particular regional, variant, or account state.

6. Troubleshooting

What you see	Likely cause	What to do
No crossed-out amount	The merchant page does not render a comparison price in the selected state, or the offer or storefront configuration differs.	Check the selected variant, market, quantity, and promotion. Capture the page as it appears; do not infer a missing amount.
The wrong price appears	A variant, quantity, region, or promotion selector may still be set to another state, or the page may not have finished updating.	Select the intended state, wait for the price area to update, then capture again.
The price is covered	A cookie notice, newsletter prompt, chat widget, menu, or sticky element overlaps the price.	Dismiss or close the obstruction, then verify that the page remains in the intended state.
The image cuts off one amount	The price block was near a screen edge or the capture used the wrong area.	Scroll or reposition until both prices fit together, capture again, and inspect the saved image.
The amount is too small or blurred	The page was scaled down, a full-page capture shrank its contents, or the saved image was compressed.	Use a visible-area capture if it contains the needed context. Open the original image and check legibility before sharing.
A sale badge appears on a listing, but not on the product page	Google sale annotations are conditional, and listing surfaces and merchant landing pages are distinct displays.	Record the exact page you need. Do not treat a listing annotation as proof that the product page renders the same price treatment.
A “Click for Price” action hides the selling price	The store may use a minimum advertised price configuration.	Capture the visible state, or use the page’s provided action if you need to record what it reveals. Adobe Commerce describes this as one possible MAP behavior.
ScreenshotNeo does not show the expected price	The URL may lead to a different market or state, or the page may require an interaction or session to select the intended product state.	Check the URL and rendered result. See the API documentation for available capture options, and verify the returned image before using it.

7. Performance, reliability, and cost

For a one-time record, a visible-area screenshot is usually the most direct path when both prices fit on screen. A full-page capture may take longer to produce or be harder to read, depending on how the chosen tool handles long and dynamically rendered pages. Allow the price to settle before capturing and inspect the output; those steps catch many avoidable errors.

For recurring monitoring, a screenshot can preserve visual context, while structured extraction can record prices as data. These are related but separate needs. ScreenshotCenter describes pairing ecommerce screenshots with extracted price, product, and availability data for ongoing tracking; that vendor article is an example of the workflow, not a claim that a screenshot alone monitors changes. ScreenshotCenter: Track ecommerce pages with screenshots and extracted prices.

ScreenshotNeo’s stated pricing is 1,000 shots per month free with no card; Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is available on every plan. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Responses identify the page verdict and billing status in X-Page-Verdict and X-Billed headers. See the docs for current request details.

Or skip the browser setup

Make one GET request to capture a product page as WebP:

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

ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter pop-ups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents using Claude, Cursor, or another MCP client take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. The API docs describe the request options. Sign up for 1,000 free screenshots a month.

FAQ

Does a crossed-out amount prove the discount is available everywhere?

No. The screenshot records a rendered display. Google’s sale annotation requirements vary by geography and destination, and the cited guidance does not establish a universal rule for every merchant page.

Should I capture the listing page or the product detail page?

Capture the page that supports the point you need to document. If you need the selected product, variant, or price context, the detail page may provide it; verify the actual rendered page.

Can I use one screenshot to track prices over time?

A screenshot is a record of one capture. Ongoing tracking requires repeated captures, and may also require structured price extraction if you need to compare values automatically.