A site on Solta shows a blank page
The site published, the link opens, and there is nothing on it. Almost always the browser refused something or the code stopped, and the browser says which. If it is a React file that is blank everywhere outside Claude, not only on Solta, start with why a Claude React artifact shows a blank page.
First, look at the console
Open the site at its own address (your-site.solta.site, not inside Solta), then the browser's developer tools — right-click, Inspect, then Console; or ⌥⌘J on a Mac and Ctrl Shift J elsewhere in Chrome. A red line there is the reason, and it usually reads like one of the sections below.
If you made the site with an AI, paste that red line back into the same conversation. It is the most useful thing you can give it, and the fix is then a new version of the same site.
“Refused to load the script”
The page loads a library from a server sites are not allowed to load scripts from. Every site carries a Content Security Policy that lets it load scripts from itself and from these public CDNs, the ones AI-written pages use:
esm.shcdnjs.cloudflare.comcdn.jsdelivr.netunpkg.comcdn.tailwindcss.comcode.jquery.com
A <script src> from anywhere else is blocked, and when that script is the one that draws the page, the page stays empty. Load the same library from one of those CDNs — almost every public package is on jsDelivr or cdnjs — or publish a folder with the file inside it, and load it by a relative path.
It stopped while running
An Uncaught error means the code started and then threw before it drew anything. A React component that does not compile is refused when you publish, with the error; one that compiles can still fail when it runs — reading something that is not there, calling a function the page never defined.
A common one for pages written inside a chat: code that calls the chat app's own functions, which exist only inside that app. On Solta a site calls a model through its own address instead, and saves through Solta's storage or the browser's.
An import did not resolve
Packages a React component imports are fetched from esm.sh by the visitor's browser. A package that is not published to npm, a path to a file of yours that was not uploaded with it (./utils in a single pasted file), or a network that blocks esm.sh all leave the page with nothing to run. More on imports.
A built app in a folder
A folder is served exactly as it is, from the root of the site's own address. A build made for a sub-path — /my-repo/assets/…, as a GitHub Pages build often is — asks for files that are not there. Build for the root (in Vite, base: "./" or "/"), and upload what the build produced, with index.html at the top, not the project's source.
It needs a server
A page that fetches from localhost, from plain http://, or from an API that does not allow other websites to call it, gets nothing back, and many pages draw nothing until that data arrives. Solta runs no server code of yours; here is where that line falls.
Only part of it is empty
A video or a map embedded inside your site — a YouTube or Google Maps frame — is a frame from another website, and a site may only frame its own pages, so that box stays empty while the rest works. Link to the video rather than framing it.
Still blank after all of this? Report a problem from the site's menu: it sends us the version you are looking at, and we look.