Prove a competitor page changed with two dated copies and a note

Monitoring-tool guides such as Visualping's competitor tracking post and PageCrawl's setup guide (both read 2026-09-16) center their monitoring products. This lesson instead teaches a vendor-independent pair of dated snapshots that you keep outside a tool dashboard.

Save a dated copy of the section that matters

Pick one section. A pricing table, a plan-limits list, an integrations grid, the headline and first paragraph of a positioning page. Whole-page copies bury a real change in navigation, footer and blog-carousel noise.

1. Open the page as a logged-out visitor

   Use a private window so you see what a prospect sees, and note the URL exactly as shown. Check: the URL in your note matches the address bar, including any region or plan parameter.

2. Copy the section as plain text

   Paste it into a file named for the competitor, page and date, for example acme-pricing-2026-09-14.txt. Check: the prices and plan names in the file match the screen. Copy-paste from a heavy client-side page sometimes drops table cells; retype the affected rows and say so in the note.

3. Take a full-page screenshot with the same date

   Save it next to the text file under the same name. Check: the screenshot shows the whole section and the address bar. A screenshot without the URL cannot be tied to the page later.

4. Add the capture to your note

   One line per capture: date and time with timezone, URL, section, filenames, and anything you retyped. Check: someone else could find the files from that line alone.

If you have no earlier copy today, this capture is your baseline and the first real comparison comes next time. For a public page, the Internet Archive's Wayback Machine may hold an earlier dated capture; if it does, save that capture's URL and timestamp as your before, and note that the baseline came from the archive rather than from you.

Hand Claude both copies and ask what changed

Paste both text files into one chat, each labelled with its date, and ask for a plain-language list of content changes. Give Claude the copies yourself. A page it fetches during the chat is not a snapshot you hold, carries no date you chose, and may not match what a logged-out visitor saw. The comparison is worth handing to Claude because a reworded pricing bullet is easy to miss by eye across two long tables.

If you check the same competitor repeatedly, work inside the Claude Project you set up for it; the Project setup lesson covers instructions and files. Anthropic's chat search and memory guide, read 2026-09-16, says those features may retrieve earlier context when enabled. Do not rely on them for the earlier page: the dated snapshot is the evidence you can compare and audit. Add each snapshot to Project knowledge as you save it, or paste the older copy into the new chat with the new one.

The wording of the request changes the answer. Ask for content changes in sentences rather than a line-by-line markup dump, and ask Claude to say when it is unsure.

Below are two copies of the same section of [competitor]'s [page], captured on [date A] and [date B]. List what changed in the content, in plain sentences: prices, plan limits, features added or removed, named customers or integrations, and claims. Ignore whitespace, formatting, navigation and layout differences. For each change, quote the before text and the after text. If you cannot tell whether something changed or only moved, say so rather than guessing.

A good answer quotes both versions for every change and names nothing you cannot find in the two files. A bad answer describes the page in general, invents a reason for the change, or reports the same sentence in a new position as a change. Read the quotes against your files before you accept any of it.

Confirm on the live page and write the note

Claude read two text files; it did not see the page. Open the live page again and find each change it named, then add one row per change to your note.

Reference: fields for one change record

A change you could not find on the live page stays out of the record. A copy-paste error, a regional variant, or a page that changed again between capture and check are all ordinary; write down which one you suspect and check again next time.

Decide whether the change is substantive

A change is substantive when it would alter what you tell sales or what you claim about the competitor: a price or plan limit, a feature added or removed, a new named customer or integration, a positioning claim that contradicts your battlecard. A reworded sentence, a moved section, a new footer link or a fresh post in a carousel is not substantive when the meaning survives the edit. Record both kinds; only the substantive ones need to be passed on.

If a substantive change affects a claim on a battlecard, it becomes the evidence for that claim's row; the claim ledger lesson covers how a row is kept. Choosing which pages to watch belongs to the competitive research plan.

Keep snapshots where next month has a before

One folder per competitor, files named by page and date, the note at the top level. Today's copy is the before for the next check, so nothing is deleted. If you use a Project, add the text copies to its knowledge as you go to preserve the exact history. Memory or chat search may retrieve context when enabled, but neither replaces the dated copies. Screenshots stay in the folder; they are for people, and the text copies are what Claude compares.

Set the cadence by how much the page matters. For example, you might check a pricing page every two weeks before renewal season and check a careers page less often. This is an illustrative cadence, not a universal threshold. Write it in the note so a missed check is visible.

When recurring checks become hard to maintain manually

A one-off check to settle a single claim should stay manual. Checking several pages across several competitors every week adds recurring work. Captures may be missed, earlier copies can become stale, and changes between checks wait until the next review. If you want automatic emails without paying, UptimeRobot's free competitor monitoring page, read 2026-09-14, advertises a free tier; the evidence record and the substantive-or-not call still stay with you.

Steve monitors competitor sites and pricing pages and pushes the signal into Slack. Someone still confirms the change on the live page and decides what sales hears. If you are at that point, Steve's competitive intelligence product is the place to look.