How to Screenshot Competitor Pages on Indian Government Websites for SEO

Short answer: Open the public page in Chrome, set a consistent viewport and page state, then use Chrome DevTools’ Command Menu to capture a full-page screenshot. Repeat the same process for the comparable page and record each URL, date, viewport, and relevant state. Screenshots help compare visible presentation—such as headings, navigation, content order, calls to action, and mobile layout. They do not reveal rankings, search traffic, metadata that is not visible on the page, or a competitor’s private analytics.

This workflow is useful for documenting how public pages are presented. It is not a way to access a competitor’s Search Console or private data. If you plan to publish a screenshot or reproduce page content, check the exact page’s current terms and copyright policy first.

1. Choose the capture that answers your question

Need	Capture	What it records
Compare the entire page’s structure	Full-page screenshot	The document beyond the visible viewport
Compare the first impression	Viewport screenshot	Only what is visible at the current viewport
Document a specific section or component	Node screenshot	The selected DOM element
Record a particular region	Area screenshot	A region selected in the page
Understand progressive loading	Network-panel screenshots	A sequence of visual states during page load

Chrome DevTools documents full-page and other screenshot techniques in its device mode and screenshot guidance. For loading sequences, enable screenshots in the Network panel and reload; thumbnails appear alongside network activity.

2. Capture a full page in Chrome DevTools

1. Open the public page in Chrome and wait until the content you want to compare has loaded.
2. Set the browser zoom and viewport. For a mobile comparison, open DevTools’ device toolbar and select a device or enter a consistent viewport size.
3. Open DevTools with F12 or Ctrl+Shift+I on Windows/Linux, or Cmd+Option+I on macOS.
4. Open the Command Menu with Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS.
5. Type screenshot, then select Capture full size screenshot. Chrome saves the image as a download.
6. Repeat for the equivalent competitor page using the same viewport, zoom, browser, and page state.

For a viewport image, choose Capture screenshot. For a selected DOM element, inspect the element first, then choose Capture node screenshot. For an arbitrary region, choose Capture area screenshot and select the region.

Capture the loading sequence

1. Open DevTools’ Network panel.
2. Enable screenshot capture in the panel’s settings or capture controls.
3. Reload the page and wait for it to finish or reach the state you need.
4. Review the thumbnails beside network activity to see how the rendered page changed over time.

This sequence can help distinguish a stable final layout from content that appears progressively. It is not a substitute for a full-page capture when you need the whole document in one image.

3. Make the comparison repeatable

Use a capture log. Keep conditions as consistent as practical so visual differences are less likely to come from your setup.

Record	Why it matters
Exact page URL and capture date/time	Pages change; the record identifies what was viewed and when.
Browser and version, viewport, zoom	These affect wrapping, responsive layout, and what appears above the fold.
Desktop or mobile emulation details	Responsive layouts can change navigation, order, and visibility.
Cookie/consent choice and other page state	A banner or dismissed state can change the screenshot.
Login/session state, if applicable	Do not compare a public logged-out page with a personalized session.
Capture type and notes	Distinguish full-page, viewport, element, and load-sequence records.

Compare like with like: for example, a service detail page against another service detail page, not a homepage against a policy page. Note visible page title and heading hierarchy, navigation and internal links, content order, calls to action, document links, mobile presentation, and visible ownership or contact details. Treat observations as a record of presentation at capture time, not as evidence of search performance.

4. What a screenshot can tell you about SEO—and what it cannot

A screenshot can document the visible hierarchy and user-facing experience: whether the main topic is prominent, how sections are ordered, whether navigation exposes related pages, and what a mobile visitor sees. It cannot reliably establish source metadata such as a meta description, canonical URL, structured data, robots directives, or the exact document title if that title is not visible in the captured page. Inspect the HTML or use appropriate browser tooling for those details.

The Indian Government Websites and Apps Guidelines (GIGW) discuss page titles and metadata, and state that ownership information helps search engines verify a site’s legitimacy and accord higher ranks in search results. Treat that as the guideline’s statement, not a guarantee of rankings or a claim about current Google ranking systems. GIGW describes guidance for government sites across organizational levels; do not assume every site implements it identically. See the official GIGW guidelines and scope and objective.

Google Search Console’s URL Inspection tool can show a rendered screenshot of how Google’s inspection tool sees a page after a successful live test. It is for inspecting a URL through Search Console; it does not provide access to a competitor’s private Search Console data. Google notes that screenshots are unavailable for the indexed URL view and for unsuccessful live fetches. See URL Inspection tool documentation.

