Back to Home
Framer Site Not Showing on Google? Fixes

The most common reason a Framer site isn’t showing on Google is that the “Show in search engines” setting was left off after development — Framer defaults pages to noindex while you build, and many sites go live without switching it on. Other frequent causes are the site simply being too new (indexing takes days to weeks), important content or navigation trapped inside overlays that crawlers can’t see, a missing or unsubmitted sitemap, or a redirect/canonical issue. Check the noindex setting first; it’s the single most common cause.
Publishing a Framer site doesn’t put it on Google instantly, and a handful of Framer-specific settings can block indexing entirely. This guide covers the real causes in order of likelihood, how to diagnose which one is yours using Google Search Console, and the fix for each. Written to get your site indexed, not to guess.
Framer Site Not Showing on Google? Reasons It’s Not Indexed
Your Framer site isn’t showing on Google most often because the “Show in search engines” toggle is still off (Framer noindexes pages during development), or because the site is too new to be indexed yet — both are common and both are fixable. Beyond those, indexing is blocked or delayed by overlay-trapped content, a missing sitemap submission, or redirect/canonical issues.
The important mindset: “not showing on Google” is rarely one mysterious problem — it’s usually one of a short list of specific, checkable causes. Work through them in order and you’ll find yours quickly.
Is your Framer site set to “noindex”?
The number-one cause is the “Show in search engines” setting being left off — Framer sets pages to noindex during development so unfinished work doesn’t get indexed, and it’s easy to publish without turning it on. Check this first, before anything else.
To fix it: in Framer, go to your site/page settings and make sure the option to show the site in search engines is enabled (noindex is off) for every page you want indexed, then republish. A quick way to confirm the current state is to view the live page’s source and check for a `noindex` meta tag, or use Google Search Console’s URL Inspection tool, which will tell you plainly if the page is excluded by a noindex directive.
Is your Framer site simply too new?
If the noindex setting is correct and your site is only days old, the most likely answer is that Google hasn’t indexed it yet — indexing a new site or page typically takes anywhere from a few days to a few weeks, and there’s often nothing wrong. New sites and pages sit in a queue; being absent from Google in the first week or two is normal, not a bug.
To speed it up: set up Google Search Console, submit your sitemap, and use URL Inspection to request indexing for key pages. Then wait — if only a handful of pages are affected, they’ll usually appear within days. Repeatedly resubmitting won’t make it faster.
Is your content or navigation trapped in overlays?
A Framer-specific cause is content or navigation links living inside overlays or modals, which don’t exist on initial page load and so aren’t seen by Google’s crawler — if your only link to a page is in an overlay menu, that page can become an orphan Google never reaches. This particularly affects sites that put feature pages, pricing, or nav exclusively in overlay components.
To fix it: make sure important content exists in the main page (not only in an overlay), and duplicate key navigation links in your footer or a standard sitemap so every page has a crawlable path to it. Framer also has a documented method for making accordion/collapsed content indexable (set the collapsed variant’s height and opacity to 0 rather than removing it), which keeps the content in the HTML for crawlers.
Is your sitemap missing or unsubmitted?
Framer generates a sitemap automatically at yourdomain.com/sitemap.xml, but Google won’t use it until you submit it in Search Console — an unsubmitted sitemap is a common reason new pages are slow to index. Confirm the sitemap loads by visiting that URL in a browser, then submit “sitemap.xml” in the Sitemaps section of Google Search Console.
If Search Console shows “Couldn’t fetch” with no other error, it’s often just queued — give it time and lean on strong internal linking in the meantime, since internal links help Google discover pages regardless of the sitemap’s status.
Could a redirect or canonical issue be blocking it?
If Search Console reports “Page with redirect,” “Duplicate,” or “Alternate page with proper canonical tag,” a redirect or canonical setting is telling Google not to index that specific URL — these are configuration issues, not penalties, and each has a clear fix. For duplicates, make the content unique or set the canonical intentionally; for redirect exclusions, confirm the URL you want indexed is the final destination, not a redirecting one.
Use Search Console’s Pages report (Indexing → Pages) to see exactly why each URL is excluded — the error message names the cause, which points you straight to the fix.
FAQ: Framer site not indexing on Google
Why is my Framer site not showing on Google? Most often the “Show in search engines” setting is still off (Framer noindexes during development), or the site is too new to be indexed yet. Overlay-trapped content, an unsubmitted sitemap, or redirect/canonical issues are other common causes.
How do I make my Framer site show up on Google? Enable “Show in search engines” (turn off noindex) and republish, set up Google Search Console, submit your sitemap at yourdomain.com/sitemap.xml, and request indexing for key pages. Then allow a few days to weeks.
How long does it take Google to index a Framer site? Typically a few days to a few weeks for a new site or page. Being absent in the first week or two is normal. Submitting your sitemap and requesting indexing in Search Console helps.
Why does Framer set pages to noindex? Framer noindexes pages during development so unfinished work isn’t indexed. You must enable “Show in search engines” before or at launch, which is easy to forget — making it the most common indexing cause.
Why isn’t my Framer navigation or overlay content indexed? Content inside overlays or modals doesn’t exist on initial page load, so crawlers don’t see it. Keep important content in the main page and duplicate key nav links in the footer or sitemap so pages have crawlable paths.
How do I check why a Framer page isn’t indexed? Use Google Search Console’s URL Inspection tool for a single page, or the Pages report (Indexing → Pages) for the whole site — both name the exact reason a URL is excluded, which points to the fix.
Struggling to get your Framer site ranking?
FramerLab builds Framer sites that are indexable and SEO-clean from launch — one H1 per page, correct indexing settings, sitemaps, schema, and crawlable structure. Senior-led, NDA-friendly.Book a discovery call.
Start at theFramerLab
Deeper on SEO: is Framer bad for SEO?
Migrating?WordPress → Framer without losing SEO
More fixes:Framer “pages too large” error
This is a sensitive area for a business relying on search traffic — if indexing issues persist after these steps, Google Search Console’s reports and the Framer community are the right next stops.
Written by Dilip, founder of FramerLab, with 5+ years designing and building on Framer. Connect onLinkedInandX.
© Framer Lab 2026. All rights reserved.
© Framer Lab 2026. All rights reserved.
Now Accepting New Projects



