Frequently Asked 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 when issues are detected through channels like email and Slack, so you can respond before your customers notice.

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 at a fraction of the cost. You can monitor uptime from multiple global locations including London, Istanbul, 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. Start monitoring your first site in minutes, and explore the full feature set or pricing plans to find the right fit for your team.

For detailed information, see the Documentation.

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 pages in depth. When something goes wrong, the service sends alerts through your chosen channel so you can respond without waiting for a user report.

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 global monitoring locations such as London, Istanbul, and New York. Each uptime check verifies the HTTP response code, response time, HTTPS connectivity, and any custom keyword conditions you configure. There is nothing to install on your servers.

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 other 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. WebPixie's agents run on its own monitoring infrastructure; after you add a domain, you choose which site checks to enable, while the Main Page 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 sends alerts after a scheduled check confirms an issue. The exact time-to-alert depends on your monitor's check interval, which can range from 30 seconds to 24 hours depending on your plan.

To reduce false-positive noise, network-related failures such as timeouts or connection errors go through up to 4 check attempts with exponential backoff. On paid plans, if all attempts fail, WebPixie also runs verification checks from other locations before opening an incident. This helps confirm a real outage versus a flaky network, so you don't get woken at 3am for a routing flicker in one region.

Email alerts fire on every plan, including Free. What Free doesn't get is Incident Management: an incident list, lifecycle tracking, incident reporting, and the ability to add a note - those start on Starter, alongside Slack (Starter and above) and webhooks (Pro and above). Webhooks integrate with PagerDuty, Opsgenie, or any incident management tool you already use. For SMS or voice workflows, route the webhook through a receiving service that provides them.

WebPixie monitors everything that can take your site offline or hurt its credibility:

• 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
• Site health score - composite 0–100 score built from intelligent analysis across the data WebPixie collects, such as security headers, SSL security and configuration validation, and DNS configuration validation, with severity-tagged findings

All of this sits in one dashboard with a single site health 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, Istanbul, 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 Main Page check runs automatically for every site. It usually takes less than 5 minutes 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.

Yes. WebPixie has a free plan with no credit card required, no time limit, and no trial expiry.

The free plan includes:

• 3 websites monitored
• 5 uptime monitors at 15-minute check intervals
• 20 link crawls 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

Paid plans add faster check intervals (down to 30 seconds), Slack alerts, webhook integrations, WebPixie API access, role-based team workspaces, longer retention, and incident management.

See the pricing page for the full breakdown of what's included in each tier, or start with the free plan and upgrade only if you need more.

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; compare what each tier includes on the pricing page.

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, 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, 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, with payment terms set in the contract and defaulting to NET 7. 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 without a long-term contract or cancellation fee. Cancellation takes effect at the end of your current billing period, so your paid plan features remain available until the period you already paid for ends. You can also change plans from your account settings, and current plan options are listed on the pricing page. Refunds are separate from cancellation timing: initial purchases may be eligible within 14 days if service usage has not begun, and renewals may be eligible within 48 hours after renewal. Full conditions are explained in the Refund and Cancellation Policy. For billing questions or account-specific help, contact support.

WebPixie refunds paid subscriptions only in the specific cases listed in the Refund and Cancellation Policy. For an initial purchase, you may request a full refund within 14 days if service usage has not begun, such as adding a site, creating a monitor, or making an API call. For renewals, you may request a full refund within 48 hours after renewal. Cancellations outside those windows take effect at the end of the paid period and do not create a refund for unused time. We also refund confirmed duplicate or incorrect charges, and qualifying WebPixie-attributable platform outages are handled as described in the Refund and Cancellation Policy. Refunds are returned through the original Stripe payment method. 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, built for sharing with stakeholders or clients who don't have dashboard access, so you do not need to export them manually. 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. Teams that manage several sites can use workspace management to keep reporting organized across clients, brands, or internal projects. 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: unlimited. 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.

