Webflow gives a site everything it needs to rank well, and a site launched without the right checks can still go live invisible to Google. The difference comes down to a list of settings and decisions that have to be made at the right point in the project, by someone who knows to check them.
This checklist is organised by when each item happens: before design starts, during the build, on launch day and in the first month afterwards. A business owner can use it to ask their agency where each item stands, or to check a site that has already launched. Several items can only be done properly at one stage. A URL map agreed after content is loaded, or alt text added to two hundred CMS items after launch, costs far more than doing the same work at the right time.
Before design starts
The decisions in this stage shape everything Google sees later. They belong in the strategy phase, alongside the customer journey and the content plan.
1. Export what the current site is earning
If you're replacing an existing site, pull the list of pages that receive organic traffic and enquiries from Google Search Console and Analytics. Those pages carry your rankings and inbound links, and the new site has to carry them across. Note the top search queries for each one so the new page can keep answering them.
- Export the top pages by clicks for the last twelve months from Search Console.
- Export the pages that generated enquiries or sales from Analytics.
- Run a crawl of the old site to capture every live URL, including ones that receive little traffic but hold inbound links.
2. Agree the URL structure and redirect map
Webflow places every CMS item at the collection slug followed by the item slug, so collection names decide your URLs. Agree what each collection is called, which static pages sit in folders and where every old URL will point on the new site. Our guide to migrating to Webflow without losing SEO covers the redirect mapping process in more detail.
- Collection slugs describe their content in words a searcher would recognise.
- Every old URL with traffic or links has a matching new URL in a redirect spreadsheet.
- Redirects point to the closest equivalent page rather than the homepage.
3. Plan the content model for search
Each CMS collection needs fields for the SEO title, meta description, social image and image alt text, as well as the content itself. Adding those fields after two hundred items have been loaded means filling them in by hand two hundred times.
During the build
These items are set up in the Designer as templates and pages are built. Each is quick to do in the moment and slow to retrofit.
4. Heading structure on every template
Webflow's visual canvas lets a designer pick a heading tag for its size. Check the structure in the Navigator panel rather than by eye.
- Exactly one H1 on each page and template, naming the page's main topic.
- H2s for the main sections and H3s for points within them, in order.
- Section titles built as real heading tags rather than text blocks styled to look like headings.
5. SEO fields bound on every CMS template
Open each collection template's page settings and bind the title tag, meta description and Open Graph image to the fields created in step 3. A template with typed-in text gives every item the same title.
- Titles around 60 characters so they display in full, written for the search each page targets.
- Descriptions that give a searcher a clear reason to click.
- Static pages have their own title and description, with no "Home" or "New Page" defaults left behind.
6. Alt text, including on CMS images
Static images take their alt text from the asset panel. CMS images need the alt text bound to a field on the template, or every featured image goes live without one. Alt text should describe what the image shows in plain words, which helps image search and anyone using a screen reader.
7. Structured data
Webflow does not generate schema markup, so JSON-LD is added as custom code in the page or template head. On CMS templates it can pull values from collection fields.
- Organisation or LocalBusiness schema on the homepage or contact page, with your name, address and phone number matching your Google Business Profile.
- Article schema on blog and resource templates, with headline, image and publish date bound to CMS fields.
- Product schema where products are sold on the site.
- Every template validated in Google's Rich Results Test or the Schema Markup Validator.
8. Performance on real devices
Webflow hosting is fast, and the build decides whether pages stay fast. Test each template in PageSpeed Insights on its mobile setting and aim for Google's "good" thresholds on Core Web Vitals: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds and Cumulative Layout Shift below 0.1.
- Images compressed, served in modern formats such as WebP and given explicit dimensions.
- Main content visible on first render, with animations triggered after it loads.
- Third-party scripts in custom code limited to the tools the business uses.
9. Navigation and internal links
Every page you want ranked should be reachable within a few clicks of the homepage through ordinary text links. Service pages should link to related case studies and articles, and CMS templates should include a related items section so new content is linked automatically. Use anchor text that describes the destination rather than "click here" or "learn more".
On launch day
Most launch-day SEO failures come from settings that were correct during the build and wrong once the site went live. Run these checks on the live domain after the final publish.
10. Indexing switched on
- yoursite.co.nz/robots.txt contains no rule blocking the whole site, and lists your sitemap.
- The traffic control settings in Webflow's SEO settings allow search crawlers.
- Sitemap indexing is on for every page and template you want in search, and off for thank-you pages, utility pages and test items.
- Staging indexing for yoursite.webflow.io is switched off.
11. One version of the domain
- The global canonical tag URL matches your default domain exactly, including https and www if you use it, with no trailing slash.
- The non-default version of the domain redirects to the default one.
- SSL is active and every page loads over HTTPS.
12. Redirects live and tested
Load the redirect spreadsheet into the site's publishing settings, then test a sample of old URLs in a browser, including the twenty pages that carried the most traffic. Each should land on its new page in a single hop.
13. Search Console and Analytics connected
- The domain is verified in Google Search Console, using the verification field in Webflow's site settings or a DNS record.
- The sitemap at yoursite.co.nz/sitemap.xml is submitted.
- Google Analytics is installed and recording visits in its real-time view.
- Form submissions and other enquiries are tracked as conversions, tested by submitting the live form.
- Your Google Business Profile links to the new site and shows current hours, phone and address.
In the first 30 days
Launch is when Google starts reassessing the site. The first month shows whether the checks above held, and problems caught in this window are cheap to fix.
14. Watch indexing in Search Console
Check the Pages report weekly. Your key pages should move into the indexed list within the first couple of weeks. Look for 404 errors on old URLs that missed the redirect map, and for pages flagged as duplicates where Google has chosen a different canonical from the one you set. If rankings drop and you can't see why, our guide to why Webflow SEO isn't working sets out the checks in order.
15. Compare performance with the old site
Compare clicks and impressions for your top pages against the same weeks before launch. Some movement in the first fortnight is normal while Google recrawls. A page that has lost most of its clicks and stays down needs its redirect, title and content checked against the old version.
16. Hand over with training
Your team needs to know where the SEO fields live, how to fill them in when they publish a new CMS item and how to add a redirect when a slug changes. Our guide to managing a Webflow site without a developer covers the day-to-day side of running the site.
The condensed checklist
For a quick review of a site that has already launched, run through this list.
- Old URLs with traffic or links all redirect to their new equivalents.
- Robots.txt, traffic control and sitemap indexing settings allow Google to crawl the pages that matter.
- Staging indexing is off and the global canonical matches the live domain.
- Unique titles and descriptions on every page, bound to fields on every CMS template.
- One H1 per page, with a logical H2 and H3 outline.
- Alt text on static and CMS images.
- Structured data validated on each template.
- Core Web Vitals in Google's "good" range on mobile.
- Key pages linked from related pages with descriptive anchor text.
- Search Console verified, sitemap submitted and conversions tracked in Analytics.
Every Webflow site we build goes through this list before launch, and the first-month checks run as part of our website support, where SEO audits and fixes continue for as long as we look after the site.
Common questions
What should I check before launching a Webflow site for SEO?
On launch day, confirm that robots.txt and Webflow's indexing settings allow search crawlers, staging indexing for the webflow.io subdomain is off, the global canonical tag matches your live domain and every old URL redirects to its new page. Then verify the domain in Search Console, submit the sitemap and confirm Analytics records a test form submission as a conversion.
How do I submit my Webflow sitemap to Google?
Webflow generates your sitemap automatically at yoursite.co.nz/sitemap.xml once auto-generation is switched on in the site's SEO settings. Verify the domain in Google Search Console, open the Sitemaps report, enter sitemap.xml and submit it. Check the report a few days later to confirm Google read it, and resubmit after any large content change or migration.
Does Webflow add canonical tags automatically?
Webflow creates a canonical tag on each page once the global canonical tag URL is set in the site's SEO settings, combining that URL with each page's slug. Static pages also have a page canonical URL field that overrides the global setting. Enter the global URL exactly as your live domain appears, with https, the correct www setting and no trailing slash.
What Core Web Vitals scores should a Webflow site aim for?
Google's "good" thresholds are a Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds and Cumulative Layout Shift below 0.1. Test each template with PageSpeed Insights on its mobile setting, and once the site has traffic, check the Core Web Vitals report in Search Console, which is based on real visits.
How do I check if my Webflow site is indexed by Google?
Open the Pages report in Google Search Console to see which URLs are indexed and why any were excluded. For a single page, paste its URL into URL Inspection, which shows whether it is indexed, when Google last crawled it and which canonical Google chose. A quick search for site:yoursite.co.nz gives a rough view without logging in.
