Bulk Captures
Windows 10 & 11 Buy license · $39.95
Workflows

How to Take Website Screenshots for SEO Audits and Client Reports

A practical workflow for website screenshots in SEO audits: which pages to capture, at which sizes, how to name them, and how to deliver them as one PDF.

Updated 5 minute read The Bulk Captures team

Website screenshots for SEO audits work best when you capture a planned set of pages, at both desktop and phone sizes, with full-page and above-the-fold views, named consistently and delivered as one PDF with the original images kept alongside. Screenshots turn an audit from a spreadsheet of issues into something a client can see: where the content sits, what the mobile layout hides, what a competitor's page looks like next to theirs. This guide sets out a practical, repeatable workflow you can use for every audit.

What screenshots add to an audit

  • Evidence. A screenshot shows exactly what you are describing, on the date you found it, which matters when a page changes before the client reads your report.
  • Clarity. "Your main heading is below the fold on mobile" lands much better with the mobile capture next to it.
  • Before-and-after proof. Captures taken at the start of an engagement are the baseline you compare against months later.
  • Competitive context. Side-by-side captures of competitor pages show layout, content depth and calls to action at a glance.

Step 1: Decide which pages to capture

Capturing an entire large site rarely helps the client. Pick pages that tell the story:

Page groupWhy include it
Home pageThe page everyone looks at first; sets the tone for the report
Main service, category or product pagesUsually the most commercially important pages
Top landing pages from analytics and Search ConsoleWhere search visitors actually arrive
One example of each templateA blog post, a product page and a location page show issues that repeat across hundreds of pages
Pages with specific issuesThin content, missing headings, intrusive pop-ups, broken layouts
Competitor equivalentsThe ranking pages for the client's main target terms

For a full baseline of a smaller site, you can capture every page from the sitemap instead. See our guide on how to screenshot all pages of a website.

Step 2: Choose sizes and views

Search engines primarily evaluate the mobile version of a page, so mobile captures belong in every audit, not just desktop ones.

  • Phone width, around 390 pixels: shows what most search visitors see.
  • Desktop width, 1920 pixels: the view clients usually review on.
  • Tablet (768) and laptop (1366) widths: add them when the layout changes noticeably at those sizes.

Capture two views of key pages:

  • Above the fold (visible area): what loads first, whether the main heading and call to action are visible without scrolling, and how much space banners and pop-ups take.
  • Full page: content depth, heading structure, internal links, how far down important content sits, and how long the mobile page really is.

Our guide to screenshotting a website at different screen sizes covers viewport choices in more detail.

Step 3: Capture the whole set in one run

Doing this by hand, 30 pages at two widths in two views is 120 screenshots, each one opened, captured, saved and renamed. A batch tool turns it into one setup.

With Bulk Captures:

  1. Paste the URL list, load it from a TXT or CSV file, or import the sitemap.
  2. Select the viewport widths, for example 1920 and 390, so every page is captured at both in the same run.
  3. Choose full page, and run a second batch with the visible area only for key pages if you want both views.
  4. Set a load delay of a few seconds so fonts, images and pop-ups appear as visitors see them.
  5. Set the naming pattern, such as {domain}_{date}_{n}, and an output folder for this audit.
  6. Choose the format: PNG for the archive, and a multi-page PDF for the client deliverable.
  7. Click Capture.

Bulk Captures visits each page as a first-time visitor, which is what you want in an audit: cookie banners and sign-up pop-ups appear exactly as they would for a new search visitor, and you can comment on how much of the screen they cover.

Run the competitor pages as a separate batch into their own folder. It keeps client and competitor files apart and makes side-by-side comparison easier.

Step 4: Name and organize for the report

A sensible folder structure saves time when you write up findings:

  • Audit-ClientName-2026-10\desktop and \mobile, or one folder per width.
  • Audit-ClientName-2026-10\competitors for comparison captures.
  • Audit-ClientName-2026-10\issues for cropped or annotated captures used in specific findings.

Domain and date in every file name means captures stay identifiable even when copied into slides or emails. For more ideas, see our guide on how to automatically name screenshots.

Step 5: Use screenshots well in the report

  • One finding, one image. Place the relevant capture right next to the issue it illustrates.
  • Crop to the point for specific issues, such as a missing heading or a pop-up covering content, and link to the full-page capture for context.
  • Pair mobile and desktop side by side when the problem only appears on one.
  • Brand your captures with your agency logo as a watermark, so they stay credited if the client forwards them. Bulk Captures can stamp a logo or text on every capture, at the corner and opacity you choose.
  • Deliver a PDF. A single multi-page PDF of all captures is easy for clients to open and review, with the PNG originals available on request.

Step 6: Repeat for progress reports

The most valuable audit screenshots are often the ones you take months later. Save your URL list and settings, then rerun the same batch after changes go live, into a new dated folder. Comparing folders side by side shows exactly what changed: new headings, restructured content, removed pop-ups, faster-loading layouts.

Keep each run rather than overwriting, so you build a visual history of the site across the engagement. It is persuasive evidence in a quarterly review.

Common pitfalls

  • Half-loaded pages: increase the load delay for slow sites. See our guide to fixing full page screenshots with missing images.
  • Only desktop captures: leaving out mobile misses the view search engines prioritize.
  • Too many screenshots: a report with 300 images is not read. Use a focused set in the report and keep the rest as an appendix.
  • No dates: undated screenshots lose their value as evidence. Put the date in the folder and file names.

Frequently asked questions

Which pages should I screenshot for an SEO audit?

Start with the home page, main category and service pages, top landing pages from analytics, and any page with an issue you are reporting.

Should audit screenshots be full page or above the fold?

Use both. Above the fold shows what visitors see first, while full page captures show layout, content depth and internal links.

How should I share audit screenshots with a client?

A single multi-page PDF is easiest for clients to open and review, with the individual images kept in a folder for your own reference.

Get three guides like this every month, plus software update notices.Subscribe →