How to Archive Competitor Landing Pages as Screenshots for SEO Research

For a reliable record of a competitor landing page, save its exact URL with the Internet Archive’s Save Page Now, keep the resulting Wayback URL, and take a separate screenshot in a browser at a recorded viewport. Store both artifacts with the capture date and a short note about what was visible. Then open the archived page and check whether its images, CSS, and other resources loaded.

The archive URL helps you retrieve the saved page later; the screenshot records the visual state you saw. Neither guarantees a complete record of dynamic content, personalization, interactions, or unavailable assets. Save Page Now saves one page at a time, including images and CSS when available, but does not follow outlinks or crawl an entire site. Internet Archive: Save Pages in the Wayback Machine.

1. Choose the page and record its context

Start with the exact landing-page URL you want to study. Record the access date and retain relevant campaign parameters or page variants if they are part of the URL. These are useful research recordkeeping practices; they are not fields the Internet Archive requires.

Live page URL, including relevant query parameters.
Date and time you accessed it, preferably with the time zone.
What you were examining, such as a campaign or offer variant.
Whether the page was viewed on desktop or mobile, and the browser viewport dimensions.

Preserve the original URL as evidence. If you also create a normalized URL for grouping pages, keep it as a separate field rather than replacing the original.

2. Save a copy with the Wayback Machine

Open Internet Archive Save Page Now.
Enter the landing-page URL and submit it for saving. You can also invoke Save Page Now through the Wayback Machine browser extension.
When the capture finishes, copy and store the permanent URL for that saved page.
Open the saved URL and inspect the archived rendering. Check that the page and key resources are present.

Save Page Now is a single-page capture. It does not save outlinks or start a site-wide crawl. The Internet Archive says the save includes images and CSS when available, but capture can fail because of site crawling restrictions or SSL settings, and some resources may be missing. See the Save Page Now help page and Wayback Machine usage help.

3. Take a separate browser screenshot

Capture the live page separately so you have a direct visual record in addition to the retrievable archive. Use a consistent browser and viewport across the pages you plan to compare. Record the viewport dimensions and whether it represents desktop or mobile; the research sources do not specify a required screenshot application, file format, or viewport.

For a repeatable manual capture, open the recorded URL in your browser, set the viewport you chose, wait for the content you are studying to appear, and take the screenshot. Note if a cookie prompt, personalization, delayed content, or other visible state affected the image. A screenshot records what appeared in that browser session, not necessarily what every visitor sees.

4. Label and store both artifacts together

Keep the screenshot beside the Wayback URL and enough context to interpret each later. A simple folder per research project or a spreadsheet with one row per page works; choose a method that preserves the relationship between the live URL, the archived copy, and the local image.

competitor-research/
  example-brand/
    landing-page-2026-10-04-desktop.png
    landing-page-2026-10-04-notes.txt

For example, the notes file can contain:

Live URL: https://example.com/campaign?source=ad
Wayback URL: [paste the permanent saved-page URL]
Captured: 2026-10-04 14:30 UTC
Viewport: desktop, 1440 × 900
Visible context: headline, offer, primary CTA; cookie prompt visible
Archive check: hero image loaded; one lower-page image missing

Replace the example values with what you actually observed. Do not describe an incomplete archive as a complete copy.

5. Compare pages on consistent terms

When comparing competitors, use the same viewport and record the capture dates and exact page URLs. Note the headline, offer, calls to action, and major visible layout changes. These are practical comparison fields, not a prescribed SEO scoring method.

Field	Why keep it
Live URL and page variant	Identifies the source and preserves relevant campaign parameters.
Access and capture date	Shows when the live page was observed and when the archive was requested.
Wayback URL	Provides a route back to the saved version.
Screenshot and viewport	Records the visible presentation and viewing dimensions.
Short context note	Explains visible prompts, missing assets, or other conditions.

Use the artifacts to document page content and presentation. A landing-page screenshot alone does not establish its ranking, traffic, or search performance.