Every member of the workspace receives the periodic report by email, regardless of role. The digest goes to Owners, Admins, and Users alike, because it is a workspace-wide portfolio summary rather than an individual or per-site report. A client contact you added as a read-only User gets the same PDF summary as the workspace owner, without needing to sign in to the dashboard. The executive summary, site scores, and uptime stats span every resource in the workspace, including monitored sites and uptime checks, while the SSL and domain detail covers the sites that had a certificate or domain incident in the period. If you manage separate clients or teams, workspace management lets you split them into different workspaces so each group receives only its own report. Report frequency is plan-based, and you can compare included intervals on the pricing page.

Choose monthly billing for maximum flexibility, or yearly billing if you want to 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 review the Refund and Cancellation Policy before committing to a yearly subscription. For billing questions tied to your account, contact support.

WebPixie can run uptime checks from multiple monitoring locations, including London, Istanbul, and New York. 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) are especially useful for customer-facing sites, agencies managing client domains, and teams that need clearer evidence before escalating an outage. 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 other 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 monitoring locations such as London, Istanbul, 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 other 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, use the free uptime calculator. Check intervals and data retention depend on your plan, which you can compare on the pricing page.

Yes, WebPixie can monitor authenticated websites and endpoints when you provide the required access details in the monitor settings. Uptime monitoring supports authentication, custom HTTP methods, custom headers, expected status codes, and body keyword validation, so you can check private dashboards, staging pages, API health endpoints, or password-protected URLs. For HTTP Basic Authentication, you can configure the username and password needed for the request. For token-based access, you can use custom headers when the endpoint accepts a static header value. WebPixie then evaluates the authenticated response using the same down-detection logic used for public pages, including multiple check attempts and cross-location verification on paid plans, and confirmed failures can open an incident. Use least-privilege credentials created only for monitoring, and contact support if your authentication flow requires something more complex.

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, does not store user login passwords, does not store credit card data, and never sells personal data. Primary customer data is stored in EU regions, while operational metadata may be processed globally for security and service operation. 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 and AI tools 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. Review each signal 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, pair it with the Link Crawler, and 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. Many teams run 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 include HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, COEP, CORP, CORS, and Cache-Control. 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.

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, pair crawler results 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 outcome, 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 full map of where your site points out. Pair it with the Indexability Checker for broader crawlability signals, and compare crawl limits on the pricing page.

Yes. The Link Crawler supports a reverse lookup: give it any URL and it returns which of your crawled pages link to that URL. 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. Point it at an external URL to find 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, pair it with the Indexability Checker, and 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, pair it with the Indexability Checker, and 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; 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; see the pricing page for 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; 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; 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 every page covered. WebPixie discovers your sitemaps automatically from the Sitemap: directive in robots.txt, and that reference is also validated by the Indexability Checker. For more on discovery, see Sitemap Monitoring, 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; 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, confirms the hostname matches, and requires TLS 1.2 or higher; 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, OCSP and CRL endpoints, and Extended Key Usage OIDs. 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.

WebPixie uses Certificate Transparency through the Certificates Manager, which turns on automatically for every site with SSL monitoring active. It periodically pulls CT-log entries for each domain you add and lists the certificates seen for that domain and its subdomains. For each certificate it shows the common name, the identity or SAN, the validity window (not before / not after), the issuer, and the serial number, giving you a running inventory of what is in the public record. The same CT data powers subdomain discovery, listing subdomains found in the logs with an action to start monitoring each one. This view is for review, not alerting: WebPixie's notifications come from SSL check failures and expiration, not from CT entries. It differs from SSL monitoring, which validates the certificate your own site actually serves rather than what exists in the logs. Compare plan limits on the pricing page.

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. 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 validates that each covered domain matches the certificate’s claims, 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: who owns the name, when it expires, which registrar manages it, 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, SPF, DMARC, and BIMI; 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 flagged 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 so you can fix it quickly instead of waiting for user reports. 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, 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. To see what is tracked, visit DNS monitoring; 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. A small number of restrictive registries publish limited data, and those cases are flagged in the dashboard so you know when a field could not be read. 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.

