Why Your Framer Pages Aren't Getting Indexed (and How to Fix It)

Framer builds fast, pre-rendered sites, so the usual JavaScript indexing problems do not apply: your content is in the HTML from the start. That means when a Framer page will not index, the cause is almost always a setting, a forgotten noindex from development, or simply not republishing after a change. Here is how to find and fix it.

Why isn't my Framer page getting indexed?

A Framer page usually fails to index because of a page setting or an unpublished change, not a rendering issue. Start with the per-page control: in a page's settings, Framer has a "Show this page in search engines" checkbox, and when it is unchecked, Framer injects <meta name="robots" content="noindex"> into that page so Google skips it. A noindex left over from development is one of Framer's own listed causes of pages not indexing, "usually added during development and forgotten when deploying to the live site." Next, confirm you republished, because Framer only applies SEO changes to the live site after you publish. Finally, check which URL Google indexed: free sites live on a shared framer.website subdomain, and you want your custom domain indexed instead. Because Framer pre-renders content into the HTML, you rarely have to worry about whether Google can read the page, only about whether something is telling it not to.

Is the page's "Show this page in search engines" setting off?

This checkbox is the most common reason one specific Framer page is missing from search. In Page Settings, under the Search engines section, Framer provides a "Show this page in search engines" control. When it is off, Framer adds a noindex robots meta tag to that page, and its help docs note this uses the noindex meta tag rather than editing robots.txt, following Google's recommended approach. So a single page that refuses to index while the rest of the site is fine almost always has this unchecked. The trap is that the toggle is frequently switched off intentionally while a page is being built, then forgotten at launch. Open the page's settings, confirm the page is set to show in search engines, and then, importantly, republish the site so the change goes live. The exact wording can vary slightly between Framer's editor versions, but the control is always a per-page switch for whether search engines may index that page.

Did you republish after changing SEO settings?

Framer applies SEO settings to your live site only when you publish, so unpublished changes are invisible to Google. This is a recurring theme in Framer's own troubleshooting guidance: fix the setting, then republish. It catches people because the editor shows your change immediately while the live site still serves the old version, so you check Google, see no difference, and assume the fix did not work. Treat "republish" as a mandatory final step after any SEO edit. The settings that share this requirement include:

• The per-page indexing checkbox, which adds or removes the noindex tag.
• Meta titles and descriptions, set per page or site-wide in Site Settings.
• The Google site verification tag, which you paste into the site's head and which only verifies after you publish.
• A custom robots.txt, if you upload one via Static Files on a higher-tier plan.

If a change is not reflected for crawlers, an unpublished edit is the first thing to check.

Does Framer render content in a way Google and AI crawlers can read?

Yes, Framer pre-renders pages to HTML on its servers, so your content is in the initial response that any crawler receives. Framer states plainly that "every page is pre-rendered to HTML on our servers before it is served," and that this pre-rendered HTML includes headings, paragraphs, semantic markup, title and description tags, Open Graph data, canonical URLs, and JSON-LD structured data. That is exactly what both Google and non-rendering crawlers need. It matters in 2026 because the AI crawlers behind ChatGPT, Claude, and Perplexity do not execute JavaScript, so they can only read content that is in the raw HTML, which on Framer it is. Framer goes a step further for AI search: it serves a Markdown version of any page when you append ?md to the URL or send an Accept: text/markdown header, and it supports the llms.txt standard. The practical takeaway is that if a public Framer page is not indexing, the cause is a setting or content value, not the rendering, which puts Framer ahead of client-rendered platforms like raw Notion sites.

Why is my framer.website subdomain indexed instead of my domain?

Free Framer sites publish to a shared framer.website subdomain, and that low-authority URL can end up indexed instead of, or alongside, your real domain. The subdomain is indexable, Framer does not noindex it by default, but it carries little ranking authority because it is shared across many sites and is not a domain you own. Custom domains require a paid plan. The duplicate-content risk appears when a site is reachable on both its framer.website subdomain and a connected custom domain: Google can index both versions and treat them as duplicates, splitting your signals. The fix is to connect a custom domain on a paid plan, make it your primary URL, and rely on Framer's canonical tags so Google consolidates on the domain you own. If the subdomain is already indexed and lingering, you can address it the same way Google recommends for any duplicate: pick the canonical, and use Search Console to nudge the unwanted version out.

How do I connect Framer to Google and get a page re-checked?

Verify the site in Search Console, submit the sitemap, then inspect and request indexing. Because you cannot upload an HTML file to a Framer site, use the HTML meta-tag verification method: copy the tag from Search Console, paste it into Site Settings so it sits in the page head, save, and republish, then click Verify in Search Console. From there:

1. Submit /sitemap.xml, which Framer auto-generates and updates on each publish, in the Search Console Sitemaps report.
2. Run URL Inspection on the exact page to see how Google views it and whether it detects a noindex.
3. Click Request Indexing for priority pages.
4. Republish after any SEO change, since nothing reaches crawlers until you do.

Framer's own guidance for a handful of stuck pages is to enable indexing, republish, and submit via URL Inspection, after which it "will probably fix itself in a few days." What none of this catches is an already-indexed Framer page quietly dropping out after a republish or a settings change. SearchOptimo re-checks the index status of every URL on a schedule and alerts you the moment a page falls out, so a regression surfaces in a dashboard instead of in your traffic.

If you are monitoring more than a handful of pages, see whether SearchOptimo is worth it for your case, or start free and watch your own URLs.