Honest review + $442 bonus stack

Reads every document in a launch at once. Then tells you where the buyer gets stuck.

JV page, JV doc, swipes, sales page, marketplace stats, live ads — read together, not one at a time. Out comes the thing no vendor writes down: where the buyer freezes after paying, plus five bonus ideas that remove it, your presell brief, 5 emails and 4 scripts. Pro turns the same research into a build spec for Claude Code — my six bonuses take it from there.

⚡ Get Page Sniper + My 6 Vibe-Coding Bonuses Core $12.95 · Pro from $27 · One-time · 30-day refund
✓ One-time price, no subscription ✓ 6 bonuses · $442 value ✓ No credits to buy — use any AI free ✓ 30-day refund
🧩 Chrome side panel 🔑 Your own AI key — OpenAI, Claude, Gemini or Grok 📋 Or paste any prompt into a free AI 🚫 No credits, no subscription

It reads the documents buyers never see — and reads them together

A sales page is written to sell you. The JV page, JV doc and swipes are written for affiliates — the only place a vendor describes the product plainly, with the funnel tier by tier, real pricing, and what each upsell actually contains.

Page Sniper collects all of them plus the sales page, the marketplace stats and live ad data, then does the part I have not seen elsewhere: it reads them together, every time. Add a document later and nothing gets overwritten — it re-reads all of the text, so where two documents disagree the contradiction gets reconciled rather than the newest one quietly winning. Nothing is parsed from layout either; the raw text goes to the AI to be read the way a person would, whatever the vendor called their tiers.

One combined picture. Then two very different questions get asked of it — which is exactly what the two tabs are.

6
Sources read as one: JV page, JV doc, swipes, sales page, marketplace, ad libraries
1
Insight no vendor states: where the buyer freezes after paying
2
Questions asked of it: how do I sell this — or what would it take to build it

The six steps, and what each one adds to the picture

It is a stepper, not a wizard — you can work them in any order, and step 4 is explicitly the one to skip if you are in a hurry. But each step feeds the next, and two of them will not work properly if you skip what comes before.

  1. The vendor's affiliate material. The JV page, the JV doc and the swipes, collected and read together. Out of it: what the offer really is, who it suits and who it does not, the funnel tier by tier with what each one holds back, what the contest actually pays, and what an affiliate honestly earns per sale rather than the headline "up to $X". It finishes by handing you the questions those pages never answered — which is what step 2 goes looking for. Anything behind a login or a Google Doc, you paste the text in; it tells you plainly that Google Docs draw text on a canvas so nothing can be collected from the page.
  2. The sales page teardown. This is where the angles live. The hook, every subhead in order so you can watch the argument being built, the copy layering, the trust signals, the CTA placement, the offer mechanics — then it names the copywriting framework and maps the page to it, so you borrow the structure without copying the words. Your email subject lines come out of this step, because they have to be built from the promises and objections the page itself makes, not from the size of the commission.
  3. The marketplace numbers. Sales, conversion, EPC and refund rate off the WarriorPlus, JVZoo or ClickBank offer page. Two things that come from this and are easy to miss: it feeds back into the step 2 teardown so the analysis knows it is reading a proven winner rather than a guess, and it takes the vendor's own keywords rather than the product title — because titles are often just a product code, and a search built on one sends you to the wrong niche.
  4. Who else is winning, and who is paying. Optional. It reads your live Google results page: organic winners and Sponsored ads, then the Meta Ad Library and Google Ads Transparency. What you get is a structural template — the section order, CTA count and trust signals that pages winning in this space actually use. It also warns you about the mistake everyone makes: search for the page you want to beat, not the product category, because "audiobook software" returns the tools themselves, which sell to a completely different person than an affiliate offer does.
  5. Where the buyer freezes after paying. The one that makes you money. It reads the whole funnel from step 1 against the front-end promise from step 2 — and it reads what each upsell contains, not what it is called. If an upsell sells templates, the front end expects you to write them. If an upsell sells done-for-you setup, the front end expects you to configure it yourself. It quotes the upsell that gives it away and names what the front-end-only buyer is left holding. Then: why they freeze there, five bonus ideas that remove it — each deliverable by one person, with how you would produce it and the exact objection it kills — and the one it would pick, with its reasoning. It refuses to suggest anything the vendor already includes or that an upsell sells.
  6. The output. Tick the bonus ideas you will actually make, add your own in a sentence of rough notes, and they get written up properly. Then: a presell brief, five emails on five different angles — one of them the bottleneck email nobody else on the launch will send — and four short video scripts with spoken beats, on-screen text and b-roll kept separate so they paste into a video maker without needing a studio or a presenter.