Yes, WebPixie provides an API for teams that want to manage monitoring programmatically. The API integration includes queries and mutations for working with monitors, uptime data, incidents, workspaces, and related monitoring resources. Authentication uses resource-scoped API keys with Basic auth, so you can limit access by resource instead of sharing a broad workspace credential. WebPixie API access is available on Starter, Pro, Enterprise plans, and you can compare plan availability on the pricing page. Developers can use the API to create monitors during deployments, pull uptime history into internal dashboards, sync incident data, or connect WebPixie with automation tools. For alert-driven workflows, API usage pairs well with incident management and webhook notifications.

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, you can integrate WebPixie with CI/CD pipelines using our API and webhook notifications. After a deployment, your pipeline can create or update monitors, register new environments, query uptime or incident state, and feed monitoring results into release checks or internal dashboards. The API integration uses API keys with Basic auth and resource-scoped access, which helps keep automation credentials limited to the resources they need. Webhooks can send incident creation and closure events, plus SSL expiration, domain expiration, and domain suspension events, to tools such as Slack, PagerDuty, Opsgenie, or your own deployment automation. This works well when paired with incident management, because confirmed monitoring failures can trigger the same response flow your team already uses. API and webhook availability depends on plan, so compare access on the pricing page.

WebPixie supports custom webhooks that send monitoring events to any HTTPS endpoint you configure. Webhooks are useful for tools such as PagerDuty, Opsgenie, incident management platforms, CI/CD automation, internal dashboards, and custom notification systems. Supported event flows include incident creation and closure for uptime checks, SSL check failures, SSL expiration, domain expiration, and domain suspension. The API integration works alongside webhooks, so teams can receive event-driven callbacks and then query or update resources programmatically. Slack is available as a native notification channel on eligible plans, while webhooks let you connect to systems beyond built-in integrations. Webhook availability depends on plan, so compare notification channels on the pricing page. For alert routing and incident lifecycle details, see incident management.

Yes, WebPixie can monitor staging, development, preview, and production environments when they are reachable by WebPixie checks. Public staging URLs can be monitored with standard uptime monitoring, including expected status codes, response time checks, body keyword validation, and custom request settings. Password-protected or token-protected environments can also be checked when you configure supported authentication details, such as Basic auth credentials or static custom headers. Teams often organize staging, development, and production monitors in separate workspaces or resource groups so permissions and alerts stay clear. Workspace management helps control who can create monitors, view reports, or change settings, and plan limits can be compared on the pricing page.

Yes, WebPixie can integrate with PagerDuty through custom webhooks on Pro and 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. WebPixie posts the same incident and SSL/domain events used across its webhook integrations to your endpoint. This works best when paired with incident management, because confirmed failures become tracked incidents before they are routed externally. Webhook availability depends on plan, so compare notification channels on the pricing page. For programmatic workflows around the same resources, see the API integration.

WebPixie does not send SMS alerts directly, but you can route alerts through webhooks to SMS-capable incident tools. For example, teams can send WebPixie webhook events to PagerDuty, Opsgenie, or a similar alerting platform, then let that tool handle SMS, phone, or mobile push delivery. WebPixie’s own notification channels include email on all plans, Slack on Starter and higher plans, and webhooks on Pro and higher plans. Confirmed monitoring failures can create incidents through incident management, then webhook delivery can pass those events to your external response tools. Compare channel availability on the pricing page. For webhook-driven automation details, see API integration.

WebPixie does not currently provide a dedicated mobile app for iOS or Android. For mobile incident awareness, teams usually rely on email alerts, Slack notifications, or the same webhook-to-PagerDuty/Opsgenie routing used for SMS delivery, so your team can still receive mobile push notifications through the tools already used for mobile response. Alerts can be driven by confirmed incidents from incident management, and webhook or API-based workflows can be planned around the API integration. For plan availability, review the pricing page.

