◆ HTML

Monitor web pages for changes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCheck the competitor's pricing page, 'Acme Solutions', every morning this week. I need to know…+
Check the competitor's pricing page, 'Acme Solutions', every morning this week. I need to know if they change their 'Pro' tier features or pricing before our strategy meeting on Friday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptI need to keep a close eye on the content structure of the 'Acme Solutions' competitor's…+
I need to keep a close eye on the content structure of the 'Acme Solutions' competitor's pricing page. Set up a system to notify me immediately if any changes occur to their 'Pro' tier features, pricing, or the overall layout, so we can react quickly to their moves.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur main competitor, 'Acme Solutions', just updated their product page, and I only found out…+
Our main competitor just updated their product page, but I only caught it because a customer mentioned it.
Our main competitor, 'Acme Solutions', just updated their product page, and I only found out because a customer mentioned it. My current monitoring system for their website content didn't flag anything. I'm afraid I'm missing critical changes. What's the likely reason my current setup failed, and what's the best next step to ensure I don't miss anything important again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find myself surprised by competitor website changes, especially on their product…+
I'm always surprised by competitor website changes, impacting our marketing response time.
I consistently find myself surprised by competitor website changes, especially on their product and pricing pages, which means our marketing team is always playing catch-up. This impacts our response time and market position. What habit should I change in how I monitor competitor website content to ensure I'm always ahead of their moves?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from HTML's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.