The thing that made me trust it. Step 5 depends on step 2, and the tool says so plainly instead of producing something plausible anyway: "read the sales page first or this is guesswork." Blocked pages are reported as blocked. The docs state outright that nobody can publicly verify which pages convert best, so it ranks on what it can actually see. And it will not publish a page with a red placeholder still on it. That attitude is rarer in this category than it should be, and it is a large part of why I am promoting this one.

Core or Pro? Same research, two different questions

Both tiers run the identical research engine — nothing in the reading, combining or analysis is held back for the upgrade. The vendor is straight about that and it is true. What you are choosing between is which tab you live in.

Core — "Promote an offer"

$12.95for 72 hours, then $19

You are the affiliate. The question is how do I sell this, and what bonus do I offer.

  • JV page, JV doc and swipes read together and reconciled
  • The funnel tier by tier, and what an affiliate really earns per sale
  • Unlimited sales page teardowns with the framework mapped
  • Marketplace stats, plus Meta and Google ad intel
  • The bottleneck + five bonus ideas, each with the objection it kills
  • Presell brief, 5 emails, 4 video scripts
  • One saved campaign

Pro — adds "Beat a winner"

from $27dimesale, rising to $37

You are the builder. Same research, different question: what would it take to build this.

  • Everything in Core
  • A build spec written for Claude Code — the tab says so in those words
  • It inherits the Core research: the funnel, where their buyers stall, the questions their pages never answer. It does not start cold
  • Separates real mechanical features from marketing — building the second kind is how people lose a month
  • An explicit "not in v1, and why" list, which is what stops a build sprawling
  • Gap scoring: what to build vs what you already have and never mentioned. Or an "I'm starting from scratch" path
  • Rewrites their page around your product · compares several winners into one composite blueprint
  • The full presell page draft, plus a design prompt you paste into Claude to get the page built
  • 100 saved campaigns instead of one
Why I point people at Pro. Core is a genuinely good $12.95 tool and if you only ever promote other people's launches, take it — it does the job properly. But Pro is not "Core with more features". It is the same research pointed at a different question, and the spec it produces is built around what the funnel revealed rather than around the winner's feature list. The tool's own reasoning for that is the sharpest line in the product: their upsells are the vendor's own admission that the gap exists. A v1 that removes what their buyers are stuck on beats a v1 that copies what they built. That is the tier my bonuses were made for.
⚡ Get Page Sniper Pro + All 6 BonusesFrom $27 · Price rises 10c per sale · 30-day refund

My honest verdict

★★★★★
A genuinely original piece of thinking, built by someone who clearly runs promotions themselves
4.7/5

What's good

  • It reads the JV page, JV doc, swipes and sales page together and reconciles them — collect a fourth document later and it re-reads everything rather than overwriting. That combining is the actual work and it is what everyone skips
  • The bottleneck read is genuinely novel: it reads what each upsell contains to work out what the front end leaves you to do alone, then quotes the upsell that gives it away
  • It only proposes bonuses the vendor does not already include and no upsell sells — so your bonus complements the funnel instead of competing with it. A small detail that shows someone thought hard about this
  • It calls out inflated "up to $X per sale" claims and works out what the front end really pays
  • The build spec has a mandatory "what is real and what is marketing" section. A sales page is not a specification, and that distinction is worth the Pro price on its own
  • Bring your own key (OpenAI, Claude, Gemini or Grok) or copy any prompt into a free AI. No credits sold by the vendor, keys stay on your device
  • It will not let you publish a page with a red placeholder still on it, and it says outright that nobody can verify which pages truly convert

Good to know

  • It is a stepper with real dependencies. Work steps 1 and 2 properly and everything after is sharp — it tells you when you have skipped something
  • Step 5 gives you bonus ideas, chosen and reasoned. Turning the one you pick into a finished file is your part, and my bonuses cover the build side of that
  • Google Docs and login-gated pages get pasted in by hand — a Ctrl+A, Ctrl+C job, and it explains exactly why
Who it's for: affiliates who want a bonus angle nobody else on the launch will have; product creators entering a category that already has winners; W+, JVZoo and ClickBank sellers who want to see what the top offers are really doing; freelancers producing a page for a niche they do not know yet. Best value: Pro, if you have ever thought about building your own product — the second tab is a different job, and it is the one my bonuses were made for.

What I'm adding on top

