If BerqWP CDN is delivering a specific file in a way that’s causing a problem, CDN Exclusions lets you keep that file loading from your own server instead. This article covers how it works and when you’d use it.
TL;DR: Under BerqWP > Content Delivery Network (CDN), the CDN Exclusions field lets you list keywords, filenames, or URL fragments, one per line, for files that should never load through BerqWP’s CDN. Anything matching what you enter loads from your own server instead.
What CDN Exclusions Does
When BerqWP CDN is enabled, your images, CSS, JavaScript, and font files are normally delivered through BerqWP’s global CDN instead of directly from your server. CDN Exclusions lets you carve out specific exceptions: any file matching a keyword you enter will skip the CDN and load from your own server as usual.
When You’d Actually Need This
Most sites never need to touch this setting, since CDN delivery is generally safe for static files. You’d use it if a specific file behaves differently when served from a different domain than your own, for example a script that checks the page’s own domain and breaks when it’s loaded from a CDN URL instead, or a file that needs to stay on your server for a licensing or security reason specific to that file.
How to Add an Exclusion
- Go to BerqWP > Content Delivery Network (CDN)
- Find CDN Exclusions
- Enter a keyword, filename, or part of the file’s URL, one per line
- Save your changes
Any file whose URL contains what you entered will be excluded from CDN delivery going forward.
A Quick Way to Tell If This Is the Right Tool
If the problem is a single file or script not working correctly once delivered through the CDN, CDN Exclusions is the right setting. If the problem is something broader, like JavaScript breaking site-wide or a theme conflict, the CSS & JavaScript tab’s Exclude CSS and Exclude JavaScript fields are usually a better fit, since those control BerqWP’s code optimization rather than CDN delivery specifically. CDN Exclusions only affects where a file is served from, not how BerqWP processes it.
