Skip to main content

Why Changes in the Head Section Require Saving First in Super.so

Head Section requires saving before it reflects on dashboard preview to prevent JavaScript loops, while CSS updates appear instantly

Charlene avatar
Written by Charlene
Updated yesterday

When adding custom code to your site, you may notice that changes made in the Head section do not immediately appear in the dashboard preview. This is expected behavior and was intentionally designed.

Why saving is required for the Head section

Code added to the head section often includes JavaScript, which runs as soon as the page loads. In the past, allowing this code to run instantly in the preview caused endless JavaScript loops, leading to:

  • Freezing or crashing previews

  • Unexpected site behavior

  • Poor editing experience in the dashboard

To prevent this, Head Section Code is only applied after you save your changes. This ensures that scripts run in a controlled way and only when the page is fully reloaded.

In short:
Saving first protects the dashboard from unstable or looping JavaScript.

Why CSS behaves differently

This behavior applies only to the Head section.

If you add or edit code in the CSS section, your changes will immediately reflect in the dashboard preview, even without saving. This is because:

  • CSS only affects styling (colors, spacing, fonts, layout)

  • CSS does not execute logic or loops

  • It’s safe to preview CSS changes live

Best practice

  • Use the CSS section for visual and layout changes you want to preview instantly.

  • Use the Head section for scripts and advanced integrations, and remember to save your changes to see them take effect.

Did this answer your question?