Choose a capture mode
Add Step → Save Page saves an HTML file in Dashboard → Files & screenshots. Choose Rendered HTML (default) for the current document after JavaScript changes, or Source HTML to fetch the current page URL again. A fresh response can differ from the original navigation response.
Both modes wait for page load. For rendered HTML, Advanced adds an optional CSS selector that must exist, an extra delay, and a readiness timeout (30 seconds by default). A timeout fails the step instead of silently saving early. Use preceding interaction or scroll steps to reveal content first.
What the HTML contains
Rendered HTML includes the main document and doctype, excluding Tab Automation’s overlays. Linked assets stay external. Embedded documents, shadow DOM, canvas pixels, and live form properties are not reconstructed. This is not an offline page archive. Rendered captures are limited to 16 MiB; source captures use the existing Download File transfer limits.
Save, test, and download
The step succeeds only after the file and its metadata are stored. Storage failures pause for retry. Test Save Page retains a Test output. Download individual HTML files or select several for a ZIP in the Dashboard. No file downloads automatically. Filenames use the Settings export folder, page host, page slug, timestamp, and capture mode. The slug comes from the last part of the page path, with index used for a homepage; query strings and fragments are omitted.
Review on-page SEO
Open Dashboard → Pages & SEO to review title tags, meta descriptions, meta keywords, headings, canonical links, hreflang alternates, robots declarations, language, viewport, social tags, and declared structured-data types, plus image alt coverage and internal, external, and nofollow link counts. Captures open By run; choose View → By domain or All pages to regroup them, and open a group to see its matching pages. Each capture keeps its run and time; open a page for full metadata, retained HTML, and its originating run.
Choose Export metadata…, then a format and a scope: selected captures or all matching captures. JSON, CSV, and Markdown are available. Select runs, domains, or individual page captures to export their matching metadata. Filtered exports include all matching captures across pagination. Pause a running run before exporting. Reports preserve capture status and inspection limits; relevant ZIP exports also contain seo.json, seo.csv, and seo.md. A page’s details also link to Google’s PageSpeed Insights and Rich results test, which open in a new tab.
SEO metadata is collected automatically from the exact saved HTML, using the selected rendered/source mode. Inspection reads at most the first 16 MiB, stops after 10 seconds, and retains up to 256 KiB of metadata. Incomplete or failed inspection is labeled and the original HTML file remains complete. This is an inventory of page declarations, without SEO scores or indexing verdicts.
See what saves to the Dashboard for where each saving step’s output appears and how it exports, and the Dashboard guide for browsing, exports, and local storage.
To turn a public sitemap into a page-by-page metadata CSV, follow How to export title tags and meta descriptions from an XML sitemap.
To keep the HTML files themselves, follow How to save rendered HTML from multiple URLs in Chrome. It covers a pasted URL list, content readiness, a sample capture, and downloading the batch.