Troubleshooting
Docs
Troubleshooting
Fixing 404 Monitor Not Tracking
Last Updated on
Read Time
3 min read
In short
What it does
The 404 Monitor uses a lightweight script in your Framer site's Custom Code to catch and log 404 errors. When the monitor shows no hits or stops working, the cause is almost always one of a few setup steps. This article covers all of them.
Where
404 Monitor and Framer Custom Code
Cost
Free

Good to know:
404 Monitor Setup Checklist: The 404 Monitor is enabled in Audit > 404 errors and the Active toggle is on. In the Setup tab, the Tracking Script shows Active after Review & Inject. Your Framer site has been published since you injected the script. Your project has a 404 page that contains the text “404” or “Page Not Found”. Intentional paths are added to Exceptions in the Settings tab so they are not logged.
404 Monitor Not Enabled
Cause: The 404 Monitor has not been switched on, so nothing is being tracked.
Fix: Open Audit > 404 errors and click Enable 404 Monitor. The Active toggle at the top right turns on, and the Hit Log, Settings and Setup tabs appear.
Tracking Script Not Injected
Cause: The Setup tab shows the Tracking Script as Not Injected. Until it is injected, the Hit Log shows “No hits yet”.
Fix: Open the Setup tab and click Review & Inject. Check the script in the review window and click Confirm & Inject. The status changes to Active.
Site Not Published Since Injecting
Cause: The script is added to your Custom Code, but it only runs on the published site. Monitoring starts after you publish.
Fix: Publish or republish your Framer project. Then wait for real visitors or bots to hit broken URLs.
No 404 Page With “404” or “Page Not Found”
Cause: The script detects errors by looking for this text on your 404 page. If your project has no 404 page, or the page does not contain either phrase, nothing is logged.
Fix: Make sure your Framer project has a 404 page containing the text “404” or “Page Not Found”, then publish again.
Domain Not Detected Yet
Cause: Hits are logged for the domains listed under Tracked Domains in Profile > Domains. A new domain is detected when you publish your Framer project to it.
Fix: Publish your project to the domain, then check that it appears in Profile > Domains. See Changing Your Domain in RankFrame for adding and switching domains.
Script Active but Still No Hits
Cause: Something in your Custom Code may have changed since you injected the script.
Fix: In the Setup tab, click Debug Scripts to see what is installed. If anything looks wrong, click Review & Re-inject, then publish again.
No Real 404 Errors Yet
Cause: The monitor is working correctly but your site genuinely has no broken URLs. This is the best possible outcome.
Fix: No action needed. Hits appear in the Hit Log when real users or bots reach broken URLs on your site.
Too Many False Positives
Cause: Paths you use on purpose, such as test paths or routes you know return a 404, are appearing in the Hit Log.
Fix: Open the Settings tab and add those paths under Exceptions, either Global or Per Language. Exceptions are never logged as 404 errors. In the same tab, Language Monitoring lets you choose which languages are monitored.
Totals Show Hits but the Log Is Empty
Cause: The domain or language filter above the log is set to one that has no hits, while others do.
Fix: Set the filters above the log to All Domains and All Languages to see every logged hit.
Removing the Script
To stop monitoring, open the Setup tab and click Remove from Custom Code, or delete the script in Framer under Site Settings, Custom Code. Publish your site afterwards.
404 monitoring per language
Switch locale in the plugin and the 404 view switches with it, so you see the errors recorded for that language version only. Exception routes can be managed per locale as well as globally, and changes apply immediately without republishing.
If you installed the 404 script before this release, it keeps working. You do not need to reinstall it.
Related features
404 Monitor: Log every broken link real visitors hit, per language.
Multi-language: Every locale detected from your sitemap and handled on its own.
Frequently asked questions
How quickly do 404 errors appear in the monitor after the script is injected?
Hits are logged as visitors reach broken URLs on your published site. Once the Tracking Script shows Active and you have published, click Refresh in the Hit Log to load new hits.
Why does the 404 Monitor show hits in the totals but the log is empty?
Do I need to republish my Framer site after injecting the script?
How do I stop intentional paths from appearing as 404 errors?
Can the 404 Monitor track errors from multiple domains?
Still stuck?
Try the troubleshooting guides, or send support the page link and a screenshot.