Competitive intelligence in SEO usually means looking at a competitor's page once and writing it down. Three months later you look at the same page, it has moved up in the SERP, and you have no idea what they changed. The page still "looks the same." You can't scroll through a year of edits to find what they added. You make a guess and move on.
Paid monitoring services solve this — VisualPing, ContentKing, Wayback-Machine-based tools — but most come with a monthly subscription and a complicated dashboard. For most operators, the question is narrower: "what changed on these twenty pages I care about, since I last checked?"
The Content Velocity Monitor answers exactly that question, for free, with no signup. Snapshots live in your browser's localStorage. Every snapshot is timestamped and labeled. Re-running the tool next week produces a diff showing word-count delta, H2 changes, schema changes, and date-field changes for every URL in the list.
How Snapshots Work
You paste a list of URLs (yours, competitors', or a mix) into the watchlist. You optionally add a label for the run — "Q2 2026 baseline" is useful. Click Snapshot now and the tool fetches each URL through the same Netlify proxy the other jwatte.com tools use, extracts a structured fingerprint, and stores it.
Each snapshot per URL stores:
- Title and meta description
- H1s and H2s (full text)
- Schema types detected in JSON-LD
- Word count of the main content (boilerplate stripped)
article:published_time,article:modified_time, andtime[datetime]values where present
That's enough to detect every substantive change short of a complete rewrite, without storing the full HTML (which would blow through localStorage in a few snapshots).
Comparing Snapshots
The history table lists every snapshot with its timestamp and optional label. Below it, you pick a URL, a from-snapshot, a to-snapshot, and click Compare.
The change report shows:
Word-count delta — the headline number. A +400 word delta on a competitor's page since your last snapshot is a signal they did a serious refresh.
H2 added / H2 removed — the most informative diff. If a competitor added three H2s covering subtopics you don't cover, that's a direct editorial signal about where they think the ranking game is heading.
Schema added / Schema removed — a competitor that added FAQPage or Speakable schema since your last snapshot just upgraded their rich-result eligibility.
Title / meta changed — shows the before and after text when the title or meta description was rewritten.
Date fields changed — article:modified_time moving forward tells you when the page was edited, even if nothing substantive changed. Useful for confirming "they touched this page" versus "they left it alone and got lucky."
Data Lives in Your Browser
Snapshots are stored in localStorage under a single key. This has three implications worth knowing.
It's persistent across sessions. Close the browser tab, come back next month, your snapshots are still there.
It's per-browser. Snapshots taken on your laptop don't sync to your phone. The export button produces a JSON file you can move between browsers or share with a colleague.
It's bounded. localStorage has a ~5–10MB cap in most browsers. Each snapshot is small (a few KB per URL), so you can hold hundreds of runs across twenty or thirty URLs before the cap matters. If you're tracking a hundred URLs weekly for a year, export and clear periodically.
Import / Export
The Export button produces a JSON file dated with today. The Import button accepts any previously-exported file and restores the history exactly. This is how you move monitoring data between machines, archive a client engagement, or share a baseline with a colleague who wants to start monitoring the same URLs.
When to Run It
Weekly on your top-priority competitor pages. Pick the five pages you'd most hate to let pull ahead of you. Take a baseline snapshot this week, then run the tool Friday afternoons. Thirty seconds per week surfaces every meaningful change.
Monthly on your own content. If you have a team editing pages, a monthly snapshot keeps a record of what changed and when. Great input for post-mortems when a rewrite helps or hurts.
Before and after an algorithm update. When Google ships a core update, snapshot the top ten ranking pages for your priority queries the day before and the day after. When the update settles, you'll see who added what in the days following — which is often the clearest signal about what Google actually rewarded.
At the start and end of a quarter. Run a comprehensive snapshot at the start of Q2 and another at the end. Compare. The diff is your quarterly competitive intelligence report, assembled in under an hour.
Honest Limits
The tool reads static HTML. If a competitor's page is rendered client-side by JavaScript, the fingerprint will be thin. This is usually only an issue with React/Vue apps that don't server-render for bots.
Snapshots don't capture images, videos, or non-text content changes. A competitor that replaces their hero image wouldn't register as a diff.
The tool is per-URL. It doesn't monitor "new pages appearing on a competitor's site." For that, watch their sitemap.xml or subscribe to their RSS feed — a different job.
Everything is local. Losing your browser profile (OS reinstall, "Clear all site data") loses your history unless you've exported. Build an export into your monthly routine.
How This Fits the Methodology
Content monitoring at scale is $100 Network territory — Chapter 26 (Monitoring at Scale) walks through dashboards that track sixteen-plus properties. This tool is the per-URL version: snapshot, store, diff. For agency work, the $20 Agency 90-Day Playbook (Chapter 30) is measured by what you published and improved, and velocity snapshots are the timestamped record of that work. For $97 Launch operators, Chapter 35's competitive auditing chapter is the static view; this is the time dimension that chapter doesn't capture.