How to Scrape a Shopify Store with BrowserQL

BrowserQL lets you navigate to a Shopify storefront in a hosted browser, wait for the page to render, and extract the text or attributes you need. Use it only for pages and data you are authorized to access. If you own the store or have merchant authorization, Shopify’s versioned Storefront API is usually the better starting point when it exposes the fields you need.

What BrowserQL does

BrowserQL (BQL) is Browserless’s declarative GraphQL interface for browser automation: send mutations that describe browser actions, and Browserless runs them in a managed browser and returns results. It supports navigation, waits, interaction, extraction, screenshots, PDFs, and session handoff. Browserless’s TypeScript and Python BAP SDKs build the same mutations under the hood; its documentation recommends those SDKs for those languages. Direct BQL is useful from other languages, for generated calls, or in the hosted IDE.

#	Preview	Product	Price
1		ScrapTherapy® Cut the Scraps!: 7 Steps to Quilting Your Way through Your Stash	$19.31	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

For a Shopify page, the basic pattern is navigate → wait for the relevant content → extract. A browser is useful when information appears only after client-side rendering or requires interaction. It does not grant permission to collect, store, or republish that information.

Check permission and choose the right source

For a store you own or where the merchant has authorized your app, first check whether the Shopify Storefront API exposes the fields you need. It is a versioned GraphQL API for buyer-facing storefront functionality such as products, collections, search, pages, blogs/articles, and carts. Shopify advises specifying a supported API version; the versioned reference here is 2026-04, with the endpoint pattern https://{store_name}.myshopify.com/api/2026-04/graphql.json and GraphQL POST requests.

#1 Best Overall

ScrapTherapy® Cut the Scraps!: 7 Steps to Quilting Your Way through Your Stash

• Country of Origin:US
• CPSIA:N
• Hazardous?:No
• Tariff:4901990050

$19.31

Buy on Amazon

Storefront API access can be tokenless, use a public access token for browser or mobile use, or use a private access token server-side. Tokenless requests have a query complexity limit of 1,000 in Shopify’s 2026-04 documentation. Product tags, metaobjects/metafields, online-store menus, and customers require token-based access. Shopify also limits automated Storefront API traffic and crawlers, most strictly when unsigned; it documents Web Bot Auth for requesting higher limits. These limits and authentication needs should be checked against the current documentation when implementing.

Do not substitute the Admin API for the Storefront API without a reason. Shopify describes the Admin API as its backend API for reading and writing merchant store data, authenticated with scopes granted by the merchant. Use the API whose purpose, permissions, and data scope match your authorized task.

Shopify’s API Terms of Use prohibit systematic or automated collection through the Shopify API—including scraping, data mining, extraction, or harvesting—unless authorized by Shopify or to the extent applicable law expressly prohibits the restriction. The terms also say API requests should be limited to the minimum data needed for the app’s intended functionality and the permissions granted by the merchant or Shopify. This concerns Shopify API use; it is not a complete legal analysis of every public webpage or jurisdiction.

For crawling a public Shopify storefront, Shopify’s Web Bot Auth guidance describes securely authorizing crawlers, scripts, or tools, with examples including accessibility and SEO audits, automated testing, and data analysis. Treat this as guidance for authorized crawling, not blanket permission for arbitrary extraction or reuse.

Send a basic BrowserQL extraction

Browserless documents three HTTP endpoints: /chromium/bql for open-source Chromium, /chrome/bql for a genuine Google Chrome build, and /stealth/bql for a privacy-hardened browser configuration. Requests require a Browserless API token in the ?token= query parameter. Pick an endpoint based on Browserless’s current documentation and your account configuration rather than assuming one is universally best. The following uses the Chromium endpoint; replace the host, token, and URL with values appropriate to your Browserless account and authorized target.

curl -X POST 'https://production-sfo.browserless.io/chromium/bql?token=YOUR_BROWSERLESS_TOKEN' 
  -H 'Content-Type: application/json' 
  --data-binary '{"query":"mutation ScrapePage { goto(url: "https://example.myshopify.com/products/example", waitUntil: domContentLoaded) { status } text { text } }"}'

