Testomato

21/05/2026

Setting up website monitoring meant starting with a blank slate. Which pages actually matter? What should you even check? It's easy to miss things and tedious to manually add the right checks for every critical page.

Now there's a better way:

1. Paste your site URL
2. Go make another coffee
3. Review the suggested checks
4. Create a monitored project in one click

Our AI onboarding wizard crawls your site, scores pages by business importance, and reads each one for context — headings, forms, meta tags, structured data. Then it suggests specific checks and verifies every single one against your live site before showing them to you.

If a check fails verification you see exactly why so you can edit the expected value, re-run it, or remove it.

Go from blank project to real monitoring coverage in about 60 seconds.

The wizard is live on all plans. Try it now.

18/05/2026

Do you know the difference between structured data, schema markup, and JSON-LD?

Which entities and relationships are most important for your site? How can they break? How long before you realize they're even broken?

At the request of a customer, we recently added a JSON-LD checker to Testomato. Most guides on this topic cover the first four phases of the schema markup lifecycle: audit, type selection, implementation, validation.

But what happens after the JSON-LD has gone live? How will you know if anything changed or disappeared?

In our latest blog post, we cover the SEO basics about schema markup, common failure modes, and how to monitor your structured data effectively.

Check out the article and if you have some schema markup on your site, try out the new JSON-LD checker. Let us know what you think. 🍅

https://testomato.com/blog/json-ld-monitoring/

30/04/2026

We shipped Content Security Policy monitoring before we had a CSP of our own.

So we had to build one starting from scratch, like most teams do. We deployed a report-only header first to collect violations without breaking anything. The data came in quickly: Gravatar images, GTM and other Google services, as well as third-party scripts that weren't in our initial allowlist.

We're still in report-only but are working toward enforcement. In the meantime, we're monitoring our own header from the outside, just like we monitor any site.

If you're starting from zero, that's where to begin: report-only first, then add monitoring once you have something to check. We wrote up the full process, including what we found when we ran CSP checks on our own site.

testomato.com/blog/content-security-policy-monitoring/

14/04/2026

Uptime and website monitoring sound like they're doing the same job. They're not.

A 404 counts as up. So does a pricing page that lost its pricing table. So does a contact form that silently stopped working. Uptime tells you the server responded. That's it.

302 instead of 301. og:image missing from your most-shared page. A form submission that goes nowhere. These all pass an uptime check. None of them pass a content or functionality check.

So we wrote a guide to website monitoring: what it checks (content, forms, redirects, meta tags), how it differs from uptime, and what to set up first.

Read the guide:

Website monitoring goes beyond checking if your server is online — it verifies that your pages load, forms work, and content is present and correct.

02/04/2026

Your pricing page just returned 301 Moved Permanently.

But you didn't move it.

✅ /home - 200 OK
🚨 /pricing - 301 Moved Permanently

A check fails. An alert fires. You go look.

Maybe a config change. Maybe a deploy side-effect. Maybe someone cleaned up a redirect rule and it overwrote the live URL. Whatever it was, it was silent. There's no error page and visitors quietly bounced from a critical page.

This is why asserting expected status codes per URL matters. Uptime tells you the server is responding. Status code checks tell you it's responding correctly.

The cheat sheet below covers the codes that come up most in monitoring.

👉 testomato.com/http-status-codes-cheat-sheet.html

31/03/2026

HTTP status codes are one of those things where you only need to know a handful by heart, but knowing the right ones tells you exactly where to start looking when something breaks.

502 vs 504. 301 vs 308. 401 vs 403. Soft 404s that return 200 and silently waste your crawl budget.

So we wrote a complete guide covering all the codes that matter for website owners and developers: what they mean, real-world scenarios for each one, and which ones are worth monitoring.

https://testomato.com/blog/http-status-codes/

16/03/2026

We help thousands of websites stay fast and available

Our website 👉 testomato.com wasn't!

361 KiB of unused JavaScript. 3.5s LCP on mobile. Exactly the kind of issues Testomato catches for our customers — and we were guilty of them ourselves.

So we rebuilt. Static site, Astro + Tailwind, PageSpeed finally in the green. 🎉

Read full story here: testomato.com/blog/website-redesign-2026

06/12/2022

Testomato is happy to announce a new feature - Automatic SSL certificate expiration monitoring:

Testomato now offers SSL certificate monitoring for HTTPS websites -- so you can always know when it's about to expire.

31/10/2022