On this page:

The tool will only check landing page URLs of elements that are enabled and that have gotten some impressions in the last 30 days. This means it will check only keywords and ads with impressions that are currently enabled and located in active ad groups and campaigns. For sitelinks, it'll check for enabled state and their association at the account, campaign, or ad group level.

Optionally you can use the advanced setting Include zero impression entities to check the URLs associated with enabled entities that have not received a single impression in the past 30 days.

Regarding the number of broken URLs we show in the email, these are based on any URL that is broken (404). The system finds a total of such URLs for each scope and projects it. If the text to monitor is broken into two or more lines in the HTML code, only the lines will be tracked.

To check redirecting 301 or 302 URLs, you can add the text (301, 302) in the tool's settings under Special Response Codes. However, if you want to get notified of redirections as well as landing pages, then you'll need to create two settings; one containing the 301 or 302 code in special response and one without the codes in the settings.

In this case, the system first checks if a URL is working. By default, it'll follow the URL it is redirecting to and will check if that URL is working. It'll therefore report on the final landing page.

The 429 response status code means that the tool sent too many requests in a short amount of time and got flagged. The way to get around this would be to whitelist our user agent Optmyzrbot/1.0.0 in your firewall service.

This issue usually occurs when the sheet has not been shared with the proper Optmyzr email with the write access. In cases like these, the tool creates a new sheet and updates it with your results. You can always locate this in Automation History while looking for that specific automation run. Also, if you had selected to receive notifications, you can find the new sheet in the email notification. Make sure to share your required sheet with automation@optmyzr-automation.iam.gserviceaccount.com.

Sometimes we are not able to check some URLs temporarily. The response comes in a bit too late or something random happens. This is identified by - RestSharp Issue - RestSharp could not test the URL.

In such scenarios, we re-test the URL using a different technique which, if it fails again, we flag it as - HttpClient Issue - One or more errors occurred. (A task was canceled.)

However, If the URL successfully responds on retry, we don't post any error messages. So this is a failure where both methods failed to get back a response. Please note that this is intermittent and usually on the next runs the URL will be successfully reported.

The URL Checker tool will not check broken URLs for Dynamic Search Ads (DSAs) as Google does not report them to us. In cases where Google sets up ads dynamically, there is a rare possibility that broken URLs would be present.

Same as DSA, dynamically generated URLs are not reported to us in Google's report, so the system won't be able to check them.