Why Is My UniLink Page Not Loading? (Causes and Fixes)

Step-by-step troubleshooting guide to diagnose and fix blank pages, 404 errors, and slow load times on your UniLink profile.

You've built your UniLink page, shared the link, and now visitors — or you yourself — are seeing nothing: a blank white screen, a spinning loader that never finishes, or a generic error page. Before you panic, know that the vast majority of loading problems come from one of a handful of predictable causes, and every one of them has a clear fix. This guide walks through each cause in order of likelihood so you can identify and resolve the issue as quickly as possible.

UniLink pages are served through a global CDN backed by Cloudflare, which means once your content is published and the domain is configured correctly, load times are fast and reliability is very high. The issues that do occur almost always originate on the configuration side — not the infrastructure side. Let's diagnose yours.

What This Guide Covers

This troubleshooting guide addresses every major reason a UniLink page might appear blank or fail to load. It covers the full stack: from publish status inside the Dashboard all the way through DNS propagation, browser caching, CDN behaviour, and block-level rendering errors.

By the end you will know exactly what is causing the problem on your specific page and you will have the information needed to fix it, whether that means clicking "Publish" in the Dashboard, waiting a few more hours for DNS to propagate, clearing a cache, or disabling a broken block.

If none of the steps in this guide resolve your issue, the final section directs you to UniLink's status page and support channels so you can rule out a platform-side outage and escalate if needed.

How to Get Started

1. Open your page URL in a private/incognito window — this bypasses any locally cached version and gives you a clean view of what visitors actually see.
2. Note the exact error — is it a blank white screen, a 404, a 500, a partial load with missing content, or an infinite spinner? The error type narrows down the cause immediately.
3. Log into the UniLink Dashboard — navigate to your page and check whether the status badge reads "Published" or "Draft". A page in Draft mode is invisible to anyone who is not logged in.
4. Test on a second device or network — if the page loads fine on mobile data but not on your Wi-Fi, the issue is a local cache or network filter, not the page itself.
5. Check the UniLink status page at unilink.us/whats-new or follow @UniLink on social media for any announced outages or maintenance windows before spending time debugging.

Step-by-Step Guide

1. Verify publish status — in the Dashboard, open your page editor and look at the top-right corner. If the button reads "Publish", your page is still in draft mode. Click it to publish. Changes to an already-published page also require you to click "Save & Publish" before they go live.
2. Check custom domain propagation — if you recently connected a custom domain (e.g. links.yourbrand.com), DNS records can take up to 48 hours to propagate worldwide. During this window some visitors — especially those in regions far from your DNS provider — may see an error. Test your unil.ink/username URL in the meantime; it should always load regardless of custom domain status.
3. Clear your browser cache — open your browser settings, clear cached images and files for the past 24 hours, then reload. On Chrome you can do a hard reload with Ctrl+Shift+R (Cmd+Shift+R on Mac) without clearing the full cache.
4. Purge the CDN cache — in the Dashboard go to Settings → Domain → and click "Purge Cache" if the option is available. UniLink's CDN caches pages for up to 5 minutes; after a publish the old version can briefly persist. A cache purge forces an immediate refresh.
5. Test on mobile vs desktop — some blocks render differently on small screens. If the page loads on desktop but appears blank on mobile, there may be a CSS conflict in a custom HTML block. Try switching to a different theme or temporarily removing custom code blocks.
6. Isolate a broken block — if the page loads partially or throws a JavaScript error in the browser console (press F12 → Console), a single block may be causing the crash. In the Dashboard, try hiding blocks one by one (use the eye icon) and republishing after each change to identify which block triggers the problem.
7. Contact support — if none of the above resolves the issue, open a support ticket from the Dashboard (Help → Contact Support) and include: your page URL, the exact error message, which browser and device you tested on, and the results of your incognito test. The support team can inspect server-side logs that are not visible to you.

Key Settings Explained

How to Get the Most Out of It

Once you have confirmed that your page loads correctly, take a few minutes to set yourself up for fast diagnosis in the future. Bookmark your unil.ink/username direct URL (separate from your custom domain) so you always have a reliable test URL that bypasses domain configuration issues entirely.

If you use custom HTML or third-party embeds — widgets, chat tools, booking calendars — test each new embed on a hidden draft page before adding it to your live page. One malformed script tag can prevent the entire page from rendering. The few minutes it takes to test in isolation will save you from hours of downtime.

When publishing big design changes, do so at a low-traffic time (early morning in your main audience timezone). The CDN cache takes a few minutes to propagate, and you want to be awake to verify the update went live correctly before your audience peaks.

Finally, keep your notification email address up to date in Dashboard → Account Settings. UniLink sends an email for platform-wide incidents. If you are aware of an outage before your audience reaches out, you can post a quick update to social media or a secondary link rather than leaving visitors confused.

Troubleshooting Common Issues