Skip to main content
Back to Solutions

Website Monitoring for Marketers

You don't have to pay for clicks that land on a broken page. WebPixie checks your landing pages on a schedule and emails you when one goes down, starts redirecting or loses its offer or tracking code. No developer needed.

No credit card required·Free plan available

Campaign pages

Your ad is running. Is the page still there?

Every click you pay for while a landing page is down is a click that cannot convert, and Google Ads may disapprove ads whose landing page does not work. You can add each landing page as an uptime monitor and set the status code it should return and a keyword it must contain, such as the headline or the form button. When a check fails, your team gets an email, and from Starter a Slack message too.

A short network hiccup is retried before an alert goes out, and on paid plans a timeout is checked again from the monitor's other selected locations. Response time is recorded on every check from multiple global locations, such as London and New York, so you can see a page getting slower before it starts timing out.

Uptime monitors

Tag: spring-campaign

  • example.com/spring-sale

    Status 200 · keyword found · 412 ms

    Up
  • example.com/webinar

    Status 503 · expected 200

    Down
  • example.com/lp/newsletter

    Status 200 · keyword found · 1,840 ms

    Up

Alert sent by email and Slack

Page changes

Someone changed the page and nobody told you

A redesign, a CMS update or a cleanup can quietly change a page your ads and emails point to. If you turn off follow redirects and accept only a 200 status, the check fails when the page starts redirecting to the homepage. If you add the offer headline or promo code as a "must contain" keyword, it fails when an old version of the page is served.

A "must not contain" keyword works the other way round: if you add words such as "sold out" or "page not found", you hear about it when they appear. Keyword checks read the HTML your server sends, so the words you pick need to be in the page source.

example.com/spring-sale

Check rules

Follow redirects
Off
Accepted status codes
200
Must contain
Spring Sale -20%
Must not contain
sold out

Last check

Keyword missing: Spring Sale -20%

Down

Tracking code

Is your tracking code still on the page?

If an update removes the Google Tag Manager snippet, the campaign keeps running and the data stops arriving. You find out days later, when the numbers look wrong. If you add your GTM container ID or pixel ID as a "must contain" keyword on your key pages, the uptime check fails when it disappears from the page.

This confirms that the code is in the page source, not that your tags fire. Tags loaded through Tag Manager are not in the source, so the keyword to check for is the container ID itself.

Incidents

Tracking checks

  • example.com/webinar

    Uptime · Keyword missing: GTM-XXXXXXX · 3 h

    CriticalOngoing
  • example.com/pricing

    Uptime · Keyword missing: GTM-XXXXXXX · 40 min

    CriticalResolved

Alert sent to every workspace member by email

Search and AI crawlers

One line in robots.txt can shut out search and AI crawlers

A relaunch can ship the staging robots.txt with "Disallow: /" in it, which keeps search engines such as Google and Bing out. The Indexability Checker reads your robots.txt line by line, shows which AI crawlers, such as GPTBot and ClaudeBot, have explicit rules, and lists any Content-Signal directives. It also checks that the file points to your sitemap and validates your llms.txt.

The file is read again every day, so the dashboard shows the version that is live. To get an email, you can add /robots.txt as an uptime monitor with a line you expect to stay, such as your Sitemap line, as a "must contain" keyword. On key landing pages, you can add "noindex" as a "must not contain" keyword.

robots.txt · example.com

Read today

  • GPTBot

    Explicit rule

    Allow /

    Allowed
  • ClaudeBot

    Explicit rule

    Disallow /

    Disallowed
  • Content-Signal

    Directive found

    ai-train=no

    Info
  • Sitemap directive

    Found in robots.txt

    Pass

Broken links

Broken links after a redesign or a cleanup

Deleting old campaign pages or moving to a new site leaves links pointing nowhere. The Link Crawler starts at your homepage, follows internal links up to your plan's limit and crawls again about once a week. It lists pages that return a 404, a server error or a redirect, and shows which of your pages link to each one, so you know which page to edit.

