Competitor Watch Example: SEO Changes Between Crawls
This example shows the aiwebpageseo Competitor Watch for a digital marketing agency tracking a direct competitor. The weekly crawl detected 3 new pages, 1 deleted page, 2 title tag changes and a new FAQ schema block added to the homepage.
| Change type | URL | Detail |
|---|---|---|
| NEW PAGE | /seo-audit-tool/ | New landing page targeting "seo audit tool" — 1,200 words, FAQ schema |
| NEW PAGE | /seo-checker-free/ | New page targeting "free seo checker" — thin content, 280 words |
| NEW PAGE | /blog/core-web-vitals-2026/ | New blog post — 2,400 words, no schema |
| TITLE CHANGED | /pricing/ | Was: "Plans & Pricing" → Now: "SEO Tool Pricing — From £9/mo" |
| TITLE CHANGED | / | Was: "SEO Tools" → Now: "Free SEO Tools for Small Business | BrandName" |
| DELETED | /old-feature/ | Page removed — was returning 200, now 410 |
| SCHEMA ADDED | / | FAQPage schema added — 5 questions targeting "what is seo" cluster |
Seven changes in a week. Every one of them was a decision somebody made, funded and shipped — which is what makes the report valuable and also what makes it dangerous. The value is the lead time: you are seeing where a competitor is placing effort weeks or months before any ranking movement it causes shows up anywhere.
The danger is reflexive symmetry. They launched a landing page, so we launch a landing page. They added schema, so we add schema. Do that consistently and you have handed authorship of your roadmap to a company whose strategy, constraints and customers are not yours — and the result is reliably a slightly worse version of their site. A competitor's move is evidence about what they believe. It is not evidence that they are right.
The useful discipline is to read the week's changes, write down the belief each one implies, and then ask whether you share it. Most weeks the honest answer is that nothing here changes what you were going to do, and the correct response is to do nothing.
| Change | What it probably means | Your move |
|---|---|---|
| /seo-audit-tool/ | A serious, funded attempt at a head term — 1,200 words with FAQ markup is a page somebody was paid to write. | If you compete for that term, read the page properly. If yours is worse, that is the finding. |
| /seo-checker-free/ | 280 words is a placeholder. They are staking a claim on a term they have not yet decided to invest in. | Nothing. A thin page is a weak competitor, not a threat. |
| /blog/core-web-vitals-2026/ | 2,400 words, no schema. The absence of markup is the tell: this is a content play, not a technical one. | Read it for what it says about their positioning. Do not write your own unless you know something they do not. |
| Title changes ×2 | They have reassessed which queries the homepage and pricing page should serve. | Check what Google actually displays for their pages before assuming the new title is the one users see. |
| /old-feature/ → 410 | A deliberate retirement. They have abandoned whatever that page held. | The most actionable line on the report. If it ranked for something you want, that ground is now vacant. |
| FAQPage schema added | Probably added in pursuit of a rich result that no longer exists for sites like theirs. | Do not copy it reflexively. See below. |
A competitor adding FAQPage markup to their homepage is exactly the sort of change that triggers an unthinking match. Before you schedule it, understand what it does and does not do in 2026.
Google restricted FAQ rich results to recognised government and health sites in 2023. An SEO tool's homepage will not receive FAQ dropdowns in search results regardless of how correct the markup is. Google also removed HowTo rich results entirely. If your competitor added FAQPage schema expecting a SERP enhancement, they have invested in an outcome that was withdrawn.
That does not make the markup worthless. FAQPage schema makes a page's question-and-answer structure explicitly machine-readable in the served HTML, which helps any parser — including retrieval systems that fetch rather than render — identify which sentence answers which question. That is a clarity benefit and it is worth having if the questions and answers genuinely exist on the page.
The order is not negotiable: write real answers first, mark them up second. A page whose FAQ answers live only inside JSON-LD, or only inside a collapsed accordion that renders client-side, has given a parser structure with nothing behind it — and structured data that does not describe the visible page is a policy violation, not an optimisation.
Everyone reads the new pages and skips the deletion. That is backwards. Launching a page is cheap and speculative; retiring one is expensive and deliberate, because it abandons whatever rankings, links and history the URL had accumulated. Nobody does that idly.
A 410 Gone is a stronger statement than a 404: it declares the resource permanently removed rather than merely absent. In practice Google treats the two almost identically, with 410 usually processed a little faster — the real signal is the intent behind it. Either the feature the page described no longer exists, or they concluded the page was a liability.
Either way, check what /old-feature/ used to rank for. If it held positions on a term you care about, that term has just become less contested, and moving into vacated ground is far cheaper than attacking a page somebody is actively defending. This is the one line on the report that might justify changing your plan this week.
Two title rewrites, both moving from short and brand-led to longer and query-led. The temptation is to conclude that longer, keyword-front titles work and to rewrite yours to match. Two things make that a bad inference.
First, you do not know whether it worked. You are watching an experiment in progress, and you will not see the result — they may well revert it in three weeks. Copying somebody else's untested hypothesis is not competitive intelligence, it is guessing at one remove.
Second, the title in the HTML is not necessarily the title in the results. Google rewrites titles for a substantial share of queries where it judges the supplied one a poor fit, typically drawing on the H1 or other on-page text. So the string in their source may never be seen by a searcher, and matching it is matching something invisible.
Change your titles when they misdescribe your pages, or when they are missing the term the page is genuinely about. That is a reason. "The competitor changed theirs" is not.
What is competitor watching actually good for?
Knowing what a competitor is investing in, before the results show up in a rankings report. A new landing page, a rewritten title, a new schema block — these are decisions somebody made, and they are visible weeks or months before any ranking movement they might cause. That lead time is the whole value. It is not a tool for copying: reproducing a competitor's page inventory produces derivative content that ranks poorly and teaches you nothing. It is a tool for noticing where they think the opportunity is, and then deciding independently whether you agree.
They added FAQPage schema to their homepage. Should I?
Not because they did, and not for the reason they probably did it. FAQ rich results were restricted by Google to recognised government and health sites in 2023, so an SEO tool's homepage will not get FAQ dropdowns in search results no matter how clean the markup. If your competitor added it expecting an enhancement, they have spent effort on something that no longer exists. FAQPage markup is still worth having where a page genuinely contains questions and answers, because it makes that structure machine-readable in the served HTML. Add it if you have real Q&A on the page. Do not add it as a SERP play, and do not invent questions to justify it.
Their new page is only 280 words. Does thin content still get penalised?
There is no thin-content penalty in the technical sense — no sanction is applied and nothing appears in Search Console. What happens is more mundane and just as costly: a 280-word page competing against thorough answers is simply a worse answer, so it ranks below them, and if a site accumulates hundreds of such pages the overall assessment of the site's content can suffer during a core update. So the competitor's thin page is not a violation to report; it is a weak page, and it tells you they are prioritising coverage over quality on that term. That is intelligence, not a reason for satisfaction.
A page changed from 200 to 410. What does that signal?
That they removed it deliberately. A 410 Gone is an explicit statement that the resource is permanently removed, as opposed to a 404, which says only that it is not there. Google treats them almost identically in practice, with 410 tending to be processed slightly faster. The strategic reading matters more than the status code: retiring a page means abandoning whatever rankings and links it held, and companies do not do that casually. Either the feature it described is gone, or they concluded the page was doing more harm than good. If it was ranking for a term you also care about, that term is now less contested.
Their title changed from 'SEO Tools' to a longer, keyword-led title. Is that worth copying?
Copy the reasoning, not the string. A title serves two masters — it is a strong relevance signal and it is the line a human reads before deciding whether to click — and a competitor's rewrite tells you they made a judgement about which of their queries mattered. Note also that Google rewrites titles in results a substantial share of the time when it judges yours a poor fit for the query, so their new title is not necessarily the title being displayed. Before you change yours, check what is actually shown in the SERP, and change it only if your current one genuinely misdescribes the page.
How often should a competitor crawl run?
Weekly is right for almost everyone, and the reason is that the decisions you are watching for take weeks to make and months to pay off. Daily crawling produces noise — A/B test variants, staging leaks, transient deploys — and it invites the worst behaviour this kind of tool encourages, which is reacting to every change a competitor makes. If a specific launch is expected, tighten the cadence temporarily. Otherwise, once a week gives you the signal without the compulsion to respond to it.
What should I actually do with a weekly change report?
Read it, write down what it suggests they believe, and then almost always do nothing. The failure mode of competitor watching is reflexive symmetry: they built a comparison page, so we build a comparison page; they added schema, so we add schema. That produces a roadmap authored by your competitor and a site that is a slightly worse version of theirs. The report earns its keep when it changes a decision you were already weighing — confirming that a market you were considering is being actively contested, or revealing that a term you assumed was locked up has just been vacated.
Related
⚔️ Watch Your Competitors for Changes
Set up a weekly or monthly watch on any competitor URL. Get notified of new pages, deleted pages, title changes and schema updates. Pay once per watch period.