Atiba de Souza.Start a conversation
WritingAI

Your Scraper Handles the Full Crawl. Your Page Can't Handle One Stranger.

By Atiba de Souza

Atiba de Souza wearing a blue baseball cap with a Superman logo and a black polo shirt. The cover reads: AI Stranger arrives The page

The target moves. Both targets.

An adaptive web scraping framework now handles everything from a single request to a full-scale crawl. It does not care that the site changed its markup last Tuesday. It re-finds the thing it came for and keeps going.

Now look at your website. Same job. Harder target.

One visitor, then another, then a thousand. Every one of them changes shape between sentences. They arrive unconvinced. They scan. They get bored. They leave. Your page does not adapt to any of it.

You built the machine that collects data, and it adapts beautifully. You never built the page that collects the decision.

A visitor does not arrive as a lead. A visitor arrives as a stranger, and the page has one job: move them.

The whole framework is one sentence

I call it The Website Copy Framework, and the entire thing sits on one line:

Every page exists to transfer trust from a stranger to the point of action, at scale.

That is the North Star. Everything else in the framework is arithmetic.

Trust transfer: the movement of belief from a stranger to your offer, one small yes at a time, until clicking is the smallest step left on the page.

Here is the judgment rule that falls out of it. If a copy choice does not move trust toward the action, it is decoration. Cut it.

Notice what that rule refuses. Cleverness. The headline that makes your peers nod. The paragraph you wrote because it felt substantial. I judge a page on movement toward the offer, never on how good the writing sounds in a conference room. A page that impresses and does not move is a page that failed politely.

The framework is one sentence, three ranks, and one page. That is the whole system. Most teams try to run it on every page at once and never decide the one action.

Rank these, or you will do all three badly

Rank 1, and it is not close: the North Star sentence. Take that line and hold every element of every page against it. One sentence, applied honestly, will beat a full rewrite done carelessly.

Rank 2: the cutting. This is where the work actually happens. Decoration is easy to spot once you are willing to call it decoration.

Rank 3, and this is the minor one: polish. Headlines that sing, layout, design. Real, worth doing, and worth exactly nothing if nothing on the page moves trust. Do not start here. Most people start here because it feels like progress and costs no honesty.

Where NOT to use this. Do not run the framework on a page that has no defined action. If you do not know the one thing you want the stranger to do, this framework will only make your confusion tighter and better organized. Decide the action first. Then apply the framework.

Also: do not rewrite the whole site on Monday. That is panic, not strategy. One page. The one with traffic and an offer on it.

The part nobody says out loud

You are not going to want to do this.

Not because it is hard. Because it costs you something specific. It costs you the line you love. The line your CEO loves. The line that got approved in a meeting where everyone felt good about it. Cutting that line feels like losing status, not like improving a page.

The fear underneath is real: strip the clever parts and the page will feel thin and plain and unimpressive, and it will look like you did less work.

Here is the rewiring it demands. You have to write to a stranger instead of to the room you have been standing in for ten years. Everything you know, everything your team knows, every shortcut in your language, is invisible to the person who just landed. You are not dumbing it down. You are finally aiming it.

And moving trust toward the action is not pressure. Pressure pushes. Trust transfer removes the last excuse standing between a person and a decision they already want to make.

The demonstration that went sideways

Live on a call with a physician I coach, I opened my ChatGPT project to screen-share the exact book-writing process I was recommending. I was going to show him how it worked. The project was empty. Every piece of the book work I had built there was simply gone, and I found that out in front of the person I was demonstrating it to.

"Let me see if I can… let's see what I can find for you here. give me a second. … My… all my ChatGPT stuff is gone. on the book. And, like, the project is completely empty, and I'm just like, what the heck happened there?"

You expect the flex. You get the hunt.

The lesson is not about ChatGPT. It is about ownership. Had the profile and outline been exported to files I owned, that demonstration would have taken ten seconds instead of a hunt through what was left. So: export every AI-produced profile, outline and draft into a file you control the moment it is good, and never treat the chat project as storage.

Now bring that home. Your best copy is usually not on your page. It is in a chat window, a Google Doc, a Slack thread, or the head of the one person who actually talks to customers. The demo of your business runs all day without you in the room, and if the good material is not in the file that runs, the stranger never sees it. Own the file. Put it where the trust has to transfer.

Impossible means go

Last month I ran a live AI workshop for virtual workers. GoHighLevel's official connector does not support the sign-in method Claude Co-work needs, and the room agreed out loud that this was a blocker. Everyone could see the wall.

I did not accept the wall and I did not buy a Zapier-style bridge. I clicked over into Claude Code and described the problem: what I wanted, what I needed, and the specific gap between the two. It wrote me a working self-hosted OAuth GHL connector. The missing integration built itself.

There is always a way around. The title of that whole thing is Impossible Means Go.

Now the hand-off, and it is the same hand-off as the empty project. The fix was not a better tool. The fix was describing the gap precisely: what I wanted, what I needed, and the space between them.

Your page stalls for the same reason. You believe the blocker is your industry, your price, your buyer, your market. Most of the time the blocker is one paragraph that never answers the question the stranger is actually asking.

