Use Apify’s Website Content Crawler Actor: set its crawler type to playwright:firefox, turn on saveScreenshots, and run a deliberately bounded crawl. The Actor stores each image in its default key-value store and adds its link to the corresponding dataset item as screenshotUrl. Screenshot saving is off by default and adds performance and storage costs, so choose the pages you need rather than crawling a whole government domain automatically.
Set up a focused Apify screenshot run
- Open the Website Content Crawler Actor in Apify Console. Enter the official page or section you want to review as a Start URL. For tighter scope, seed one or more specific pages instead of a broad homepage.
- Choose the crawler type. Set it to
playwright:firefox. The Actor’s screenshot option is supported only with this crawler type; see the Actor input documentation. - Enable screenshot saving. Turn on
saveScreenshots. It is off by default. The Actor saves screenshots in its default key-value store and puts a link in each corresponding dataset item’sscreenshotUrlfield. - Set crawl boundaries. Use include or exclude URL globs,
maxCrawlDepth, andmaxCrawlPagesto keep the run focused. Sitemap discovery is available when broader page discovery is useful, but may take longer than supplying deliberate Start URLs. The Actor documents these limits as a way to prevent an unintended crawl expansion; see its crawl configuration. - Run the Actor. In Console, start the run and wait for it to finish. Apify’s run guide describes launching an Actor, waiting for completion, and finding results in the Output tab. You can export results there, or automate runs through an API request or JavaScript/Python client library as described in the Actor run documentation.
- Review the dataset. Open the output dataset and use each item’s
screenshotUrlto view its image. Dataset items can also be retrieved through the dataset API in several formats; see Apify dataset documentation. Retain the page URL or another page identifier with each image so a reviewer can tell what it depicts.
Choose Console or an API/client-library run
| Approach | Best fit | Trade-off |
|---|---|---|
| Apify Console | A one-off review or a run that needs manual configuration. | Simple to launch and inspect in the Output tab; repeating the same review requires configuring or launching runs again. |
| API or client library | Repeatable captures or integration into an existing review workflow. | Requires setting up the API call or client code; results can still be inspected or retrieved through the dataset. |
Decide how to find the pages
Use explicit Start URLs for a bounded review
Supply the exact pages or sections whose rendered appearance matters. This gives direct control over scope and makes it easier to associate each image with a planned check. Include URL patterns and page caps as appropriate so links encountered during crawling do not expand the run beyond the review.
As an Amazon Associate I earn from qualifying purchases.
Use sitemap discovery when coverage matters more
Sitemap discovery can help find pages beyond those linked from the seed pages, but the Actor documentation says it can take longer. It is a discovery option, not a reason to omit page and depth limits: review the resulting scope and keep the run proportionate to the task.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Handle robots.txt and site access carefully
The Actor offers a respectRobotsTxtFile setting. Its current description says that when enabled, the crawler consults robots.txt, but does not use a specific user-agent identifier and does not support the crawl-delay directive. Do not treat this checkbox as complete robots-policy or rate-limit compliance; see the Actor configuration documentation. Check the target government site’s published access conditions and verify that a small, bounded run behaves as expected. The Actor documentation does not guarantee successful rendering for every site or permission to automate captures there.
Use screenshots as evidence in a GIGW-informed review
India’s current Guidelines for Indian Government Websites and Apps, or GIGW 3.0, apply to government websites and applications at central, state, district, and local levels. They address usability, user-centricity, universal accessibility, and security. The guidelines say: “These Guidelines address common issues and practical challenges that government organisations face during development and management of their websites/apps.” See the official GIGW scope and objective.
Visible checks screenshots can support
- Whether government identity and ownership information appears on important pages.
- Whether a visible update or review date is present.
- Whether page content and layout appear as expected at the time of capture.
GIGW identifies ownership information and dates as checkpoints and notes that some require manual evaluator review. A screenshot is useful evidence of what was visible in one rendered state; retain the page URL and capture date in review notes.
Checks that need more than an image
- Page titles and language attributes require inspecting the page or its markup.
- Minimum information requirements for home and subsequent pages require content review.
- Accessible table markup cannot be established from a visual image alone.
- Print behavior requires a separate print check.
- Accessibility, security, and backend behavior require appropriate additional technical, manual, or security evaluation.
GIGW 3.0 supports STQC Certified Quality Website certification; departments may self-assess using its compliance matrix or submit a website to STQC. An Apify screenshot run is neither a certification nor proof of complete GIGW conformity. The official introduction also notes that cybersecurity guidance changes and assessments should account for updated CERT-In guidance. See GIGW 3.0.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
ScreenshotNeo provides a one-request screenshot API and an MCP server for AI agents. Its clean-shot steps accept consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, with the outcome indicated by X-Page-Verdict and X-Billed headers. AI agents can use its MCP tools, including take_screenshot, get_page_info, and capture_pdf.
Example cURL request, using the target site URL you want to capture:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.india.gov.in -o shot.webpSee the ScreenshotNeo API documentation for parameters and setup. ScreenshotNeo offers 1,000 screenshots a month free with no card; paid plans start at $5 for 3,000. It is a separate capture option, not an Apify Actor or a substitute for checking a target site’s access conditions. Learn about ScreenshotNeo or sign up for 1,000 free screenshots a month with no card.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common run problems
No screenshot link appears
Check that saveScreenshots is enabled and the crawler type is playwright:firefox. Screenshot capture is optional, off by default, and documented for that crawler type only.
The run captures more pages than intended
Review your Start URLs and URL globs, then set or reduce maxCrawlDepth and maxCrawlPages. A broad seed or sitemap discovery can expose more pages than a small visual review requires.
The run is slower or uses more storage than expected
Screenshot saving reduces performance and increases storage costs. Narrow the page set, use page caps, and enable it only for runs where images are needed.
A target page fails to render or the run is blocked
The Actor’s documentation does not promise that every target will render or permit automated access. Check the site’s access conditions, test a small set of pages, and inspect the run result rather than assuming a missing image indicates a configuration error.
Quick Recap
Keep the review reproducible
- Record the run date and each target page URL alongside its screenshot.
- Keep the page scope and relevant crawl limits with the review notes.
- Separate visible observations from checks that require markup inspection, interaction, print testing, or security review.
- Treat each image as a record of a single rendered state, not evidence of continuing compliance or of site behavior outside what the image shows.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