WebPixie helps manage incidents by turning confirmed monitoring failures into tracked incident records. Incident management covers the full lifecycle from detection to notification, tracking, and closure for events such as uptime down, SSL check failure, SSL expiration, domain expiration, and domain suspension. Each incident includes the affected resource, start time, severity, occurrence count, status, duration, and closure timing. Severity levels range from INFO to CRITICAL, which helps teams prioritize response instead of treating every alert the same way. When the underlying check recovers, the incident closes automatically and is marked resolved, so history stays accurate without manual cleanup. Notifications can be sent through email, Slack, or webhooks depending on your plan, and per-resource notification controls help route alerts to the right people. You can compare incident and notification availability on the pricing page, and pair incidents with uptime monitoring for availability workflows.

Yes, WebPixie can monitor multiple websites, APIs, services, and HTTP endpoints across your infrastructure. Uptime monitoring supports HTTP and HTTPS checks with custom methods, headers, expected status codes, authentication, and body keyword validation, so each endpoint can have rules that match its purpose. You can monitor production sites, status endpoints, landing pages, API health routes, staging URLs, and other reachable services in the same workspace. Capacity is plan-based: site limits are Free (3 sites), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), and uptime check limits are Free (5), Starter (20), Pro (50), Enterprise (unlimited). Use workspace management to organize services by team, environment, client, or product area, and configure notifications per resource. You can compare all limits on the pricing page.

Monitoring intervals are plan-based, with current minimums set as: Free (15 minutes), Starter (5 minutes), Pro (1 minute), Enterprise (30 seconds). You can also configure longer intervals up to 24 hours for lower-priority monitors, so a critical API health endpoint can run more often than a low-risk marketing page. In uptime monitoring, the interval affects how quickly WebPixie can detect a failure before the down-detection logic confirms the issue and opens an incident. Faster intervals are useful for customer-facing applications, checkout flows, authentication services, and status endpoints where even short downtime matters. Slower intervals may be enough for informational pages or non-critical internal tools. Check intervals, uptime check limits, and monitoring locations vary by tier, so compare the details on the pricing page. Confirmed failures can then flow into incident management and your configured notification channels.

WebPixie has two layers of false-positive protection for uptime checks. First, when a 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 other locations before opening an incident. 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. 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; when checks recover, the incident closes automatically and is marked resolved. Per-plan check intervals are on the pricing page.

WebPixie delivers notifications by email on every plan, with Slack and webhooks available on higher tiers. Email goes out on incident creation and closure and on SSL expiration, domain expiration, and domain suspension events, with templates in English and Turkish. Slack notifications are available from Starter, and outgoing webhooks from Pro, which is how you connect tools like PagerDuty or Opsgenie: WebPixie posts the event to a webhook URL and your receiving tool routes it onward. Notifications are controlled per resource, so each uptime monitor or other service can alert the right channel without flooding everyone. Confirmed failures originate in incident management, so the same incident that opens in WebPixie is the one that reaches your channel, and it closes when the underlying issue clears. WebPixie does not send SMS or voice alerts and does not run on-call escalation chains. Channel availability by plan is on the pricing page.

Yes, agencies can manage multiple client websites from one WebPixie account using workspaces and plan-based site limits. Workspace management lets you separate clients, brands, or projects so each workspace can have its own monitors, team members, roles, reports, and notification settings. This is useful when one client needs read-only report access while another client should remain visible only to your internal team. Site capacity depends on your plan: Free (3 sites), Starter (10 sites), Pro (50 sites), Enterprise (unlimited). Agencies can monitor uptime, SSL, DNS, domain expiration, link health, and page analysis for each client from the same dashboard. You can compare site, user, and report limits on the pricing page. For agency-specific workflows, see solutions for agencies.

Yes, you can give clients access to their monitoring reports without giving them control over settings. With workspace management, you can invite a client to the relevant workspace and assign a read-only User role so they can view monitoring data, reports, analytics, uptime status, and incident history. Owners keep control over billing and workspace configuration, while Owners and Admins manage monitor creation and notification settings. This works well for agencies that manage separate workspaces per client, because each client sees only the resources tied to their own workspace. WebPixie also generates periodic PDF reports by email on the schedule included in your plan, so clients can receive summaries without signing in. You can compare report frequency and user limits on the pricing page, and review broader agency workflows under solutions for agencies.

