PUBLISHING LAB
Inspect a finished website folder locally before publishing. Get a file-by-file report of HTML metadata, indexing directives, missing assets and possible private files, then export the repair list.
Inputs are processed in this browser. The tool sends no entered values or selected files to a server. Exported files stay under your control.
It does not build React source, inspect CSS imports or runtime requests, certify security, or test forms and hosting routes. Select the finished static output and verify the public URL after publishing.
Before uploading a finished folder, inspect each HTML file's title, description, H1 count, canonical address, robots directive and share-image declarations. The report also checks selected local asset references and flags possible private files. Download the CSV to keep a file-by-file repair list.
Example: a selected about.html with a title but no description or canonical is reported with those missing fields. A noindex directive is a review item: it can be intentional for a private page. This is a diagnostic, not a ranking score.
The selected HTML is parsed without running scripts. Remote URLs, HTTP headers, routing, CSS references, runtime behavior and image dimensions are not tested. A declared share image is not proof that the image loads publicly.
Method reference: Google Search Essentials. Review page purpose before changing indexing directives.
Method reviewed October 5, 2026 · GeminiLaunch · Original planning aid prepared with AI assistance. References explain the method; they do not endorse or validate your inputs.
Check an AI-generated website for exposed secret keys. Understand browser-visible code, public identifiers, server-side credentials, and rotation steps.
Read the guide →Launch troubleshootingFix an AI-generated contact form that looks finished but sends nothing. Choose a real endpoint, test delivery, and handle errors before launching.
Read the guide →Files and assetsFix missing images on an uploaded HTML website by checking file paths, filename case, folder structure, and references to local or temporary files.
Read the guide →Client deliveryHand off an AI-built website with source files, account ownership, tested forms, domain records, rollback instructions, and a clear update process.
Read the guide →WEBSITE PUBLISHINGConnect a website domain with a clear DNS plan, preserve email records, check HTTPS and redirects, and verify the published pages before announcing the launch.
Read the guide →