Take it step by step
- Save the relevant page HTML and import it.
- Review titles, descriptions, headings, links and image alternative text.
- Distinguish authoring problems from the limits of the saved snapshot.
- Verify changes on the deployed page with separate network and accessibility checks.
A situation to try.
A missing canonical in saved source may be real, or a script may add it later. Check rendered markup and the deployed response before deciding.
Use the tool’s synthetic example first where available. The example here explains a decision; it is not a reported benchmark result.
Before you call it done.
- Look for a descriptive main heading.
- Check internal links and image context.
- Compare source with rendered content when relevant.
Know the limits.
This is not a live crawl, ranking report, Core Web Vitals measurement or complete accessibility audit.
This tool’s current boundary: Audits supplied HTML only. It does not crawl a live website or measure rankings.
Evidence and scope
Technical source guidance and task-specific output checks. These do not establish that every file, browser or device passes.
Use the checks above on your own exported result. A source explains the format or mechanism; it is not proof that this export preserved every feature.
Technical reference: Google Search documentation ↗
Choose the right tool for this step.
Imported HTML audit
Inspect imported HTML for common markup and SEO issues.
On your deviceWhy use it: Review the supplied snapshot.
Before you start: Does not measure server responses or field performance.
Meta and social tags
Generate page and social metadata from supplied facts.
On your deviceWhy use it: Prepare corrected metadata.
Before you start: Verify it on the published page afterward.
Preparation tools process locally. Official service links take you to the authority’s website. Inspect any exported copy before sharing it.