Team collaboration in WebPixie is managed through workspaces, invitations, roles, and workspace-level monitoring access. Workspace management supports Owner, Admin, and User roles: Owners have full control including billing, Admins can manage sites, monitors, and incidents, and Users have read-only access to monitoring data and reports. You can invite teammates by email, assign the right role for each workspace, and keep clients or internal teams separated by project. Configuration changes are tracked in an audit trail, including monitor creation, notification updates, invitations, and role changes. Teams can collaborate on incident management by sharing incident history, status, severity, affected resources, and closure timing. User limits depend on your plan, so compare team capacity on the pricing page.

You isolate clients with separate workspaces. In workspace management each workspace holds its own sites, monitors, incidents, reports, and members, so each client's data stays separate from other client workspaces. For a freelancer or a client contact who should see only part of what you monitor, invite them to a dedicated workspace scoped to just that client rather than mixing them into a broader one. Roles set what each person can do: Owners control workspace settings and billing, Admins manage sites and incidents, and Users get read-only access to monitoring data and reports. Email invitations bring people in with the role you choose, and every configuration change is recorded in an audit trail. This lets an agency run many clients from one account without mixing their data. You can compare site and user limits per plan on the pricing page, and see more workflows under solutions for agencies.

Site capacity is set by your plan, broken down as Free (3 sites), Starter (10 sites), Pro (50 sites), Enterprise (unlimited), so an agency can match capacity to the size of its client base. Each site can carry uptime, SSL, DNS, domain, link health, and page analysis at once, and uptime checks have their own per-plan limits separate from the site count. Because clients are organized with workspace management, you can spread your site allowance across client workspaces however you need, rather than being locked to a fixed split. User seats and report frequency also scale with the plan, which matters when you add client contacts as read-only viewers. The full breakdown of sites, uptime checks, users, and reports is on the pricing page, and agency-specific workflows are covered under solutions for agencies.

Uptime affects SEO by keeping your pages reachable for search engine crawlers and real users. A brief outage may not cause an immediate ranking change, but repeated downtime can interrupt crawling, reduce trust in page availability, waste crawl opportunities, and create poor user signals when visitors land on errors. Uptime monitoring helps you detect access problems quickly, including timeouts, unexpected status codes, and missing expected content. For marketers, this matters most on high-value pages such as campaign landing pages, product pages, checkout flows, and content that receives frequent organic traffic. WebPixie pairs uptime checks with multiple check attempts and cross-location verification on paid plans to reduce false positives before alerting your team. For search visibility, combine uptime checks with the Indexability Checker and Link Crawler to catch blocked pages, broken links, and crawlability issues.

Yes, you can monitor campaign landing pages and find out fast when one is broken, slow, or incorrect. Uptime monitoring can check each landing page for reachability, response time, expected status code, redirects, and body keywords such as a campaign headline or form text. This helps catch issues like expired pages, failed deployments, broken tracking redirects, server errors, and missing conversion elements while campaigns are active. You can configure alerts through the notification channels available on your plan, so marketing, growth, or DevOps teams can respond before budget is wasted. For page-quality issues beyond availability, the Main Page Analyzer can surface caching, header, redirect, canonical, and meta problems that may affect conversion or search visibility. Use the Link Crawler to find broken links connected to campaign pages.

Yes, you can monitor multiple campaign pages at once and organize them by workspace, site, or resource. Marketing teams often group landing pages by brand, client, product launch, paid channel, or campaign period so reporting and alerts stay readable. With workspace management, you can invite teammates, separate client or internal projects, and control who can view reports or change settings. Each landing page can have its own uptime monitoring rules, including expected status codes, response time tracking, keyword validation, and notification settings. Per-resource notifications help each campaign owner receive only the alerts tied to their pages. Plan limits determine how many sites and uptime checks you can run, so compare capacity on the pricing page. For page quality and redirect issues, combine campaign groups with the Main Page Analyzer.

