Skip to content
Documentation

Broken link checker

Scan your bookmarks for dead URLs and fix them in place

The broken link checker scans every URL in your bookmarks file, checks whether the page still responds, and lists anything that returns an error or is unreachable. You can edit or delete each broken bookmark inline without leaving the modal.

Where to start a scan

  • From the bookmarks page: open the ⋮kebab next to the collection picker and choose Check for broken links. The scan covers the active collection only.
  • From account settings: open account settings and use the Scan button in the Bookmarks file section.
Note: The checker is a Pro feature. URLs are probed by themnera.io server (your browser cannot read status codes from third-party domains directly because of CORS), so the proxy is gated to Pro subscribers. See pricing for plan details.

What you see during a scan

  1. mnera.io loads your bookmarks file from your Solid pod.
  2. Unique URLs are sent to /api/link-check in batches.
  3. A progress bar tracks how many URLs have been checked.
  4. Any failing URL is shown immediately, with the HTTP status code or a short error message (for example HTTP 404, HTTP 500, Timed out, or Unreachable).

Fixing a broken bookmark

Each broken entry has two actions:

  • Edit — opens an inline form with the title and URL. Save to update the bookmark in your pod and remove it from the broken list. Your description and topics are preserved.
  • Delete — asks for confirmation, then removes the bookmark from your pod permanently.

Use Re-scan to run the check again over what's left after your fixes.

How a URL gets flagged

For each URL, the server sends an HTTP HEAD request with an 8-second timeout and follows redirects. If the server returns 405, 501 or 403 toHEAD (some sites don't allow it), mnera.io retries with a minimal GET request. Anything returning a status of 400 or higher, timing out, or failing to resolve is flagged as broken.

What is sent to the mnera.io server

  • The list of URLs from your bookmarks file (in batches of up to 50).
  • Your mnera.io session cookie, used to confirm you're signed in.

The server discards the response body of each probe and returns only the status code (or error label) to your browser. Probe results are not stored, not logged per user, and not used for anything other than answering your scan request.

Limitations

  • False positives. Some sites block automated requests, rate-limit by IP, or refuse user-agents they don't recognise. These return error codes even though the URL is fine in a browser. Always open the link yourself before deleting if you aren't sure.
  • Soft 404s. Pages that have been replaced with a generic “not found” landing page but still return HTTP 200 cannot be detected. The checker only looks at status codes, not page contents.
  • Private and internal URLs. URLs pointing tolocalhost, RFC1918 addresses, or other private hosts are rejected by the proxy with the message Unsupported or private URL.