Your Webflow website is not showing up on Google because a setting is actively blocking search engines from reading your pages. You likely have search engine indexing disabled in your project settings, or you have not set your custom domain as the default. You need to remove these blocks and submit your sitemap to Google Search Console.
Why is my Webflow website not showing up on Google?
When your Webflow website is not showing up on Google, you have to separate discovery from indexing. A page can be known to Google but not crawled. It can be crawled but not indexed. It can be indexed but ranked too low to be visible. You need to find exactly where the process stops. Do not just submit your sitemap again and hope for a different result. You have to check your settings in a specific order.
You blocked search engines in your Webflow settings
The most common reason a Webflow site stays hidden is a single toggle in your project settings. Webflow includes a feature to disable search engine indexing across the entire project. This is useful when you are building the site and do not want unfinished pages leaking to the public. It is fatal when you launch.
When this toggle is turned on, Webflow injects a noindex meta tag into the head code of every single page. Google respects this tag strictly. It will drop your entire site from search results, even if you have a perfect sitemap and great content.
How to check this in under a minute:
- Open your Webflow project settings.
- Click on the SEO tab in the top navigation.
- Scroll down to the Indexing section.
- Look for the toggle named Disable Search Engine Indexing.
If this toggle is switched on, turn it off immediately. Save your changes and publish your site to all domains. Google will not return instantly. You have to wait for their bots to crawl your site again and read the updated code. You can verify the tag is gone by opening your live website, right clicking the page, and selecting View Page Source. Search the code for the word noindex. If you cannot find it, your site is clear.
You published to the staging domain instead of a custom domain
Webflow gives every project a free staging domain ending in webflow.io. This address is for testing interactions and layout changes. You should never try to rank this staging domain in search results.
If you search for your brand and find nothing, check which address you are actually publishing to. You might have connected a custom domain but forgot to set it as the default. When multiple domains load the exact same website, Google gets confused by the duplicate content. It might choose to index the staging domain instead of your real address, or it might index neither.
Go to your project settings and click on the Publishing tab. Find your custom domain in the list of connected domains. Click the Make Default button next to it. This forces all traffic from the staging domain to redirect to your real address. Google will now know which version is the canonical version to rank.
While you are in the Publishing tab, make sure you disable indexing for the webflow.io subdomain. Webflow provides a specific toggle for this. You only want your custom domain to appear in search.
Your page settings are hiding specific URLs
Sometimes your homepage appears in search, but your service pages or blog posts do not. This means your global project settings are fine, but your individual page settings are broken.
Webflow allows you to control indexing on a page by page basis. You might have accidentally excluded a page from search while duplicating a draft.
Open the Webflow Designer. Open your Pages panel on the left side. Click the gear icon next to the missing page to open its settings. Scroll down to the SEO Settings section. Look for the Sitemap indexing toggle. If it is off, turn it on. Save and publish.
You must also check your CMS collection pages. If your blog posts are missing, open the CMS Collection Pages section in the Pages panel. Click the gear icon for your blog post template. Ensure the indexing is enabled here as well. A single wrong click on a template page will hide every single blog post in that collection.
You have a robots file blocking crawlers
Your robots.txt file tells search engines which parts of your website they are allowed to visit. A single typo in this file will block Google completely.
Go to your Webflow project settings and click on the SEO tab. Scroll down to the robots.txt section.
If you see the line "Disallow: /" in this box, you are telling every search engine to stay away from your entire website. Delete that line immediately. You only need to use this file if you are actively trying to hide specific folders, like an internal client portal. For a standard business website, you can leave this box completely blank.
Blocking a crawler is not the same as adding a noindex tag. If you block Google in your robots.txt file, it cannot read the page instructions at all. You can read more about how crawling works to understand why this file is so sensitive. If Google cannot crawl the page, it cannot process your title tags or your content.
You have not verified your site in Google Search Console
Google does not automatically know your website exists. You have to tell them. You do this through Google Search Console. If you have not set up this free tool, you are operating blindly. You need to verify your domain ownership to access the diagnostic data.
Follow these exact steps to verify your custom domain:
- Go to Google Search Console and click Add Property.
- Enter your custom domain in the Domain property box, not the URL prefix box.
- Google will generate a TXT record for you to copy.
- Go to the registrar where you bought your domain, like GoDaddy or Namecheap.
- Open your DNS settings and add a new TXT record. Paste the code from Google into the value field.
- Return to Google Search Console and click Verify.
DNS changes can take a few hours to propagate. If it fails, wait and click verify again later. Once verified, you can see exactly how Google views your website.
You can use the URL Inspection tool at the top of the dashboard to check any specific page. Paste your full URL into the search bar and hit enter. This tool tells you if the page is discovered, crawled, or indexed. It will highlight any technical errors blocking the page. This is the only way to know for sure why a page is failing. You can read more about this exact diagnostic process in Hassaan Javed's technical guide.
You have not submitted your XML sitemap
A sitemap is a list of every public page on your website. Webflow can generate this automatically, but you have to turn the feature on.
Go to your Webflow project settings and click on the SEO tab. Scroll down to the Sitemap section. Turn on the Auto generate XML sitemap toggle. Save your changes and publish your site. Your sitemap now lives at yourdomain.com/sitemap.xml.
Generating the sitemap is only the first step. You must submit it to Google. Open Google Search Console. Click on Sitemaps in the left menu. Type sitemap.xml into the box and click Submit.
Google will now read this file and discover your pages. Look at the status column. It should say Success. If it says Couldn't fetch, check that you spelled the file name correctly and that your site is published.
Remember that a successful sitemap supports discovery. It does not force indexing. Google still has to decide if your pages are worth showing to users.
You have duplicate content confusing the index
If you have multiple pages with the exact same content, Google has trouble choosing which one to show. Often, it will choose to show none of them. This is common in Webflow when you create multiple landing pages for different cities but forget to change the text.
Every indexable page should point to a preferred public URL. You manage this using canonical tags. A canonical tag tells Google which version of a page is the master copy.
Webflow allows you to set a global canonical domain in your SEO settings. Go to Project Settings, click SEO, and find the Global Canonical Tag section. Enter your default custom domain here, including the https:// part. This prevents issues with www and non-www versions of your site competing against each other.
If you have specific pages that are duplicates of others, you need to set page level canonical tags. You can add a custom tag in the head code section of the duplicate page, pointing to the original page. This consolidates your ranking signals and clears up the confusion for search engines.
Your redirects are broken
If you rebuilt an old website in Webflow, your old URLs no longer exist. If you did not set up redirects, Google will follow its old index, hit a 404 error page, and eventually drop your site from search results.
You need to redirect old addresses directly to the closest relevant destination on your new Webflow site. Go to your project settings and click on the Publishing tab. Scroll down to the 301 Redirects section.
Enter the old URL path in the Old Path box, and the new URL path in the Redirect to Page box. Click Add Redirect path, then publish your site.
You must also remove any redirecting URLs from your sitemap and update your internal links. Visitors and crawlers should reach the final page without bouncing through a chain of redirects. If you need a complete overhaul of your structure, you can read about our approach on our work page.
Your template pages are generating soft errors
Webflow CMS creates a template page for every collection. If you have a collection for team members but you only created two team members, Webflow still generates the template structure for the rest. Sometimes, empty template pages get crawled by Google. Google sees a page with no content and flags it as a soft 404 error. This drags down the quality score of your entire website.
You need to ensure your CMS templates actually have content binding them together. If a collection is not ready for the public, you need to exclude the entire template from search. Open your Pages panel, click the gear icon next to the CMS template, and check the box to exclude it from search results.
Your website is too new to rank
If you fixed all the technical settings and submitted your sitemap, you might just need to wait. New websites take time to get indexed and recognised by Google.
Google has to crawl your site, evaluate your content, and compare it to millions of other pages. This process takes days or weeks. It does not happen overnight.
If you search for your exact domain name and your site appears, your indexing is working. If you search for a broad keyword like local services and you do not appear, you do not have a technical problem. You have a ranking problem.
Ranking requires authority. You build authority through inbound links from other reputable websites. You also need relevant page titles and useful content. If you are struggling with this phase, run your site through the free website check to see what is missing.
Your content lacks depth and focus
Google ranks pages that answer the user query better than the current results. If your pages are thin, vague, or copied from another site, Google has no reason to index them. Low value content is a primary reason pages get crawled but not indexed.
Review your service pages to see if they actually explain what you do, or if they just list a few bullet points. You need to write concrete, specific details about your business. You need to balance depth and quality.
Check your title tags and meta descriptions. These sit in your Webflow page settings. Your title tag is the blue link that appears in search results. It needs to include the primary keyword you want to rank for. If your homepage title just says Home, you are wasting your most powerful ranking signal.
If you are tired of fighting with settings and just want a system that generates leads, we can help. We specialise in taking broken setups and rebuilding them as a proper mobile site that actually works. You can contact us through our pricing page to see how a clean build makes a difference.
Stop guessing with your technical settings. Fix your domains, clear your robots file, and submit your sitemap. Your Webflow website will start showing up on Google when you remove the barriers you accidentally placed in front of it.