Blog / Framer & site building /

Metadata defaults for framer pages

The page looks gorgeous in the Framer canvas. Then you publish, and the browser tab says “Home”. The social preview shows an old image. Oops.

Metadata defaults are easy to forget because they sit outside the visible design. Set a sensible site-level baseline, then check the page-level values that matter before publishing.

A default is a fallback, not a replacement for meaningful titles and descriptions on important pages. Make the values clear, consistent and easy for the people editing the site to maintain.

Separate global defaults from page details

A site-wide title pattern can include a brand name or other consistent element, while each page still needs a title that describes its own purpose. If every URL inherits exactly the same title and description, search results become vague and social shares lose context. It’s one of the first things I check on any site I review. Use global settings for what is genuinely shared and page settings for the unique subject.

Start by listing the pages that need their own metadata: home, services, product or feature pages, pricing, contact, articles and legal pages. Decide who owns updates when the content changes. A published title should match the page rather than an internal project name or a temporary design label.

Write titles for people scanning results

A title should identify the page and make its value understandable. Put the key subject in ordinary language and avoid repeating the same phrase several times. If a brand name is helpful, include it consistently, but do not let it crowd out the page description.

Search engines can choose a different title in results. That does not make the title field useless; it means the page should have coherent headings and visible content too. Review the title beside the H1 and page copy. If they promise different things, decide which one represents the page and align the rest.

Treat descriptions as useful summaries

Meta descriptions may be used as snippets, but search engines can generate a different snippet based on the query. Write a concise summary that tells a person what the page covers and what they will find. Avoid promises the page cannot fulfil or boilerplate repeated across every URL.

Descriptions are especially worth reviewing on pages that receive impressions but attract few relevant clicks. Check the query mix and page first; a low click rate is not always a description problem. The description should support the page’s purpose, not serve as a guarantee of a particular snippet.

Check social metadata too

Open Graph and related social fields control how a link may appear when shared on supported platforms. Choose a representative image and text that make sense when the URL is copied into a message. A social preview image should be legible when cropped and should not contain details that become unreadable at small sizes.

Check whether the site has defaults and page overrides. If an article uses the home-page image by mistake, a share can look unrelated even when the page itself is correct. After changing metadata, use the platform’s preview or inspection tools where available and remember that cached previews may take time to refresh.

Confirm canonical and indexing settings

Metadata work should include canonical and indexability checks. A page can have an excellent title and still be excluded from search because it is noindexed, canonicalised elsewhere or blocked. Confirm that the canonical points to the intended public URL and that staging or duplicate pages are not being exposed accidentally.

Framer’s controls and interface can change, so use the current editor and official help material for the actual project. Don’t paste code or inject custom tags without understanding how they interact with the site’s existing metadata. One source should own each important field. I’d rather have one clear setting than two that fight each other.

Build a short publishing checklist

Before publishing, check the title, description, social image, H1, canonical, indexability and preview at mobile width. Confirm the page is linked from a relevant part of the site and that the metadata reflects the final copy, not the first draft. When changing a URL, add redirect planning to the checklist.

Use repeatable defaults without making pages sound alike

A title pattern can save setup time, but it should not flatten every page into the same formula. If the global pattern automatically adds the brand name, preview how it reads on a long title and a short one. If a page has a specific audience or service, its own title should make that clear rather than relying on the site-wide default to do all the work.

Create a small inventory of fields that must be checked before publishing. Include the title, description, social image, canonical and indexing choice, plus the page’s visible heading and next step. Assign an owner for metadata on pages that change often. A default can cover the routine case, but someone still needs to review important pages when the offer or content changes.

Don’t judge metadata in isolation. A strong title cannot compensate for a page that does not answer the query, and a neat social image cannot repair a broken form. Treat defaults as part of a wider publishing workflow, then verify the result in the live page and the actual share preview.

Test the default with unusual page names

A default title pattern should survive more than the homepage and a short service label. Test a long article title, a page with punctuation and a CMS item whose name is still a draft. Make sure the output does not repeat the brand twice or leave a separator hanging at the end. A pattern that behaves well in the common case can look careless in edge cases.

Review templates with multiple language or collection variants if the site uses them. Check that an override belongs to the correct page and that changing a global default does not erase a useful custom value. Keep a note of the expected output so another editor can distinguish a deliberate page title from an inherited fallback.

A good default saves repeated setup. A page-level review keeps the site specific. You need both.

Try this now: copy the link to your most important Framer page and paste it into a message to yourself. Does the preview look like that page, or like your homepage from six months ago? Fix whatever surprised you.