From Starter, Sitemap Monitoring also flags crawled pages that are missing from your sitemap. Results appear in the dashboard after each crawl.

Links · example.com

Crawled 2 days ago

1,284

OK

37

Redirect

9

Broken

Broken links

  • /lp/black-fridayon 14 pages404
  • /blog/2024-guideon 3 pages404
  • /pricing-oldon 2 pages404

Email setup

Your newsletter needs SPF and DMARC set up right

Your newsletter goes out from your domain, and mailbox providers such as Gmail expect bulk senders to publish SPF and DMARC records. DNS Monitoring checks your domain every day and analyzes its SPF, DMARC and BIMI records, with guidance on how to fix what it finds.

WebPixie also keeps a log of DNS changes with the old and new value, so after someone edits your DNS you can see what changed.

Email records · example.com

Checked today

  • SPF

    Record found

    Pass
  • DMARC

    Policy: p=none

    Review
  • BIMI

    No BIMI record found

    Info

SSL and domain

No browser warning, no lapsed campaign domain

A visitor who sees "Your connection is not private" rarely clicks through, whatever the ad promised. SSL Monitoring checks your certificate every day and, by default, warns 15 days before it expires.

Domain Monitoring warns 30 days ahead by default, which matters for a campaign domain that nobody remembers to renew.

Expiration warnings

Campaign domains

  • springsale-example.com

    Domain

    9 days

    High
  • example.com

    SSL certificate

    13 days

    Medium

Team and reports

You know before your boss asks, with facts to forward

By default every workspace member gets the alert email, so you hear about a problem from WebPixie first. From Starter, each one is kept as an incident with its type, start time and duration, and every check records the time, location, status code and response headers. You can send that to your developer or agency instead of "the site is broken".

You can tag monitors by campaign or channel to see one launch at a time. Stakeholders can join the workspace as read-only Users, and every member receives a PDF report on your plan's schedule with the Site Score, uptime and, from Starter, the incidents of the period.

Monthly report

Marketing workspace · December 2026

Sites monitored

3

Median score

84

Incidents

2

Resolved

2

  • Top site by score

    example.com · 0 incidents

    Excellent
  • Needs attention

    springsale-example.com · domain expires soon

    Warning

You can set up monitoring for your next launch

Nothing to install, no code and no developer needed.

  1. 1

    You add your site and campaign pages

    You enter your domain, then add each landing page as an uptime monitor.

  2. 2

    You add keywords and tags

    You pick a word from the page source that must appear, such as the headline, and tag monitors by campaign or channel.

  3. 3

    Alerts go where you work

    Alerts go to every workspace member by email, to Slack from Starter and to webhooks from Pro.

Plans differ in how many uptime monitors you can run, how often they check and how many links each crawl checks. You can compare them on the pricing page.

Frequently Asked Questions

Common questions for marketers using WebPixie.

Google Analytics and Search Console tell you what happened after the fact, while WebPixie checks the pages you choose on a schedule and emails you when one fails. Analytics shows a drop in traffic once visitors are already lost, and if the tracking tag itself goes missing, it shows nothing at all. Search Console reports crawl and indexing problems after Google has visited the page and processed the result, which can take days, and it does not watch a campaign page on a schedule you set. With uptime monitoring each landing page gets its own check, with the status code it should return and a keyword it must contain, such as the headline or your Tag Manager container ID. When a check fails, every workspace member gets an email by default. WebPixie also reads your robots.txt every day in the Indexability Checker and crawls your internal links about once a week with the Link Crawler. Analytics and Search Console stay your tools for traffic and search performance; WebPixie tells you whether the pages behind those numbers are up and showing the right content.

