A Framer SEO checklist.

1. Get the page fundamentals right

The list below breaks this down into the parts that matter most. Read through each one and note anything that applies to your own setup.

• Give every indexable page a unique, descriptive title.
• Write a useful meta description that matches the page answer.
• Use one clear H1 and a logical heading hierarchy.
• Set a canonical URL where duplicate routes or parameters can exist.
• Add descriptive alt text to informative images.

2. Check technical discovery

Here is the process broken into clear steps. Take them one at a time and check each off before continuing.

1. Publish to the intended custom domain and test the HTTPS version.
2. Open robots.txt and confirm important pages are not disallowed.
3. Open the XML sitemap and check that it uses the canonical domain.
4. Inspect representative URLs in Search Console after publishing.

3. Add sharing and structured data

Open Graph controls how a page appears when shared. JSON-LD helps search engines understand an organisation, article, breadcrumb or software product, but only add schema that describes visible page content.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Studio",
  "url": "https://example.com"
}

Final QA

Before making changes, work through the points below. Each one covers a different part of the picture, so treat them as a set rather than picking favourites.

• Test mobile layout and core interactions.
• Check internal links do not point to staging domains.
• Confirm redirects for old URLs.
• Measure the published page, not only the canvas preview.

Pre-publish diagnostic sequence

Follow the sequence below from start to finish. The order matters: later steps assume the earlier ones are done.

1. Crawl the staged domain with a link checker and fix broken internal links first.
2. Confirm every page has exactly one canonical tag pointing to itself or the preferred version.
3. Check that Framer's SEO panel fields are filled for every page, not just the homepage.
4. Run a Lighthouse pass on the slowest template and note any render-blocking assets.
5. Re-check robots.txt after the final publish, since a staging override can survive a domain switch.

Warning signs that launch is not ready

A few moving parts are involved here. The points below cover each of them, so you can see the full scope before deciding where to start.

• Titles or descriptions still read as placeholder or default text.
• The sitemap references the staging subdomain instead of the live domain.
• CMS collection pages share one identical title across every record.
• Search Console shows the wrong property or has never been verified.
• Core pages return a soft 404 or redirect loop when tested directly.