← all plays

When a page looks empty

Scrape the sites that need a real browser

Sometimes you grab a page and almost nothing's there. No list, no content, just a loading spinner. That's a page that builds itself a half-second after it opens, so a plain grab catches it before the content shows up. The fix is to use a real browser. The technical name is a headless browser: a normal browser running invisibly in the background, with Claude at the wheel.

You can have Claude drive an actual browser in the background. It opens the page, waits for everything to appear, scrolls, clicks "show more," and then you read the finished page, exactly what a person would see. The tool for this is called Playwright.

The trigger is simple

If a plain grab comes back empty, the content is being built on the fly, and you need a real browser to let it finish. That's the only signal you need.

Open it, and wait for the good part

The browser opens the page in the background (no window pops up). The one mistake everyone makes is reading the page too soon, before it's done loading. The fix is to wait for the actual content to appear instead of waiting a fixed number of seconds.

# the idea, in plain terms open the page in a real browser wait until the listings actually show up # now read it, like a person would

Scroll and click for the rest

Lots of sites only show the first handful, then load more as you scroll or when you click a button. A real browser can do both. Scroll to the bottom, click "show more" until it's gone, and the page keeps filling in. Once it stops growing, you've got it all.

Then it's the workhorse again

Once the page is fully loaded, you're right back to the everyday play: hand the finished page to Claude, ask for the parts you want, get a clean list. The browser's only job is to turn an empty-looking page into a full one.

when to reach for a real browser
What you seeWhat it meansWhat to do
The grab comes back nearly emptybuilds on the flyuse a real browser
Stuff appears as you scrollloads in chunksscroll to the bottom
A "show more" buttonmore is hiddenclick until it's gone
Content behind a tab or clicktucked awayclick, then read
Works, then suddenly blockedit caught ongo to the next play
basically the decision treestep up only when needed

A real browser is heavier and slower than a plain grab, so it's the second choice, not the first. Try the simple grab first, fall back to the browser only when the page comes up empty, and most of your work stays fast and free.

How it works under the hood

What it uses

The browser
Playwright, runs in the background
Wait right
Wait for content, not a timer
Interact
Scroll and click for more
Read
Hand the finished page to Claude

Worth knowing

Don't read early
Wait for the real content to show up.
It's heavier
Use it only when a plain grab fails.
Tidy up
Close pages when done, they pile up.
If blocked
Step up to the next play.

Got a site that won't give up its data?

Send me the page.

If it loads for a person, I can load it for a scraper and pull what's there.

Free to do yourself. All the plays are right here.

Keep going