A homepage change log for each rival
Keep a dated record of what each rival puts on their home page, their headline, offer and proof, so you can see what they are testing and what they keep.
The problem
Rivals change their home page often, and you only see today's version. You cannot tell whether a new headline is a test, a rebrand or a response to you.
The output
A dated log per rival of the home page headline, main offer, calls to action, proof shown and navigation, with a summary of what changed between snapshots and what it may mean.
Why it matters
The home page is where a business states its positioning in public. Changes to the headline, the main promise or the proof on show tell you how a rival sees its own market. A headline that changes every month suggests testing; one that settles and stays suggests it is working for them.
The competitor website monitor loop is in build and not on sale; when it ships it will capture these snapshots and flag what changed. Until then, a monthly screenshot and a short written record give you the same log, and an Intel loop comparison scores first impressions side by side with quoted evidence.
What you need
- - The home page address of up to three rivals
- - A folder for full-page screenshots, named by rival and date
- - A log sheet with columns for headline, sub-headline, main offer, calls to action, proof shown and navigation items
- - Your own home page, recorded the same way
Setup
- Visit each rival's home page on a desktop and a phone, and take a full-page screenshot of each. Name the files by rival and date.
- Copy the headline, sub-headline and main call to action word for word into the log, and note the main offer and any proof (reviews, awards, guarantees, logos).
- Note the main navigation items in order; changes there often signal a new product line or service.
- Record your own home page in the same way so you can see where you sit.
- Once you have two or more snapshots, paste the log into the prompt below to summarise what changed.
The prompt
Paste this into any capable model, followed by the evidence you gathered in the setup.
You are helping a UK business read changes in its rivals' home pages. Below is a log with one row per snapshot: rival, date, device, headline, sub-headline, main offer, calls to action, proof shown, navigation items. Rows marked OURS are our own home page. Do this: 1. For each rival, list what changed between consecutive snapshots, quoting the before and after wording. 2. Classify each change: new promise, new offer, new proof, new navigation item, design or wording only. 3. For each rival, say what the changes suggest about their direction, marked as a hypothesis, and how confident you are given the number of snapshots. 4. Compare with OURS: where is our headline, offer or proof weaker or less specific than a rival's, quoting both? 5. Suggest up to five changes to our home page, each rated for effort (low/medium/high) and likely impact (low/medium/high), with a reason. Rules: - Quote the evidence for every point, word for word, and say where it came from (which rival, which page or ad, which date I captured it). - Label each point OBSERVATION (you can see it in the evidence) or HYPOTHESIS (your reading of why). Never present a hypothesis as a proven cause. - Never invent a figure, a date, a price or a result. If the evidence does not show it, write "not in the evidence". - Use British English and plain words. Home page log: [paste the log here]
Doing it by hand today
Take the snapshots on the first working day of each month, and add an extra one whenever a rival launches a sale or a rebrand. Keeping to a fixed point in the month makes changes easy to spot.
Visit as an ordinary visitor would. If you automate screenshots, keep to one request per page and respect the rival's robots.txt file.
After a few snapshots the log is a dated record of what each rival tested and what it kept. Read it before you change your own home page.
Sources
- robots.txt tells search engine crawlers which URLs the crawler can access on a site, and is used mainly to avoid overloading a site. developers.google.com/search/docs/crawling-indexing/robots/intro · checked 13 October 2026
Start from a one-off read.
The free Insight Report and an Intel loop are live today, and they are the reads these loops will repeat.