Webflow SEO Checklist: Meta, Redirects, Sitemap and Indexing

Webflow gives designers a lot of control over the markup of a site, and it hosts, generates a sitemap and manages redirects from the same dashboard. That makes Webflow SEO mostly a matter of working through a short list of settings, in the right order, at the right time: staging first, launch second, and the first weeks after that.

This guide is a checklist for people building or relaunching a site in Webflow, whether you are a freelancer handing over a project or an owner checking the work. It covers page titles and meta descriptions, the sitemap, 301 redirects, indexing controls for staging and live sites, canonical URLs and the pre-launch checks that Webflow's own training material recommends. Where the guide describes where a setting lives, it follows the paths used in Webflow University's launch checklists. Webflow changes its interface from time to time, so if a menu has moved, look for the same setting by name.

It does not promise rankings, and it does not replace good content. It makes sure that the technical side does not get in the way, and it points to other guides for the details of each topic.

Before you begin

You need editor or admin access to the project in Webflow, access to the site's domain settings, and a Google Search Console account for the final steps (see Set Up Google Search Console: Complete Website Owner Checklist). If you are replacing an existing site, make a list of the old URLs you want to keep: crawl the old site or export its sitemap. Settings and plan features available to you depend on your Webflow plan and workspace, so check what your account includes rather than assuming.

Decide who owns the checklist. Launch problems usually come from a step that everybody assumed somebody else did, such as turning staging indexing off or adding redirects.

Step-by-step instructions

Step 1: Keep the staging site out of search

While you build, your site lives on a Webflow staging subdomain. Webflow's launch checklist says to disable staging subdomain indexing in Site settings > SEO > Indexing, so do it at the start of a project, not on launch day, before unfinished pages can be found.

This setting is about the staging domain, so you still need the live-site checks below for your custom domain. For the wider problem of test sites in search results, read Prevent a Staging Site From Being Indexed.

What success looks like: The staging address returns a noindex instruction (view source and look for a robots meta tag, or use a header check), and your live domain does not carry the same instruction.

Step 2: Write titles and meta descriptions for every page

Webflow's training describes title tags and meta descriptions as page-level settings, found in Page settings > SEO settings. For CMS collection pages, the title and description can pull from CMS fields, so each item gets its own. The pre-launch checklist asks you to confirm that titles and descriptions are accurate, descriptive and unique, including the dynamic metadata on CMS pages.

Open a sample of each template: home, a standard page, a CMS item and a collection list. Look at the source for the <title> and meta name="description". A CMS template whose field is empty for some items may output a blank or repeated value, so check items with missing content too. Write SEO Title Tags and Meta Descriptions That Match Search Intent covers wording. Webflow also lets you set Open Graph values for how links look when shared, per page and per CMS item.

What success looks like: No template outputs an empty or duplicate title or description.

Step 3: Use the Audit panel

Webflow's built-in Audit panel flags common issues before you publish, such as missing alt text, missing meta titles and skipped heading levels. Run it on every page you are about to publish. Fix the flagged items that matter for accessibility and clarity: images that carry meaning need descriptive alt text, and decorative images can be marked as decorative. Keep one clear h1 per page and do not skip heading levels for visual styling. Use style classes for the look instead.

What success looks like: The Audit panel shows no missing meta titles or alt text on pages you intend to publish.

Step 4: Review the sitemap

Webflow creates and updates sitemap.xml automatically as you add and publish pages. The build and launch checklist places the settings in Site settings > SEO > Sitemap and asks you to confirm that the sitemap lists only the intended public URLs, then to submit it to search engines after launch. For localized sites it also asks you to review hreflang support.

Open /sitemap.xml on your published site and scan for URLs that should not be there: thank-you pages, utility pages, test pages or private landing pages. Compare it with what you want indexed. For the rules a sitemap should follow, see How to Create a Valid XML Sitemap for Your Website.

What success looks like: The sitemap loads on the live domain and contains canonical, public URLs only.

Step 5: Set up 301 redirects before launch

If you are replacing an existing site or changing URLs, plan redirects now. In Webflow's launch checklist the setting lives at Site settings > Publishing > 301 redirects. The checklist asks you to crawl the site for broken links, unexpected error responses and outdated paths, and to add 301 redirects for permanently moved URLs.

Google's documentation explains why the type matters: permanent redirects (such as 301 or 308) tell Google the target should be canonical, and temporary ones tell Google to keep the source page in results. It also says server-side redirects are the most reliably interpreted. Map each old URL to its closest equivalent, not to the home page, and test that each lands on a 200 page in one step. 301 vs 302 Redirects: Use the Right One for Each Situation and Redirect Chains, Loops, and Incorrect HTTP Status Codes go deeper.

