Link Checker Report

===============

Summary

This report provides an overview of the link checker results for the given repository. The report includes the total number of links checked, the number of successful links, the number of links with errors, and the number of links that were excluded or redirected.

Errors per input

Errors in 2-js-basics/2-functions-methods/translations/README.zh-cn.md

• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/10?loc=zh_cn | Network error: Not Found
• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/9?loc=zh_cn | Network error: Not Found

Errors in 6-space-game/4-collision-detection/translations/README.hi.md

• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/36?loc=hi | Network error: Not Found
• [ERROR] [file:///home/runner/work/intro-web-dev/intro-web-dev/6-space-game/4-collision-detection/solution/spaceArt/readme.txt](file:///home/runner/work/intro-web-dev/intro-web-dev/6-space-game/4-collision-detection/solution/spaceArt/readme.txt) | Cannot find file
• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/35?loc=hi | Network error: Not Found

Errors in translations/README.ru.md

• [429] https://docs.microsoft.com/learn/paths/web-development-101/?WT.mc_id=academic-77807-sagibbon | Network error: Too Many Requests
• [429] https://docs.microsoft.com/users/jenlooper-2911/collections/jg2gax8pzd6o81/?WT.mc_id=academic-77807-sagibbon | Network error: Too Many Requests
• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/ | Error (cached)
• [ERROR] https://open.vscode.dev/microsoft/Web-Dev-For-Beginners | Error (cached)
• [429] https://channel9.msdn.com/Series/Beginners-Series-to-JavaScript/?WT.mc_id=academic-77807-sagibbon | Network error: Too Many Requests
• [429] https://channel9.msdn.com/Series/Beginners-Series-to-Nodejs/?WT.mc_id=academic-77807-sagibbon | Network error: Too Many Requests

Errors in translations/README.it.md

• [ERROR] [file:///home/runner/work/intro-web-dev/intro-web-dev/translations/CODE_OF_CONDUCT.md](file:///home/runner/work/intro-web-dev/intro-web-dev/translations/CODE_OF_CONDUCT.md) | Cannot find file
• [ERROR] [file:///home/runner/work/intro-web-dev/intro-web-dev/translations/TRANSLATIONS.md](file:///home/runner/work/intro-web-dev/intro-web-dev/translations/TRANSLATIONS.md) | Cannot find file
• [429] https://channel9.msdn.com/Series/Beginners-Series-to-Nodejs?WT.mc_id=academic-13441-cxa | Network error: Too Many Requests
• [ERROR] [file:///home/runner/work/intro-web-dev/intro-web-dev/translations/CONTRIBUTING.md](file:///home/runner/work/intro-web-dev/intro-web-dev/translations/CONTRIBUTING.md) | Cannot find file
• [429] https://docs.microsoft.com/learn/paths/web-development-101?WT.mc_id=academic-13441-cxa | Network error: Too Many Requests
• [429] https://docs.microsoft.com/users/jenlooper-2911/collections/jg2gax8pzd6o81?WT.mc_id=academic-13441-cxa | Network error: Too Many Requests
• [ERROR] https://open.vscode.dev/microsoft/Web-Dev-For-Beginners | Error (cached)
• [429] https://channel9.msdn.com/Series/Beginners-Series-to-JavaScript?WT.mc_id=academic-13441-cxa | Network error: Too Many Requests
• [429] https://docs.microsoft.com/it-it/learn/student-hub?WT.mc_id=academic-13441-cxa | Network error: Too Many Requests
• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/ | Error (cached)
• [429] https://aka.ms/student-page | Network error: Too Many Requests

Errors in 7-bank-project/api/README.md

• [429] https://aka.ms/learn/express-api | Network error: Too Many Requests

Errors in 3-terrarium/3-intro-to-DOM-and-closures/translations/README.ko.md

• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/19?loc=ko | Network error: Not Found
• [403] https://www.researchgate.net/publication/221417012_Profile-Based_Focused_Crawler_for_Social_Media-Sharing_Websites | Error (cached)
• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/20?loc=ko | Network error: Not Found

Errors in 4-typing-game/typing-game/translations/README.hi.md

• [ERROR] https://localhost:5500/ | Network error: error sending request for url (https://localhost:5500/) Maybe a certificate error?
• [404] https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/21?loc=hi | Network error: Not Found
• [404] [https://ashy-river-0debb7803.1.azurestaticapps.net/quiz/22?loc=hi](https://ashy-river-0de
  Q&A: Link Checker Report

Q: What is a link checker report? A: A link checker report is a summary of the results of a link checking process, which involves scanning a website or a repository for broken or invalid links.

Q: What are the different types of errors that can occur in a link checker report? A: The different types of errors that can occur in a link checker report include:

• 404 errors: These occur when a link is not found or is invalid.
• 429 errors: These occur when a link is too busy or is experiencing high traffic.
• 403 errors: These occur when a link is forbidden or is not accessible.
• Timeout errors: These occur when a link takes too long to load or is not responding.
• Unknown errors: These occur when a link is not recognized or is not responding.

Q: What is the purpose of a link checker report? A: The purpose of a link checker report is to identify and fix broken or invalid links on a website or in a repository. This can help to improve the user experience, reduce errors, and increase the overall quality of the website or repository.

Q: How can I use a link checker report to improve my website or repository? A: You can use a link checker report to identify and fix broken or invalid links on your website or in your repository. Here are some steps you can follow:

1. Review the link checker report to identify the broken or invalid links.
2. Check the links to see if they are still valid or if they have been moved.
3. Fix the broken or invalid links by updating the link or removing it if it is no longer needed.
4. Test the links to make sure they are working correctly.

Q: What are some common causes of broken or invalid links? A: Some common causes of broken or invalid links include:

• Typos: Typos can cause links to be broken or invalid.
• Moved or deleted content: If content is moved or deleted, links to that content may become broken or invalid.
• Changes to website structure: Changes to the website structure can cause links to become broken or invalid.
• Server errors: Server errors can cause links to become broken or invalid.

Q: How can I prevent broken or invalid links from occurring in the future? A: You can prevent broken or invalid links from occurring in the future by:

• Regularly checking links: Regularly checking links can help to identify and fix broken or invalid links before they become a problem.
• Using a link checker tool: Using a link checker tool can help to identify and fix broken or invalid links.
• Testing links: Testing links can help to ensure that they are working correctly.
• Keeping website structure consistent: Keeping website structure consistent can help to prevent broken or invalid links from occurring.

Q: What are some best practices for link checking? A: Some best practices for link checking include:

• Regularly checking links: Regularly checking links can help to identify and fix broken or invalid links.
• Using a link checker tool: Using a link checker tool can help to identify and fix broken or invalid links.
• Testing links: Testing links can help to ensure that they are working correctly.
• Keeping website structure consistent: Keeping website structure consistent can help to prevent broken or invalid links from occurring.

Q: How can I get started with link checking? A: You can get started with link checking by:

• Using a link checker tool: Using a link checker tool can help to identify and fix broken or invalid links.
• Regularly checking links: Regularly checking links can help to identify and fix broken or invalid links.
• Testing links: Testing links can help to ensure that they are working correctly.
• Keeping website structure consistent: Keeping website structure consistent can help to prevent broken or invalid links from occurring.