The GraphQL mutation navigates to one product page, waits for the DOM content-loaded event, returns the navigation status, and extracts page text. Replace the example URL with a page you are permitted to access. This is a generic example; Shopify themes vary, and no store-specific selector or field layout is assumed.

Wait for JavaScript-rendered content

domContentLoaded may occur before a storefront’s asynchronously rendered content is present. If the value you need is missing, use BrowserQL’s documented waitForSelector or waitForEvent operation to wait for the relevant page state, then extract. Choose a selector by inspecting the authorized page you are working with; selectors can change when the merchant changes themes or markup.

Extract only what the task needs

Text extraction is a practical first inspection, but it can include navigation, promotional copy, and unrelated page content. Once you understand the rendered structure, extract only the needed text, attributes, or structured data using BrowserQL’s documented operations. Keep the collection to the minimum necessary for the stated purpose, and separately establish whether storage, redistribution, or commercial reuse is permitted.

Scale carefully beyond one page

A successful one-page extraction does not establish that a site-wide crawl is appropriate or reliable. Begin with a permitted product or collection page, confirm that the fields are present after rendering, and expand only if the purpose requires it. BrowserQL session duration is plan-dependent; Browserless documentation accessed 2026-10-03 listed these maximums, which are volatile and should be rechecked:

Plan labels, allowances, and limits can change. For longer jobs, account for the applicable session ceiling and avoid treating a browser session as an unlimited crawl. Shopify API limits and Browserless session limits are different constraints; check both when designing an authorized workflow.

BrowserQL or Shopify’s Storefront API?

This is a decision framework, not a performance comparison; no comparative performance test is established here. If BrowserQL’s stealth configuration, CAPTCHA solving, fingerprint mitigation, or proxies are available in your Browserless setup, they remain technical product capabilities—not evidence of authorization or permission to use the resulting data.

Troubleshooting common failures

• Request is rejected or unauthorized: check that the Browserless token is present as the token query parameter, is valid for the account, and that the selected endpoint matches your configuration.
• Navigation status is unsuccessful or content is absent: confirm that the URL is correct and accessible to your authorized browser session. If the page renders content asynchronously, wait for the relevant selector or event before extracting.
• Text is returned but the desired field is hard to isolate: inspect the actual rendered page, then target the specific text, attribute, or structured data with the documented extraction operations. Do not assume a selector works across different Shopify themes.
• Session ends before the task finishes: check the plan’s current maximum session duration and reduce the scope of the session or divide work into permitted, appropriately sized tasks.
• Storefront API query is rejected or lacks a field: check the requested API version, whether the field needs token-based access, the token’s granted permissions, and Shopify’s current query and automated-traffic limits.
• A bot check or CAPTCHA appears: do not interpret bypass capability or a completed request as authorization. Confirm the store owner’s permission and the applicable rules before proceeding.

Or skip the browser setup

If your goal is a clean screenshot rather than extracting structured page data, ScreenshotNeo is a website screenshot API and MCP server. Its one-call GET endpoint returns an image or PDF; the API options and response details are in the ScreenshotNeo documentation.

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

ScreenshotNeo accepts cookie or consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. A screenshot is not a substitute for data extraction or authorization to reuse a store’s content.

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

Frequently Asked Questions

Can BrowserQL extract a Shopify product’s price?

It can extract information present in the rendered page, but the exact field and selector depend on the store’s current theme and markup. For an authorized store, use the Storefront API if it exposes the required field.

Does a public Shopify product page mean I can scrape and republish its data?

No. A page being publicly viewable or successfully loaded does not itself establish permission to collect or republish its data. Check the applicable authorization, terms, and law for your use.

Is BrowserQL the same as Shopify’s Storefront API?

No. BrowserQL automates a browser; the Storefront API is Shopify’s versioned GraphQL API for buyer-facing storefront functionality.

Quick Recap

Bestseller No. 1

ScrapTherapy® Cut the Scraps!: 7 Steps to Quilting Your Way through Your Stash

Country of Origin:US; CPSIA:N; Hazardous?:No; Tariff:4901990050

$19.31

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.