Yes, WebPixie checks for broken internal links with the Link Crawler. The Link Crawler starts from your homepage, follows discovered public internal links up to your plan limit, and records per-link health data such as HTTP status code, response time, content size, page title, favicon, redirect status, and timeout behavior. This helps identify 4xx errors, 5xx errors, missing pages, slow destinations, and redirect responses that can affect user experience or search visibility. The crawler also discovers the outbound links on each page and extracts their rel values (nofollow, sponsored, ugc), anchor text, and occurrence count, so you can review your external link profile, though outbound links are listed for review rather than health-checked. Canonical URLs, hreflang tags, and other meta data are recorded for the internal links WebPixie crawls. Re-crawls run on a schedule, typically about once a week, and crawl limits depend on your plan. You can compare limits on the pricing page, then pair results with the Indexability Checker for broader crawlability review.

Yes, WebPixie tracks SSL certificate status, expiration, chain validity, and TLS configuration for monitored sites. SSL monitoring runs daily checks that validate the full certificate chain from leaf to intermediate to root, verify cryptographic signatures, and inspect TLS version, cipher suite, key exchange, and key strength. WebPixie also surfaces Subject Alternative Names, OCSP and CRL endpoints, and Extended Key Usage OIDs; Certificate Transparency entries are available in the Certificates Manager. Expiration alerts are sent by default 15 days before a certificate expires, giving your team time to renew before visitors see browser warnings. SSL check failures and expiration events can create tracked incidents through incident management, depending on your plan. If you manage several domains or subdomains, use the Certificates Manager to review the CT-log inventory in one place.

Yes, WebPixie shows response time data for landing pages during uptime checks. Uptime monitoring measures how long each monitored page takes to respond from the selected monitoring locations, so you can spot slowdowns, timeouts, and regional access problems while campaigns are running. This is especially useful for ad landing pages, checkout entry points, lead forms, and campaign pages where slow server response can reduce conversions. WebPixie can also validate expected status codes and body keywords, helping confirm that the page is both reachable and serving the right campaign content. The Main Page Analyzer adds technical context by checking response time, protocol behavior, redirect chains, cache headers, cookies, and other header-related issues. For broken or slow linked destinations, combine this with the Link Crawler.

WebPixie alerts you when a monitored page becomes unreachable or fails the conditions you configured. No monitoring tool can guarantee that a search engine has not attempted to crawl during an outage, but fast detection helps reduce the duration and SEO risk of availability problems. Uptime monitoring checks for timeouts, connection failures, unexpected status codes, redirects, and missing expected content, then uses multiple check attempts and cross-location verification on paid plans to reduce false positives before opening an incident. Alerts are sent by email on every plan, with Slack and webhooks available on eligible plans, so the right team can act quickly. Confirmed outages can be tracked through incident management, including severity, affected resource, and closure timing. For search-specific risk, combine outage alerts with the Indexability Checker to catch crawl-blocking configuration problems.

Website monitoring is important because it gives you fast visibility into availability, security, and domain problems that can affect customers. If your site is down, slow to respond, serving errors, or failing expected content checks, visitors may leave before they buy, submit a form, or trust your business. Uptime monitoring helps catch outages and response problems early, while SSL and domain expiry checks give lead time before renewal deadlines. DNS checks show record changes with old and new values, so you can review misconfigured records without waiting for a customer complaint. For business owners, SSL monitoring and domain monitoring are especially important because certificate and domain expirations are predictable problems with clear renewal dates.

Yes, you can set up WebPixie by adding your website URL and choosing the checks you want to run. After a site is added, WebPixie can begin checking availability through uptime monitoring, reading SSL certificate details, reviewing DNS records, and collecting domain information. The dashboard presents results as statuses, scores, alerts, and reports, so business owners do not need to read raw headers, WHOIS output, or certificate chains to understand the main risks. You can keep the default settings for routine monitoring, then adjust notification channels, expected status codes, keyword checks, or team access later. If you manage multiple people or clients, workspace management helps keep access organized. For broader site checks, the Main Page Analyzer summarizes homepage quality signals in one view.