5. Publication and reuse: check the page’s policy

Private analysis and public republication are different uses. Before embedding or distributing a screenshot, or reproducing text or other page content, check the target page’s own current terms and copyright policy. The GIGW Website Policies page says: “Contents of this website may not be reproduced partially or fully, without due permission from NIC.” That statement applies to the GIGW website’s policy; it does not establish the rules for every Indian government website. The same policy asks for acknowledgement when its material is referred to elsewhere. Read the GIGW Website Policies and verify the policy on the specific page you plan to use. This guide does not determine legal exceptions.

6. Or skip the browser setup

For repeatable API captures, ScreenshotNeo takes a screenshot from one GET request. The API can return PNG, JPEG, WebP, or PDF, and supports options such as full-page capture, device presets and custom viewports, element capture, wait conditions, custom CSS, and cookies. See the ScreenshotNeo API documentation for parameters and formats.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://guidelines.india.gov.in/guidelines/ -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://guidelines.india.gov.in/guidelines/"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://guidelines.india.gov.in/guidelines/'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

The Node.js example uses the built-in fetch API and Bun’s file writer. In Node.js, save the response body with the built-in filesystem API:

import { writeFile } from 'node:fs/promises';

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://guidelines.india.gov.in/guidelines/'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

ScreenshotNeo accepts cookie/consent banners like a visitor and removes 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 cost nothing, and response headers report the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000, and every feature is on every plan. See ScreenshotNeo.

Create a free account for 1,000 screenshots a month with no card.

7. Troubleshooting

Symptom	Likely cause	Fix
The screenshot is only the visible screen	You selected the viewport capture command.	Use Capture full size screenshot from the Command Menu.
A menu, banner, or overlay differs between pages	Consent, popup, or session state differs.	Record the state and repeat both captures consistently. Do not dismiss a banner on one page and leave it on the other without noting the difference.
Lower-page images or sections are missing	The page loads content lazily or has not reached the relevant state.	Scroll through the page to trigger lazy content, wait for it to settle, then capture again. For transient loading behavior, use Network-panel screenshots.
Mobile comparison looks inconsistent	Viewport, device emulation, or zoom changed.	Use the same dimensions and zoom for both pages and record them.
Command Menu does not show a screenshot command	DevTools may not have focus, or the command text is incomplete.	Click inside DevTools, reopen the Command Menu, and search for screenshot.
The image seems to prove a title or metadata value	That detail may not be visible in the screenshot.	Inspect the page title and metadata separately in the rendered document or source.
Search Console has no rendered screenshot	The live test may have failed; screenshots are not available for indexed URL view.	Run a live URL test for a page you are authorized to inspect and review the fetch result.
An API capture returns an error or unexpected content	The URL may redirect, be inaccessible, time out, or return a non-image response.	Check the response status and headers, confirm the URL is publicly reachable, and consult the API docs for response verdicts and supported options.

8. Performance, reliability, and cost

For a handful of pages, DevTools avoids setting up a capture script or paying for an API. Keep a capture log and save files with descriptive names, such as department-service-mobile-2026-10-04.png. Re-capture if a page is still loading or content is missing; a screenshot is only as representative as the state captured.

For recurring or bulk comparisons, automate capture and keep the URL, timestamp, viewport, and options with each result. A screenshot service can make repeat runs easier, but output can still vary when the source page changes or serves different content by session, location, or time. Check response status and billing/verdict information rather than assuming every request produced a valid page image. ScreenshotNeo offers caching with a chosen TTL, asynchronous jobs with signed webhooks, and bulk capture for up to 100 URLs per call. Pricing is Free for 1,000 shots/month, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free.

9. FAQ

Can I use this to see a competitor’s Google rankings?

No. A screenshot records visible page presentation. It does not expose rankings, traffic, search volume, or private analytics.

Should I use a full-page image for every comparison?

No. Use a viewport image for first impressions, a node or area capture for a component, and a full-page image for whole-document structure. Use load-sequence screenshots when the timing of content appearance is the question.

Can I use Search Console to inspect a competitor’s URL?

Search Console’s rendered screenshot belongs to URL Inspection for pages inspected through an account. It is not a way to inspect another site’s private Search Console information.

Does GIGW’s reproduction policy apply to every government site?

The cited policy is specific to the GIGW website. Check the exact target site’s policy and terms before reproducing its material.