Look at where the Pro tab lands you: a build spec headed "Build it: a spec for Claude Code." What the thing is in two sentences. The one mechanism it lives or dies on. A v1 feature list with an explicit not building this in v1, and here is why section. A pass separating the page's real mechanical features from its marketing. A deliberately boring stack. And as the last line, the first command to run.

That is a great place for a research tool to hand off. It has done the hard, unglamorous half and points you at the terminal with the thinking already done.

My six bonuses are the next twenty minutes. Which plugins to install first, the project file that keeps the build inside the spec's own "not in v1" lines, the commands that matter, the rollback that saves your afternoon, and a memory so the agent stops asking who your audience is. Free through my link, on either tier.

📦 Package 1 — SET UP

From never having opened a terminal to a working build on a live URL — then the plugin stack that makes every session after it better. Value $164.

🎬

Claude Code in 20 Minutes The centrepiece New

A screen recording of a real first session, start to finish — including the part where it breaks.

  • Install, first run, and the one thing that makes people nervous answered in ten seconds: it can see one folder and nothing above it
  • /init, then the two sections it will never write for you — and why those two decide whether your build finishes
  • Plan mode on a real brief, with me disagreeing with the plan and changing it in chat instead of in code
  • A working single-file tool, built live, then deliberately broken and rolled back — the segment that saves the most time and the one every other Claude Code intro leaves out
  • Live on a real URL at the end. Opened on a phone, on camera
  • Recording drops Friday 7 August. Buy now and it lands on your bonus page the moment it is up — the other five are available immediately
🔌

The Vibe Coder's Plugin Vault New

Eleven free Claude Code plugins and MCP servers worth installing — and, more usefully, the seven you should not.

  • The Starting Four — plan-first workflow, memory between sessions, live version-correct library docs, and a terse mode that meaningfully cuts your token bill
  • Exact install command for each, plus when to skip it — because every plugin you install eats context before you type a word
  • A symptom-to-fix table: "it writes files immediately and sprawls", "session two re-litigates session one", "code looks right but the library rejects it" — each mapped to the one plugin that solves it
  • The install order that works, spread over five sessions rather than one afternoon
  • Nothing here is mine and I earn nothing from any of it. All free, all open source

📦 Package 2 — BUILD

Everything that turns a good specification into a shipped v1 — the project file, the commands, and the working habits. Value $181.

📄

The CLAUDE.md Starter Pack Plugs into Pro's build spec New

Four ready-to-paste project files. Drop one in the folder, paste Pro's spec, and the build stays inside the lines.

  • Four templates as separate files: web app, single-file HTML tool, Chrome extension, and landing/sales page
  • The landing template carries the rule that protects your business: never invent testimonials, prices, results or logos — anything unknown comes back as a visible marker, and the page does not publish with one on it
  • The HTML tool template carries the BYOK pattern and the must still work offline from a file:// URL constraint
  • The 11-section anatomy behind them, including the two sections almost nobody writes — what v1 deliberately does NOT do, and never do this. Page Sniper hands you a "not in v1" list; this is what makes Claude hold the line on it
  • The end-of-session prompt that turns every correction you made into a permanent rule
⌨️

The Claude Code Command Deck New

Twenty commands that decide whether a build ships or sprawls — including four almost nobody finds.

  • /rewind — rolls your code and the conversation back. This one command saves more time than everything else combined, and most people never learn it exists
  • @ file references — the highest-value keystroke in the tool, and invisible in the interface
  • Subagents and /resume, explained in terms of what they stop going wrong
  • Loops done properly: the two parts every loop needs — a condition Claude can verify itself, and a stop limit — plus why "keep going until it's good" costs you money
  • Custom slash commands, hooks, MCP, a full reference table, and the model routing rule
⚡

The Weekend Saver New

Twenty-three operating habits. Nothing to install — this is all things you do differently.

  • Ask for a complexity sort before you ask for code. The single highest-value move on the list: it tells you where the real risk is, and hands you a list you can run on a cheaper model
  • Diagnose before you fix — the prompt that gets an AI to admit it does not know, instead of confidently producing a fix for a problem it never understood
  • One change at a time, commit on green, timebox every bug at twenty minutes, ship at ugly, set a cut-line before you start
  • Clear vs compact, and why using the wrong one keeps dead context in your window forever
  • Ends with a copy-paste pre-flight prompt — the five questions to ask before a single file gets written, which is the difference between a v1 and a fortnight

📦 Package 3 — REMEMBER

Page Sniper remembers the offer. This is the brain every project you run reads from. Value $97.

