Need deeper analysis? See the related editorial article for background and trade-offs. Use this guide for the practical steps.
Code paste is useful for quick experiments, but real teams work with files. This hands-on guide explains how to upload source documents, preview safe edits and download corrections while retaining control of your original content.
Use this checklist alongside the local checker. Every step is free and can be repeated without an account or daily quota. Only approve corrections that reflect the real page. Where Google eligibility matters, follow the linked official documentation rather than treating a local result as certification.
Step 1: Choose the right source file
Upload the file format that matches your real implementation so a correction preserves the right surrounding context.
Look for: A JSON file may contain only structured data, while an HTML page can contain multiple JSON-LD scripts inside other content.
Example: A WordPress export may contain a JSON-LD snippet, while a static product page can be uploaded as .html.
Keep in mind: This checker does not execute uploaded scripts or fetch external assets.
Step 2: Distinguish opening from uploading
Read the file in the browser, show its name and size, then inspect its content locally using the same rules as pasted text.
Look for: In a privacy-first browser tool, selecting a file does not have to mean sending it to a remote web server.
Example: When a user selects product.jsonld, the editor should display that source and allow a deliberate Check action.
Keep in mind: Explain hosting requests separately from the handling of the uploaded contents.
Step 3: Review parsing results first
Run a check and read errors, warnings and detected entities before selecting the fix preview.
Look for: A corrected document should not be offered before the source problem has been identified.
Example: A JSON syntax failure caused by a trailing comma is different from a Product missing a required Google property.
Keep in mind: Not every issue has a safe automatic correction.
Step 4: Preview changes before download
Open the before/after panel, inspect changed fields and confirm the correction did not change real product or business information.
Look for: The most important safety feature is keeping the original unmodified and displaying the proposed corrected text.
Example: Fixing http://schema.org to https://schema.org is usually low risk compared with modifying a sale price.
Keep in mind: Never replace production files without human approval.
Step 5: Save a corrected copy
Download a new .jsonld or .html file from the browser and keep the original beside it until verification completes.
Look for: A distinct corrected filename makes it easier to test, compare and roll back changes.
Example: Rename product.html to product.corrected.html to signal that it is a candidate, not an already deployed page.
Keep in mind: A download cannot edit a live CMS or a GitHub repository by itself.
Step 6: What HTML corrections should preserve
Operate only on script tags with the application/ld+json type and preserve the rest of the HTML document.
Look for: Repairing embedded JSON-LD should not remove navigation, styles, analytics tags or unrelated JavaScript.
Example: A page with two JSON-LD blocks should retain both blocks even if only one contains a typo.
Keep in mind: Treat complex malformed HTML as a case requiring manual review.
Final review checklist
Recheck syntax and warnings after editing, compare the corrected file against the original, export a report, and validate applicable features using official tools. If a result is unclear, keep the original data instead of guessing business facts.
Official sources: Google documentation and additional reference. For more detail, read the complete article.
Frequently asked questions
Answers are educational. FAQ markup does not guarantee Google FAQ rich results.
Should I publish an auto-corrected file immediately?
No. Review the diff and confirm factual accuracy before deploying.
Are corrected downloads identical to the original?
Only approved, actual changes should be marked corrected; unchanged files remain unchanged.
