Black Friday30% off your first year on yearly plans with30% off yearly · . Ends 1 Dec.See pricing

Docs

404 Monitor

404 Monitor Overview

404 Monitor Overview

404 Monitor Overview

Last Updated on

Read Time

5 min read

In short

What it does

Learn how the RankFrame 404 Monitor works, how to enable it and inject the tracking script, and where your tracked domains are listed to track broken links on your Framer site.

Where

404 Monitor in the plugin sidebar

Cost

Free

Goes live

After the tracking script is added and you publish.

What the 404 Monitor is

The 404 Monitor is a passive error tracking tool built into RankFrame. Once you enable it, a lightweight script runs on your published Framer site and records every request that returns a 404 status. All captured errors appear in the errors table inside RankFrame so you can review them, prioritize fixes, and add redirects where needed.

Broken links damage SEO in two ways: search engines stop passing link equity through them, and visitors who land on dead pages leave immediately. The 404 Monitor surfaces these problems automatically without any manual checking.

Good to know:

You do not need to be on a paid plan to use the 404 Monitor. Trial users get full access and all errors are tracked from day one.

Where to find it

The 404 Monitor lives under Audit, in the 404 errors section. To open it:

  1. Open the RankFrame plugin inside Framer.

  2. Click Audit in the main navigation.

  3. Select 404 errors.

The page subtitle reads: “Automatically detect and log broken pages on your Framer site.”

How to set it up

Setup takes a few steps. Complete them in order so errors start coming in as soon as you publish.

1

Open 404 errors

Go to Audit and click 404 errors.

2

Enable the monitor

Click Enable 404 Monitor. The Active toggle at the top right turns on, and three tabs appear: Hit Log, Settings and Setup.

3

Inject the tracking script

Open Setup and click Review & Inject. A review window shows the script currently installed and the script that will be installed at the end of the <body> tag (bodyEnd). Nothing else in your Custom Code is changed. Click Confirm & Inject, and the Tracking Script status changes to Active.

4

Publish your Framer site

The script only runs on the published site, so publish or republish your project. Monitoring starts after publishing.

Your Framer project must have a 404 page that contains the text “404” or “Page Not Found” for the script to detect errors.

The domains errors are logged from are listed in Profile, under Domains. New domains are detected automatically when you publish your Framer project to a new URL. To manage them, see Changing Your Domain in RankFrame.

Stats at a glance

At the top of the Hit Log, four summary figures give you an instant sense of how many broken links exist on your site.

  • Total Hits: every 404 hit recorded across all tracked domains

  • Unique Routes: the number of distinct paths that returned a 404. One broken path hit many times still counts once

  • Locales Affected: how many language versions of your site have 404s

  • Domains: how many of your tracked domains have 404s

Below the figures, the log lists each broken path with its domain, hit count, language and last hit. Filter by domain or language, sort by newest first, click Refresh to load new hits, and use Export to download the list.

A high Unique Routes count with many hits per route often signals a structural problem like a renamed page or a broken redirect rather than isolated external link typos.

Tracking script status

The Setup tab shows the status of the tracking script. Not Injected means the script is not in your Custom Code yet. Active means it is installed and, once your site is published, 404 errors are detected and logged.

Use Review & Re-inject only if you have problems, and Debug Scripts to check what is installed. To remove the script, click Remove from Custom Code, or delete it in Framer under Site Settings, Custom Code.

Trial plan access

There is no restriction on the 404 Monitor during a trial. All 404 errors are tracked from the moment you enable the script, and the full errors table is available without any limits. You do not need to upgrade before you start collecting data.

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.

Multi-language sites

The 404 view follows the selected locale, and exception routes can be set globally or for one language only. See Per-Language 404 Exceptions.

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

Does the 404 Monitor work on Framer preview URLs?

No. The monitoring script only runs on your published live site. Preview URLs inside the Framer editor are not tracked.

Can I monitor more than one domain at the same time?
Will the monitoring script slow down my site?
How do I stop monitoring?
Are there routes I should exclude from tracking?
Was this page helpful?

Still stuck?

Try the troubleshooting guides, or send support the page link and a screenshot.