Publix decided we were not a customer before we asked for anything. On 24 August 2026 a request to publix.com from a server in Germany returned a page titled "International | Publix Super Markets", a polite landing page for visitors outside its footprint, with none of the store site behind it. A US cloud exit got the same page. Four other US cloud exits got HTTP 403 outright. Whatever rule sits at the door, it looks at the network a request comes from and not only at the country, and it shows the real site to addresses that look like the households in its eight states.
That footprint is the second thing to know. Publix runs more than 1,400 supermarkets in Florida, Georgia, Alabama, South Carolina, North Carolina, Tennessee, Virginia and Kentucky, with more than 260,000 associates (Publix, facts and figures), and it is the center of a deal culture built around the weekly ad and its BOGO offers. The ad is per store, the deals are per region, availability is per store, and the whole thing turns over weekly.
Which proxy type
US residential proxies pinned to one of Publix's eight states, ideally the state of the stores you read, driving a real browser, one store per session. Any login goes on its own static ISP proxy. Datacenter and free exits never reach the site, as counted below.
Publix as a target
The weekly ad, per store, with the BOGO offers that the deal community lives on and digital coupons layered over it. Store availability and pickup or delivery, which Publix offers through Instacart for delivery and through its own curbside program, so the per-store online view is readable on the Instacart storefront as well as on publix.com. The locator, with more than 1,400 stores that grow by a handful a month. And the pharmacy, which is not a data job.
Jobs a proxy is right for
- Weekly ad and BOGO tracking by region. Which offers run where, and when the ad flips. Deal sites publish it weekly; brands verify their promotion; shoppers compare regions.
- Store-level availability and price checks. What a store carries and charges, read per store, and how the online view compares.
- Locator and new-store tracking. Diffing the store list as Publix pushes into Kentucky and grows in the Carolinas.
- Regional assortment. What a Miami store carries that a Nashville store does not.
- Promotion verification for suppliers. A brand paying for an ad placement wants to see it at a real store in the region it bought.
Jobs a proxy is not for
Club Publix and coupon stacking. Accounts attach to phone and email; creating many runs against Publix's terms.
Pharmacy. Not a data job under any tool.
Ordering somewhere you are not. Curbside needs a car; delivery needs a real address in the footprint.
The door, measured twice
First run, 24 August 2026: one direct request from a datacenter server in Germany, with a normal browser user-agent, returned HTTP 200 and the International landing page. The twenty free proxies from our free proxy list, mixed countries: 14 did not connect at all, and all 6 that connected were shown the International page.
Second run, the same evening, 15 elite free proxies filtered to the United States: four exits on well-known cloud networks got HTTP 403, one got the International page, and the rest never connected. No US cloud address was shown the store site.
Read together, the rule is not "US or not". It is closer to "household or not": a residential address in the footprint gets the site, everything that looks like a server gets a landing page or a refusal. We did not test a US residential exit through the free pool, because the free pool has none. The setup below is built on that reading. How websites detect proxies covers the network-reputation side of that decision.
Non-US server
International page
US cloud exit
403 or International page
Residential in the footprint
store site
Store session
ad, BOGO, availability
Type by job
| Publix job | Proxy type | Why |
|---|---|---|
| Weekly ad and BOGO tracking | Rotating US residential in the footprint, sticky per store | Gets past the household check; the ad is per store |
| Store-level availability and price checks | Rotating US residential, state-pinned | Prices and stock are per store |
| Locator and new-store tracking | US residential, slow pacing | Paged queries from one address is the metered pattern |
| Promotion verification | Rotating US residential, region-pinned | See the placement as shoppers there see it |
| Any login | US ISP (static residential) | One fixed, trusted location per account |
| Anything | Datacenter or free | Landing page or 403, 0 of 11 connecting exits reached the site |
For the background on why residential and datacenter addresses are treated so differently, datacenter vs residential proxies.
Free proxies here
None of the eleven connecting exits, across two runs, reached the store site. Free proxies are datacenter addresses and that is what the door turns away, so there is no manual-look case to describe here. The free USA proxy page explains why US exits dominate the free pool and why that does not help against a household check. For the weekly sweep, our US residential proxies start at $0.44/GB, pay as you go, no KYC, pinned to Florida, Georgia or any of the other six states.
Setup
- Residential exit in the footprint. This is the entry ticket. Pin to the state of the stores you read; Florida for Florida stores.
- Real browser, cookies kept. Once inside, the site is an application with a store choice held in the session. The Puppeteer proxy guide shows the launch.
- Sticky session per store, read on the ad cycle. Choose the store, read the ad and the categories you track, record store number and week, rotate. Read once per cycle and diff, not daily. Sticky vs rotating proxy sessions lays out the two modes.
- Treat the International page as a block signal. If a residential exit is shown it, that exit is being treated as a server; retire it. For the rest, avoiding IP bans while scraping.
Sizing
Weekly ad across all 8 states, weekly:
stores sampled per state 10-40 (Florida heaviest)
pages per store session ~5
sessions per exit per day 4-6
exits in rotation ~25-30 US residential in the footprint
Ad pages with images blocked are small and bandwidth is the meter, so the store list sets the bill. A weekly cycle runs for a quarter and stops, with the balance on our pricing page kept for the next one.
Where it ends
A residential address in the footprint is what gets a page instead of a landing page, and it is all the proxy contributes. Accounts, the pharmacy and Publix's terms, which prohibit scraping, stay exactly where they were. Past that, a state-pinned residential exit with a real browser lets a legitimate data job read the public ad, deals, availability and locations the way shoppers in each region see them: one store per session, human pacing, and the landing page treated as a signal.
The chain with an open door and a store list growing even faster is in proxies for ALDI; the pharmacy chain with the same regional-ad economy behind an Akamai door is in proxies for Walgreens.
Sources
- Publix Super Markets, facts and figures (more than 1,400 supermarkets in Florida, Georgia, Alabama, South Carolina, North Carolina, Tennessee, Virginia and Kentucky; more than 260,000 associates): corporate.publix.com
- HProxy measurement, 24 August 2026: one direct request from a German datacenter server (International landing page); 20 mixed elite free proxies from our free proxy list (14 no connection, 6 International page); 15 US elite free proxies (four cloud exits HTTP 403, one International page, the rest no connection).