Can I add these checks to the deployment pipeline instead?

If you control the pipeline, yes, and it is worth doing: a test that fails the build when a production page contains noindex catches the problem before release. On client sites you usually do not control the pipeline, which is why monitoring the live site is the fallback.

Does a CDN or cache affect what monitoring sees?

It can. If a CDN serves a cached version, the monitor may see the old or new HTML for a while after a deploy. When an alert looks odd, check the response headers (for example cf-cache-status on Cloudflare or Age) to see whether you are looking at a cached copy.

Which change should I fix first if several appear together?

Anything that removes pages from search comes first: noindex, robots.txt Disallow rules and canonicals pointing elsewhere. Missing analytics tags come next, because every day without them is data you cannot recover. Title and meta changes can follow.

Does Deltio monitor pages that are not in the sitemap?

Deltio builds its page list from the sitemap, so URLs missing from it are not checked on the daily cycle. That is one more reason to fix a sitemap that leaves out important pages.

How much does Deltio cost?

Starter is £24 a month, or £20 a month billed annually, for up to 50 sites and 5,000 URLs. Professional is £49 a month (£41 annually) for up to 200 sites, and Enterprise is £119 a month (£99 annually) for up to 500. Every plan has a 14-day free trial.

← Back to the blog

Website Code Change Monitoring: Catch the Deploy That Broke Your SEO

Website code change monitoring means watching a site's live HTML for the edits search engines and analytics depend on, and getting an alert when one appears. A developer deploys, no ticket mentions SEO, and a rewritten title, a moved canonical or a missing GA4 tag stays in production until someone goes looking.

Agencies see a version of this regularly. Rankings slide for a month, someone digs in, and the cause is a template change from a routine release. The development team did nothing wrong by their own standards: the page renders, the tests pass, the client signed off on the design. What changed is the part of the markup that only crawlers and tracking scripts read.

Which parts of the markup to watch

Most of a page's code can change freely without SEO consequences. A small set of elements cannot.

Element	How it tends to break	Effect
`<meta name="robots">` and `X-Robots-Tag`	A staging setting or environment variable shipped to production	Pages removed from the index
`<link rel="canonical">`	New template builds it from the wrong URL, or points to a staging host	Google indexes a different URL, or ignores the page
`<title>` and meta description	SEO plugin reset, or a template that overrides per-page fields	Lower click-through, sometimes lower relevance
`<h1>`	Redesign turns the headline into a styled `<div>`, or the logo becomes a second H1	Weaker on-page topic signal
GA4, GTM, Meta Pixel snippets	A new build drops the container from the layout	Reporting and ad attribution stop
Cookie consent banner	CMP swapped or removed	Tags blocked, or firing without consent

robots.txt is not in the page HTML, but it changes in the same releases and deserves the same attention. A Disallow: / left over from a staging environment does more damage than every item in the table.

Source HTML versus rendered HTML

On a server-rendered site, the HTML the server returns is what matters. On sites built with React, Vue or similar frameworks, the head tags may be set by JavaScript after the page loads, so the raw source and the rendered DOM can differ. Google renders JavaScript, but a canonical that exists only after rendering, or one that differs between source and rendered versions, is a common source of confusion. When you investigate a change, compare view-source: with the Elements panel in DevTools, and use the URL Inspection tool in Search Console to see the rendered HTML Google recorded.

Why the usual signals arrive late

Your team is probably not on the client's deploy notifications. Search Console reports consequences rather than causes: pages move into "Excluded by 'noindex' tag" in the Page indexing report only after Google has recrawled them, and the report updates with a delay. Rank trackers show the drop once it has happened. And nobody opens the source of a page that looks fine in a browser.

That window is where silent SEO changes do their damage, and the answer is a comparison that runs whether or not anyone remembered to look.

What useful change detection reports

It compares instead of checking presence. Knowing that a title exists is worth little; knowing it read "Men's Running Shoes | Brand" yesterday and "Collection" today is what you can act on. It works per URL, because template changes usually affect one section, not the homepage. And the alert carries the URL, the old value, the new value and the date, which is exactly what you need to send the client.

Handling the alert

Load the page in a private window to rule out caching. Decide whether the change was deliberate: a copywriter's improved title needs nothing, while a canonical pointing at a staging host needs fixing today. Send the client the evidence and ask what went out that day. If the change turns out to be part of a redesign or replatform, stop fixing URLs one at a time and work through the website migration SEO checklist.

What Deltio compares, and what it does not

Deltio reads each site's sitemap and pages once a day and compares the result with the previous check. On each page it looks at noindex, canonical, title, meta description and H1, flagging values that are missing, duplicated or out of range and alerting when they change. It also checks robots.txt, URLs added to or removed from the sitemap, GA4, GTM and the Meta Pixel, and the cookie consent banner. Alerts go to Slack and email per site. After a release you know about, you can run a manual SEO scan instead of waiting for the next daily check, and Professional and Enterprise plans can export results to CSV.

It does not do visual diffing or screenshots, and it does not diff arbitrary code such as scripts or CSS. It focuses on the elements above. It also runs daily, so it is not a replacement for tests in a deployment pipeline. Marketing tag monitoring covers the tracking side in more depth.

Frequently asked questions

Can I add these checks to the deployment pipeline instead?: If you control the pipeline, yes, and it is worth doing: a test that fails the build when a production page contains noindex catches the problem before release. On client sites you usually do not control the pipeline, which is why monitoring the live site is the fallback.
Does a CDN or cache affect what monitoring sees?: It can. If a CDN serves a cached version, the monitor may see the old or new HTML for a while after a deploy. When an alert looks odd, check the response headers (for example cf-cache-status on Cloudflare or Age) to see whether you are looking at a cached copy.
Which change should I fix first if several appear together?: Anything that removes pages from search comes first: noindex, robots.txt Disallow rules and canonicals pointing elsewhere. Missing analytics tags come next, because every day without them is data you cannot recover. Title and meta changes can follow.
Does Deltio monitor pages that are not in the sitemap?: Deltio builds its page list from the sitemap, so URLs missing from it are not checked on the daily cycle. That is one more reason to fix a sitemap that leaves out important pages.
How much does Deltio cost?: Starter is £24 a month, or £20 a month billed annually, for up to 50 sites and 5,000 URLs. Professional is £49 a month (£41 annually) for up to 200 sites, and Enterprise is £119 a month (£99 annually) for up to 500. Every plan has a 14-day free trial.