Framer Canonical URLs: Verify the Published Origin After Domain Changes

After changing a Framer site's domain or proxy arrangement, verify the canonical URL in the published HTML. The hostname people see, the origin represented in metadata and the URLs used in navigation should describe the same intended public site.

Framer's custom canonical guidance says directly connected domains are usually handled automatically. A reverse proxy can require explicit configuration because Framer may not know the final public origin.

Write down the intended URL pattern

Record the preferred scheme, hostname and path structure before changing settings. Include the homepage, a normal page and a CMS detail page.

For example, a product directory needs each detail path to remain attached to its own record. Pointing every record at the homepage would lose that relationship even if the hostname were correct.

LaunchAF is a directory-style product associated with Framer in the technology catalogue. This is an example of the page family to review, not evidence of its hosting or proxy arrangement.

Inspect actual published HTML

Publish the intended configuration, request the public URL and inspect its canonical link. Confirm both the origin and the path.

A preview can help find configuration mistakes, but it does not establish what a crawler receives from the real public address. A proxy, redirect or stale deployment can alter the result.

Check that the canonical target resolves to the expected page and that it is not a private preview address or an obsolete domain.

Follow internal links across page families

Begin at the homepage and open a collection, a detail page and a footer page. Confirm that navigation keeps visitors on the intended public origin.

Look for absolute URLs embedded in reusable components and old content. A global domain setting may not rewrite every link an editor typed manually.

Where an old address redirects, verify the destination for that particular page. A broad homepage redirect is rarely an adequate replacement for a still-relevant detail page.

Compare discovery and sharing surfaces

Framer provides a published sitemap. Inspect representative entries and compare them with the canonical URLs of those pages.

Also review sharing metadata and any structured data configured for the page. These representations should identify the same subject at the same intended address.

The CMS metadata review explains how record fields can be checked alongside the visible content.

Keep evidence from the change

Save the tested URLs, redirect destinations and canonical values before and after the configuration change. Include the time and deployment or publishing reference.

This record helps distinguish a stale external preview from an incorrect site response. It also gives a reviewer something more precise than a screenshot of the domain settings.

Do not treat a canonical tag as a guarantee of indexing or preferred search appearance. It is one consistency signal within a site whose content, links and accessible URLs must also make sense.

Repeat the review whenever a domain, reverse proxy or collection path changes. A few deliberate page-family checks can reveal a configuration error before it spreads through navigation and newly published records.