Your site changed. Did the campaign find out?
The ad keeps delivering, the site keeps responding, and the gap between the two only shows if somebody compares them on purpose. Oracle compares — every day — and tells you when what changed changes what the campaign should be advertising.
Included in every plan. Reading and comparing do not consume AI credits.
What reaches you
Broken page
/servicos/mreach
Has been answering 404 since yesterday and is still taking clicks from the “Sites e e-commerce” ad group. Pause the group or point it at /servicos.
Página nova
/enterprise
“Enterprise plan, above 60 campaigns”. No ad group advertises this. Worth a group of its own with “google ads for agencies”.
Examples of the real alert format. Nothing is changed in your account unless you say so.
Why it exists
Three times in one month, in our own account.
This is not hypothetical. These are the cases that got this feature written, with the date each one happened.
The new page nobody advertised
We published the Enterprise plan page. The campaign carried on sending everyone to the home page for days, and nobody searching for management at scale ever saw the page written for them.
Six service pages, zero ads
A partner site had six service pages live for months. Every ad pointed to the home page — R$ 715 in 30 days taking people with a specific intent to a generic one.
Twenty-five invisible features
Another product published 25 feature pages, each one answering a search. The campaign was still bidding on generic terms, against the people who sell exactly that.
In none of the three was there an error on screen. The campaign was delivering, the site was responding, and the money went out pointing at an old version of the product.
How it works
It reads, compares, and only then judges.
The order matters: comparing is cheap and deterministic, judging costs money and is where excess lives. Almost everything dies before it reaches the model.
- 1
Reads the site like a reader
Once a day, Oracle takes the public routes — from sitemap.xml, or from the home page links when there is no sitemap — and stores the title, the description, the sections and a summary of the text of each one.
- 2
Compares it with yesterday
A page that appeared, a page that vanished, a page that started answering with an error, a rewritten title, a new section. The comparison is between two whole versions, not between loose lines.
- 3
Says what to do about it
Only what survives the filtering reaches the AI, which answers in Portuguese: does this change what the campaign ought to advertise? If it does, which ad group, which keyword, which landing page.
What reaches you
An alert that fires every day is not an alert.
The hard part is not detecting a change — it is deciding what deserves to interrupt someone. Half of this feature is what it deliberately does not report.
Avisa
- A new page the campaign does not advertise yet
- A landing page that started answering with an error
- A rewritten price, offer or value proposition
- A new section describing something the ad does not mention
- A page that went offline and still takes clicks
- A changed title and description — what Google reads first
Fica quieto
- Rotating banners and testimonials that change on every visit
- The date in the footer, a visitor counter, a new post on the blog
- Bundle hashes and attribute order, which change on every build
- Sections reordered with no new text
An alert that shows up every day is an alert nobody reads — precisely in the week the genuinely new page is born.
Questions
What people usually ask
- How often is the site read?
- Once a day, per campaign. The crawl visits up to 30 routes, one at a time and with a pause between them — it identifies itself in the User-Agent as OracleAdvisorSiteWatch, so whoever runs the site can recognise it and, if they prefer, block it.
- Does this spend AI credits?
- Reading and comparing spend nothing. The model is only called when the comparison finds something that got past the filters — a new page, a broken page, a new title or section. A site that has not changed costs nothing, and nor does a site where only the footer changed.
- Do you store my site's HTML?
- No. For each route we store the title, the description, the section headings and a hash of the visible text — what a person would read. The whole HTML changes on every build because of bundle hashes and attribute order, so storing it would produce 'everything changed' every day, besides becoming an archive of other people's sites growing with no use.
- Can I watch a site that is not mine?
- The field accepts any public address, and there are legitimate uses — following a partner's page, for example. But the feature was built for the site the campaign advertises: that is where a change becomes an advertising decision.
- What happens when it finds something?
- It appears on the campaign's Observar URL tab — the product interface is in Portuguese — with what changed, why that matters and a suggestion you can apply: which ad group, which keyword, which landing page. Nothing is changed on its own inside your Google Ads account.
It is included in every plan, and it lives in the Observar URL tab of every campaign.
Try the platform