framer.app showing in Google: how to remove your staging site
Your Framer staging address (yoursite.framer.app or .framer.website) is a public copy of the site, so Google can crawl and index it alongside your custom domain. On a paid plan, set Staging to Protected in Project Settings > Versions & Staging and publish, so visitors and crawlers must log in to Framer. Then add the staging address as a URL-prefix property in Search Console and request removal of everything under that prefix.
What you'll see
Searching your brand shows results on a framer.app or framer.website address, sometimes with draft pages or old copy. Your custom domain ranks lower than expected, or both versions of the same page appear in results.
Why it happens
1. Staging is public by default
The staging subdomain exists so you can review changes before publishing to your domain. Unless it is protected, anyone with the URL, including Googlebot following a stray link, can load it.
2. Two copies of the same pages
When the staging site and the live domain carry the same content, Google has to pick one. It does not always pick your custom domain, and drafts on staging can show up as if they were live.
3. Links to staging leaked out
A staging link shared in a tweet, a client email that got forwarded, a portfolio or a template marketplace gives Google a path to the subdomain.
4. The site launched on staging before the domain was connected
If the site ran on the framer.app address for weeks before you bought or connected a domain, Google may have indexed it there first. Those older results linger until Google recrawls both addresses and settles on one.
How to fix it
- Search site:yoursite.framer.app (and site:yoursite.framer.website if you used that) to see which staging pages Google holds.
- If you plan to remove them through Search Console, add the staging URL as a URL-prefix property first and verify it with the HTML tag method, pasting the tag into Site Settings > Custom Code > Head and publishing to staging.
- Open Project Settings > Versions & Staging, set Staging to Protected, and publish. Protected staging needs a paid Framer plan; check the plan page for current details.
- In Search Console, open the staging property, go to Removals, create a new request, choose to remove all URLs with this prefix, and submit the staging URL.
- On your live domain, check that each important page has Show this page in search engines turned on in its page settings, and request indexing for the homepage with URL Inspection in the custom-domain property.
- Find and update any public links that still point at the staging address.
How to check it's fixed
- The staging URL opened in a private window asks you to log in to Framer instead of showing the site.
- Over the following weeks, a site: search for the staging address returns fewer results and your custom domain appears for brand searches.
What a QAlaunch scan shows for this
- A canonical tag on your live pages that points at a framer.app or framer.website address instead of your domain.
- Scanning the staging URL shows whether it is still publicly viewable or now behind a login wall.
- A robots noindex tag accidentally left on live pages you want indexed.
See exactly what a full report contains in the sample report.
Frequently asked questions
Is a Search Console removal permanent?
No. A removal hides URLs from results for about six months. Protecting staging is what keeps them from coming back, so do both.
What if I am on the free Framer plan?
Protected staging is a paid feature. Without it, keep staging links private, make sure your live domain has strong, unique pages, and use Search Console removals for anything that leaks.
Will protecting staging hurt my live site’s ranking?
No. It only affects the staging subdomain. It helps the live domain by leaving Google one copy of each page to rank.
How long until the staging results disappear?
Removal requests are often processed within a day or two, but Google can take several weeks to drop every staging URL for good. Keep checking with a site: search and leave the protection on.
Rather have a QA engineer test it by hand?
If this is a site you're launching or handing to a client, I'll go through it by hand, including the Framer-specific issues a scan can't reach, like logged-in flows.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
More for Framer: all Framer fixes
Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: BRIX Templates: stop Google indexing your Framer staging subdomain · Framer Help: troubleshooting Google indexing