Built it with AI? You see what broke and what to fix
WebPixie watches the sites and apps you ship with tools like Cursor, Claude Code, Lovable or Bolt. It checks that they are up and show the right page, keeps an eye on certificates, domains and security settings, and explains each problem in plain words you can hand back to your AI tool.
No credit card required·MCP on every plan·Free plan with no time limit
Is it up?
It worked in the preview. Is it up for everyone else?
A green "deployed" badge means the build finished. It does not tell you whether the live site still answers tonight, from another country, after the host restarts it or once your own domain points at it. When it stops answering, the first person to notice is often a user posting about it.
WebPixie checks your site from multiple global locations, such as London and New York, on a schedule you choose, from every 30 seconds to once a day depending on your plan. When a check fails you get an email, and a second one when the site is back. From the Starter plan, each outage is also kept as an incident with how long it lasted.
To see what downtime costs you, you can count the signups, waitlist joins or sales you get in a normal hour. Even a 99.9% uptime promise allows about 43 minutes of downtime a month, and the free Uptime Calculator turns any percentage into minutes.
Uptime monitors
3 projects
myapp.com
Checked from London · 200 OK
184 ms
Up- Down
waitlist.myapp.com
Timeout after 15 s · email sent
recipe-helper.app
Checked from New York · 200 OK
326 ms
Up
After an AI change
The AI's last change broke a page and nobody noticed
You ask for a small tweak, the AI rewrites three files, and the signup page now shows "Application error". The homepage still loads, so nothing looks wrong unless you click through every page after every change.
You can add the pages that matter, such as /signup, /pricing or /login, as their own uptime monitors; the free plan has room for 3 uptime monitors. You can give each one a phrase that must appear, like "Create account", or text that should never appear, like "Application error". If the check fails, you get an alert.
The Main Page Analyzer also loads your homepage in a browser every day and lists the JavaScript errors it finds in the console.
Keyword checks read the HTML your server sends, not the page after JavaScript has run. If your app builds its pages in the browser, you can pick text that is in the page source, such as the page title, or monitor an API route your app calls.
Uptime monitors
myapp.com
/signupMust contain "Create account"
Missing
Down/pricingMust contain "per month"
Found
Up/Must not contain "Application error"
Not found
Up
Alert email sent for /signup
Security settings
The AI set up HTTPS and security settings. Are they right?
Security headers, HTTPS redirects, cookie settings and TLS versions are easy to get half right, and an AI tool will happily tell you it is done. You may not know what any of them mean, and you should not have to.
The Main Page Analyzer checks your homepage every day: its security headers, the redirect from HTTP to HTTPS and the cookies it sets. SSL/TLS Monitoring checks the certificate and flags old TLS versions and weak ciphers. Each finding is ranked from Critical to Info and comes with fix guidance.
You can copy the finding and its guidance into the tool that built the site, such as Cursor or Claude Code, and ask it to fix that one thing. The next daily check shows whether the fix worked.
WebPixie checks what your live site shows from the outside. It does not read or review your code.
Finding · myapp.com
Daily homepage check
Browsers are not told to always use HTTPS
Security headers · HSTS
Without this header, a visitor’s browser can still try the insecure http:// address first before it is redirected.
Fix guidance
What you paste into your AI tool
WebPixie says myapp.com does not send a Strict-Transport-Security header. Add it to my hosting config with a max-age of one year and tell me which file you changed.
MCP server
You can ask your AI assistant instead of learning another dashboard
You already spend your day talking to an AI. The WebPixie MCP server works on every plan, including Free, and connects Claude (claude.ai and Claude Code), ChatGPT, Codex and VS Code to your account through a sign-in and a consent screen. You can ask which project went down this week, what the latest check found or when a certificate expires.
With read and write access, it can set up monitoring for you as well. If you ask it to add the project you just shipped with SSL and domain checks and to watch /signup for "Create account", the assistant adds the site and the monitor. On the consent screen you choose read-only or read and write for each workspace.
Claude Code
WebPixie MCP · read and write
- I just deployed waitlist.myapp.com. Add it to WebPixie and watch the signup page.
- Added waitlist.myapp.com with SSL, domain and DNS checks, plus an uptime monitor on /signup that must contain "Join the waitlist". Monitoring has started.
- Did any of my projects go down this week?
- One did: recipe-helper.app timed out on Tuesday night and answered again 18 minutes later. Every other monitor passed all its checks.
Domains, certificates and free tiers
A free hosting tier or a hobby domain lapses quietly
The domain you bought on a whim renews on a card that has since expired, and the reminder goes to an inbox you never check. When it lapses, the site and any email from that domain stop together. Domain monitoring checks your registration every day, warns you 30 days ahead by default and alerts you if the registrar puts the domain on hold.
SSL monitoring checks the certificate on each site daily, warns you 15 days before it expires and alerts you if browsers would no longer trust it, for example when it was issued for a different address than the one visitors use.
Some free hosting tiers put an app to sleep or pause its database after a quiet spell, and visitors get a slow first load or an error page. A keyword check catches the error page, and the response-time chart helps you catch slowdowns before they become outages.
Renewals still happen at your registrar or host. WebPixie tells you in time.
Renewals
3 projects
recipe-helper.app
Domain registration · renew at your registrar
9 days
Highmyapp.com
SSL certificate · renews at your host
12 days
Mediumwaitlist.myapp.com
Domain status · not on hold
Active
OK
Many projects
Ten side projects, one place to look
When you ship a new idea every few weeks, the old ones keep running on hosts, domains and certificates you no longer remember. The project with paying users sits between five experiments.
You can keep every project in one workspace, sorted into folders and tagged, for example "live" or "experiment". Each site gets a WebPixie Site Score from 0 to 100 and a list of findings, so you can see which project needs you first. A PDF digest of the whole workspace also lands in your inbox on your plan's schedule.
The free plan covers 1 site and 3 uptime monitors. The Starter plan covers 10 sites and 20 uptime monitors, and higher plans cover more.
Sites
Launched
- myapp.comliveScore86
- waitlist.myapp.comliveScore79
Experiments
- recipe-helper.appliveScore61
Search and AI
Can search engines and AI assistants find what you built?
An AI tool may copy a robots.txt from a template or keep the "noindex" tag it added for the preview. The site looks normal to you, while search engines such as Google and Bing, and the crawlers behind AI assistants such as ChatGPT and Claude, are told to stay away.
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. From the Starter plan, Sitemap Monitoring also shows pages missing from your sitemap.
These checks cover access, not rankings. Want an alert if a noindex tag ships? You can add "noindex" as text that must not appear on your homepage monitor.
robots.txt · myapp.com
Daily analysis
- User-agent: *
- Disallow: /
- User-agent: GPTBot
- Allow: /
What WebPixie reports
Syntax
ValidAI crawlers with explicit rules
GPTBotSitemap line
Missingllms.txt
Found
Signup emails
Your signup emails land in spam
Magic links, welcome emails and password resets are often the first thing a new user gets from you. If they land in spam, the user decides your signup is broken.
Email providers look at records on your domain, such as SPF and DMARC, to decide whether mail really comes from you. DNS monitoring reads your domain's records every day and lists any that are missing or set up incorrectly. It also keeps every DNS change with its old and new value, so after you switch email providers you can see exactly what changed.
WebPixie cannot see whether a particular email reached the inbox, but a missing or broken record is one of the first things to rule out.
Email records · myapp.com
Checked today
- Found
Email sender check (SPF)
Lists who may send mail for your domain
- Missing
Email protection (DMARC)
Tells providers what to do with fake mail
Mail record changed
Old and new value kept
Yesterday
Change
You can start monitoring in three steps
Nothing to install and no code to add, wherever your project is hosted.
- 1
You paste your URL
You add your site and choose what to watch, or ask your AI assistant to add it over MCP. Monitoring begins right away.
- 2
You choose where alerts go
Alerts go to your email by default. Slack alerts start on the Starter plan and webhooks on Pro.
- 3
You fix it with your AI tool
When an alert or finding arrives, you paste it with its fix guidance into the tool that built the site. The next check shows whether the fix worked.
The free plan covers 1 site and 3 uptime monitors with email alerts and the MCP server, with no time limit. Once a project has users, a waitlist or revenue, or you run several, paid plans add more sites, faster checks, outage history and Slack alerts. You can compare them on the pricing page.
Frequently Asked Questions
Common questions from people who build with AI tools.
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.
Everything WebPixie can watch on what you ship
You can turn on the checks each project needs.
Related Solutions
You can keep what you shipped working
Free plan with MCP, no credit card required.