Yes. You can add each campaign landing page as its own uptime monitor, and WebPixie emails your team when the page goes down, redirects or stops showing the content you expect. Every click you pay for while the page is broken is wasted, so the rules matter. In uptime monitoring you set the status codes that count as up, a keyword the page must contain, such as the headline, the form button or a promo code, and words it must not contain, such as "sold out". If the page should never redirect, you can turn off follow redirects and accept only 200; the check then fails when the page starts sending visitors to the homepage. Keyword checks read the HTML your server sends, so text added later by JavaScript may not be seen. A word that is in the page source works best. Network errors are retried before an alert, and on paid plans a timeout is checked again from the monitor's other selected locations. You can also set a monitor to alert only after several failed checks in a row. On paid plans each failure is kept as an incident with its duration, and workspace tags group your pages by campaign, so you can filter to one campaign at a time and switch notifications off for a short-lived test page.

Yes. You can add your Tag Manager container ID or pixel ID as a "must contain" keyword on a page, and the uptime check fails when that code is no longer in the page. This catches a common problem: a site update or a new template drops the snippet, the campaign keeps running and the data quietly stops arriving. With uptime monitoring you add the ID, such as GTM-XXXXXXX, to the monitors for your most important pages, and every workspace member gets an email when it goes missing. On paid plans the problem is also kept as an incident with its start time and duration, which tells you which days of data to question. The check reads the HTML your server sends. It confirms that the code is in the page source, not that your tags fire or that the data reaches your analytics. Tags that Tag Manager loads later, such as a GA4 tag, are not in the source, so the check should look for the container ID itself. You can add the same keyword to several monitors and group them with workspace tags.

Yes, if you set up two uptime checks for it: one on your robots.txt file and a "noindex" keyword check on your key landing pages. A relaunch or a staging setting left in place can add "Disallow: /" to robots.txt or a noindex tag to your pages, and organic traffic falls before anyone looks. The Indexability Checker reads robots.txt every day and shows it line by line, including which AI crawlers have explicit rules, so you always see the version that is live. A change to the file shows up there rather than as an alert. For an email, you can add /robots.txt as an uptime monitor with a line you expect to stay, such as your Sitemap line, as a "must contain" keyword. The check then fails if the file stops loading or is replaced by a version without that line. On each key landing page, you can add "noindex" as a "must not contain" keyword, and the check fails when a noindex meta tag appears in the HTML. Keyword checks read the page source, so a noindex sent as an HTTP header is not covered. The Link Crawler also tags crawled pages that your robots.txt disallows.

Yes. The Indexability Checker reads your robots.txt line by line and shows which known AI crawlers, such as GPTBot, ClaudeBot, Google-Extended and PerplexityBot, have explicit rules there. It also lists any Content-Signal directives, such as search, ai-train or ai-input, so you can confirm that your file says what your team decided. WebPixie validates your llms.txt file in the same view, and the Main Page view notes whether your homepage returns Markdown when a client asks for it, which some AI tools prefer. These are signals from your own files; WebPixie does not report how often any crawler visits. The Link Crawler adds a tag for pages your robots.txt disallows, and the Main Page Analyzer shows the canonical URL of your homepage.

Uptime affects SEO because search engines can only crawl and index pages that respond, and Google documents that repeated server errors slow down its crawling. A short outage is unlikely to change rankings on its own. When a site keeps returning server errors or timing out, Google crawls it less often, and URLs that keep failing can eventually drop out of the index. Uptime monitoring checks the pages you choose, such as landing pages, product pages and pages that bring in organic traffic, and emails your team when one times out, returns an unexpected status code or loses the content you expect. Network errors are retried before an alert, and on paid plans a timeout is checked again from the monitor's other selected locations, so a single blip does not wake anyone up. Alerts go by email on every plan, with Slack and webhooks on higher plans, and on paid plans each outage is kept as an incident with its duration. For the search side, the Indexability Checker shows what your robots.txt allows, and the Link Crawler lists internal links that return errors.

Everything WebPixie can watch for your marketing site

You can turn on the checks your site needs.

Related Solutions

You can start with your most important landing page

Free plan, no credit card required.