The resulting automation spreadsheet has multiple tabs, one for each case. You can find the details on what each one means here.
When a URL is checked, and the response is a 404 error, then it'll be logged here. A 404 error means that the webpage the URL Checker is trying to access couldn't be found or doesn't exist. It could be due to a mistake in the Final URL or because the page has been moved or deleted.
This sheet has all the URLs that returned response codes 200 or 202 and which don't contain any matching text.
A 200 status code means "OK." It indicates that the request was successful, and the server is sending back the requested information or resource. In simple terms, it means everything is good, and you're getting the content you expected.
A 202 status code means "Accepted." It indicates that the server has received the request but hasn't completed processing it yet. It's typically used for asynchronous operations, where the server acknowledges the request but needs more time to finish the task. It's like a "hold on. I'm working on it" response.
LP Content Warnings
When the URL Checker is able to access the landing page (or returns a successful response code 200 or 202), we fetch the entire HTML Code of that page and then check for the text from the "text to monitor" fields. If such text is found, it's logged in this sheet.
The URLs that fail to return any response are logged under this issue, as they weren't checked. For example, when the automation encounters a 500 error, it implies that the landing page couldn't be accessed and crawled properly. This could impact the URL Checker's ability to detect error codes, monitor specific text, or gather other information from the landing pages for analysis or further actions.
This sheet has all the URLs that were checked and which returned any response codes.
This sheet has the URLs which returned response codes such as 500 (InternalServerError) or Forbidden (403).
When the automation encounters a 500 (InternalServerError) error, it implies that the landing page couldn't be accessed and crawled properly. This could impact the URL Checker's ability to detect error codes, monitor specific text, or gather other information from the landing pages for analysis or further actions.
When the automation encounters a 403 (Forbidden) error, it means that the server is refusing access to the landing pages or blocking the URL Checker tool. As a result, the automation cannot crawl the HTML code or detect possible error codes or text as intended.
This sheet will include the URLs which returned one of the special response codes you specified in the "Check for special response codes" field.
If you run the automation in "Apply mode," this sheet acts as a log and contains all the changes the URL Checker applied to the different entities it is monitoring.