So write that paragraph. Not the one about what you believe in. The one that says what the stranger wants, what they have right now, and the specific gap between the two, in their words instead of your category's words. If what sits underneath is "will this work for a business my size," the paragraph answers that in one plain sentence, then says what happens next. That is the connector. You just built the bridge instead of buying it.

And if you cannot write that paragraph, that is the real information. It means you do not know the gap yet, and no amount of design covers for that.

Inconsistent pages and consistent pages

Inconsistent pageConsistent page
Written to people who already trust youWritten to the stranger who just arrived
Headline describes the companyHeadline states the change the stranger gets
Proof arrives after the askProof arrives before the ask
Every element is decoration, none is load bearingEvery element moves trust toward the one action
Gets rewritten in a panic when it stops workingGets one page tested at a time, on purpose
Best material lives in a chat windowBest material lives in a file you own

The loop that turns one stranger into scale

No

Yes

Stranger arrives

The page

Does this move trust
toward the action?

Decoration. Cut it.

Keep it. It is load bearing.

Point of action

Next stranger, and the next

That loop is the whole framework. One stranger, one page, one test, repeated. That repetition is the "at scale" part. It was never about volume. It was about the same judgment applied every time.

Monday

Start with Rank 1, because everything below it is arithmetic. Before you touch the page, write the one action in a single sentence: the one thing you want the stranger to do when they land. If you cannot write that sentence, stop here. That was the whole job today, and it is the highest-ranked work in the framework.

Then Rank 2, and this is the part that costs you. Open the page with traffic and an offer on it. Read it out loud as the stranger, because you were one once and you have forgotten what it felt like. Mark every line: moves trust, or decoration. Now cut the decoration without negotiating with yourself.

Your hand will resist, and it will resist for the reason named earlier. The line you cut is the line that got approved. It is the one that makes you sound like the leader you are. Cutting it feels like losing status you earned, not like improving a page. It is not a loss. The line you keep so the page feels substantial is the line standing between a stranger and a decision they already want to make. A page that keeps its clever lines for the room is charging the stranger for your comfort.

Keep Rank 3 away from this until Rank 2 is done. If all you finish Monday is Rank 1 and one real cut, that is a complete day's work. Polish on top of an uncut page is decoration with better typography.

Two small moves finish it, and both come from things that already happened.

Take the good material out of the chat window and put it in a file you control, so the next demonstration, the next hire, and the next campaign starts from what you own instead of from what survived.

And where the page hits something that looks like a blocker, do not accept the gap and do not pay someone to bridge it. Write the paragraph that names what the stranger wants, what they have now, and the space between those two. Describe the problem out loud and go around.

The scraper adapts to the site. You have to adapt to the human. Same discipline, tougher target, better payoff.

Questions

What people ask next

If the team genuinely disagrees on whether a line is load-bearing or just decoration, how do you settle that argument without it turning into another status fight?
You hold the line against the North Star sentence, not against who wrote it: does this specific line move trust toward the one action, yes or no. That question has nothing to do with whose idea it was or how good it sounded in the room, which is exactly why it defuses the status fight instead of feeding it. If nobody can answer the question with a yes, it's decoration, regardless of who loves it.
What's the actual signal that a page is 'done' so you move on to the next one, instead of endlessly re-testing the same page forever?
Done is when the cutting work runs out, meaning every remaining element on the page is load bearing and nothing left is pure decoration. At that point you're in rank 3 territory, polish, which the framework treats as worth doing but not worth obsessing over since it moves nothing on its own. Once the page is judged clean against the one sentence, you move to the next page with traffic and an offer on it rather than keep circling the same one.
If you cut everything that isn't strictly moving trust toward the action, doesn't the page risk sounding as flat and generic as every other stripped-down page out there?
Flat and generic happens when you cut without replacing, but the framework isn't asking you to cut and leave a gap, it's asking you to write the paragraph that answers the stranger's actual question in their words instead of your category's words. That specificity, naming exactly what they have now and the gap to what they want, is what keeps a stripped page sharp instead of bland. The risk isn't from cutting too much, it's from never writing the one paragraph that was supposed to replace the decoration.
What do you do when a page legitimately needs to serve two actions at once, like a purchase and a sign-up, and picking just one feels like leaving money on the table?
The framework is explicit that it only works once you've decided the one action; running it without that decision just organizes your confusion more neatly. So you don't force one page to carry two actions, you decide which one is the point of action for this page and test that one, then build or test a second page for the other action. Trying to make a single page move trust toward two different asks is how you end up with a page that moves trust toward neither.
How do you even find that one paragraph that closes the stranger's real gap if nobody on the team actually talks to customers directly?
The article's own point is that your best copy is usually not missing, it's unowned, sitting in a chat window, a doc, a Slack thread, or in whoever on the team gets closest to customer conversations even informally. Go find that person and that material first, rather than assuming you have to invent the paragraph from scratch. If genuinely nobody in the business has ever heard the stranger's actual question, that's real information too, and it means you need to get someone in front of customers before you touch the page.