Before a large migration, check the redirect documentation inside your Webflow account for current limits and pattern support.

What success looks like: Every old URL on your list reaches a live new page through a single 301.

Step 6: Check indexing controls and robots.txt

The pre-launch checklist asks you to check page indexing controls, robots.txt directives and staging indexing so that public pages are discoverable and excluded content is handled. Review each exclusion and ask what you actually want:

If a page should be reachable but not shown in search, the right tool is a noindex instruction. Google's documentation says a robots meta tag with noindex tells Google not to show the page in results, and that crawlers can read it only if the page is not blocked in robots.txt.
If you block a page in robots.txt, Google cannot see a noindex on it, and the URL can still appear in results if other pages link to it.
Pages excluded from the sitemap are not necessarily excluded from search. Sitemaps are suggestions, not instructions.

See Noindex vs robots.txt: Choose the Right Way to Keep a Page Out of Search for the full decision. Open /robots.txt on the live domain and make sure it does not contain a rule that blocks everything.

What success looks like: Live pages that should be indexed carry no noindex, and the robots.txt file does not block them.

Step 7: Confirm canonical URLs

The checklist asks you to confirm that canonical tags point to the intended URLs and that no page emits conflicting tags, with extra attention on domain migrations, localized content and reverse proxy setups. View the source of a page on the live domain and read its rel="canonical". It should be the exact address, with the right protocol and host, that you want in search. Check CMS items as well as static pages.

If you use both a www and non-www host, or serve the site through a proxy, make sure only one is canonical and the others redirect. Google treats canonical tags as a signal alongside redirects and sitemap inclusion, so make all three agree. See Fix Duplicate URLs and Incorrect Canonical Tags.

What success looks like: Each page's canonical points to itself on the final live domain over HTTPS.

Step 8: Launch checks and Search Console

Webflow's checklist says to confirm that the domain is connected and SSL is active before publishing, and to design and build a 404 page. After the site is live, verify ownership in Google Search Console, submit the sitemap and use URL Inspection on the home page and a deep page. Bing is covered in Set Up Bing Webmaster Tools and Verify Your Website. Crawvix's scan can serve as a cross-check on the same list: it flags a robots.txt that blocks Googlebot or Bingbot, accidental noindex on sampled pages and sitemap problems.

Watch the Page indexing report for a few weeks. Expect some lag; neither Google nor Bing publishes a schedule for new sites.

What success looks like: Search Console reads the sitemap and shows the home page as indexable.

Final verification checklist

Staging subdomain indexing is off, and the live domain is not set to noindex.
Every template outputs a unique title and meta description, including CMS items.
The Audit panel shows no missing meta titles or alt text on published pages.
/sitemap.xml loads on the live domain and lists only intended public URLs.
301 redirects exist for each moved URL and land on live pages in one step.
/robots.txt does not block the pages you want in search.
Canonical tags on key templates point to the final HTTPS address.
SSL is active and a custom 404 page exists.
Search Console is verified and the sitemap is submitted.

Common mistakes to avoid

Turning off staging indexing late. Do it at the start, so the staging site never gets listed.
Assuming a staging setting covers the live site. The live domain needs its own checks.
Leaving CMS metadata fields empty. A template without data produces blank or repeated tags.
Redirecting old pages to the home page. Send each to the closest equivalent.
Blocking a page in robots.txt and expecting noindex to work. Google cannot read the noindex on a blocked page.
Letting test or utility pages into the sitemap. Review the sitemap before you submit it.
Conflicting canonicals after a proxy or domain change. Check the rendered source on the live domain.
Skipping headings and alt text because they are "design" work. The Audit panel flags both for a reason.

Frequently asked questions

Does Webflow generate a sitemap automatically?

Webflow's training says sitemap.xml is created and updated automatically as you add and publish pages. Review it in Site settings and confirm it lists only the URLs you want indexed.

Where do I set up 301 redirects in Webflow?

Webflow's launch checklist places them in Site settings under Publishing, in the 301 redirects section. Check the in-product documentation for current limits and pattern support on your plan.

How do I stop Webflow's staging site being indexed?

Webflow's checklist says to disable indexing of the staging subdomain in Site settings under SEO, in the Indexing section. Do it early and confirm by checking the staging page source.

Can I set a different title and description for each page?

Yes. They are set per page in Page settings under SEO settings, and CMS template pages can pull them from fields so each item gets its own. Check for empty fields.

Will following this checklist improve my rankings?

It removes technical obstacles to crawling and indexing. It does not decide where pages appear. That depends on content, competition and other factors outside this checklist.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.