Troubleshooting
Fix common Site Kit validation, asset, variant, and source-conversion errors.
type does not match content.type
Keep the outer section type and content.type identical.
unknown variant
Read SECTION_REGISTRY[type].variants and choose one of its keys. The importer
can coerce an unknown variant, but fixing it before import is safer.
references unknown asset
Add an assets[] row with that exportId, or remove the media reference. A
dangling reference would be dropped during import.
no assets/<id>.<ext> file
Put exactly one matching blob in the directory. Do not include two formats with the same export id.
Import skips an image
Check the declared MIME type and dimensions against the real bytes. Very large, extreme-aspect, malformed, or unsafe SVG files fail closed.
The layout has no matching section
Use the closest editable section, simplify the design, or report a candidate for a generic new variant. Do not smuggle the layout through raw HTML.
Next.js code does not import
That is expected. Site Kit converts content and structure, not application code. Render the site, inventory the result, and map it to typed sections.