Links and references

How the CMS keeps links between your pages working when pages are renamed, moved or deleted, and what it tells you when they are not.

Verified November 15, 2026

Your content links to itself all the time: a button to the services page, an image in a hero, a navigation entry. Those links are plain values in your files (/sluzby/, /src/assets/hero.png, a translationKey), which is what keeps your repository readable by any build. The CMS adds what plain files lack: it knows which page lives at which address and which files point at it, so renaming a page does not leave broken links behind, and a link that broke anyway is shown to you.

What counts as a reference

The CMS reads your schema to find them:

  • Links: link fields whose value is an address on this site (/kontakt/), plus addresses in rich text and in the page body ([text](/kontakt/), href="/kontakt/"). Outside URLs, mailto:, tel:, anchors and {{variables}} are not references.
  • Assets: image and file fields, resolved through your storages to a file in the repository.
  • References: reference fields, resolved to an entry by its path or by a key field such as translationKey.

A page's address comes from its collection's previewPath template, the same rule the live preview uses. A collection without a template is left alone. See Preview deep-linking.

The three states

Every reference the CMS knows has one of three states, and the editor treats them differently:

StateMeaningShown as
resolvedThe target exists, or the address is in the site's knownPaths.Nothing; the page link shows the title.
brokenThe link pointed at a page that was moved or deleted, or names an asset or entry the repository lacks.A warning in the Errors panel and a badge.
unverifiedAn address no content file produces. Usually a route from code.A quiet hint.

A link is never called broken on first sight. The CMS has to have seen it resolve once; it then knows what the link pointed at and can tell you "Services moved" rather than just "404". Routes your site serves from code (/styleguide/, /api/*) go in knownPaths so they stop appearing as hints.

Renaming a page

Change a page's slug (or move its file) and publish. When other pages link to the old address, the editor shows them before anything is committed:

  • the old and the new address;
  • the pages whose links would break, with how many links each;
  • the redirect rule that will be added to your redirects file, or a note that the site declares none.

Confirm, and one commit carries the page, the rewritten links on the other pages and the redirect. Decline, and only the page changes; the other pages' links are then reported as broken until you fix them.

The same dialog appears for Rename or move on a page tile in the pages list, for sites whose addresses follow file names.

# .norcube/cms/config.yml
redirects:
  file: public/_redirects
  format: netlify

Pages linking here

The Errors panel of every page lists the pages that link to it, and the delete confirmation says how many will lose a link. Reference fields that point by key (the navigation's translationKey) are not affected by renames at all, since the key does not change; they appear in the list but need no rewrite.

What the CMS cannot fix

  • Links written in your site's code or templates.
  • Links from other websites. The redirect is what keeps those working.
  • A rename made outside the CMS (a git mv in the terminal). The next time someone opens a page linking to it, the link is flagged as broken, and the page link's picker offers the new page.

On this page