Frequently Asked Questions
You can find answers to common questions about WebPixie's monitoring solutions, features, and pricing.
General Questions
WebPixie is an all-in-one, AI-supported monitoring and analysis platform that watches the uptime of your sites and services, SSL certificates, DNS records, domain expiration, and broken links from a single dashboard. It alerts you through channels like email and Slack when a site goes down or a certificate or domain nears expiry, and lists other findings with fix guidance.
WebPixie is built for teams that want to use multiple monitoring and analysis tools automatically from a single screen. Instead of paying for a separate uptime checker, SSL monitor, domain tracker, link checker, and so on, you get all of it in one workspace with one subscription, and you can start on the free plan. You can monitor uptime from multiple global locations, such as London and New York, validate SSL certificate chains daily, watch DNS records across 20+ record types including DNSSEC, and track domain expiration alongside WHOIS/RDAP changes - all from the same dashboard.
WebPixie has a free plan with no credit card required. You can start monitoring your first site in about a minute and explore the full feature set or pricing plans to find the right fit for your team.
The Documentation has detailed information.
WebPixie is for anyone who runs a website that customers, clients or users rely on, from a single business site to dozens of client sites or a SaaS product spread across several subdomains. A business owner uses it to get notified when the site goes down or a domain nears expiry. An agency keeps every client site in one workspace, sorted with folders and tags, and walks into check-ins with a list of what to fix. A SaaS team watches the app, the API, the docs and the marketing site from one place instead of several tools. The free plan covers one site with email alerts and has no time limit, which is enough for a low-stakes site; paid plans add faster checks, incident tracking, Slack and webhooks, more sites and teammates. You can compare them on the pricing page.
Website monitoring is the practice of automatically checking whether a website is reachable, responding well, and returning expected results. Monitoring services like WebPixie check your site from multiple global locations, verify HTTP response codes, check SSL certificate validity, watch for DNS record changes, and crawl your internal links. When something goes wrong, the service sends alerts through your chosen channel and keeps each check result, so you can see when the problem started.
There are several types of website monitoring, each catching a different class of issue:
- Uptime monitoring: Is the site or service reachable?
- SSL monitoring: Is the certificate valid and not about to expire?
- DNS monitoring: Are there configuration problems?
- Domain monitoring: Is the registration about to lapse?
- Link Crawler: Are your internal links working, and where do your pages link out?
Most teams need all of them. That's exactly why WebPixie brings them together on a single platform.
WebPixie runs scheduled checks against your site from multiple global locations, such as London and New York. Each uptime check verifies the HTTP response code, response time, HTTPS connectivity, and any custom keyword conditions you configure.
For uptime checks, you can choose a check interval from 30 seconds to 24 hours, depending on your plan. To reduce false positives from network-related problems such as timeouts or connection errors, WebPixie makes up to 4 check attempts with exponential backoff. On paid plans, if all attempts fail, WebPixie also runs verification checks from the monitor’s other selected locations before opening an incident.
For SSL monitoring, the full certificate chain (leaf → intermediate → root) is validated daily with cryptographic signature verification.
For DNS monitoring, 20+ record types are checked daily via the authoritative DNS server, with public resolvers used as fallback. For domain monitoring, WHOIS or RDAP data is fetched daily across 1000+ TLDs (depending on the TLD).
All of this runs from our infrastructure. There's nothing to install, no agent to maintain, and no configuration on your servers. After you add a domain, you choose which site checks to enable, while the homepage check runs automatically for every site.
You can monitor any publicly accessible website or service, including corporate sites, e-commerce stores, blogs, web applications, marketing landing pages, status pages, and API endpoints. Uptime monitoring works over HTTP and HTTPS and supports custom ports, custom request methods and headers, expected status codes, and body keyword checks, so each target can have rules that match what it actually serves. Sites that sit behind HTTP Basic auth or a static header token can be monitored too, as long as you supply those access details. Beyond availability, the same domain can also be watched for SSL, DNS, domain expiry, and link health in one workspace. How many sites and uptime checks you can run depends on your plan, which you can compare on the pricing page.
WebPixie watches the things that most often take a site offline or make it look broken:
- Uptime - HTTP/HTTPS endpoints checked from multiple global regions with custom methods, headers, status codes, and keyword validation
- SSL certificates - full chain validation, expiration tracking, TLS version and cipher analysis
- DNS records - 20+ record types including A, AAAA, MX, CNAME, TXT, CAA, plus DNSSEC validation and email authentication (SPF, DMARC, BIMI)
- Domain expiry - expiration date, registrar status flags, transfer locks, and nameserver changes via WHOIS or RDAP
- Link Crawler - discovered internal links checked with status codes and redirect responses, plus an inventory of outbound links with rel attributes; canonical URLs and hreflang data are captured for crawled internal pages
- WebPixie Site Score - a 0–100 score built from intelligent analysis across the data WebPixie collects, such as security headers, SSL and DNS configuration; findings are ranked by severity and each one links to fix guidance
All of this sits in one dashboard with a single WebPixie Site Score that summarizes overall reliability at a glance. Each monitor type can be configured independently or use sensible defaults.
No. WebPixie runs entirely from our own monitoring infrastructure across multiple global locations, such as London and New York. There's no agent to install on your website, your servers, or your devices. You don't need access to your hosting environment or your DNS panel.
The only setup step is entering your domain name in the dashboard and selecting the checks you want to enable. Depending on your selections, WebPixie fetches the SSL certificate, reads DNS records, crawls your links, and checks uptime; the homepage check runs automatically for every site. It usually takes about a minute to collect and analyze the available data.
Domain monitoring is the practice of checking a domain's registration data on a schedule, warning before expiration, and surfacing registration changes for review. The data comes from RDAP or WHOIS, depending on what each registry supports, and covers the expiration date, registrar identity, transfer lock status, registry status flags, and nameservers. WebPixie runs these checks daily across more than 1000 TLDs, so a missed renewal can trigger an expiration warning while unexpected registrar, nameserver, or lock changes stay visible with the old and new value. It works alongside DNS monitoring and uptime monitoring in one workspace, and you can start on the free plan with the limits shown on the pricing page.
DNS monitoring is the practice of checking your domain's DNS records on a schedule and surfacing unexpected changes for review. Those records include A, AAAA, MX, CNAME, TXT, CAA, NS, and SOA, along with DNSSEC validation and email authentication like SPF, DMARC, and BIMI. WebPixie runs these checks daily via the authoritative DNS server, with public resolvers as fallback, across 20+ record types, so an edited record or a broken DNSSEC chain shows up with the old and new value, instead of a silent change you discover later. DNS changes are visible in logs but do not create incidents. It works alongside domain monitoring and uptime monitoring in one workspace, and you can start on the free plan with the limits on the pricing page.
Pricing & Billing
Yes. WebPixie has a free plan with no credit card required, no time limit, and no trial expiry.
The free plan includes:
- 1 website monitored
- 3 uptime monitors at 15-minute check intervals
- Link Crawler checks of up to 20 links per website
- SSL certificate monitoring with 15-day expiry warnings
- DNS record monitoring including DNSSEC validation
- Domain expiry monitoring via WHOIS or RDAP
- WebPixie Site Score (0-100 composite health metric)
- Indexability Checker (robots.txt, llms.txt, and indexability basics)
- Email alerts
- 1-month data retention
- Monthly reports
- MCP server access, so you can ask your AI assistant about your monitors
The free plan stops being enough when you need more than 1 site or 3 uptime monitors, a teammate in the same workspace, failures verified from your other locations before an alert, incident tracking with a history of each outage, or Sitemap Monitoring. Paid plans add those, plus faster check intervals (down to 30 seconds), integrations such as Slack and webhooks, WebPixie API access and longer retention.
The pricing page has the full breakdown of what's included in each tier, and you can start with the free plan and upgrade only if you need more. Free workspaces that are not in active use may be paused or removed after an email notice, as described in the Terms of Service.
The right plan depends on how many sites you watch, who needs alerts and how fast you need to hear about a problem. If one site and an email when it breaks are enough, the free plan covers it. If you run several sites or work with a teammate, Starter covers up to 10 sites and 3 users, with 1-minute checks, failures verified from your other locations, incident tracking and integrations such as Slack. If you look after client sites or a store where every minute counts, Pro covers up to 50 sites and 10 users, with 30-second checks, integrations such as webhooks and priority support. Enterprise adds unlimited sites and users, custom integrations and new monitoring locations on request. An agency keeps all client sites in one workspace sorted with folders and tags, so the site count, not the client count, decides the plan. You can start free and upgrade later without setting anything up again; you can compare every limit on the pricing page or see how agencies use WebPixie.
Yes. You can upgrade or downgrade your WebPixie plan at any time from your account settings without recreating monitors or changing your workspace configuration. Upgrades apply immediately, and WebPixie charges only the prorated difference for the remaining billing period. Downgrades stay active until the end of the current billing cycle, so your existing monitor limits, check intervals, and integrations continue working until renewal. Plan changes affect features such as the minimum check interval in uptime monitoring, Slack alerts, webhook integrations, retention periods, and workspace member limits. You can start with the Free Plan and move to a higher tier only when your monitoring requirements grow; the pricing page shows what each tier includes.
When you reach your plan’s monitor limit, WebPixie prevents creating additional monitors until you upgrade or free capacity. Existing monitors continue working according to your current subscription, but the dashboard will not let you add another monitor beyond the plan allowance. To add more checks, you can upgrade to a plan with higher site or monitor limits or remove an existing monitor you no longer need. You can compare included site, uptime monitor, link crawl, user, retention, and report limits on the pricing page. If you need more frequent recurring checks, a higher plan may also reduce the minimum interval available for uptime monitoring. For account-specific limit questions or Enterprise capacity, you can contact support.
We accept major credit and debit cards through Stripe for self-serve monthly or yearly WebPixie subscriptions. You can choose a paid plan on the pricing page, enter your card details during checkout, and manage renewals from your account settings. Stripe processes card payments for Visa, Mastercard, American Express, Discover, and other supported card networks based on your billing country. Enterprise customers can contact us to discuss invoice-based billing. Plan upgrades are prorated for the remaining billing period, while downgrades are scheduled for the next renewal. Payment, cancellation, and refund details are also covered in our Terms of Service.
Yes, you can cancel your WebPixie subscription at any time, with no long-term contract or cancellation fee. Cancellation takes effect at the end of your current billing period, so your paid plan features stay available until the period you already paid for ends. You can change or cancel your plan from your account settings, and current plan options are listed on the pricing page. Refunds are separate from cancellation timing: an initial purchase can be refunded within 14 days if service usage has not begun, and a renewal within 48 hours after it renews. The exact conditions are in the Refund and Cancellation Policy. For billing questions or account-specific help, you can contact support.
WebPixie refunds paid subscriptions only in the cases listed in the Refund and Cancellation Policy. The two main windows are the initial purchase, which can be refunded within 14 days if service usage has not begun, and a renewal, which can be refunded within 48 hours after it renews. What counts as service usage is explained in the policy. Outside these windows, a cancellation takes effect at the end of the paid period and does not refund unused time. Duplicate or incorrect charges and qualifying outages caused by WebPixie are handled separately under the same policy. Refunds go back to the original payment method, or are handled as described in the refund method section if that is not possible. You can review billing options on the pricing page or contact support for account-specific help.
Periodic report frequency depends on your WebPixie plan, with available intervals currently set as: Free: monthly; Starter: bi-weekly, monthly; Pro: weekly, monthly; Enterprise: weekly, bi-weekly, monthly. Reports are generated automatically and delivered by email as workspace-wide PDF attachments, sent to every member of the workspace whatever their role, so members who don't open the dashboard still see the summary and nothing needs to be exported by hand. They summarize portfolio-level signals such as monitored sites, median WebPixie Score, uptime overview, incidents, and common issues for the reporting period, with certificate and domain detail covering the sites that had an SSL or domain incident in that window. The incident breakdown and totals are included on plans with Incident Management (Starter and above). You can compare which report intervals are included in each tier on the pricing page. Reports cover the whole workspace. A client who needs their own report and login needs their own workspace, which has its own plan. Report data is based on the monitors and checks available in your plan, including uptime monitoring history where applicable.
Monitoring data retention depends on your WebPixie plan, with current limits set as: Free: 1 month; Starter: 3 months; Pro: 12 months; Enterprise: custom. This retention applies to workspace and feature-level monitoring history, such as uptime checks, SSL results, DNS findings, domain data, incidents, and report inputs. Longer retention helps teams review trends, compare incidents over time, and keep more historical context for SLA or operational reviews. You can compare retention limits by tier on the pricing page. If you change plans, the retention period available to your workspace follows the active subscription and its published limits. Legal, invoice, access log, and error log retention may follow separate rules described in the Privacy Policy and Data Processing Agreement.
Monthly billing gives you maximum flexibility, while yearly billing lets you save 17%. Yearly billing costs less than paying month by month, which is roughly like getting 2 months included at no extra cost. Monthly billing is better if you are testing WebPixie, managing a short-term project, or want the easiest path to change or cancel after each billing period. Both billing options include the same monitoring features, limits, reports, and integrations for the selected plan. You can compare monthly and yearly prices on the pricing page. Cancellation and refund timing are handled separately, so it is worth reviewing the Refund and Cancellation Policy before committing to a yearly subscription. For billing questions tied to your account, you can contact support.
Invoices and your payment card are managed in the Stripe customer portal. There you can see your invoice history and add or replace the card used for payments. Upgrading, downgrading or cancelling a plan happens in WebPixie's own billing screen instead, so plan changes and their proration stay in one place. Payments run through Stripe and accept major credit and debit cards, and Enterprise customers can arrange invoice-based billing by contacting the team. The pricing page lists what each plan includes.
Technical Questions
WebPixie runs uptime checks from multiple global locations, such as London and New York. You choose which locations each monitor uses, up to your plan’s limit, and on paid plans you can request additional regions through support; they are usually opened within 24 hours. These locations help verify whether your website is reachable from more than one network path, which is useful when a problem affects only a specific region, provider, or route. Each uptime monitoring check can validate response status, response time, expected content, and other configured conditions before an incident is created. If no region is selected, WebPixie assigns one automatically. Multi-location checks and cross-location verification (available on paid plans for monitors with more than one location) are especially useful for customer-facing sites, agencies managing client domains, and teams that need clearer evidence before escalating an outage. You can compare plan coverage on the pricing page.
WebPixie marks a site as down when an uptime check fails the response rules configured for that monitor. A failure can come from a timeout, connection error, unexpected HTTP status code, missing body keyword, or another expected condition that does not match. Uptime monitoring supports custom HTTP methods, headers, expected status codes, authentication, and keyword validation, so “down” can mean more than a simple 500 error. For network-related failures such as timeouts or connection errors, WebPixie makes up to 4 check attempts with exponential backoff before confirming the failure. On paid plans, if all attempts still fail, WebPixie also runs verification checks from the monitor’s other selected locations before opening an incident, which reduces false positives further. Failures from deterministic conditions, such as an unexpected status code or a missing keyword, open an incident on the first failed check without retry. If the issue is confirmed, WebPixie creates or updates an incident and sends notifications through the channels available on your plan. Check intervals and location availability are plan-based, and you can compare them on the pricing page.
WebPixie calculates uptime as the share of monitored time your site responded successfully, using the industry-standard method that excludes periods when monitoring was not active. The basic formula is successful (up) time divided by total monitored time, multiplied by 100 (Uptime % = Up time ÷ Total monitored time × 100). Uptime monitoring checks your site at your plan's interval from multiple global locations, such as London and New York, and records each check as up or down. Time before a monitor was created, or while it was paused, is left out of the total rather than counted as downtime, so the percentage reflects only what WebPixie actually observed. A single network-error check does not count as down right away, because timeouts and connection errors go through up to 4 check attempts with exponential backoff before the failure is confirmed. On paid plans, verification checks from the monitor’s other selected locations also run before a network-related incident opens; a check that fails from one location but passes from the others is recorded and left out of the percentage instead of counting as downtime, which keeps a brief routing flicker from distorting the figure. The resulting percentage is what you compare against an SLA target, where the allowed downtime is the error budget the target permits. To translate a target like 99.9% into plain minutes for a day, week, month, or year, you can use the free uptime calculator. Check intervals and data retention depend on your plan, which you can compare on the pricing page.
WebPixie stores the website and workspace data needed to provide monitoring, alerts, reports, and technical analysis. This includes domain names, uptime targets, response status, response times, SSL certificate information, DNS and WHOIS/RDAP data, incident history, workspace users, and feature-level analysis outputs. For crawler, indexability, and page analysis features, WebPixie processes only publicly accessible page content and links; authenticated checks are available separately through uptime monitoring when you configure credentials for that monitor. WebPixie does not store your site content as a standalone archive and never sells personal data. It does not store your WebPixie account password (sign-in is handled by our authentication provider). Credentials you add to an uptime monitor for authenticated checks are stored so the checks can run. Where data is stored and which service providers process it are listed in the Privacy Policy. Workspace retention follows your plan limits on the pricing page, with additional rules in the Privacy Policy and Data Processing Agreement.
WebPixie Site Score is a normalized 0-100 health score based on the monitoring signals available for your website. It is the output of intelligent analysis across the data WebPixie collects, such as security headers, SSL security and configuration validation, and DNS configuration validation, rolled into one summary score. SSL and DNS checks contribute certificate chain validity, expiration risk, resolver results, DNSSEC, and record health. The Main Page Analyzer adds homepage signals such as redirects, canonical tags, cookies, and HTTP security headers. Indexability Checker findings add crawl and discovery visibility signals rather than a standalone indexing verdict. The score is meant to summarize risk at a glance; individual findings and severities should be reviewed to understand what to fix first.
The Indexability Checker covers signals that affect whether search engines such as Google and Bing and AI assistants such as ChatGPT and Claude can discover, crawl, and index your important pages. TXT Files validates robots.txt and llms.txt, Main Page surfaces canonical and alternate signals, Link Crawler contributes page-level robots access signals, and Sitemap Monitoring contributes sitemap coverage signals. Each signal can be reviewed in the feature view where it is collected, alongside the Link Crawler and Main Page Analyzer details that provide its context.
Yes. The Indexability Checker validates and analyzes robots.txt and llms.txt line by line, giving each file a valid or invalid result and flagging syntax it cannot parse. This lives in the TXT Files view, where you can see how a directive is interpreted instead of guessing whether a rule is written correctly. It also checks whether a sitemap is referenced in robots.txt, so a missing reference is visible during review. On the Main Page view, WebPixie surfaces the canonical URL and alternates as supporting visibility signals rather than a standalone indexing verdict. Indexability signals contribute to the WebPixie Site Score without requiring you to inspect each technical finding manually. For link-level crawl health, it pairs with the Link Crawler, and you can compare plan limits on the pricing page.
They answer different questions. The Link Crawler is about link health: starting from your homepage it follows discovered public internal links and reports each checked link's status code, response time, redirect status, and whether it loads successfully, while also listing the outbound links each page points to without checking them. The Indexability Checker is about crawl signals: it validates robots.txt and llms.txt, reports robots.txt sitemap-reference presence, uses canonical and alternate signals from the Main Page view, and includes crawler-derived robots-disallowed tags. A link can be healthy yet blocked from search engines, and a page can be visible to crawlers yet link to broken destinations, so the two signals do not replace each other. The crawler deliberately ignores robots.txt while following links, because it must fetch a page to confirm it works; search eligibility is reviewed through indexability signals instead. You can use both and compare plan limits on the pricing page.
The Main Page Analyzer checks the technical health, security posture, and SEO-critical signals on your homepage. WebPixie calls the homepage and evaluates response time, protocol support, HTTPS enforcement, redirect chains, canonical URL, hreflang tags, meta tags, cache directives, cookie attributes, and HTTP security headers. Header checks cover headers such as HSTS, CSP and X-Frame-Options. The Main Page Analyzer assigns findings a severity level such as Critical, High, Medium, Low, or Info so teams can decide what to fix first. It complements Indexability Checker checks for crawl and indexing signals, and uptime monitoring checks for ongoing availability and response behavior.
The connection-timing waterfall in the Main Page Analyzer breaks a homepage request into timed phases, so you can see where load time is spent. It records DNS lookup, TCP connection, TLS handshake, pre-transfer wait, time to first byte, content download, and the total, each as its own measurement. When a page feels slow, the waterfall shows whether the delay sits in DNS resolution, the TLS handshake, or the server's time to first byte, which points you at the layer to fix. It runs alongside the request and redirect path, HTTP protocol support flags, and canonical data on the Main Page view. This timing data, along with the browser-measured page load time and the rendered HTML size, is live today; Lighthouse-based SEO and performance scoring is in development and not yet part of the analysis. The waterfall complements response-time trends from uptime monitoring, and you can compare plan limits on the pricing page.
Yes. The Main Page Analyzer detects which protocols your homepage supports and shows flags for HTTP, HTTP/2, HTTP/3, HTTPS, and whether HTTP redirects to HTTPS. These flags tell you whether visitors and crawlers can negotiate a faster HTTP/2 or HTTP/3 connection or are falling back to older protocols. The same view records the full request and redirect path with per-hop headers, the canonical URL and its alternates, and the connection-timing waterfall, so a missing HTTPS redirect or an unexpected hop is visible in one place. Protocol and header signals here overlap with what SSL monitoring validates on the certificate side, which is why teams often watch both. You can compare plan limits on the pricing page.
WebPixie checks 15+ HTTP security headers that your homepage returns, using 50+ checks that look at whether each header is present and how it is configured. They include HSTS, Content-Security-Policy, X-Frame-Options and the flags on cookies the page sets. Because values are checked as well as presence, a header that exists but is set too loosely, such as a short HSTS max-age, still produces a finding. The security headers checker is part of the Main Page Analyzer, which also covers request timing, protocol support, and the redirect chain on the same page. Certificate validity, TLS versions, and cipher strength are checked separately by SSL monitoring.
No. Security header analysis runs on your homepage, the page WebPixie loads for its daily main page snapshot, and not on every page of the site. The homepage is where most visitors and crawlers arrive, and on many sites its headers come from the same server or CDN configuration as the rest of the site. If part of your site runs on a different stack, such as a separate app or docs subdomain, you can add that subdomain as its own site so its homepage headers are checked too. The Link Crawler records the response headers of each crawled internal link. Header findings appear in the Main Page Analyzer view, and the number of sites you can add depends on your plan, as shown on the pricing page.
WebPixie re-checks your homepage security headers every day, and the results show up as findings in the dashboard and feed your Site Score. Each daily snapshot reads the headers your homepage returns, so a header that disappears after a deploy or a CDN change appears in the next day's results. Each finding carries a severity level (Critical, High, Medium, Low, or Info) and links to guidance on how to fix it, so you can see which header to change first. After a release, you can open the Main Page Analyzer view to confirm your headers are still in place and to see which findings are open. To keep track of your site's availability around the clock, it pairs with uptime monitoring.
Every security header finding is ranked as Critical, High, Medium, Low, or Info, and each one includes fix-guidance links and reference material explaining how to resolve it. The severity tells you where to start: a missing header with a direct security impact ranks above an optional header or an informational note. The reference material points to the relevant standard or documentation, so the person changing the server or CDN configuration has what they need. Header findings also feed the composite WebPixie Site Score along with WebPixie’s other analyses, so a fixed header is reflected in the score after the next daily check. Security header checks are included on every plan, including Free, and you can compare plan limits on the pricing page.
The Link Crawler re-scans discovered links on a schedule, typically about once a week, with a minimum of 24 hours between runs. WebPixie starts by discovering links from your homepage, then schedules automatic re-crawls across the sites in your workspace. Crawl limits per site depend on your plan, and the current limits are listed on the pricing page. During each Link Crawler scan, WebPixie health-checks each internal link it crawls, recording status code, response time, content size, page title, favicon, rel attributes, canonical URLs, hreflang tags, and related meta data. Outbound links are listed for review rather than health-checked, but still carry their rel attributes, anchor text, and occurrence count. This helps you catch broken internal links, slow pages, redirect responses, and link-level issues, and review the outbound links each page points to. For broader crawlability and indexing signals, crawler results pair with the Indexability Checker.
The Link Crawler discovers and lists the external links your pages point to, but it does not health-check them. On every crawl run it follows and health-checks the internal links between pages on your monitored domain, recording status code, redirect status, and response time for each. For outbound links to other domains, it records the anchor text, how often each appears, and the rel attributes such as nofollow, sponsored, and ugc, so you can audit your external link profile without WebPixie testing those third-party destinations. This keeps the crawl focused on the pages you control while still giving you a map of where your pages point out, up to your plan’s link limit. It pairs with the Indexability Checker for broader crawlability signals, and you can compare crawl limits on the pricing page.
Yes. The Link Crawler supports a reverse lookup: given any URL, it returns which of your crawled pages link to that URL. You can point it at one of your own pages to see that page's internal inbound links, which helps you understand your internal link structure and how link equity flows toward your most important pages. Pointed at an external URL, it finds every page on your site that links out to that destination, which is useful when you need to update or remove a specific outbound link across your site. Each result carries the same per-link detail as the rest of the crawl, such as anchor text and the page's own status. This works from the links discovered during the normal homepage-based crawl, up to your plan limit. For broader crawlability signals, it pairs with the Indexability Checker, and you can compare crawl limits on the pricing page.
No. The Link Crawler follows only publicly accessible links, starting from your homepage, so it does not log in or send credentials, and pages that require authentication are not crawled. If you need to check a private URL, uptime monitoring supports authentication, custom headers, and expected status codes, though it checks one endpoint at a time rather than crawling a whole site. You can review per-plan crawl limits on the pricing page.
No. The Link Crawler does not skip links that robots.txt would disallow, because it has to fetch each linked page to confirm the link works and to read the sublinks on it. Honoring robots.txt mid-crawl would leave gaps in your link health report, so the crawler checks discovered links up to your plan limit and labels robots-disallowed URLs for review. Whether a URL is eligible for search engines or AI crawlers is a separate question that belongs to indexability rather than link health. This keeps link health and crawl eligibility as two distinct signals. For the search-eligibility side, it pairs with the Indexability Checker, and you can review per-plan crawl limits on the pricing page.
Sitemap Monitoring discovers your sitemap tree automatically from the Sitemap: directive in your robots.txt, then walks supported sitemap indexes down to leaf files. It supports XML and text sitemap files, including gzip-compressed responses, and catalogs declared URLs per leaf sitemap along with lastmod, changefreq, and priority when present. Nested or recursive sitemap indexes are not supported and are flagged as unsupported. The discovery cycle re-checks daily as part of your site’s daily snapshot; an individual sitemap file is re-fetched daily when it supports cache validators such as ETag or Last-Modified, otherwise it can go up to about a week between fetches. Sitemap Monitoring is available on Starter and above; you can compare plans on the pricing page.
Once Sitemap Monitoring has successfully completed its first full discovery cycle, WebPixie cross-checks it against the Link Crawler: crawled internal links that are not present in your declared sitemap are labeled "not found in your sitemap". This surfaces pages engines may never discover through your sitemap, such as a new page you forgot to add or an old URL your sitemap generator dropped. It is a coverage signal, not a health check: the label only compares sitemap membership against crawled internal links, it does not mean the page is broken or blocked. Sitemap Monitoring is available on Starter and above; the pricing page has the details.
The Indexability Checker only reports whether a Sitemap: directive is present in your robots.txt, a presence check. Sitemap Monitoring goes further: it actually fetches the declared sitemap tree, walks supported sitemap indexes down to leaf files, and catalogs declared URLs with lastmod, changefreq, and priority when present. It also cross-checks sitemap coverage against the Link Crawler, flagging crawled internal links that are missing from your sitemap. Sitemap Monitoring is available on Starter and above, while the robots.txt presence check is included on every plan; you can compare plans on the pricing page.
No. Sitemap Monitoring surfaces its findings in the dashboard for review; it does not open incidents or send notifications. WebPixie's automated incidents and alerts come only from uptime, SSL, and domain events, such as a site going down or a certificate failing its check. Sitemap Monitoring instead catalogs your declared URLs and flags things worth reviewing, like a sitemap index it could not fully process or a crawled internal link that is missing from your sitemap. Those coverage signals sit next to your other site data so you can act on them during review, rather than as a paged alert. If you want events that notify you, incident management tracks the availability and certificate events above. Sitemap Monitoring is available on Starter and above; you can compare plans on the pricing page.
Sitemap Monitoring supports standard XML and plain-text sitemap files, including gzip-compressed responses. During discovery it reads your sitemap index and walks the sitemaps it references down to the leaf files, then catalogs every declared URL along with its lastmod, changefreq, and priority when present. The sitemap protocol allows up to 50,000 URLs and 50 MB per file; on top of that, WebPixie applies its own processing caps, reading up to 10,000 URLs per sitemap file, up to 100 sitemap files per site each discovery cycle, and up to 50,000 sitemap URLs per site in total, while a file over 50 MB is skipped as too large. Most sites stay well within these limits, and splitting a large sitemap into multiple files under one index keeps more pages within the limits. WebPixie discovers your sitemaps automatically from the Sitemap: directive in robots.txt, and that reference is also validated by the Indexability Checker. Sitemap Monitoring covers discovery in more detail and is available on Starter and above on the pricing page.
No, and neither do search engines. A sitemap index file may list individual sitemap files, but it cannot list other sitemap index files, so a nested or recursive index (an index that points to another index) is outside the sitemap protocol. Google states this directly: a sitemap index file can't list other sitemap index files, only sitemap files (opens in new tab). Sitemap Monitoring follows the same rule: it walks a normal sitemap index down to its leaf files, but when it meets a nested sitemap index it flags that entry as unsupported instead of following it further. If you see that flag, the fix is to flatten the structure so your top-level index points directly at sitemap files, which also keeps your sitemaps discoverable by search engines. Sitemap Monitoring is available on Starter and above; you can compare plans on the pricing page.
WebPixie surfaces certificate validity, chain consistency, expiration, TLS configuration, and certificate identity details for each monitored site. SSL monitoring validates the served certificate against the trusted root CAs and confirms the hostname matches; it then extracts the full certificate chain from leaf to intermediate to root and verifies cryptographic signatures for RSA, EC/ECDSA, Ed25519, and Ed448 certificates. It also reports TLS version, cipher suite, key exchange, key strength, Subject Alternative Names, and Extended Key Usage OIDs, and queries OCSP (falling back to CRL) to confirm the certificate has not been revoked. Expiration tracking is included, with default warnings 15 days before a certificate expires so teams have time to renew. SSL check failures and expiration events can create incidents through incident management, depending on your plan. Teams managing several domains can use the Certificates Manager to review Certificate Transparency inventory across domains and subdomains. The certificates docs have the full field reference.
Yes. Because the Certificates Manager reads Certificate Transparency logs, it surfaces certificates seen for your domain and subdomains even when they were not requested through your own process. An unexpected certificate can signal a misconfiguration or an unauthorized issuance, and seeing it in the log is the first step to acting on it, so you can tell a legitimate renewal from something that warrants review. It turns on automatically with SSL monitoring and lists each certificate's common name, SAN, validity window, issuer and serial number. This view is for review: WebPixie does not send an alert when a new certificate appears in the logs. The same data set powers subdomain discovery: subdomains found in Certificate Transparency logs and in your main certificate's SANs are listed with an action to start monitoring each one. WebPixie reports what the public record shows; it does not issue, renew, or revoke certificates, which stays with your certificate authority. This complements the per-site checks in SSL monitoring, and you can compare plan limits on the pricing page.
Certificate Transparency (CT) is a public, append-only logging system that certificate authorities write to whenever they issue a certificate, so anyone can audit which certificates exist for a domain. It was created to catch mis-issuance: before CT, a certificate authority could issue a certificate for your domain, by mistake or after a compromise, and you might never find out. Because every issuance is now recorded in public logs, an unexpected certificate becomes visible instead of silent. This matters for security, because an attacker holding a valid certificate for your domain can impersonate your site convincingly and intercept traffic while the browser padlock still looks normal. CT does not prevent a bad certificate from being issued; its value is making that issuance discoverable so you can respond. WebPixie surfaces CT data for review in the Certificates Manager, while the per-site chain and expiry checks that actually alert you live in SSL monitoring.
No. WebPixie monitors SSL certificates; it does not issue or renew them. Renewal stays with your certificate authority, such as Let’s Encrypt, your hosting provider, or another CA. The recommended workflow is automatic renewal at your CA paired with SSL monitoring to confirm the renewal actually happened. Daily revalidation catches the common failure where a Let’s Encrypt auto-renewal breaks silently and the original certificate keeps moving toward expiry. WebPixie sends an expiry warning 15 days before expiry by default, and a failed check can open a tracked incident through incident management on supported plans. Teams managing many certificates can review public CT-log inventory in the Certificates Manager.
Yes. WebPixie monitors both wildcard certificates, which cover *.example.com, and SAN certificates, which cover several specific domains under one certificate. On every daily check, SSL monitoring extracts the Subject Alternative Names and confirms the monitored hostname is covered by the certificate, alongside full chain validation and expiry tracking. This is useful for teams running many subdomains under a single wildcard or multi-brand certificates that list several domains. If you manage several certificates across domains and subdomains, the Certificates Manager gives you a CT-log inventory in one place, and a failed SSL check can open a tracked incident through incident management on supported plans.
Domain monitoring and DNS monitoring watch two different layers that depend on each other. Domain monitoring tracks the registration relationship: which registrar holds it, when it expires, and whether transfer locks or status flags change. DNS monitoring tracks the records served by authoritative DNS servers, such as A, AAAA, MX, and TXT, along with DNSSEC and email authentication. The domain sits at the registry layer, while DNS operates below it, and a valid registration is what keeps DNS resolving at all. Most teams need both, because a lapsed registration and a broken record produce the same outcome, an unreachable site. WebPixie covers both in one workspace so registration and records stay visible side by side.
WebPixie monitors more than 20 DNS record types, grouped by what they control. Name resolution covers A, AAAA, CNAME, NS, and SOA; email authentication covers MX records, plus SPF, DMARC, and BIMI policies; certificate authority restrictions use CAA; and DNS security covers the DNSSEC records DNSKEY, DS, CDNSKEY, and CDS. General purpose records like TXT and SRV are included too, along with reverse DNS (PTR) lookups for IPv4 and IPv6. Each type is checked daily, and a changed value is logged with its old and new value. This is the same data that feeds DNS monitoring findings and your WebPixie Site Score, and it works next to SSL monitoring and domain monitoring in one workspace.
Yes. WebPixie validates the full DNSSEC chain on every daily check, covering the DNSKEY records, the DS records in the parent zone, the RRSIG signatures, and the NSEC negative-response records. The result is reported as secure, insecure, bogus, or indeterminate, so you can tell a correctly signed zone from an unsigned one or a broken one. This matters because when DNSSEC breaks, validating resolvers refuse to return the record at all, and the domain goes dark for users on those resolvers. The daily check flags a bogus chain on your dashboard, so you can see it and fix it. DNSSEC checks run on every plan, including the free one on the pricing page, and are part of DNS monitoring.
WebPixie queries every monitored DNS record daily from the authoritative DNS server, then compares each response to the previous one. When a response changes, WebPixie flags it with the previous value, the new value, the record type, and the detection timestamp. If the authoritative server does not respond, the check falls back to a public resolver such as Google, Cloudflare, or Quad9, so a temporary outage on one source does not block detection. That context helps you tell an authorized update from your team apart from an unexpected modification worth investigating. DNS changes are visible in your logs but do not create incidents; they sit next to uptime monitoring in the same workspace. For a one-off manual check right now, you can use the free DNS Lookup tool.
No. WebPixie monitors DNS records; it does not host them. Your records stay wherever you run them today, whether that is Cloudflare, AWS Route 53, NS1, your registrar, or another provider, and you keep managing them there. WebPixie adds an independent daily check via the authoritative DNS server, with public resolvers as fallback, so when a record changes or a DNSSEC chain breaks, you see it with the old and new value without moving anything. Keeping hosting and monitoring separate is deliberate, because an outside observer can flag a misconfiguration that the system serving the records would not catch on its own. DNS monitoring shows what is tracked; it pairs with domain monitoring for the registration layer, and you can start on the free plan on the pricing page.
WebPixie covers more than 1000 TLDs through WHOIS or RDAP, resolved per TLD from the IANA database. That includes the major generic TLDs like .com, .net, and .org, country-code TLDs like .io, .co, .uk, and .de, and newer gTLDs like .app, .dev, and .ai. The protocol used, RDAP or WHOIS, is selected automatically per TLD based on what each registry supports. Some registries publish limited data or redact contact details, so not every field is available for every domain; the raw WHOIS or RDAP output is shown as well. You can run a one-off check with the free Domain Lookup tool, or track your names on a schedule with domain monitoring on the free plan shown on the pricing page.
An incident opens when an uptime check confirms a site or endpoint is down, when the SSL check fails, when a certificate or domain gets close to expiry, and when a domain is suspended. Each incident records its type, severity, start time and duration, and it closes on its own once the problem clears. SSL and domain expiry incidents also raise their severity as the date gets closer. Other results, such as DNS changes, broken links, sitemap signals and security header findings, stay in the dashboard as findings with fix guidance and do not open incidents. The Incident Management page shows how alerts and incidents work together, and the Uptime Monitoring and Domain Monitoring pages explain what each check covers.
Yes. The daily DNS check reads and analyzes your SPF, DMARC, BIMI, TLS-RPT and MTA-STS records. A wrong or missing record can send your emails to spam or let someone else send mail in your name, so each problem is listed as a finding with fix guidance, and a record that is not published shows as not found. For MTA-STS, WebPixie checks the TXT record; it does not fetch the policy file. Every DNS change is also kept with its old and new value, so you can see when an email record changed and what it was before. The DNS Monitoring page explains how the analysis works, and the free DNS Lookup tool gives a one-off view of any domain's records.
For Developers
You can point an uptime monitor at a page or health endpoint and require a keyword only the new release returns, such as a build ID, plus your accepted status codes. A plain ping counts any 200 as up, even a blank page or an error template, so the keyword is what proves the right version is answering. In uptime monitoring you can also set the HTTP method, headers, a JSON or form body and Basic, Token or Digest auth, which covers API endpoints as well as pages. Your deploy script can update the expected keyword through the API integration on Starter, Pro, Enterprise plans, so each release is checked against its own build ID. The check happens on the monitor's next scheduled run, with an interval from 30 seconds to 24 hours depending on your plan. A keyword mismatch counts as a failure on the first check, without the retries used for timeouts. The intervals for each plan are listed on the pricing page.
You can pause the monitor before the release and resume it afterwards, from your deploy script through the API or by asking your AI assistant over MCP. While a monitor is paused it is not checked and sends no alerts, and the paused window counts as unmonitored, so a planned pause does not lower your uptime rate. With the API integration on Starter, Pro, Enterprise plans, pauseUptimeLink and resumeUptimeLink take up to 100 monitors per call; the MCP server works on every plan and understands a prompt like "Pause the staging monitor while we deploy". Outside planned pauses, uptime monitoring already filters out short blips: timeouts and connection errors are retried before an incident opens, and paid plans confirm them from the monitor's other selected locations. A wrong status code or a missing keyword is a real answer from your server, so it counts on the first failed check. If a restart tends to return a few errors, you can set the monitor to alert only after several failed checks in a row.
Yes, WebPixie can monitor staging, development and preview environments the same way as production, as long as their URLs are reachable from the internet. Protected staging works too: uptime monitoring can send Basic, Token or Digest credentials or custom headers, check the status codes you accept and require a keyword in the response. For certificate and domain checks, you can add staging as its own site so it gets daily SSL monitoring and expiry warnings; each site counts toward your plan's site limit. You can tag staging, development and production monitors by environment to filter them in the dashboard and the API, and turn off notifications for monitors that should stay quiet. During a deploy, you can pause the staging monitor and resume it afterwards; the paused time does not count against its uptime rate. Keeping every environment in one workspace with tags means one plan covers them all. You can compare site and monitor limits on the pricing page.
Yes, the daily analysis reads your robots.txt and llms.txt line by line, so a "Disallow: /" line or a removed AI crawler rule shows up in the next analysis. The Indexability Checker shows whether the files are valid, which AI crawlers such as GPTBot, ClaudeBot, Google-Extended and PerplexityBot have explicit rules, which Content-Signal directives are set and whether robots.txt has a Sitemap line. The Main Page view also shows your homepage's canonical URL and whether it serves Markdown to clients that ask for it. From Starter, Sitemap Monitoring flags crawled pages that are missing from your sitemap. These results appear in the analysis rather than as an alert. If you want an alert, you can add "noindex" as a keyword that must not appear on your homepage uptime monitor, and the next check fails if a noindex tag ships to production.
Yes, your pipeline can call the GraphQL API to create, update, pause and resume monitors and to read monitor state, incidents and analysis findings after a deploy. A common setup pauses the production monitor before the release, resumes it afterwards and sets the expected keyword to the new build ID, so the next scheduled check confirms the right version is live. The API integration is available on Starter, Pro, Enterprise plans and uses API keys over Basic auth. A key can be read-only and limited to specific sites and monitors, so a CI job only touches the environment it deploys. Monitor creation is also capped per day at your plan's monitor limit, so it works best to keep one monitor per environment and update its target instead of creating a new one for every preview deploy. Checks run on each monitor's own interval. To get alerts into your own tooling, webhooks send incident events to an HTTPS endpoint you set, and each event matches a record in incident management. Webhook availability depends on plan, and you can compare plans on the pricing page.
Yes, WebPixie has a GraphQL API with more than 20 queries and 15 mutations, included on Starter, Pro, Enterprise plans. The API integration covers sites, uptime monitors, incidents, tags and workspaces, so a deploy script can create a monitor for a new environment, pause it during a release, resume it afterwards and read the latest analysis findings. Authentication uses API keys over Basic auth. A key acts with the workspace role of the user who created it, can be read-only and can be narrowed to specific sites and uptime monitors, so you never have to share a broad workspace credential. Teams also pull uptime history into internal dashboards and sync incident data with their own tools, and for alert-driven workflows the API pairs well with incident management and webhook notifications. The API docs cover endpoints and authentication setup. If you would rather work through an AI assistant than code, the MCP server connects Claude, ChatGPT, Codex and VS Code to your account on every plan.
Yes, but REST API access is separate from standard plan API access and is enabled through custom sales arrangements. The GraphQL API in the API integration is how you manage monitoring programmatically, with queries and mutations for monitors, uptime data, incidents, and workspaces. The REST API is built on WebPixie's Tools infrastructure and exposes diagnostic tools WebPixie runs inside the product, such as DNS lookup and domain or WHOIS lookup, as services you can call from your own code. It is not a second way to manage your account; monitoring management stays in GraphQL. Both API surfaces use API keys over Basic auth, where a key inherits the workspace role of the user who created it and can then be narrowed to specific resources. GraphQL API access is available on Starter, Pro, Enterprise plans; REST tools API access is handled through sales-led arrangements.
Yes, WebPixie can post monitoring events to any HTTPS endpoint you set with webhooks, so your own service, an on-call tool or an internal bot can react to them. Events cover incident openings and closures for uptime and SSL checks, SSL and domain expiry warnings and domain suspensions. If your on-call tool expects its own format, a small relay service in between can translate the event. Email alerts work on every plan, Slack is a built-in channel on eligible plans and webhooks are part of the higher plans, so you can compare notification channels on the pricing page. Notifications are set per resource, so you can keep staging quiet while production alerts go out. Each event matches a record in incident management, where you can follow its duration and add notes, and the API integration lets your service query or update the same resources after it receives an event.
You decide: on the consent screen you choose read-only or read and write for each workspace and can narrow access to specific sites and uptime monitors. A read-only connection does not even list the write tools, so the assistant cannot change anything there. With read and write, the MCP server follows the same rules as the API integration: the assistant can never do more than your own workspace role allows, and account, billing and team management are not available to it. Before a delete, the assistant is instructed to tell you what will be removed and wait for your confirmation. That is an instruction to the assistant rather than a check WebPixie enforces, so it is worth reading delete requests before you approve them. You can change access later by connecting the assistant again with new settings, and you can remove a connection by contacting support; it stops on the next request, and the removal is recorded in the audit log of every workspace it reached. The details are in the MCP permissions docs.
For one side project where a short outage costs little, the free plan is often enough, and it has no time limit. It covers 1 site and 3 uptime monitors at 15-minute check intervals, with email alerts and SSL, DNS, domain and link checks for that site. The MCP server works on the free plan too, so you can ask your AI assistant about your monitors or pause one before a deploy. The GraphQL API integration starts on paid plans, and so does incident management with a history of each outage and how long it lasted. Paid plans also check more often, confirm network failures from the monitor's other locations, add Slack alerts and cover more sites, which starts to matter once you run an app, an API and staging side by side. You can start free and upgrade later without setting anything up again. You can compare the plans on the pricing page.
Integration Questions
Yes, through webhooks: WebPixie posts incident and SSL/domain events to PagerDuty, and webhooks are available on higher plans. Webhooks send monitoring events to an HTTPS endpoint you configure, so PagerDuty can receive alert-routing events from WebPixie and route them through the policy your team already uses. This works best when paired with incident management, because confirmed failures become tracked incidents before they are routed externally. Webhook availability depends on plan, and you can compare notification channels on the pricing page. Programmatic workflows around the same resources are covered by the API integration.
Using WebPixie with AI
The WebPixie MCP server lets an AI assistant connect to your WebPixie account so you can ask about your monitoring data in plain language. MCP (Model Context Protocol) is a standard way for assistants to use other tools, and WebPixie runs its own MCP server. After you add the server address to your assistant and sign in, the assistant can read uptime data, SSL and domain expiry, DNS, links, sitemaps, and incidents from the workspaces you approve. If you allow it, it can also make changes such as pausing a monitor. The server uses the same data and rules as the API integration, so your workspace role applies, and it covers the same areas you see in uptime monitoring and incident management. The MCP docs have setup guides.
Claude (claude.ai and Claude Code), ChatGPT, Codex, and VS Code can connect to the WebPixie MCP server. Each one lets you add an MCP server or custom connector by address: you add the WebPixie server address, sign in with your WebPixie account, and approve the access you want on the consent screen. If the platform or tool you use is not on WebPixie’s allowed client list, you can contact us and we will make it available for you quickly. Connecting does not require a paid plan, so you can try it on a Free workspace and then compare what other plans add on the pricing page. Once connected, the assistant works with the workspaces you selected and follows your role in workspace management. Step-by-step guides for each assistant are in the MCP docs.
No, the WebPixie MCP server uses OAuth sign-in instead of API keys. When you add the server address to your assistant, you are sent to WebPixie to sign in and approve access on a consent screen, and the assistant receives its access from that approval, so there is nothing to create, copy, or rotate. API keys belong to the API integration, where scripts and services authenticate with Basic auth. The two are separate: an API key does not work with the MCP server, and an MCP connection does not create an API key. Both follow the same access rules, including your workspace role and read-only settings, so choosing between them mostly comes down to whether you are talking to an assistant or running code. You can find the steps in Connect Your Assistant.
Only if you allow it. You choose read-only or read and write for each workspace on the consent screen. With read-only access the assistant cannot make changes and does not see the tools that would. With read and write access it can do things such as pausing or resuming a monitor, and it is instructed to ask you before deleting anything. You can also narrow a workspace to specific sites and uptime monitors, so an assistant only reaches the resources you pick. Account, billing, and team settings stay in the dashboard and are not available to assistants. Anything an assistant changes follows the same rules as the API integration, and the effects show up in your uptime monitoring like any other change. AI assistants can make mistakes, so it is worth reviewing important changes before relying on them. Access and Permissions covers every choice on the consent screen.
Every plan includes MCP access, including Free. You do not need a paid plan to connect an assistant. What the assistant can see and change depends on your workspace, so plan limits such as the number of sites and monitors, check intervals, and data retention still apply to the data it reads. If you also want to automate monitoring from your own code, the API is part of the paid plans. You can compare what each plan includes on the pricing page, and see how scripts and services connect on the API integration page. Workspace roles also decide who can approve write access for an assistant, which is covered in workspace management.
You can remove an assistant's connection by contacting support; it stops on the assistant's next request, and the removal is recorded in the audit log of every workspace it reached. Each connection belongs to your user and covers the workspaces you approved on the consent screen. To change what an assistant can reach, you can connect it again with new settings: every new connection asks you to choose workspaces, access mode and, if you want, specific sites and monitors. The workspace management page explains how roles shape what an assistant can do, and Access and Permissions covers how connections work.
For DevOps Teams
On paid plans, WebPixie confirms the failure, opens one incident, sends one notification and closes the incident on its own when the endpoint recovers. For a timeout or connection error, the check is first retried in place, with up to 4 attempts in total, then verified from the monitor's other selected locations; a wrong status code or a keyword mismatch counts as down right away. The confirmed failure becomes an incident with its type, severity, start time and duration, and your team is notified by email and, depending on the plan, in Slack or through a webhook. While the incident is open, WebPixie re-checks the endpoint more often than its normal interval, so recovery is seen sooner and the outage length is measured accurately. When a check passes, the incident is marked resolved and a second notification goes out. Uptime incidents are always Critical, while SSL and domain expiry incidents start lower and move up in severity as the date gets closer. The incident record, with the notes your team adds, gives you the timeline for the postmortem. On the Free plan, you still get the email alert, but there is no incident list or history. You can see how checks work under uptime monitoring and the full lifecycle in the incidents docs.
WebPixie keeps network blips from opening incidents with two layers of protection: in-place retries for timeouts and connection errors, and verification from other locations on paid plans. First, when an uptime check hits a network-related failure such as a timeout or a connection error, WebPixie makes up to 4 check attempts with exponential backoff, so a brief blip does not open an incident. Second, on paid plans, if all attempts still fail, WebPixie runs verification checks from the monitor’s other selected locations before opening an incident. A monitor with a single location has no other location to verify from, so it is best to select at least two for the endpoints that page people. If the site is reachable from those locations, no incident opens and the failed check is recorded as unverified rather than confirmed down, and it is left out of your uptime percentage instead of counting as downtime. Failures that are not network-related, like an unexpected status code or a keyword mismatch, open an incident on the first attempt, because they reflect a real response from the server. For an endpoint that flaps, you can set the monitor to notify only after several failed checks in a row. You also control what counts as up: an accepted status-code list, keyword checks for content that must or must not appear, and a configurable request timeout all shape the verdict. When a failure is confirmed, it flows into incident management with a severity and a type, and you get one notification when the incident opens and one when it closes, not one per failed check. When checks recover, the incident closes automatically and is marked resolved. Per-plan check intervals are on the pricing page.
Yes. Each uptime monitor has a setting for how many failed checks in a row are needed before the alert goes out, and it is 1 by default. You can raise it for an endpoint that flaps, such as a service behind a slow upstream that returns an occasional 502, so a single bad answer stays out of your channels. The setting sits on top of WebPixie's own protection: timeouts and connection errors are already retried in place and, on paid plans, verified from the monitor's other selected locations before they count as a failure. A wrong status code or a keyword mismatch is not retried, so that is where the threshold helps most. A value of 1 suits endpoints where a single failure matters, like a login or payment route. The threshold holds back the notification, not the record: every check is still logged with its status code, location and response time in the uptime monitoring history. Once the alert goes out, the incident works as usual and closes on its own when checks pass again.
Yes. Alerts go out by email on every plan, in Slack from Starter and through outgoing webhooks from Pro, and a webhook is how you forward incidents to the on-call tool you already use. WebPixie sends a notification when an uptime, SSL or domain incident opens, when its severity changes significantly and when it closes, with email templates in English and Turkish. The same incident that opens in WebPixie is the one your channel receives, and it closes on its own when checks pass again. WebPixie detects and records the incident; your on-call tool decides who gets paged and how. Notifications are switched on or off per resource, so low-priority uptime monitors can stay quiet while production endpoints alert. By default, email goes to every member of the workspace. The channels included in each plan are on the pricing page.
WebPixie notices an outage on the next scheduled check, so the check interval you set for each monitor decides how quickly a failure is seen. The interval can be anything from 30 seconds to 24 hours, depending on your plan. Check options such as the method, headers, status codes, keywords and authentication are available on every plan. After a failing check, a timeout or connection error is retried in place and, on paid plans, verified from the monitor's other selected locations, which adds a short delay but keeps blips from paging you. A wrong status code or a keyword mismatch counts as down on the first check. The notification goes out as soon as the failure is confirmed, and the open incident is then re-checked more often so recovery is seen sooner. Endpoints that page people work best with a short interval, while low-risk pages can stay on a longer one. You can see how checks are confirmed under uptime monitoring and the interval for each plan on the pricing page.
Yes. Each uptime monitor can send HTTP Basic, Token or Digest authentication, custom request headers and a request body as form data, raw text or JSON, with the HTTP method you choose. You decide which status codes count as up, and a keyword check can require or forbid text in the response, so a health route that returns 200 with an error message still fails. A timeout of up to 15 seconds, a custom User-Agent and a follow-redirects switch round out the settings, and all of them are available on every plan; only the check interval depends on the plan. Every check records its location, response time, status code and response headers, and a failed check opens an incident on paid plans. You can compare intervals and monitor limits on the pricing page.
Yes, as long as the job or service can answer over HTTP or HTTPS, because WebPixie checks what your services expose from the outside. An uptime monitor target can include a port and a path, such as billing.example.com:8443/status, and the usual settings apply to it: method, headers, authentication, accepted status codes and timeout. For background work, you can expose a small health route that reports the state of a queue, a worker or the last run of a scheduled job, then add a keyword check that fails when the state is wrong, for example when the response contains "stale" or "failed". The route can be protected with a token that the monitor sends, so only authorized callers can read it. A failure opens an incident on paid plans and reaches your team through your alert channels. Around the endpoint itself, SSL monitoring validates the certificate on every resolved IP, domain checks warn before a registration expires, and DNS checks keep a history of record changes.
Checks run from multiple global locations, such as London and New York, and you choose the locations for each monitor; if you pick none, WebPixie assigns one. Cross-location verification only uses the monitor's other selected locations, so a monitor with a single location is only ever checked from there, which matters for teams with data-residency rules. On paid plans, Support opens additional regions within 24 hours if you need coverage closer to your users. To let checks through a WAF or an allowlist, you can add a secret custom request header or a custom User-Agent to the monitor and allow requests that carry it; both settings are available on every plan. That keeps the rule tied to your own monitor rather than to network addresses. Each check records the location it ran from, so the uptime monitoring history shows which region saw a failure. Location counts for each plan are on the pricing page, and you can contact us to request a region.
Yes. You can pause an uptime monitor from the dashboard before planned work and resume it afterwards, or do both from your deploy pipeline through the GraphQL API. A paused monitor runs no checks and opens no new incidents, so a planned restart does not wake anyone. Paused time is recorded as unmonitored and left out of the uptime percentage, so a deploy window does not lower the figure you report. With the API, available on paid plans, one call pauses up to 100 monitors and another resumes them, which fits a pre-deploy and a post-deploy step in CI. For that step, it is best to use a key limited to the service's own monitors, so it cannot touch anything else. When a new service ships, the pipeline can also create its monitor, so coverage keeps up with what is deployed. Resuming is the step not to forget: a paused monitor stays silent until someone turns it back on. Uptime monitoring covers monitor settings, and the uptime API reference covers the pause and resume mutations.
Yes. Each service you run on its own subdomain, such as an API, an app, docs or a marketing site, can be a site in one workspace, with its endpoints added as uptime monitors. Uptime monitoring gives each endpoint its own method, headers, auth, accepted status codes, keyword check and interval, so a payment API and a docs page can follow different rules. For each site you choose which checks run, such as SSL, DNS and domain monitoring, and the Certificates Manager lists subdomains seen in Certificate Transparency logs, so you can add the ones you missed. Tags label monitors by service and environment and let you filter to production or staging, and per-resource notification settings decide which monitors send alerts. Capacity depends on the plan: site limits are Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), and uptime monitor limits are Free (3), Starter (20), Pro (50), Enterprise (unlimited). You can compare all limits on the pricing page.
Metrics tools watch your systems from the inside, while WebPixie checks from the outside what users and integrations reach over the public internet. It also covers the certificates, DNS and domains around those endpoints. An internal dashboard can look healthy while an expired certificate on a forgotten subdomain or a lapsed domain keeps users out. Uptime monitoring checks your public endpoints from multiple global locations, SSL monitoring validates the certificate on every resolved IP each day, and the Certificates Manager lists subdomains seen in Certificate Transparency logs. Domain checks warn before a registration expires, and DNS checks keep a history of record changes. WebPixie runs alongside your metrics stack: metrics help explain why something broke, and WebPixie shows whether people can reach it. Depending on your plan, incidents go to the same Slack channel or, through a webhook, to the on-call tool you already use, so there is no new place to watch. You can compare plans on the pricing page.
Public status pages are coming soon; they are in development and not available yet. Until then, incidents reach your team by email on every plan and, depending on your plan, in Slack or through a webhook, so you can update customers through the channel you use today. On paid plans, each incident record keeps its type, start time, duration and the notes your team adds, which gives you the facts for a customer update or a postmortem. If you report uptime to customers, the uptime percentage in uptime monitoring leaves out unverified failures and paused time, so it reflects real downtime rather than blips or planned work. If a status page matters for your team, you can tell us what you need from it, such as which services it should list or how incidents should appear.
For Digital Agencies
Yes. The simplest setup is to add every client site to a single workspace and organize it with folders and tags, so one dashboard covers your whole client list. Workspace management lets you put each client's sites in a folder and tag sites and uptime monitors by client, contract or project, then filter by a tag to focus on one client. For each site you choose which checks run, such as uptime, SSL, DNS, domain and link checks. Site and monitor limits apply per workspace and depend on the plan: Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited). A plan belongs to one workspace, so opening a separate workspace for every client means a separate subscription for each one. You can compare limits on the pricing page and see agency workflows under solutions for agencies.
The right plan depends on the number of client sites and uptime monitors you need in one workspace, because limits apply per workspace and the two are counted separately. Site limits are Free (1 site), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), and uptime monitor limits are Free (3), Starter (20), Pro (50), Enterprise (unlimited). A site covers the daily checks for one domain, such as SSL, DNS, domain and link checks, while each uptime monitor watches one URL. A client whose homepage and checkout page you want to watch therefore uses one site and two monitors, so it helps to count monitors as well as sites when you size the plan. Incident tracking is included on the Starter, Pro, Enterprise plans, and check intervals, team seats, Slack and webhook alerts and the support level also change by plan. If you are moving a large client list from another tool, you can talk to us and we will walk you through WebPixie. The full breakdown is on the pricing page.
Yes, through a workspace that holds only that client's sites, because WebPixie roles apply to a whole workspace rather than to single sites. If you invite a client contact with the read-only User role to your shared agency workspace, they will see every site in it, including other clients' sites. Inside your agency, one workspace with a folder per client is enough, and nothing in it is visible to anyone outside your team. Once a client should log in, their sites belong in a separate workspace that runs on its own plan: either the client pays for it and invites your team as Admins, or you run it for them. Each plan has its own user limit, so it is worth checking that it leaves room for the client and your team. Inside that workspace the client can follow uptime, incidents, WebPixie Site Score and the periodic PDF report without changing any settings. You can see how roles work in workspace management and compare user limits per plan on the pricing page.
Your team shares one workspace, and each person gets the Owner, Admin or User role that fits their job. As workspace management describes, Owners control billing, membership and workspace settings, Admins manage sites, uptime monitors and incidents, and Users have read-only access. On paid plans, everyone sees the same incident during an outage, with its severity, affected resource and duration. Admins can add a note to it, such as what the host said or when the client was told, so whoever picks it up next has the context. Every configuration change is recorded in an audit trail. User limits depend on the plan, so you can compare team capacity on the pricing page.
You can bring each client the uptime rate, incident history and open findings of their own sites, while the automatic PDF report summarizes a whole workspace. For a monthly update, each uptime monitor shows its uptime rate, down count and response-time chart over a date range you pick, and on paid plans you can filter the incident list by site to show what happened and how long it lasted. The site's findings and WebPixie Site Score show what is still open. Each finding is ranked by severity and linked to fix guidance, so it can become a line in the client's maintenance plan, and domain and certificate expiry warnings arrive weeks before a renewal, which gives you a reason to call the client in time. The periodic PDF report is emailed to every member of a workspace and covers the median Site Score, the top and bottom sites and the incidents of the period. In a shared agency workspace it covers all of your clients, so it suits your team's own review; a client gets their own report from a workspace that holds only their sites. The schedule depends on the plan: Free: monthly; Starter: bi-weekly, monthly; Pro: weekly, monthly; Enterprise: weekly, bi-weekly, monthly. You can compare schedules on the pricing page.
No. WebPixie checks client sites from the outside with ordinary requests, so nothing is added to the site and there is no agent to install. Uptime monitoring sends a request per monitor at the interval you choose, and the daily checks fetch the homepage once along with certificate, DNS and registry data. The Link Crawler is the largest check: about once a week it requests the internal pages it finds, up to your plan's link limit per site, which is a light load for a typical site. You do not need hosting access or DNS changes to start. If a client's firewall blocks unknown traffic, you can set a custom User-Agent on each uptime monitor so its requests are easy to allow; this setting applies to uptime monitors only, not to the daily checks or the Link Crawler.
Yes. WebPixie checks any publicly reachable website from the outside, so it works the same way on WordPress, Webflow, Shopify or a custom build, with nothing to install on the site. Uptime monitoring can also require a keyword on the page, which catches a page that loads but shows the wrong content, such as a maintenance screen. On hosted platforms such as Shopify, the platform manages the servers and the SSL certificate, so uptime, domain expiry and broken links are usually the most useful checks there. SSL monitoring matters most for sites that you or the client host. The Link Crawler works on any platform and finds pages that return a 404 after a content change.
Not yet. Public status pages are in development and coming soon to WebPixie. Today, uptime monitoring watches your client sites, and on paid plans a failed check opens an incident and alerts your team by email, or by Slack and webhooks on higher plans, so you can update the client yourself. Each incident records its type, severity, start time and duration, which gives you the facts for that update. The Free plan sends the same email alert without the incident record. When status pages launch, we will share what they include and which plans offer them. Until then, you can compare what each plan includes on the pricing page.
You can add them in the dashboard one at a time, or script the whole list with the GraphQL API, which is available on the Starter, Pro, Enterprise plans. In the dashboard, each new site takes a domain and your choice of checks, such as SSL, DNS, domain, link and sitemap checks, and monitoring begins right away. The API has mutations for creating sites, uptime monitors, folders and tags, so a short script can read your client spreadsheet and set up each site, its uptime monitors and its client folder in one pass. API keys can be made read-only or limited to specific sites, so the import needs a key with write access that is not limited to specific sites. Plan limits are worth keeping in mind, since sites and uptime monitors are counted separately per workspace. If you are moving a large client list from another tool, you can talk to us and we will help you plan the move.
Yes, it shows the signals that decide crawler access: the robots.txt and llms.txt rules, explicit rules for known AI crawlers, and the crawled pages that robots.txt blocks. The Indexability Checker reads robots.txt and llms.txt line by line with validation results, so a staging rule that blocks every crawler stands out after a launch. It lists which AI crawlers, such as GPTBot, ClaudeBot, Google-Extended and PerplexityBot, have explicit rules, any Content-Signal directives, and whether robots.txt points to a sitemap. The Link Crawler marks crawled pages that robots.txt disallows, and on the Starter, Pro, Enterprise plans, Sitemap Monitoring also flags pages that are missing from the sitemap. The homepage view shows the canonical URL and alternates too. These are signals to review rather than a ranking report or a verdict on whether a search engine has indexed a page. On-page SEO checks and Lighthouse scores are coming soon, and the marketers solution covers search and AI visibility in more depth.
Yes, once you tell it what to look for: an uptime monitor can require words that must or must not appear on the page. A PHP error or a maintenance screen often still returns a page, so a check that only waits for an answer would report the site as up. In uptime monitoring you can require the client's brand name or a button label such as "Add to cart", and treat phrases such as "critical error" or "Briefly unavailable" as a failure. You can also set the accepted status codes, choose whether redirects are followed, and add HTTP authentication for a password-protected staging site. When a rule fails, your team is alerted, and on paid plans the failure opens an incident with its duration. WebPixie checks only the words and codes you set, so it helps to add the error messages each client's platform shows. You can compare check intervals on the pricing page.
Once you add the site, its first checks show what was left behind: findings ranked by severity, broken internal links, and certificates seen for the domain and its subdomains. Site analysis reviews security headers, SSL setup, DNS records including SPF and DMARC, and domain status, and each finding links to fix guidance, so you can turn the list into a first-month work plan. The Link Crawler lists pages that return a 404 or a server error, together with the pages that link to them. The Certificates Manager pulls Certificate Transparency logs and lists the certificates issued for the domain and its subdomains, which often turns up an old staging host or a forgotten campaign site. Each discovered subdomain has an Add Site action to start monitoring it. Domain monitoring shows the registrar, the expiry date and the status flags, so you know when the next renewal is due.
Yes. Once the client contact has joined the workspace, the owner can transfer ownership to them, and the client then controls the workspace settings, membership and billing. This works well when you set up monitoring for a client in a workspace that holds only their sites: you configure the sites and uptime monitors, invite the client, and hand the workspace over when the project ends or the client wants to pay for it directly. Your team can stay on as members if the client keeps you in the workspace. Only the owner can transfer ownership, not an admin. The workspace management page explains roles and invitations, and the pricing page shows what each plan includes.
For Marketers
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.
Yes. WebPixie checks any publicly reachable URL from the outside, so landing pages built in HubSpot, Webflow, WordPress or another page builder work the same way, with nothing to install. You can add the page URL as an uptime monitor, set the status code it should return and pick a keyword it must contain. One thing to know about builders: keyword checks read the HTML the server sends and do not run JavaScript. Most builders put the headline and form labels in that HTML, but a form or widget that a script loads after the page opens may not be there. You can open the page source in your browser and search for your keyword; if it is there, the check can see it. If your landing pages sit on their own subdomain, such as go.example.com, you can add that subdomain as a site too, so its SSL certificate is checked every day. The Link Crawler then follows the links on that site and lists pages that return an error.
Yes. The Link Crawler follows the internal links on your site about once a week and lists every page that returns a 404, a server error or a redirect. Broken links usually appear after a redesign, a site migration or a cleanup of old campaign pages. The Link Crawler starts at your homepage and checks internal links up to your plan's limit. For each broken URL it shows which of your pages link to it and how often, so you know exactly which page to edit. Results appear in the dashboard after each crawl. Outbound links to other sites are listed with their nofollow, sponsored or ugc attributes, but they are not checked. On paid plans, Sitemap Monitoring adds one more signal: crawled pages that are missing from your sitemap. Link limits differ by plan, so it is worth comparing them on the pricing page if your site has many pages.
Yes. DNS Monitoring checks your domain every day and analyzes its SPF, DMARC and BIMI records, which mailbox providers look at when your newsletter arrives. Gmail and other large providers expect bulk senders to publish SPF and DMARC, and a missing or broken record is easy to miss because nothing on the website looks wrong. DNS monitoring shows each record, says when one is not found and explains what to fix, with guidance links you can forward to whoever manages your DNS. WebPixie also keeps a log of DNS changes with the old and new value, so after someone edits a record you can see what changed. The check reads the records themselves; it does not send test emails or measure where your newsletter lands. The same daily check covers TLS-RPT and MTA-STS records, and Domain monitoring warns you 30 days before the domain you send from expires.
Yes. SSL Monitoring checks your certificate every day and, by default, warns you 15 days before it expires, which leaves time to renew before visitors see a browser warning. On a landing page, many visitors leave rather than click past that "Your connection is not private" warning, whatever the ad promised. SSL monitoring raises the severity as the date gets closer and sends one more email when it becomes critical. The daily check also fails when the certificate has already expired, does not match the domain or is not trusted by browsers, and every workspace member gets an email. On paid plans each of these is kept as an incident with its duration. If a campaign runs on its own domain or subdomain, you can add it as a site so its certificate is checked too. The Certificates Manager lists the certificates that public logs show for your domain and its subdomains. Renewal itself stays with whoever manages your hosting; WebPixie tells you when it is due.
Yes. Every uptime check records how long your landing page takes to respond, so you can see a page getting slower over days or weeks before it starts timing out. Uptime monitoring measures server response time from the monitoring locations you select, and each monitor shows a response-time chart with minimum, average and maximum values for the date range you pick. If a response takes longer than the timeout you set, up to 15 seconds, the check counts the page as down and you get an alert. This measures how fast the server answers, not how long the full page takes to render in a browser. For your homepage, the Main Page Analyzer also breaks the response into DNS lookup, connection, TLS and time to first byte, and records the browser load time. Lighthouse-based performance scoring is in development and coming soon.
You can send them the check details WebPixie records: the time, location, status code, response time, error and response headers of each failed check. That is far more useful than "the site is down", because it shows what the server actually returned and when. In uptime monitoring each monitor keeps a full check history that you can filter to failed checks only. On paid plans the problem is also kept as an incident with its type, such as a timeout, its severity, when it started and how long it lasted, and you can add a note for the team. Findings from the site analysis, such as a weak DMARC record or a missing security header, come with links that explain how to fix them, so you can forward a finding as it is. The workspace owner can also invite your developer, and with workspace management give them the Admin role to change monitors or the read-only User role to follow results. WebPixie does not fix the site itself; it gives the person who does the facts they need.
Not yet. Lighthouse-based performance and SEO scoring and an on-page SEO audit of titles, meta descriptions and headings are in development and coming soon. Today WebPixie covers the technical side that keeps pages reachable and crawlable. The Link Crawler finds broken internal links and records each crawled page's title, meta tags, canonical and hreflang. The Indexability Checker reviews robots.txt and llms.txt, Sitemap Monitoring shows sitemap coverage, and the Main Page Analyzer shows your homepage's connection timing, page load time and redirect chain. Uptime and keyword checks confirm that campaign pages stay online and show the right content. These checks do not replace a full SEO tool.
For Business Owners
Your host usually watches its own servers, while WebPixie checks your website from the outside, the way a customer sees it. It also covers parts your host may not handle at all. A server can be running while your homepage shows an error, a plugin breaks the booking page, or the certificate stops being trusted. The domain is often registered somewhere else entirely, so a failed renewal is not your host's alarm to raise. Uptime monitoring checks your pages from multiple global locations and can confirm that a page shows the words you expect. Domain monitoring and SSL monitoring warn you weeks before either one expires. You also keep your own record of downtime and response times, which helps when your host's report says everything was fine. On a managed platform such as Shopify or Wix, hosting and the certificate are usually the platform's job, so a keyword check on the order page, domain monitoring and the Link Crawler are the most useful checks. WebPixie runs alongside your host and needs no access to your hosting account.
For a single site where a short outage is not costly, the free plan is often enough, and it has no time limit. It covers 1 website and 3 uptime monitors at 15-minute check intervals, with email alerts and a monthly report, and it includes SSL, DNS, domain and link checks for that site. Paid plans make sense when the site brings in orders, bookings or leads: they check more often, re-check a timeout from the monitor's other selected locations before alerting, and add incident management with a history of every outage and how long it lasted. They also add Slack alerts, more sites and team members. You can start on the free plan and upgrade later without setting anything up again. You can compare the plans on the pricing page or read how checks work in uptime monitoring.
Yes. You type your web address, choose what to watch, and monitoring begins right away, with no plugin, no hosting login and no DNS change. WebPixie checks your site from the outside, the way a visitor reaches it, so it works the same for WordPress, Wix, Shopify, Squarespace or a custom-built site. When you add the site, you pick the checks: uptime monitoring for outages, plus daily checks of your certificate with SSL monitoring, your registration with domain monitoring, and your DNS records. Alerts arrive by email, so you can forward them to whoever runs your website. In the dashboard, results appear as statuses, a Site Score from 0 to 100 and findings ranked by urgency, so you never need to read raw certificate or WHOIS data. Later, when you feel ready, you can add a monitor for your booking or order page and tell it a phrase that must appear there.
You can forward the finding to whoever runs your website, such as your developer, agency or hosting provider, because each finding explains the problem and links to fix guidance. WebPixie ranks findings as Critical, High, Medium, Low, or Info, so you can see which ones need attention first and which can wait. A finding names the affected part of the site, for example a missing security header, an SSL setting or a DNS record, which gives the person fixing it a clear starting point. After the fix goes live, the next check updates the finding and your WebPixie Site Score. If an alert is about an expiring domain or certificate, the renewal usually happens in your registrar or hosting account. You can see how findings work on the Main Page Analyzer and Security Headers Checker pages.
WebPixie keeps checking your site around the clock, so an outage at night or on a weekend is caught on the next scheduled check and emailed to you. Checks run from multiple global locations on the interval you set for each monitor, from every 30 seconds to once a day depending on your plan. A timeout or connection error is retried before anyone is alerted, and on paid plans WebPixie also re-checks from the monitor's other selected locations, so a brief network blip does not send a false alarm. Once the site is down, WebPixie checks it more often to spot the recovery sooner, then emails you again when it is back. Email alerts come with every plan; paid plans add Slack, and higher plans add webhooks. If you already use Slack on your phone, that alert is hard to miss. On paid plans each outage is also kept in incident management with its duration. You can read how checks work on uptime monitoring and compare alert channels on the pricing page.
No. WebPixie emails you only about a short list of events that affect customers, and it retries short network blips before they count as an outage. Alerts cover the site going down and coming back, a certificate that stops working or is about to expire, and a domain that is expiring or put on hold. On paid plans a timeout is also re-checked from the monitor's other selected locations before anyone is alerted. You can also set a monitor to alert only after a number of failed checks in a row. Expiry warnings do not repeat every day: a certificate warning grows more urgent as the date nears and sends one more email only when it becomes critical. DNS record changes, broken links and findings are not sent as alerts; they wait for you in the dashboard. If one monitor is too noisy, you can switch off its notifications without touching the others. You can see which events send alerts on incident management, and how retries work on uptime monitoring.
Only your own numbers can answer that, but the sum is simple: orders, bookings or enquiries per hour, times their average value, times the hours your site was down. On top of that comes any ad spend on clicks that landed on a dead page, and the time spent answering customers who could not get through. A Friday-evening outage that nobody notices until Monday puts a whole weekend into that sum, so how quickly you find out often matters as much as the outage itself. The free Uptime Calculator turns an uptime percentage into minutes of downtime and has a cost mode for this estimate. Uptime monitoring shortens the unnoticed part by checking your site on a schedule and emailing you when it stops answering, and again when it is back. To check right now whether a site is down, you can use the free Website Down Checker.
When your domain expires, your website and your business email usually stop working together, so customers cannot reach you and replies or invoices bounce. Depending on the registrar and the domain ending, the name may then enter a grace or redemption period before it can be lost. Renewals often fail quietly, for example when the card on file expires and the reminder goes to an old mailbox nobody reads. Domain monitoring checks your registration every day and, by default, warns you 30 days before expiry, with the warning growing more urgent as the date nears. If the registrar puts the domain on hold, or a .tr domain is frozen, WebPixie alerts you that the domain is suspended. Alerts arrive by email on every plan; paid plans also send them to Slack and keep each event in incident management. The renewal itself still happens at your registrar, and the free Domain Lookup tool shows your current expiry date in one check.
Yes. WebPixie checks your certificate every day and, by default, emails you 15 days before it expires, so there is time to renew it before visitors see a warning. The certificate is what puts the padlock next to your address in the browser. When it expires or stops being trusted, visitors get a full-page "Your connection is not private" warning instead of your site, and many leave rather than click past it. SSL monitoring raises the warning's urgency at 7 days and again at 3 days, and it also alerts you when a daily check finds the certificate untrusted or issued for the wrong address. Many hosts renew certificates automatically, but automatic renewal can fail after a move or a settings change, which is exactly the case this catches. The renewal itself happens at your hosting company or website platform, so the alert can go to whoever manages it. On paid plans each warning is also tracked in incident management; you can compare plans on the pricing page.
WebPixie checks whether search engines and AI crawlers are allowed to reach your site; it does not track your rankings or what AI assistants say about your business. Access is the part that breaks quietly: a robots.txt line left over from a redesign can shut out every crawler, and pages that return errors can drop out of results. The Indexability Checker reads your robots.txt and llms.txt line by line, shows which AI crawlers such as GPTBot and ClaudeBot have rules, and checks that robots.txt points to your sitemap. The Link Crawler finds broken internal links and marks pages that robots.txt blocks. On paid plans, Sitemap Monitoring also flags pages that are missing from your sitemap. An on-page SEO audit covering titles, descriptions and headings is coming soon. Uptime checks help too, because a site that is down when a crawler visits cannot be read.
Yes. Every uptime monitor keeps an uptime rate, a count of how many times the site went down, and every check with its time, location, response time and error. That gives you facts to bring to your host or developer instead of a feeling that the site "keeps going down". The response-time chart shows the minimum, average and maximum over a date range you pick, which helps when the complaint is that the site is slow rather than offline. Uptime is calculated the industry-standard way, leaving out periods that were not monitored. On paid plans, incident management also lists every outage with how long it lasted. How far back you can look depends on your plan's data retention: Free: 1 month; Starter: 3 months; Pro: 12 months; Enterprise: custom. The periodic PDF report sums this up on your plan's schedule, so you can forward it as it is. You can see the checks on uptime monitoring and retention by plan on the pricing page.
Yes. WebPixie emails you a PDF health report on your plan's schedule, so you can see how your site did without logging in. The schedule by plan is Free: monthly; Starter: bi-weekly, monthly; Pro: weekly, monthly; Enterprise: weekly, bi-weekly, monthly. The report opens with a short summary: how many sites you monitor, their WebPixie Site Score and whether they stayed up. It then lists the domain, certificate and uptime problems of the period, so a quiet month gives you a short report. On paid plans it also counts incidents and shows how quickly they were resolved, which comes from incident management. The report covers your whole workspace, so if you later add a second site, both appear in the same email. It goes to everyone in the workspace, which keeps your web developer in the loop once you invite them. You can see what the uptime figures are based on in uptime monitoring and compare report schedules on the pricing page.
No. WebPixie monitors the state of a domain's registration; it does not register, transfer, sell, or renew domains. Your registration relationship stays entirely with your existing registrar, and you keep using that registrar for renewals and transfers. What WebPixie adds is an independent daily watch over that registration: expiration and suspended-domain states can generate warnings, while registrar, transfer-lock, nameserver, and status-flag changes are surfaced for review. The separation is deliberate, because an outside monitor catches problems a registrar's own emails can bury, including a renewal that quietly failed. Domain monitoring shows exactly what is tracked, and for a single manual check you can use the free Domain Lookup tool. Ongoing monitoring is available on the free plan on the pricing page.
For E-commerce
Yes. WebPixie checks that your cart and checkout pages load and show the content you expect, but it does not add products, fill in the checkout form or place an order. You can add each page as its own uptime monitor and set the status code it should return. Then you can add text that must never appear, such as "Fatal error" or "There has been an error processing your request", and text that must appear, such as the page heading. If a plugin update or a broken theme replaces the page with an error, the next check fails and you get an alert. The check arrives the way an anonymous visitor does, with an empty cart, so some stores show a short message or send it back to the cart page; text that appears in that state works best. Keyword checks read the HTML your server sends, which matters on headless storefronts that build the page in the browser. Product pages work the same way, with "Add to cart" as the text to look for. The Link Crawler adds a weekly look at the links that lead to these pages.
On a hosted platform, the platform keeps its servers and your certificate running, so WebPixie helps with the parts that are still yours. The first is your domain: if it is registered in your name, domain monitoring warns you weeks before it expires, because a lapsed domain takes the store and your order emails down together. The second is your email records: DNS monitoring checks the SPF and DMARC records that mailbox providers look at before they trust your order confirmations. The third is your content: a theme or app change can leave a product page without its Add to cart button, and a keyword check on that page catches it. The Link Crawler also lists menu and product links that lead to deleted pages. Nothing needs to be installed in your store, and the free plan is often enough for these checks. If the store later moves to hosting you manage, SSL monitoring and faster uptime checks can be turned on then.
WebPixie works with any store that is reachable on the public internet, because every check runs from outside, the way a shopper reaches your site. That includes WooCommerce, Magento and Adobe Commerce, PrestaShop, OpenCart and custom or headless storefronts, and nothing is installed on the store. On a store you host yourself, the server and the certificate are yours or your host's to watch, so it is worth turning on uptime monitoring and SSL monitoring for it. Uptime monitors accept a custom HTTP method, request headers and a request body, so on a headless setup you can also check the API your storefront calls, with text the response must contain. If a staging store sits behind a password, Basic, Token or Digest authentication lets the check through. Keyword checks read what your server sends, not what JavaScript adds later in the browser. For a quick one-off look at whether a store is reachable, you can use the free Website Down Checker.
For a small store where a short outage costs little, the free plan can be enough, and it has no time limit. It covers 1 site and 3 uptime monitors at 15-minute check intervals with email alerts, plus SSL, DNS, domain and link checks for that site, with a crawl of up to 20 links. Paid plans make sense once orders depend on the store: they check more often, re-check a timeout from the monitor's other selected locations before alerting, and leave room for more product, cart and checkout monitors. They also add incident management with a history of each outage and how long it lasted, Slack alerts, Sitemap Monitoring and room for your team. You can start free and upgrade later without setting anything up again. You can compare the plans on the pricing page.
You can add the pages the sale sends traffic to as their own monitors a few days ahead, so you see their normal response times before the traffic arrives. That usually means the sale landing page, the main category, a bestseller and the cart, each as an uptime monitor with text such as the offer headline or "Add to cart". Tagging them with the campaign name shows them together. The response-time chart is worth watching in the days before: a page that keeps getting slower is a warning you can act on before it turns into an outage. Short network hiccups are retried before an alert goes out, and on paid plans a timeout is checked again from the monitor's other selected locations. If a busy page tends to flap, you can set it to alert only after a number of failed checks in a row. Planned maintenance before the sale? You can pause the monitor, and the paused time is left out of your uptime rate. During the sale, Slack alerts on paid plans put the alert where the team is already talking, and incident management records how long each outage lasted.
The sum uses your own numbers: orders per hour, times your average order value, times the hours the store was down. On top of that comes what you spent on ads and emails that sent shoppers to a page that did not load, and the time spent answering customers whose orders failed. It is worth running the sum for your busiest hour as well as a normal one, because an outage during a sale or a campaign costs far more than one at 4 a.m. How long nobody notices often decides the total, so the time between the outage starting and someone hearing about it is the part worth shortening. The free Uptime Calculator turns an uptime percentage into minutes of downtime and has a cost mode for this estimate; even 99.9% uptime allows about 43 minutes a month. Uptime monitoring checks your store on a schedule and emails you when it stops answering and again when it is back. To check right now whether a store is reachable, you can use the free Website Down Checker.
Yes. When a certificate expires or stops being trusted, browsers show a full-page "Your connection is not private" warning instead of your store, and few shoppers enter card details after seeing it. On a store you host yourself, the certificate is your job or your host's. Automatic renewal handles most cases, but it can fail after a server move, a DNS change or a new load balancer. SSL monitoring checks the certificate your store serves every day and, by default, warns you 15 days before it expires, with more urgent warnings at 7 and 3 days. It also alerts you when a daily check finds the certificate untrusted, self-signed or issued for a different address. If the store runs on several servers, WebPixie checks each address and shows you one that serves a different certificate. Certificates Manager lists the certificates issued for your domain and its subdomains, so an unexpected one is easier to spot. On a hosted platform such as Shopify, the platform manages the certificate. The renewal itself happens at your host or certificate provider.
Your storefront stops loading and email on that domain stops too, so order confirmations, shipping updates and customer replies bounce. Renewing it is usually your job wherever the store runs, because the domain is registered in your name, often at a different company than your host or platform. Auto-renewal can fail quietly, for example when the card on file expires and the reminder goes to an old mailbox. Domain monitoring checks your registration every day and, by default, warns you 30 days before it expires, with more urgent warnings at 15 and 7 days. It also alerts you if the registrar puts the domain on hold or it enters a deletion state after expiry. If you sell under several country domains, you can add each one, and they are all watched the same way. Renewal still happens at your registrar. To see an expiry date right now, you can use the free Domain Lookup tool, and plans are compared on the pricing page.
WebPixie checks the domain records that mailbox providers look at before they trust your email, which is one of the first things to rule out. Providers such as Gmail check SPF, which lists who may send mail as your domain, and DMARC, which tells them what to do with mail that fails those checks. A store often sends from several places: the store itself, an email service for order mail and a newsletter tool. Each one has to be allowed, and a new sender added without updating SPF can see its mail treated as suspicious. DNS monitoring reads your records every day, analyzes SPF and DMARC, and lists what is missing or set up incorrectly with guidance to fix it. It also keeps every DNS change with its old and new value, so after a switch of email service you can see exactly what changed. These records are usually yours to manage even when the store runs on a hosted platform. WebPixie cannot see whether a particular email reached the inbox. To look up your records once, you can use the free DNS Lookup tool.
Yes. The Link Crawler starts at your homepage, follows internal links across the store and lists the ones that return a 404, a server error or a redirect. For each broken link it shows which of your pages link to it, so you know which menu, banner or product description to edit. It crawls again about once a week, and results appear in the dashboard after each crawl. Each crawl checks links up to your plan's limit, and a large catalog can have more links than that, so it helps to add your best-selling product and category pages as uptime monitors as well; those are checked on the schedule you set. On paid plans, Sitemap Monitoring reads your sitemap and shows crawled pages that are missing from it. After a migration, an old product URL that now returns a 404 usually needs a redirect to its replacement, and the crawl shows where it is still linked from.
Yes, with a keyword check on that product page, which alerts you when text you name appears or disappears. You can add the page as an uptime monitor and set "Out of stock" or "Sold out" as text that must not appear, and you hear about it when a bestseller sells out. You can set the price or "Add to cart" as text that must appear, and you hear about it when an update removes it. Matching ignores upper and lower case and looks for the text anywhere in the HTML your server sends, so wording that appears only in that state works best: a "Sold out" label in a related-products block on the same page would also count. Text that JavaScript adds after the page loads is not seen. Each product you watch uses one uptime monitor from your plan, so the products that matter most are a good place to start. The check runs on the interval you choose, and the alert reaches every workspace member by email. On paid plans each event is also kept as an incident, so you can see how long the product was unavailable.
WebPixie checks whether search engines and AI crawlers are allowed to reach your store; it does not track rankings, product listings or what AI assistants say about your products. Access is the part that breaks quietly. A relaunch can ship a staging robots.txt with "Disallow: /", which keeps search engines such as Google and Bing, and the crawlers behind AI assistants such as ChatGPT and Claude, away from the whole catalog. The Indexability Checker reads your robots.txt and llms.txt line by line every day, shows which AI crawlers, such as GPTBot and ClaudeBot, have their own rules, and checks that robots.txt points to your sitemap. The Link Crawler marks pages that robots.txt blocks, and on paid plans Sitemap Monitoring shows crawled pages missing from your sitemap. Keeping the cart, checkout and filter pages out of search is normal; what to look for is a rule that also catches product or category pages. To get an email if a product page turns noindex, you can add "noindex" as text that must not appear on its uptime monitor.
Yes. Alerts go by email to every member of the workspace by default, so anyone you invite hears about a problem when you do. On paid plans you can invite people by email: your developer or agency as an Admin, who can manage sites, monitors and incidents, and a colleague who only needs to look as a read-only User. Roles apply to the whole workspace. Slack alerts start on the Starter plan, and from Pro a webhook can pass alerts to the on-call or chat tool your developer already uses. Workspace management explains roles and invitations. An agency that runs several client stores often keeps them in its own workspace, sorted with folders and tags; the agencies page covers that setup. Every member also receives the PDF report on your plan's schedule, which helps when someone outside your company runs the store. You can compare team sizes on the pricing page.
For SaaS Companies
A good place to start is what customers would notice first: the login page, a health route on your API and the app itself, plus the certificates and domain behind them. Each route can be added as an uptime monitor with a keyword or status rule, so a page that loads with an error still counts as down. Then the app, the API, the docs and the marketing site can be added as sites, which turns on daily SSL, DNS and domain checks for each one. The Certificates Manager lists subdomains seen in Certificate Transparency logs, which helps you find the ones you forgot, such as an old launch page. After that, the pages that bring in signups, such as pricing and the sign-up form, are worth their own monitors. The free plan covers 1 site and 3 uptime monitors, which is enough for the most important routes. The pricing page shows how far each paid plan goes.
Before launch or with a handful of users, the free plan is often enough, and it has no time limit. It covers 1 site and 3 uptime monitors at 15-minute check intervals, with email alerts and SSL, DNS, domain and link checks for that site. The MCP server works on the free plan too. What changes once paying customers rely on the product is speed and confirmation. Paid plans check more often, verify network failures from the monitor's other locations before alerting, keep each outage as an incident with its duration, add Slack alerts and the GraphQL API, and let you invite teammates. They also cover more sites, which matters once the app, the API, the docs and the marketing site each need their own certificate and DNS checks. You can start free and upgrade later without setting anything up again. You can compare the plans on the pricing page.
Yes, at the request level: each route you add is called with the method, headers, body and auth you set, and judged by its status code and content. You can point a monitor at your login page with a keyword that must appear, such as "Sign in", or at an API health route with a keyword that must not appear, such as "error", so a 200 response carrying an error counts as down. Monitors can send Basic, Token or Digest auth, custom headers and a request body as form data, raw text or JSON, which lets you check a protected endpoint such as /v1/me with a test account's token. You also choose which status codes count as up. Every check keeps its status code, response time and response headers in the uptime monitoring history. WebPixie sends one request per check and does not click through a multi-step sign-up in a browser, so each important step's route needs its own monitor. On paid plans, failures become incidents that close on their own when the route recovers.
Once you add each subdomain as a site, WebPixie checks its certificate every day, while the Certificates Manager helps you find the subdomains you forgot. SSL monitoring validates the served certificate and its chain, warns you 15 days before expiry by default, and raises the severity at 7 and 3 days on the same incident. A certificate that is expired, untrusted or issued for the wrong name fails the check, which sends an email alert on every plan and opens an incident on paid plans. The Certificates Manager pulls Certificate Transparency logs for your domain and lists the certificates seen for it and its subdomains, with an Add Site action for each subdomain you are not watching yet. WebPixie also checks whether every IP behind a name serves the same certificate and shows a mismatch, such as one node behind a load balancer, as a finding. Renewal still happens with your certificate provider or host. The free plan covers 1 site, so a product with several subdomains needs a paid plan; the pricing page has the details.
WebPixie retries network failures, confirms them from other locations on paid plans and sends one notification per incident, so a two-person team hears about real outages without every blip. A timeout or connection error is first retried in place with backoff. On paid plans, if it still fails, it is checked from the monitor's other selected locations; if the site answers there, no incident opens and the check stays out of your uptime figures. A monitor with a single location has nowhere else to verify from, so important routes need at least two. For a route that flaps, each uptime monitor can wait for several failed checks in a row before alerting. When an incident opens you get one notification, and one more when it closes, by email on every plan, in Slack from Starter and through webhooks from Pro. Notifications can be switched off per resource, so staging can stay quiet while production alerts. Email goes to every workspace member by default.
You can pause monitors before a deploy and resume them after, by hand or from your pipeline; on paid plans the GraphQL API can also create monitors for new services. A paused monitor runs no checks and opens no incidents, and paused time is left out of the uptime percentage, so a planned deploy does not count as downtime. With the API integration, available on Starter, Pro, Enterprise, the pipeline that ships a new service can add its uptime monitor with tags such as production. API keys can be read-only and limited to specific sites and uptime monitors, so a CI job only touches what it needs. The MCP server is open on every plan: with read and write access, you can ask an AI assistant such as ChatGPT or Claude to pause a monitor before a release, or ask what is down right now. For short blips during a rollout, the uptime monitoring setting that waits for several failed checks in a row before alerting also helps.
Yes: each monitor's uptime rate is calculated the industry-standard way, leaving out unmonitored and paused time, and every check is kept so you can back the number up. Failures that cross-location verification dismissed as false positives are left out too, so the figure reflects real downtime. Each check records its time, location, status code, response time and error, and on paid plans incident management lists every outage with how long it lasted. How far back you can look depends on data retention: Free: 1 month; Starter: 3 months; Pro: 12 months; Enterprise: custom. The periodic PDF report sums up uptime and incidents across the workspace on your plan's schedule. Before you promise a number, it is worth checking what it allows: 99.9% is about 43 minutes of downtime a month, and the free Uptime Calculator converts any target. The check interval should match the promise, because a monitor that checks less often can miss a short outage between two checks. Plans and retention are compared on the pricing page.
Public status pages are coming soon; they are in development and not available yet. Until then, incidents reach your team by email on every plan, in Slack from Starter and through webhooks from Pro, so you can post updates to customers through the channels you already use, such as an in-app banner or your support replies. On paid plans, each incident records its type, severity, duration and your notes, which gives you the facts for the customer update and for the follow-up afterwards. When a customer asks how reliable the product has been, the uptime rate and check history in uptime monitoring give you numbers to share, with paused time left out. If a status page matters for your decision, you can contact us and tell us what you need from it.
WebPixie shows whether the DNS records mail providers check, such as SPF and DMARC, are present and set up correctly, which is one of the first things to rule out. DNS monitoring reads your domain's records every day and analyzes SPF, DMARC and BIMI, listing a record that is missing or malformed as a finding with fix guidance. It also keeps every DNS change with its old and new value, so after you switch email providers or add a new sending service, you can see exactly what changed and when. DNS changes are kept as history and do not send alerts, so it is worth looking at the DNS view after any change to your email setup. WebPixie cannot see whether a particular email reached an inbox. If the domain itself lapses, every email from it stops; domain monitoring warns you 30 days before expiry by default, so the renewal does not catch you out.
WebPixie shows the signals that decide access, such as your robots.txt and llms.txt rules, pages robots.txt blocks and pages missing from your sitemap, without claiming to know your rankings. The Indexability Checker reads robots.txt and llms.txt line by line, lists which AI crawlers, such as GPTBot and ClaudeBot, have explicit rules, shows any Content-Signal directives and checks whether robots.txt points to a sitemap. That makes a common launch mistake easy to spot: a Disallow line copied from staging that keeps search engines such as Google and Bing away from the whole docs site. The Link Crawler goes through each site about once a week, lists broken internal links with the pages that contain them and marks pages robots.txt blocks. On paid plans, Sitemap Monitoring also shows crawled pages that are not in your sitemap. Each docs or marketing subdomain is its own site, so you can add every one you care about. An on-page SEO audit is coming soon.
WebPixie shows what anyone can see from outside about your sites' security setup, so you can fix gaps before a reviewer asks. It does not fill in the questionnaire for you. The Security Headers Checker looks at headers such as HSTS, CSP and X-Frame-Options and at cookie settings, and the SSL analysis covers TLS versions, cipher strength, the certificate chain and key size. DNS checks add DNSSEC, CAA and email authentication, and domain checks show transfer and delete locks. Each finding is ranked from Critical to Info with fix guidance, and the next check updates it once the fix is live. The WebPixie Site Score sums these up as a number from 0 to 100 for each site, a quick way to see which subdomain needs attention first. For questions about your monitoring itself, every configuration change in the workspace is recorded in an audit trail that we can provide on request, and workspace roles control who can change what.
For what customers reach over the public internet, yes: uptime, SSL, certificate discovery, DNS, domain and link checks live in one workspace instead of several tools. Each subdomain is a site with its own daily SSL, DNS and domain checks, and each route is an uptime monitor, so the pinger, the certificate script and the domain reminder in someone's calendar can go. Alerts for all of them arrive through the same channels, and on paid plans they share one incident list. The workspace also shows findings from header, SSL, DNS and domain analysis, and a Site Score for each site. WebPixie checks from the outside over HTTP and HTTPS, so your error tracking and server metrics stay in place for what happens inside the app; the two answer different questions. Every check is listed on the features page.
Yes: on paid plans you invite teammates by email to one workspace, and each person gets a workspace-wide role that decides what they can change. Owners handle billing, members and workspace settings; Admins manage sites, uptime monitors and incidents; Users get read-only access, which suits support staff who need to check whether something is down before answering a ticket. Folders and tags keep the product, the API and the marketing site apart within the workspace, and every configuration change is recorded in an audit trail. Alert emails go to all members by default, and notifications can be switched off per resource. How many members each plan allows is on the pricing page, and workspace management explains how roles and invitations work. Anyone on the team can also connect an AI assistant through the MCP server and ask what is down right now.
For Vibe Coders
A successful deploy only tells you the build finished; monitoring tells you whether visitors can still reach the right page hours, days or weeks later. Sites built and hosted with AI tools break in ways a deploy log never shows: the host restarts the app or puts it to sleep, your own domain stops pointing at it, a certificate expires, or a later change breaks one page while the rest still loads. Uptime monitoring checks your site from the outside, from multiple global locations, on a schedule you set, and emails you when it stops answering and again when it is back. A keyword check on an important page, such as your signup page, also fails when the page loads but shows an error instead of your content. SSL monitoring and domain monitoring check your certificate and your registration every day and warn you weeks before either expires. To check a site by hand right now, you can use the free Website Down Checker.
No: you paste your web address, pick what to watch, and WebPixie explains what it finds in plain words, ranked by how urgent it is. It checks your site from the outside, the way a visitor reaches it, so there is nothing to install, no code to add and no setting to change at your host. Results appear as simple statuses, a WebPixie Site Score from 0 to 100 and a list of findings from Critical to Info, so you know what to look at first. Each finding links to fix guidance that explains the problem and how to solve it, which you can hand to your AI coding tool as it is. The Main Page Analyzer covers the security headers, HTTPS redirect and cookies of your homepage, and DNS monitoring covers records such as SPF and DMARC that decide whether your emails are trusted. You can learn the terms along the way, but you do not need them to start.
You can add each important page as its own uptime monitor with a phrase that must appear on it, and WebPixie alerts you when a check finds the phrase missing. After an AI tool rewrites a component, a page can still load with a normal status code while it shows an error message, a blank screen or the wrong content. In uptime monitoring you can require text such as "Create account" on /signup, or forbid text such as "Application error", and choose which status codes count as up. Keyword checks read the HTML your server returns, not the page after JavaScript runs, so for an app that builds its pages in the browser, it is best to choose text that appears in the page source or monitor an API route your app calls. The Main Page Analyzer also loads your homepage in a browser every day and lists JavaScript console errors. Checks run on the monitor's interval, from every 30 seconds to once a day depending on your plan, so you hear about a broken page on the first check after it ships.
Yes. Every finding names the problem and its severity and links to fix guidance, which is the kind of specific instruction AI coding tools handle well. Instead of asking your tool to "make the site secure", you can paste one finding, for example a missing Strict-Transport-Security header or an HTTP address that does not redirect to HTTPS, and ask it to fix exactly that. Findings come from the daily Main Page Analyzer run on your homepage, the Security Headers Checker and the SSL, DNS and domain checks, and they are ranked from Critical to Info so you can start with the most urgent. After your tool makes the change and you deploy it, the next check updates the finding and your Site Score, so you can see whether the fix worked. WebPixie does not change your code or your hosting settings itself. A short note of what you asked the tool to change helps; if a later finding looks related, you will know where to look.
WebPixie checks the security settings your live site shows to visitors: security headers, HTTPS and redirects, cookies, the certificate and TLS setup, and your domain's locks. The Security Headers Checker looks at headers such as HSTS, Content-Security-Policy and X-Frame-Options on your homepage every day, along with how its cookies are set and whether a redirect chain drops back to plain HTTP along the way. SSL/TLS monitoring validates the certificate, its chain and its revocation status, and flags old TLS versions and weak ciphers. Domain checks show whether your domain is locked against transfers. Each finding has a severity and fix guidance, and together they feed your WebPixie Site Score. These are checks of the configuration anyone on the internet can see. WebPixie does not read your code, so a bug in your app's logic or database rules is outside what it can find. The full list of homepage checks is on the Main Page Analyzer page.
Yes. Connected to the WebPixie MCP server with read and write access, your assistant can add the site, create uptime monitors and pause or resume them for you. The MCP server works on every plan, including the free plan. Supported clients are Claude (claude.ai and Claude Code), ChatGPT, Codex and VS Code; you connect by signing in to WebPixie and approving a consent screen, with no API key to copy. On that screen you choose which workspaces the assistant can reach and whether each one is read-only or read and write, and you can narrow access to specific sites and uptime monitors. After that, a prompt such as "Add myapp.com with SSL and domain checks and watch /signup for Create account" is enough. The assistant can also answer questions such as which project went down this week or when a certificate expires. It can never do more than your own workspace role allows, and before a delete it is instructed to ask you first. Setup steps for each client are in the MCP docs.
For one project where a short outage costs you little, the free plan is often enough, and it has no time limit. It covers 1 site and 3 uptime monitors at 15-minute check intervals, with email alerts and SSL, DNS, domain and link checks for that site. The MCP server is included, so you can ask your AI assistant about your monitors or have it add one. Two things usually change the answer: you ship several projects, or one of them now has users, a waitlist or revenue. Paid plans then cover more sites and monitors, check more often, confirm network failures from the monitor's other locations, keep each outage as an incident with its duration, and add Slack alerts and team members. You can start free and upgrade later without setting anything up again. You can compare the plans on the pricing page.
You can put them all in one workspace and sort them with folders and tags, so each project's status, Site Score and findings sit side by side. With workspace management you can group sites into folders, for example "Launched" and "Experiments", and tag sites and uptime monitors with labels such as "live" or "paid users" that you can filter by. Each site shows its WebPixie Site Score from 0 to 100 and its findings, so the project that needs attention stands out. A PDF report of the whole workspace is emailed on your plan's schedule, with site scores, uptime and the issues your projects have in common. Alerts are set per site and per monitor, so you can keep them on for the project with users and switch them off for an experiment. How many sites and monitors fit depends on your plan; the limits are on the pricing page. When you retire an experiment, you can pause or remove its monitors so the report reflects what is still running.
WebPixie catches what visitors run into when a free tier hits a limit or sleeps: an error page, a timeout, slow responses or an expiring certificate. Free tiers often come with limits such as an app that sleeps after a quiet period, a database that pauses or a monthly usage cap. When one of them kicks in, visitors may get a slow first load, the host's error page or no answer at all. Uptime monitoring counts a timeout or an unexpected status code as down, and a keyword check that requires text from your page fails when the host shows its own error page instead. The response-time chart of each monitor shows slow starts and helps you catch slowdowns before they become outages. If your own domain points at the host, SSL monitoring and domain monitoring check the certificate and the registration every day. WebPixie cannot see your host's usage dashboard or billing, so it tells you what visitors experience, not why the host stopped serving.
When a domain expires, the site and any email sent from that domain usually stop working together, and after a grace period someone else may be able to register it. Side project domains are easy to lose: they renew on a personal card that has since expired, and the registrar reminder goes to an inbox you rarely open. Bookmarks, links you shared and signup emails all break at once. Domain monitoring checks your registration every day and, by default, warns you 30 days before expiry, with the warning level rising at 15 and 7 days. If the registrar puts the domain on hold, WebPixie alerts you that the domain is suspended. Alerts arrive by email on every plan, and paid plans also keep each event in incident management. The renewal itself happens at your registrar, and the free Domain Lookup tool shows the current expiry date of any domain in one check.
WebPixie checks whether search engines and AI crawlers are allowed to reach your site; it does not track your rankings or what AI assistants say about you. That covers search engines such as Google and Bing and the crawlers behind AI assistants such as ChatGPT and Claude. Sites made with AI tools often start with a template robots.txt or a noindex tag meant for the preview, and both shut crawlers out without any visible error. The Indexability Checker reads your robots.txt and llms.txt line by line, shows which AI crawlers have rules and any Content-Signal directives, and checks that robots.txt points to your sitemap. The Main Page view also shows the canonical URL of your homepage and whether it answers AI tools that ask for Markdown. On paid plans, Sitemap Monitoring flags crawled pages that are missing from your sitemap. For an alert, you can add "noindex" as text that must not appear on your homepage monitor in uptime monitoring, and the next check fails if the tag ships.
A common cause is missing or incorrect email records on your domain, such as SPF and DMARC, which providers use to decide whether mail really comes from you. When an AI tool wires up an email service for magic links or welcome emails, the DNS side is easy to skip or leave half done, especially after you move to your own domain or switch providers. DNS monitoring reads your domain's records every day and lists SPF and DMARC records that are missing or set up incorrectly, with fix guidance you can follow at your DNS provider or hand to your AI tool. It also keeps every DNS change with its old and new value, so you can see what changed after a move. WebPixie cannot see whether a particular email reached the inbox, and content and sender reputation play a part too, but a broken record is one of the first things to rule out. For a one-off look at your records, you can use the free DNS Lookup tool.
WebPixie emails you about a short list of events, such as your site going down or a certificate or domain about to expire, and retries short network blips first. Alerts go to email on every plan, to Slack from the Starter plan and to webhooks from Pro. A timeout or connection error is retried before it counts as an outage, and on paid plans it is also re-checked from the monitor's other selected locations before an incident opens. You can set a monitor to alert only after several failed checks in a row, and switch notifications off for an experiment without touching your other projects. Expiry warnings do not repeat every day. DNS changes, broken links and findings are not sent as alerts; they wait for you in the dashboard, and your AI assistant can read them through the MCP server. You can see which events send alerts on incident management and how retries work on uptime monitoring.
Still have questions?
Our team is here to help. Once you get in touch, we'll answer any questions you have.