🧠

The Second Brain Build New PDF + Obsidian starter vault

A knowledge base that compounds instead of resetting. Claude Code writes it, Obsidian is how you steer it, every project you run reads from it.

  • Built on Andrej Karpathy's LLM Wiki pattern, and the difference from uploading files to an AI is the whole point: retrieval makes the model rediscover your knowledge on every question. A wiki compiles it once and keeps it current — new sources get integrated into what already exists, contradictions get flagged, cross-references are already there
  • The three layers: immutable raw sources you never let it edit, the wiki it owns entirely, and the schema file that turns it from a chatbot into a disciplined maintainer. That file is the whole game and it is why most people's attempts produce sludge
  • Obsidian as the management layer — graph view to spot orphans, backlinks, Bases dashboards, and the Web Clipper: any article, sales page or forum thread into your vault in one click. Agent on one side, vault on the other, watching pages change as it works
  • The three operations — ingest (one source touches 10–15 pages), query that cites your pages rather than training data, and lint for contradictions, orphans, stale claims and gaps. Plus the move almost everyone misses: file good answers back as pages, so your own thinking compounds too
  • Every project reads from the same vault. The read protocol you drop into each project's CLAUDE.md — this is what turns a personal wiki into infrastructure. Write a page in one project and it already knows your voice, your audience's objections and how the last three launches went
  • Getting outside data in: Web Clipper, MCP so the agent reads and writes the vault directly, transcripts, exports, and an autonomous research loop that files its own homework
  • And what a marketer's vault actually holds — offers with real EPC and refund rates, vendor track records, audience language in their words, decisions with their reasons attached, and launch post-mortems. The pages nobody writes and the ones you will be glad exist in a year
  • The starter vault: a working Obsidian vault — three-layer structure, a marketing-specific schema file, index/log/hot-cache, and one worked example page per type
Total bonus value $442 — yours free with Page Sniper (Core $12.95 or Pro from $27) through my link.
⚡ Get Page Sniper + All 6 BonusesCore $12.95 · Pro from $27 · 30-day refund

Take Pro and three more unlock

Take Pro or any upgrade in the funnel and these three come with it. The build spec ends at "what done looks like for v1" — a good place to stop. These carry you from a working v1 to something you can take money for.

🛠️

Beyond Web Apps: The AI Tool Builder's Playbook Upgrade bonus

Pro's spec opens by deciding what the thing is. This is what to read before you let it decide.

  • The formats past a web app — extensions, server tools, agents, embedded helpers — and which one a given gap actually wants
  • How to choose the shape before you choose the stack, which is the decision that quietly costs people a month
  • Pairs directly with Pro's build spec: read this before you paste the spec, not after
  • Value $97
⏱️

24 Hours Software Building Upgrade bonus

The compressed-timeline method: idea to shipped software inside a day.

  • The scoping discipline that makes a 24-hour build possible — mostly a list of things you agree not to do
  • Where to cut, what to fake, and what genuinely cannot be skipped
  • Reads as the practical companion to the spec's three-group feature list — must have, should have, and deliberately not in v1
  • Value $67
⚖️

The Legal Pages Vault The one nobody thinks about Upgrade bonus

You are about to publish a product and take money for it. These are the pages that has to sit behind.

  • Ready templates: privacy policy, terms, earnings disclaimer, refund policy, affiliate disclosure
  • The GDPR-facing basics for selling to anyone in Europe, in plain English
  • This is the bonus people ignore right up until a marketplace review or a payment processor asks for it — and then it is urgent
  • Value $47
Upgrade bonuses: $211 more — unlocked with Pro or any upgrade in the funnel.

Claim them at imdominator.com/bonus-claim — paste your WarriorPlus receipt, pick the bonus from the dropdown, confirm.

How to claim your bonuses

  1. Clear your cookies (or open a private window) so my affiliate ID is the one that registers.
  2. Grab Page Sniper through this link — Core at $12.95, or Pro from $27 if you are building your own product.
  3. Check your WarriorPlus purchase page. Bonuses from affiliates appear under your transaction — look for my bonus delivery link there.
  4. Anything missing? Email me your receipt ID at affilateprofitblog@googlemail.com and I'll send everything manually within 24 hours.

Questions, answered

What does Page Sniper actually do?

