General FAQs
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.
How can I report on 301 or 302 redirecting URLs?
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.
What happens if I don't add 301, 302 in special response codes in the URL Checker 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.
What does the Status Code "Returned Response Code 429" mean, and how do I prevent this?
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.
Why didn't the URL checker automation update the sheet that I shared in the schedule with the results?
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.
Why do I see the following error message in the report: Error message: RestSharp Issue - RestSharp could not test the URL. HttpClient Issue - One or more errors occurred. (A task was canceled.)?
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.
Can the URL checker flag broken URLs for my DSA campaigns?
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.
While the tool provides information such as the Campaign ID and Name, Ad Group ID and Name, and Ad ID for DSAs, details like Headlines, Descriptions, and other ad-specific information will not be displayed. We only show those details for easily expandable ads like RSAs.
Does the URL checker flag broken URLs in PMax asset groups?
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.
Can the URL checker specify more than one text phrase to monitor?
Yes, you can specify multiple phrases as comma-separated values in the Text to Monitor field.
Note: the checker searches the full raw HTML source of the page, not just the visible content. If a phrase spans multiple lines in the page's source code, it may not be detected. For best results, use phrases that appear on a single line.
How can I report specific product URLs?
We currently only support reporting on product URLs in Search ads, and we do not work with product URLs in Shopping ads. To report specific product URLs, such as the iPhone link, the URL must be added as a final URL in your Search ads.
Can the URL Checker check more than one final URL per ad or keyword?
Yes. Enable the Check extra URLs setting to check all final URLs configured on each entity in your ad account, not just the first one. This is useful when you're running A/B tests with multiple final URLs set up on the same ad or keyword.
Why are my landing pages flagged in LP Content Warnings when they're working fine?
This usually means one of your Text to Monitor keywords matched a string in the page's source code rather than something a real visitor would see.
Some landing pages often embed JavaScript bundles, translation files, and app state data in their HTML — these can contain phrases like "404: page not found" or "out of stock" as internal labels, even on fully working pages.
To reduce false positives, use longer and more specific phrases that would only appear in the visible content of a genuinely broken page. Also note that you don't need to add "404" as a keyword — the tool already detects 404 responses automatically and logs them in the 404 Error tab.