Yola is a managed website builder with a drag-and-drop editor and built-in Google Analytics support. Analytics troubleshooting on Yola is limited by the platform's walled-garden approach: you have a designated GA integration field and a custom HTML widget, but no access to server configuration, template files, or the overall HTML structure.
Yola-Specific Debugging Approach
Yola provides two methods for analytics: the built-in GA integration and custom HTML widgets. Start by checking both.
Verify Built-in Analytics
- Yola Dashboard > Site Settings > General > Google Analytics: Enter your GA Tracking/Measurement ID
- After entering the ID, you must Publish the site for changes to take effect
// In browser console on your published Yola site
console.log('GA loaded:', typeof gtag === 'function' || typeof ga === 'function');
// Check for GA script
var gaScripts = document.querySelectorAll('script[src*="gtag"], script[src*="google-analytics"], script[src*="analytics.js"]');
console.log('GA scripts found:', gaScripts.length);
gaScripts.forEach(s => console.log(' ', s.src));
// Check for dataLayer
console.log('dataLayer:', window.dataLayer?.length || 0, 'events');
Check Custom HTML Widget
Yola allows a "Custom HTML" widget that can contain scripts. Check if any widgets contain analytics code:
- Open the Yola site editor
- Look for Custom HTML widgets on each page
- Click each to inspect its contents
Most Common Yola Analytics Issues
1. Site Not Published After Adding Analytics ID
Symptoms: GA Tracking ID is entered in settings but no data appears in Google Analytics.
Root cause: Yola requires an explicit publish action after any settings change. The draft/editor version does not include analytics code.
Fix: Click the Publish button in the Yola editor. Wait 5-10 minutes for the change to propagate through Yola's CDN, then verify on the published site URL.
2. Using Universal Analytics ID Instead of GA4
Symptoms: GA Tracking ID is entered and the site is published, but no data appears in GA4.
Root cause: Yola's built-in integration may expect a specific ID format. If you enter a UA-XXXXXXX-X (Universal Analytics) ID but only have a GA4 property, or vice versa, tracking will not work.
Fix: Ensure you are using the correct ID format:
- GA4: G-XXXXXXX (starts with G-)
- Universal Analytics: UA-XXXXXXX-X (starts with UA-, deprecated July 2024)
Check your Yola version's documentation for which format is supported. If Yola only supports UA IDs, use a Custom HTML widget to add GA4 manually:
<!-- In a Custom HTML widget placed on every page -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXX');
</script>
3. Custom HTML Widget Only on One Page
Symptoms: Analytics works on the homepage but not on other pages.
Root cause: Custom HTML widgets are page-specific in Yola. If you added a widget with analytics code to only one page, other pages are untracked.
Fix: Either use the built-in GA integration (which applies site-wide), or add the Custom HTML widget to every page in your Yola site.
4. Page Transitions Not Generating Pageviews
Symptoms: Only the initial page load registers analytics. Navigating between Yola pages shows no additional hits.
Root cause: Some Yola themes use AJAX-like page transitions that do not trigger full page reloads.
Fix: Add a navigation detection script in a Custom HTML widget:
// Detect Yola page transitions
var yolaLastPath = window.location.pathname;
setInterval(function() {
if (window.location.pathname !== yolaLastPath) {
yolaLastPath = window.location.pathname;
if (typeof gtag === 'function') {
gtag('event', 'page_view', {
page_path: yolaLastPath,
page_title: document.title
});
}
}
}, 1000);
5. Yola's Built-in Statistics vs Google Analytics Discrepancies
Symptoms: Yola's built-in visitor statistics show different numbers than Google Analytics.
Root cause: Yola includes its own analytics dashboard. It uses different tracking methodology, may count bots and crawlers differently, and has different session definitions than GA.
Fix: This discrepancy is expected and normal. Use GA as your authoritative data source for external reporting. Yola's built-in stats are useful for quick checks but should not be directly compared.
Environment Considerations
- Managed platform: No FTP, SSH, or server access. All changes through the Yola editor
- Publish required: Every change requires an explicit publish action. Unpublished changes are not visible to visitors
- CDN-served: Published sites are served via CDN. Changes may take several minutes to propagate
- SSL on premium plans: Custom domain SSL may require a premium plan. Mixed-content issues can block analytics on HTTP-only sites
- Mobile version: Yola generates a separate mobile version. Verify analytics appears on both desktop and mobile views by checking both URLs
- Yola subdomains: Free sites use
yoursite.yolasite.com. Custom domains require a premium plan. Ensure GA is configured for the correct domain
Performance Issues
- LCP Issues - Yola builder output rendering and CDN delivery timing
- CLS Issues - Layout shifts from widget loading and Yola's responsive framework
Tracking Issues
- Events Not Firing - Debug publish state, ID format issues, and per-page widget placement
Related Resources
- Yola help center
- Global Issues Hub for platform-agnostic solutions