Downtime cost depends on your traffic, revenue model, lead value, and how long customers cannot complete key actions. For an ecommerce site, the cost may be lost orders and abandoned carts; for a service business, it may be missed forms, phone calls, bookings, or paid campaign traffic. A practical estimate is to combine expected revenue or lead value per minute with support time, ad spend waste, and recovery work. Uptime monitoring helps reduce that exposure by checking your site on a recurring schedule and alerting when configured response rules fail. Confirmed outages can open incidents through incident management, so your team can track impact and closure history. If you want to check right now whether a site is down, run a free one-off check with the Website Down Checker. Monitoring interval and notification options vary by plan, so review the pricing page when estimating coverage needs.

If your website goes down at night or on the weekend, WebPixie can still detect the outage and send alerts. Uptime monitoring runs on the interval available for your plan and checks your configured response rules, such as status code, timeout, authentication, headers, or body keyword expectations. To reduce false positives from network-related problems such as timeouts or connection errors, WebPixie makes up to 4 check attempts with exponential backoff before treating the issue as confirmed. On paid plans, if all attempts fail, WebPixie also runs verification checks from other locations before opening an incident. When the failure is confirmed, WebPixie can open or update an incident through incident management and notify the channels available on your plan, such as email, Slack, or webhook. This helps the right person respond even outside office hours. Check intervals, locations, and notification options vary by plan, so compare coverage on the pricing page.

If your domain expires, your website, email, and related services may stop resolving for customers. The exact impact depends on your registrar, TLD rules, DNS setup, and whether the domain enters a grace or redemption period. In many cases, visitors can no longer reach the site, email delivery can fail, and search engines may start seeing availability problems. Domain monitoring checks WHOIS or RDAP data daily across supported TLDs and tracks expiration dates, registrar status flags, nameservers, and protection states. WebPixie sends domain expiration alerts by default 30 days before expiry, with higher severity as the deadline gets closer. Domain expiration events can also create incidents through incident management, and DNS monitoring helps you see related record or nameserver problems.

Yes, WebPixie checks SSL certificates daily and sends expiration warnings by default 15 days before renewal is due. SSL monitoring validates the served certificate against the trusted root CAs, confirms it matches your hostname, and requires TLS 1.2 or higher, then reads the full chain, checks the expiration date, and surfaces details such as issuer, subject names, TLS version, cipher suite, and OCSP and CRL endpoints. Early warning matters because an expired certificate can trigger browser security warnings, block customer trust, and make checkout, login, or form submission feel unsafe. If a certificate check fails or expiration reaches an alert threshold, WebPixie can notify your team and, on supported plans, create an incident through incident management. Teams with several domains or subdomains can use the Certificates Manager to review CT-log inventory in one place.

WebPixie warns you weeks before a domain expires, not on the day it lapses. Registration is revalidated every day, so the warning arrives with enough lead time to act, and the alert rises in severity as the date approaches. Daily checks also catch silent auto-renewal failures, such as an expired billing card or a payment that did not go through, which are easy to miss because nothing sends a second reminder. Renewal notices usually land in one mailbox the wider team cannot see, so WebPixie alerts you independently through email, Slack, and webhook, with channel availability set by your plan on the pricing page.

Yes, WebPixie can email periodic workspace-wide PDF summaries according to your plan schedule. Reports are sent monthly on Free, bi-weekly and monthly on Starter, weekly and monthly on Pro, and all available report intervals on Enterprise. Each report summarizes the monitored period across your sites, so you can review availability, incidents (including any certificate or domain issues flagged during the period), and portfolio health without opening every individual check. The incident count and breakdown come with incident management on Starter and above; they are not shown on the Free plan. Uptime monitoring data helps show whether monitored sites stayed reachable, while SSL monitoring highlights certificate validity and expiration risk. The report also reflects broader site-health context through the median WebPixie Score, which rolls up checks such as SSL, DNS, and homepage analysis from the Main Page Analyzer. Report frequency and plan availability can be compared 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. To see exactly what is tracked, visit domain monitoring, 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.