What does the mixed-content option do?

It checks whether a page served over HTTPS loads resources over insecure HTTP. StatusCake can report the resources that caused the warning.

Why is there no normal page view in my logs?

A basic certificate check can complete at the TLS layer before an HTTP request reaches the application. Edge or TLS logs may still record the connection.

Can an SSL test use a custom user agent?

Yes. StatusCake provides a custom user-agent field for SSL tests, so the header can differ from one customer's test to another.

Does StatusCake SSL Monitoring respect robots.txt?

The bot record marks robots support, but robots.txt cannot stop the earlier TLS certificate exchange. StatusCake does not document a stable SSL-specific robots token.

Does the SSL test affect AI visibility?

No. StatusCake documents certificate monitoring, not AI search or training data collection.

StatusCake SSL Monitoring Bot Guide

What is StatusCake SSL Monitoring?

A StatusCake SSL test starts with an HTTPS endpoint chosen by the customer. It checks the certificate on a schedule and warns about expiry or common certificate problems. The test is scoped to that endpoint rather than discovering pages across the site.

The customer can tell StatusCake to follow redirects and inspect the final destination's certificate. An optional mixed-content check goes further by loading the page and looking for resources requested over insecure HTTP. That option can create more application traffic than a basic certificate check.

Some SSL activity may be visible only in TLS or edge logs because the certificate is exchanged before an HTTP page request reaches the application. StatusCake also lets the customer set a custom user agent, so an HTTP request from an advanced check does not have one universal SSL-specific identifier.

Certificate monitoring has no documented role in AI search or model training. A working HTTPS setup keeps the site accessible to normal clients, including crawlers, but the StatusCake test itself does not change whether an AI service indexes or cites the site.

Not relevant for AI search

Is StatusCake SSL Monitoring relevant for AI search?

No. StatusCake SSL Monitoring is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

StatusCake SSL Monitoring runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle StatusCake SSL Monitoring

Permit the TLS connection and any enabled redirect or mixed-content check when your team relies on the SSL report. If a firewall blocks the test, StatusCake may report the monitoring failure instead of the certificate state you wanted to measure.

Use the StatusCake test settings to change the check rate, pause monitoring, or remove the endpoint. The record has no stable SSL-specific robots token, and robots.txt cannot prevent the certificate exchange that occurs before an HTTP request. If network access needs an exception, use StatusCake's current SSL monitoring locations and the user agent configured on that test.

Examples

After a renewal, StatusCake connects to the configured HTTPS endpoint and records the replacement certificate without crawling unrelated pages.
A test follows a 3xx redirect to another hostname and checks the certificate at the final destination, so the team sees traffic on both hosts.

Frequently asked questions about StatusCake SSL Monitoring

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

It checks the certificate at a configured HTTPS endpoint for expiry and common problems. Redirect following and mixed-content monitoring are optional.