We audit external resources your pages load from other domains — scripts, fonts, stylesheets, embedded content — and check for CORS errors specifically, which is a browser-security issue distinct from a broken hyperlink or a missing local image, and often only visible in the browser console rather than on the page itself.
Check your browser console on the affected page first
Open your browser’s developer console (F12 or Cmd+Option+I) on a page you suspect is affected. A CORS-related error explicitly names the blocked resource and the policy that blocked it, which tells us immediately whether this is genuinely a CORS issue or something else entirely.
Broken external resource & CORS audit
External scripts, fonts, and embeds audited for load failures and CORS-specific console errors.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to browse the site so affected pages can be identified
- The specific page or console error you noticed, if you already have one
- FTP or hosting access, in case a correction is possible on your side
This or something else?
| You want external resources and CORS-related console errors audited specifically | This fix covers it |
| The issue is a broken hyperlink a visitor clicks, not a loading resource | Broken link scan & repair, in the Links, Redirects & Routing category |
| A specific image is broken or missing from your own media library | Broken or missing image restoration |
| JSON-LD structured data is broken specifically by a page builder | JSON-LD broken by page builder – repair |
What we do
- Crawl the site to identify every external resource loaded from another domain
- Check each for load failures and CORS-specific console errors
- Identify the specific policy or header causing each CORS block
- Correct what’s within our control, or document what needs to change on the external source’s side
- Verify affected pages load correctly after correction
What is included
- An audit of external resources and CORS-related errors
- Corrections made where within our control
- Clear documentation of anything requiring a change on an external source’s side
- The pre-fix backup, kept for 30 days
Not included
- Broken hyperlinks a visitor clicks — a separate, related fix
- Broken or missing images from your own media library — a separate, related fix
- Changes required on a third-party service’s own server, which remains outside our control
- Ongoing monitoring for future CORS issues
Questions about this fix
What's actually different between this and a broken link?
A broken link is something a visitor clicks that leads nowhere useful; this covers resources a page tries to load automatically (a font, a script, an embed) that fail or get blocked, often invisibly to a visitor but visible in the console.
Can you fix a CORS error caused by a third-party service?
Only if the fix is on your side — many CORS errors require a header change on the external service's own server, which we can document clearly for you to raise with that provider.
Would a visitor even notice this kind of issue?
Sometimes not directly, though a blocked script or font can cause a page to behave or display incorrectly in ways that do affect the visible experience.
How would I have caught this myself?
The browser console shows CORS errors explicitly when they occur, though most site owners don't routinely check it, which is exactly why this kind of issue often goes unnoticed.
Is this specific to a particular type of external resource?
No — scripts, fonts, stylesheets, and embedded content can all be affected, and we check across all of them rather than assuming one type is the cause.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.