Know when they move.
Add competitors and Crawld crawls and audits their sites weekly, pulls their keywords, and gives you a change feed. Mark as seen and move on.
What it reports
| Tracked | Why it matters |
|---|---|
| Title tags | The clearest sign a page was re-aimed at a different query. |
| Meta descriptions | Usually a click-through experiment. |
| Headings | A new H2 set is a rewritten argument, even if the word count barely moves. |
| Body copy | What changed, not that something did. |
| Pricing | The change most likely to need a response the same week. |
| Links | New internal routes show what they are consolidating around. |
| New and removed pages | A competitor rarely announces a launch or a quiet retirement. |
| Status changes | A page that started or stopped returning 200. |
Reports are diffs, not snapshots. "This H2 changed from X to Y on Tuesday" is actionable. "Here is their current page" is a browser.
Alongside the diff, each competitor gets the same 129-check audit your own site runs, and their target keywords are pulled and kept beside your own. Read as a change feed: mark an entry as seen and it drops off the list.
Polite by construction
Up to 3 competitor sites per brand. 12 pages per site. One request at a time. Once a week. robots.txt obeyed, including crawl-delay. The user agent names the bot and links to a page explaining how to block it. These are not settings; they are how the crawler is built.
Why three sites
Monitoring twenty competitors is a way of monitoring none. Three forces the question of who you actually lose to, which for most sites is a shorter list than the pitch deck.
Not built yet Coming soon
Turning a detected change into a recommended response is not built. What ships is the change detection. The in-app copy says the same.
Competitor tracking is included in Pro. Pricing →