The symptoms arrive in a few familiar forms. Organic enquiries have tailed off since the new site launched. A service page that used to sit on page one has disappeared. Or the site has been live for six months and Search Console shows a few hundred impressions a month, most of them for your own business name.
The temptation is to start rewriting content or to blame the platform. Before doing either, check the setup. A handful of configuration mistakes can stop a well-built Webflow site from ranking at all, and each of them can be confirmed or ruled out in under an hour. Below are the five we check first when a Webflow site's search performance has stalled or dropped, in the order we check them, with how to confirm each one and how to fix it.
Open Search Console before anything else
Every check below starts in Google Search Console, the free tool that shows how Google sees your site. If nobody connected it at launch, verify the domain now and give it a few days to collect data. Three reports do most of the diagnostic work. The Pages report (under Indexing) lists which URLs are indexed and the reason each excluded URL was left out. The Performance report shows clicks and impressions by page and query, and lets you compare date ranges either side of a drop. URL Inspection tells you exactly how Google last crawled a single page, including the canonical it chose.
Write down when the problem started. A drop that lines up with a launch, a migration or a batch of CMS edits points straight at setup. A slow slide over a year points more towards content and competition.
Mistake 1: Google has been told to stay away
During a build, sites are kept out of search on purpose. If one of those settings survives launch, Google obeys it on the live domain and rankings fall away within weeks.
How to check
Visit yoursite.co.nz/robots.txt and look for a line reading Disallow: /, which blocks the whole site. In Webflow's site settings, check the indexing section, including the traffic control toggles that write robots.txt rules for search and AI crawlers. Then open the page settings for your most important pages and CMS templates and confirm the sitemap indexing toggle is on, because turning it off adds a noindex tag to that page. In Search Console, the Pages report will show "Blocked by robots.txt" or "Excluded by noindex tag" against affected URLs.
How to fix it
Remove the blocking rule or switch the setting back, publish and resubmit the sitemap in Search Console. Then request indexing for your top ten pages through URL Inspection so Google recrawls them first.
Mistake 2: Google is indexing the wrong version of the site
Every Webflow site has a staging address at yoursite.webflow.io alongside the custom domain. If the staging subdomain is open to indexing, Google can find two copies of every page and has to pick one. It also has to choose between www and non-www versions of your domain, and between URLs with and without tracking parameters.
How to check
Search Google for site:yoursite.webflow.io. Any results mean the staging copy is indexed. In URL Inspection, compare the user-declared canonical with the Google-selected canonical for a key page. If they differ, or the Pages report shows "Duplicate, Google chose different canonical than user", Google is crediting a version you did not intend. View the page source and check the canonical tag too. A global canonical URL entered with the wrong protocol or the wrong www setting points every page at an address that redirects elsewhere.
How to fix it
Turn off staging indexing in the site's SEO settings and republish. Set the global canonical tag URL to match your default domain exactly, including https and www if you use it, with no trailing slash. Make sure the non-default version of the domain redirects to the default one.
Mistake 3: URLs changed and nothing redirected them
Webflow makes it easy to edit a slug, rename a CMS collection or rebuild a page under a new address. Each of those changes leaves the old URL returning a 404 unless a permanent redirect sends visitors and Google to the new one. The old URL might have held years of rankings and inbound links, and without a redirect that value is lost.
How to check
In the Pages report, open "Not found (404)" and look for URLs that used to matter. In the Performance report, compare the three months before the drop with the three months after, sorted by page, and look for pages that lost most of their clicks. If you migrated from another platform, export the old site's top pages from Analytics and test each URL on the live domain.
How to fix it
Add a 301 redirect for every changed URL in the site's publishing settings, pointing each old address at the closest equivalent page rather than the homepage. Redirects recover most of the lost value if they go in quickly. Our guide to redesigning without losing search rankings covers the full redirect mapping process for a larger change.
Mistake 4: CMS templates are producing duplicate titles and descriptions
Your title tag and meta description are what searchers see in the results, and they decide whether a page earns the click. On Webflow CMS sites, a single template generates the title and description for every item in a collection. If the template's SEO fields were typed in as fixed text rather than bound to collection fields, every article, case study or location page shares one title. If they are bound to a field your team leaves empty, Google writes its own.
How to check
Search Google for site:yoursite.co.nz followed by a collection folder, such as /case-studies, and read the titles that come back. Repeated titles are obvious at a glance. A crawl with a tool such as Screaming Frog or Ahrefs Site Audit lists every duplicate title and description across the site.
How to fix it
Open each collection template's page settings and bind the SEO title and meta description to dedicated fields in the collection, then fill those fields for every item. Write each title for the search it targets, keep it short enough to display in full and give the description a clear reason to click.
Mistake 5: Google cannot find pages through your internal links
Internal links tell Google which pages matter and how your content connects. On Webflow sites, CMS items are often reachable only through a paginated collection list or a filter, and landing pages built for a campaign are often linked from nowhere at all. Google can find those pages through the sitemap, but a page with no internal links pointing at it carries little weight.
How to check
In the Pages report, look at "Discovered, currently not indexed" and "Crawled, currently not indexed". A long list of CMS items in either can mean Google found them and decided they were not worth indexing, which is a mix of linking and content quality. Check your most important service pages and count how many other pages link to them, and with what anchor text. Links reading "click here" or "learn more" tell Google nothing about the destination.
How to fix it
Link to each important page from the pages that relate to it, using anchor text that describes the destination. Add related articles or case studies to CMS templates so new items are linked automatically. Make sure every page you want ranked is reachable within a few clicks of the homepage through ordinary links.
What about alt text, headings and page speed?
Missing alt text, a broken heading hierarchy and slow-loading animations all hold a Webflow site back, and they deserve fixing. They don't explain a sudden drop, because they were there before the drop happened. Treat them as build quality issues rather than emergencies, and fix them as part of a planned round of improvements. We cover each of them in common Webflow SEO pitfalls, along with how to avoid them during a build.
Core Web Vitals are worth one specific check. Google replaced First Input Delay with Interaction to Next Paint in 2024, so older audit reports may be measuring a metric that no longer counts. PageSpeed Insights and the Core Web Vitals report in Search Console both use the current set.
When the setup is clean and rankings still aren't moving
If all five checks come back clean, the site is configured properly and the problem sits in what it says rather than how it is set up. Pages that don't match what buyers are searching for, thin service pages and content that answers nobody's question will hold rankings back on any platform. We've written about that side of the problem in why a website isn't ranking.
When you'd like a second pair of eyes, a website audit works through these checks and the content side together, and tells you which fixes will move rankings first. For Webflow sites we look after, SEO audits and fixes sit within our ongoing support, so problems like these are caught when they happen.
Common questions
Why has my Webflow site disappeared from Google after launch?
The most common cause is an indexing setting carried over from the build: a robots.txt rule blocking the site, a traffic control toggle switched off or a noindex on key pages. Check yoursite.co.nz/robots.txt and the Pages report in Search Console. Missing redirects from the old site's URLs are the next most likely cause, especially after a migration from another platform.
How do I check whether Webflow is blocking Google from my site?
Open your robots.txt file in a browser and look for a Disallow rule covering the whole site. Then use URL Inspection in Search Console on your homepage and a key service page. It reports whether the page is indexed, whether crawling is allowed and whether a noindex tag was found. Webflow's indexing settings live in the site's SEO settings and each page's settings.
Why is Google showing my webflow.io address in search results?
The staging subdomain is open to indexing, so Google has found a second copy of your site. Turn off staging indexing in the site's SEO settings and republish, then confirm your global canonical tag URL matches your custom domain exactly. The webflow.io results will drop out as Google recrawls, and the custom domain will be credited instead.
How long does it take to recover Webflow rankings after fixing a setup mistake?
It depends on how often Google crawls your site and how long the problem was live. Requesting indexing for key pages through Search Console speeds up the recrawl. Sites that were blocked for a short time recover faster than sites where redirects were missing for months, because in that case inbound links may have been dropped or pointed elsewhere.
Does changing a CMS slug in Webflow hurt SEO?
It does if the old URL is left without a redirect. The page loses whatever rankings and inbound links the old address held, and visitors from old links land on a 404. Add a 301 redirect from the old slug to the new one in your site settings whenever a slug changes, and avoid renaming slugs on pages that already rank well.