6. Understand what the records can and cannot show

Archive URL: a retrievable saved version, subject to what the archive could capture.
Local screenshot: a visual record of the browser state at capture time.
Neither: a guarantee that dynamic content, personalized states, interactions, or every asset has been preserved.

Check available capture dates and inspect the saved rendering rather than assuming it represents every visitor’s experience. The Internet Archive’s guidance discusses consulting captures and missing resources. Using the Wayback Machine.

7. Keep SEO interpretation separate from capture access

Google recommends that important page resources be accessible to Google and describes using URL Inspection to check how Google renders a live page. Google also explains that robots.txt controls crawling and is not a reliable way to keep a URL out of search results. Those are Google Search guidance points; they do not determine whether the Internet Archive can capture a page. See Google’s SEO Starter Guide and Google’s robots.txt guidance.

Google Search Essentials groups guidance into technical requirements, spam policies, and key best practices, and meeting requirements does not guarantee a page will be crawled, indexed, or served. Use your competitor-page archive to document what was visible, not to infer search outcomes from appearance. Google Search Essentials.

8. Troubleshoot incomplete or failed captures

Symptom	Possible cause	What to do
Save Page Now does not produce a usable capture	The site may prohibit crawling, or SSL settings or another technical issue may interfere.	Retain the live URL and date, retry later if appropriate, and keep a local screenshot as a separate record. Do not assume the screenshot is an archive copy.
Images or styling are missing in the archived page	Those assets may not be available to the archive.	Record which resources are missing and keep the separately captured screenshot with the archive URL.
The archived page differs from the screenshot	The artifacts capture different states or times; dynamic content and personalization may vary.	Record capture times, viewport, visible prompts, and any known page variant. Describe each artifact as the state it shows.
You expected linked pages to be saved too	Save Page Now saves the submitted page; it does not crawl outlinks or the whole site.	Submit each page you need individually and retain its own archive URL.
You cannot find the capture later	The permanent saved-page URL may not have been stored with the research record.	Keep the URL at the time of saving, alongside the original live URL and capture date.

9. Performance, reliability, and cost considerations

The workflow has two separate capture steps: an archive request and a browser screenshot. For research across many pages, keep a queue or checklist so every page has both artifacts or a note explaining what could not be captured. Verify the archive rather than treating a successful submission as proof that every resource was preserved.

This research material does not establish a specific Save Page Now cost, capture-time guarantee, or screenshot-tool benchmark. Avoid assuming a capture will succeed or that a saved page includes every resource. A browser screenshot can preserve what you saw locally, but it does not make the archive complete or provide a retrievable archived page by itself.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. A single request can return a PNG, JPEG, WebP, or PDF. For an API capture, pass the target URL and your access key:

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

import requests

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

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

See the ScreenshotNeo API documentation for request options. Cookie banners are accepted and removed, along with known newsletter popups and chat widgets, before the shot. Bot checks, blank pages, and failed loads are never billed; response headers report the page verdict and billing status. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. A screenshot API gives you an image, so keep using Save Page Now when you also need a retrievable Wayback capture.

Frequently asked questions

Does a Wayback capture prove what every visitor saw?

No. It is the available saved version of a page, and dynamic content, personalization, interactions, or unavailable resources may not be represented.

Will saving one landing page also save its links?

No. Save Page Now is for the submitted page and does not crawl its outlinks or the whole site.

Does robots.txt tell me whether the Internet Archive can save a page?

Do not infer that from Google’s robots.txt guidance. It describes Google Search crawling behavior, not Internet Archive capture decisions.

Does a competitor screenshot establish SEO performance?

No. It records page presentation. It does not by itself show ranking, traffic, indexing, or search performance.

Can I assume I have unrestricted rights to reuse a competitor’s screenshot?

No general rule for competitor landing-page screenshots is established by the cited guidance. Google’s screenshot guidance is specific to Google Search screenshots and does not settle rights for other sites or all uses.