The "No value passed for parameter 'siteSlug'" error typically indicates that Webflow's system didn’t receive or couldn’t identify the correct site configuration during a project setting update—often when saving analytics or integration settings.
1. Understand the Error: 'siteSlug' Missing
- 'siteSlug' is an internal Webflow parameter that uniquely identifies your project (site).
- If it's missing, Webflow's backend can't associate your changes (like a GA Measurement ID) with the correct project.
2. Common Causes of This Error
- Session Timeout: If your login session expired while editing settings, the form submission can fail.
- Browser/Extension Conflicts: Ad blockers or browser extensions (especially privacy-focused ones) can block Webflow’s scripts or request parameters.
- Bug in Webflow UI: Occasionally, the Webflow Designer or Project Settings UI can glitch, especially during updates.
- Improper Project Load: If the settings page was opened in a stale tab or reloaded improperly, necessary parameters may not be available.
3. How to Fix It
- Log Out and Log Back In: Fully log out of Webflow, log back in, and retry adding the GA Measurement ID.
- Use a Different Browser: Test in a clean browser session like incognito/private mode or switch browsers (e.g., Chrome → Firefox).
- Disable Ad Blockers: Temporarily turn off extensions like uBlock Origin, Ghostery, etc.
- Reopen the Project Settings: Close the current tab and reopen the Project Settings via the Webflow Dashboard to ensure proper parameter loading.
- Clear Cache: Clear your browser cache or use a private window to eliminate stale data.
4. Is the Domain (.studio) Causing the Issue?
- No, your domain ending in .studio does not cause this issue.
- Webflow fully supports .studio and other custom domain TLDs; the error relates to internal project handling, not DNS or domains.
Summary
The 'siteSlug' error is caused by a temporary issue with Webflow’s Project Settings not receiving site data, often due to session expiration or ad blockers. It’s not related to your .studio domain. Logging out, using an incognito tab, and disabling browser extensions usually resolve it.