Get Broken images and screenshot of page with broken images from a list of page urls. You can still use chrome wile this runs because it uses a headless version of chromium, so you don't need to worry about blocking chrome usage while it runs.
- npm install.
- create an .env file with content like this
- SAME_SITE_LINKS is a comma separated list of urls to test
- (HT_USER and HT_PASS are optional, use only if your site is password protected).
- npm start
- Results are stored in broken_images.txt and multiple screenshots called page-#.png
Instructions (Broken Links - Check if some links also exist in another domain. For example after migrating wordpress posts to another wordpress site)
- npm install.
- create an .env file with content like this
- SAME_SITE_LINKS is a comma separated list of urls from the original domain (without the domain or protocol. Example: home,about,contact)
- (HT_USER and HT_PASS are optional, use only if your site is password protected).
- (NEW_DOMAIN is required and is the new domain to check if those urls exist)
- npm run broken-links
- Results are stored in broken-links.txt
- npm install.
- create an .env file with content like this
- SAME_SITE_LINKS is a comma separated list of urls to test
- (HT_USER and HT_PASS are optional, use only if your site is password protected).
- It looks for an img tag inside an element with a class 'grop-post_image'. You might want to change this.
- npm run featured-image
- Results are stored in missing_featured_images.txt and multiple screenshots called page-#.png
- .txt files are overwritten on each run.
- .png files are NOT overwritten on each run. (For a clean run remove all png files)
- You can make sure to use the same NODE version with nvm. (Install nvm and run: nvm use)
- Improve performance
- Code Refactoring
- Better Instructions
- More options to make the tool less specific. (Example: Featured Image selector should be an option)