Something is wrong
Work out what broke, in order
Almost every report resolves to one of five causes. Check them in this order and you will usually stop at the second.
My change is not on the site
The single most common report, and it has four causes in descending order of likelihood.
1
No build has run. Saving an edit marks it pending. It reaches nobody until a build picks it up. Go to the site Overview: it tells you how many changes are not on the preview site yet. See preview and publish.
2
The preview is built and the site is not published. Build preview and Publish live are two separate actions. Doing the first is not doing the second.
3
The last build failed. Look at the Overview for a failure banner, then read the build logs. Your live site is still the previous version, which is the intended behaviour.
4
Your browser is holding an old copy. Load the address in a private window before blaming anything else.
My page returns a 404
The page is not in the Page Map. Content and address are two separate things: a page file with no Page Map entry has no address at all, and nothing warns you.
Settings, then Page Map, and add it. See pages and navigation.
If it is in the Page Map and still missing, check the path for a typo and check the build succeeded.
My image is not showing
Three causes, all of them in the reference rather than the file.
•
The field contains a path rather than a filename. It wants photo.jpg, never /photo.jpg and never a full web address.
•
The filename does not match the upload exactly, including its capitalisation.
•
The image went into the wrong folder for its collection: an article image belongs in the articles folder, a page image in the images folder.
Details in images.
My build failed
A failed build ships nothing, so your live site is safe. Open More, then Build Logs, and read from the bottom upward.
Three causes account for most of them.
•
An image referenced by a filename that was never uploaded.
•
A Page Map entry pointing at a page file that does not exist.
•
A content entry missing a field its collection requires, most often a cover image or its alt text.
A build reported as stopped rather than failed was interrupted, not rejected. Run it again.
My site looks wrong on a phone
Your desktop layout is the default for every screen size. A phone gets it unless you override something.
The four usual causes are multi-column layouts, fixed widths, oversized padding, and headline sizes. Each is fixed with a phone override that redeclares only the property that changes. See mobile layout.
Narrow your browser to 375 pixels and look for horizontal scrolling. Any sideways movement means something on the page is wider than the screen.
A style refuses to apply
Custom CSS, under Design, holds Cascading Style Sheets (CSS) applied on top of everything else, on every page. A rule written there overrides whatever you just set in the editor.
Check there before concluding the editor is at fault. The same applies in the other direction: a value written into a block's raw css field cannot be overridden by a phone or tablet rule, because breakpoints only operate on the named options.
An old link goes to the wrong place
Somebody changed a slug. The slug is the address, so changing it silently breaks every existing link.
Add a redirect from the old address to the new one, and point it at the final address rather than at another redirect. See redirects.
Everything looks fine and nobody is finding the site
That is a different problem from a broken site, and it has its own answers. Start with a web audit on the published address, then read why a site is not showing up on Google.
Still stuck
Send three things to hello@inboundsavvy.com: the site name, the address of the page, and what you expected to see instead. Those three turn a diagnosis into a reply.
Next
Build preview, then publish live
How an edit becomes a preview, then a live site, and what to do when a build fails.
Add a page and give it an address
Creating a page is two jobs. Skip the second and the page has no address.
Get an image onto a page
How to upload an image, where it lands, and the limit that will stop you.
Still stuck?
Send us the site name and what you were trying to do. A person answers, usually within one business day.