It is a Chrome side panel with two tabs. Promote an offer walks six steps: collect the vendor's JV page, JV doc and swipes and read them together; tear down the sales page for its hook, subhead sequence, trust signals and copywriting framework; pull the marketplace stats; optionally read your live Google results plus the Meta and Google ad libraries; work out where the buyer stalls after paying and get five bonus ideas that remove it; then generate a presell brief, five emails and four video scripts. Beat a winner is the Pro tab and takes the same research somewhere else — see the next answer.

What does the "Beat a winner" tab do?

It is for building rather than promoting. It carries the Core research across, scores your existing product against a page that already converts (or takes an "I'm starting from scratch" path), then writes a build spec you paste straight into Claude Code: what the thing is, the one mechanism it lives or dies on, a v1 feature list with an explicit "not in v1, and why" section, a split between the page's real mechanical features and its marketing, the user's path screen by screen, a boring standard stack, and the first command to run. It also suggests product names, rewrites the winner's page around your product, and can reduce several winning pages to one composite blueprint.

Do I need an API key?

The live page reads are keyless. The AI steps use your own OpenAI, Anthropic, Gemini or Grok key, stored on your device only — or you copy the prompt and paste it into any of those on a free account. There are no credits sold by the vendor.

Core or Pro — which should I take?

If you only promote other people's launches, Core does the job at $12.95. If you have ever thought about building your own product, take Pro — the Beat a Winner tab is a different job, not a bigger version of the same one, and it is what my bonuses were built around. Core buyers still get all six bonuses; the skills apply to the presell page you have to build either way.

Do I need to know how to code to use Pro?

No, and this is the question most people are actually asking. Pro writes the specification; Claude Code does the building. What you need is the ability to start a session, read a plan, say no to it, and roll back when something breaks. That is judgement rather than coding, it takes about twenty minutes to learn, and it is exactly what my six bonuses teach.

Why does the Pro price keep changing?

It is a dimesale. Pro opened at $27 and rises ten cents every time somebody buys, stopping at $37. Whatever the button says when you load the page is what you pay, and it does not go back down. Core is $12.95 for 72 hours, then $19.

Is it a subscription?

No. One payment on both tiers, with a 30-day money-back guarantee — deliberately longer than the launch, so you can run it on a real promotion start to finish.

What about pages behind a login, or Google Docs?

You paste the text in yourself. The tool is upfront about why: Google draws document text on a canvas rather than putting it in the page, so there is nothing to collect, and it will not download the doc unless it is shared publicly. Select all, copy, paste. Same for anything behind a login. Some competitor pages and ad libraries also block reading — it tells you that rather than handing you an empty analysis.

Is this a scraper? Will it get me in trouble?

It reads pages you open in your own browser, on your own device — the same pages anyone can visit. The competitor list comes from a Google search you ran yourself, and the ad data comes from Meta's and Google's own public ad libraries, which exist so that ads can be inspected. You are asked once to approve reading external pages and that permission stays on your device.

What do the bonuses actually add?

They cover the next twenty minutes after Pro hands you the spec. A recorded 20-minute first Claude Code session — install to live URL, including a deliberate break and a rollback. A curated vault of eleven free plugins and MCP servers with what each one changes and which four to start with. Four ready-to-paste CLAUDE.md project files. A command reference covering the ones almost nobody finds. Twenty-three working habits. And a seven-file second brain so the agent knows your business without being told each time. Take Pro or any upgrade and three more unlock, covering what happens after the build.

What happens when this launch closes?

According to the vendor, this page comes down and Page Sniper moves to a single full version at $97, with the $12.95 and $27 options no longer existing and no upgrade path between them. Check the current terms on the order page before you buy.

The vendor offers a 30-day money-back guarantee on both tiers. Check the current terms on the order page before you buy.

The pages already making money in your niche will tell you how they do it

Page Sniper does the part almost nobody has the patience for: reading every document around a launch, reconciling them into one picture, and working out from the funnel itself where the buyer gets stuck after paying. That is your bonus angle, your email angles, and — on Pro — the specification for a product that removes it. Take it up to the first command, and my six bonuses handle everything after that.

⚡ Get Page Sniper + My $442 Bonus StackCore $12.95 · Pro from $27 · One-time · 30-day refund
✓ Instant access ✓ 6 bonuses delivered on your purchase page ✓ 3 more with Pro ✓ 30-day refund
Wait — before you go

Grab my free 7 Vibe-Code Killers 🎁

Seven things that quietly kill an AI-built page or tool — and every one of them is invisible until somebody else finds it.
The checklist I run before anything I build goes live.
Email in → PDF out — plus my private WhatsApp group where I post what's working right now.
Takes 10 seconds. Don't overthink it.