---
title: "Webflow SEO: what to set up, limits and a checklist — Dardo"
description: "What Webflow does for SEO and what you configure: canonicals, redirects, staging, schema, Localize hreflang, speed by country and a 20-step checklist."
url: "https://dardo.studio/en/blog/webflow-seo/"
language: "en"
translations: {"es":"https://dardo.studio/es/blog/seo-en-webflow/","pt":"https://dardo.studio/pt/blog/seo-no-webflow/"}
updated: "2026-10-22T04:20:07.383Z"
---

[Blog](https://dardo.studio/en/blog/)

# Webflow SEO: what Webflow does out of the box, what you must set up, and a launch checklist

Webflow builds your sitemap, image variants and hreflang. You set canonicals, redirects, staging indexing, schema and CMS fields. Here's how, with 2026 data.

By [Nicolás Cerón](https://www.linkedin.com/in/nicoceron/) ·October 21, 2026

![A watchmaker's workbench at night with rows of open brass clock movements under a lamp, and a single crimson winding key fitted into the largest one.](https://dardo.studio/_astro/01M5GX8MZ257JNSXWKRJDA334X_Z1qADwf.webp)

## Key takeaways

- Webflow writes canonical tags only after you set the global canonical URL in Site settings › SEO, with the protocol, www if you use it, and no trailing slash.
- Importing a CSV of 301 redirects in Webflow replaces every existing redirect, so export first, append the new rows and import the combined file.
- Pages blocked in robots.txt or noindexed with custom code stay in Webflow's auto sitemap; only the Sitemap indexing toggle takes them out.
- Translated URL slugs need Localize Advanced (USD 29 a month per locale, billed yearly); on Essential (USD 9) a localized page keeps the primary slug under its locale folder.
- In September 2026, 71.3% of Webflow sites passed Core Web Vitals on mobile worldwide, against 52.8% of all sites, but only 43.6% for visitors in Colombia and 45.4% in Brazil.

## The short answer

Webflow does a lot of SEO plumbing for you: it writes `sitemap.xml` on every publish, makes responsive image variants, lets you bind titles, descriptions, Open Graph images and schema to CMS fields, and generates hreflang when you use Localize. What it doesn't do is decide for you. You have to set the global canonical URL, turn off indexing of the `webflow.io` staging domain, write the redirects, give every CMS template its SEO fields, and handle pagination and thin Collection pages yourself.

The checklist at the end covers 20 settings. Most take minutes; the expensive mistakes are a CSV redirect import that wipes your existing rules and a staging domain that got indexed before launch.

## What Webflow does by default, and what you set

All of this is from Webflow's help center and [pricing page](https://webflow.com/pricing), read on 21 October 2026. "Paid plan" means a paid Site plan (Basic from USD 15 a month, Premium from USD 25 a month, billed yearly) or a paid Workspace.

| Feature                 | Out of the box                                               | What you set                               | Plan                    |
| ----------------------- | ------------------------------------------------------------ | ------------------------------------------ | ----------------------- |
| XML sitemap             | Generated and updated on publish, with lastmod               | Per-page and per-item exclusion            | Item exclusion: Premium |
| Canonical tags          | None until you set one                                       | Global canonical URL, page-level overrides | All                     |
| 301 redirects           | One is created if you tick the box when changing a page slug | Rules, wildcards, CSV import               | Paid                    |
| robots.txt              | Sitemap line added automatically                             | Your rules, AI bot toggles                 | Paid                    |
| Staging domain          | yoursite.webflow.io is published                             | Turn off staging indexing                  | Paid                    |
| Titles and descriptions | None                                                         | Per page; CMS templates bind fields        | Paid                    |
| Open Graph              | None (random or no preview)                                  | Per page; CMS templates bind fields        | All                     |
| Structured data         | None                                                         | Schema markup field or custom code         | Paid                    |
| Responsive images       | srcset variants on upload                                    | Alt text, formats                          | All                     |
| hreflang                | Generated by Localize (head and sitemap)                     | Locales, translated slugs                  | Localize add-on         |

## The sitemap: automatic, with limits

Webflow's [auto-generated sitemap](https://help.webflow.com/hc/en-us/articles/33961355371667-Create-a-sitemap-in-Webflow) is rebuilt every time you publish, includes a `<lastmod>` for each URL, adds hreflang entries when Localize is on, and is listed in your robots.txt automatically. Turn it on in Site settings › SEO › Sitemap, publish, then submit `/sitemap.xml` in Search Console.

Five limits to know before you rely on it:

- **robots.txt doesn't remove a page from it.** Webflow's [indexing guide](https://help.webflow.com/hc/en-us/articles/33961368603539-Disable-search-engine-indexing) says a page you block in robots.txt, or noindex with your own custom code, stays in the sitemap. Only the **Sitemap indexing** toggle in Page settings removes it, and that toggle only exists while the auto sitemap is on.
- **CMS items go one by one.** Each item has its own Sitemap indexing switch (paid Site plans only). There's no switch for a whole Collection; a request for one has been open on Webflow's wishlist [since May 2024](https://wishlist.webflow.com/ideas/WEBFLOW-I-6584).
- **A custom sitemap loses hreflang.** If you paste your own, you add hreflang by hand.
- **You can't delete** `**/sitemap.xml**` once you've published one.
- **Size.** Google accepts at most [50,000 URLs or 50 MB per sitemap file](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap). Premium caps a site at 20,000 CMS items, so a normal site fits in one file; we couldn't find Webflow documentation on how it splits a larger Enterprise sitemap, so check yours if you're near that size.

## Canonical tags: set the global URL once

Webflow only writes canonical tags once you fill in **Site settings › SEO › Global canonical tag URL**; it then combines that base URL with each page's slug. Webflow's [canonical guide](https://help.webflow.com/hc/en-us/articles/33961263684115-Set-canonical-tags-to-improve-SEO) has three rules that matter:

1. Include the protocol and, if your default domain uses it, `www` (`https://www.example.com`).
2. Leave off the trailing slash, or every canonical gets a double slash (`//contact`).
3. Don't also inject a canonical through Google Tag Manager or custom code. Two canonical tags send conflicting signals, and Google says not to [specify different canonical URLs for the same page](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls).

Leaving it empty isn't fatal: Google says a site "will likely do just fine" without a declared canonical, because it then picks the best URL itself. Webflow's own blog served no canonical tag when we checked on 21 October 2026. But set it if your site answers on more than one hostname, uses URL parameters, or runs behind a reverse proxy.

You can override the canonical on a **static page** in its SEO settings, which is how you point a campaign duplicate at the main page. The docs don't describe a per-item canonical for CMS pages.

One side effect: because the canonical is the base URL plus the slug, query strings are dropped. That's what you want for `?utm_source=` links, and a problem for pagination (see the common problems below).

## Redirects: rules, wildcards and the CSV that replaces everything

[301 redirects](https://help.webflow.com/hc/en-us/articles/33961294898835-How-do-I-set-up-redirects-in-Webflow) need a paid Site plan or Workspace and live in Site settings › Publishing › 301 redirects. How they behave:

- **Capture groups.** `/news/(.*)` → `/blog/%1` moves a whole folder in one rule; `/blogs/(.*)/(.*)` → `/articles/%1/%2` handles two levels.
- **Escaping.** In the old path, put `%` before these characters: `% - & * ( ) = _ + ?`; the new path needs no escaping. The docs list the hyphen too, yet their own simple example `/old-url` isn't escaped, so test one rule on a hyphenated path before you import hundreds.
- **Query strings.** Webflow strips a slash before `?`, so the old path is `/slug%?param%=value`, not `/slug/%?…`.
- **Order.** Oldest rules run first, so add specific rules before broad wildcards.
- **Volume.** There's no hard cap, but Webflow recommends at most 1,000 rules and wildcards wherever possible.
- **Locales.** Rules don't apply to localized paths: `/old-url` and `/es/old-url` need two rules.
- **Live pages win.** A redirect from a path that still has a published page or CMS item won't fire; draft, archive or rename it first. Tick "Permanently redirect the old URL" when you change a static page's slug and Webflow writes the rule for you.
- **Trailing slashes.** Webflow URLs have none, and on the Webflow-built sites we checked on 21 October 2026, `/blog/` answered with a 301 to `/blog`. An old WordPress-style `/about/` with an unchanged slug therefore resolves without a rule of its own, through one extra hop.

The trap is the [CSV import](https://help.webflow.com/hc/en-us/articles/33961211526291-Import-export-301-redirects): **a new import overwrites every existing redirect**. The file has two columns (old path, new path), a 16 MB maximum, and one invalid row makes the whole import fail. Always export first, append your new rows, and import the combined file:

```txt
/news/(.*),/blog/%1
/services/webdesign,/services/websites
/pricing%?plan%=pro,/pricing
```

Our [redirect map generator](https://dardo.studio/en/tools/redirect-map-generator/) reads two sitemaps and drafts the old-to-new map; the [migration SEO checklist](https://dardo.studio/en/blog/website-migration-seo-checklist/) covers what to test after you switch.

## robots.txt, noindex and the staging domain

You write [robots.txt rules](https://help.webflow.com/hc/en-us/articles/41954080897683-Set-robots-txt-rules) in Site settings › SEO › Indexing. Once a robots.txt exists you can't delete it, only replace it (`User-agent: *` with an empty `Disallow:` allows everything). The same panel has traffic-control toggles that write rules for groups of search and AI bots, and a field for a Content-Signal header (`ai-train=no, search=yes`), which Webflow notes is a proposal, not a standard. Blocking AI bots saves bandwidth but can cost you visibility in AI answers; our guide to [blocking AI crawlers](https://dardo.studio/en/blog/block-ai-crawlers-robots-txt/) weighs each one.

To keep a page out of Google, use the Sitemap indexing toggle, which adds `<meta content="noindex" name="robots">`. Don't use robots.txt: Google says a blocked URL [can still appear in results](https://developers.google.com/search/docs/crawling-indexing/robots/intro), just without a description, because it can't read the noindex.

The **staging domain** (`yoursite.webflow.io`) is a full copy of your site. To stop it being indexed, set Staging indexing to off in the same panel; this needs a paid plan, and it works by serving a `Disallow: /` robots.txt on the subdomain only ([staging docs](https://help.webflow.com/hc/en-us/articles/33961419650067-Webflow-staging-subdomain)). Do it before you share the link with anyone, because if Google already indexed the staging pages, a Disallow stops it from recrawling them, not from listing them. In that case, set the global canonical to your production domain, verify the staging subdomain in Search Console and use the [Removals tool](https://support.google.com/webmasters/answer/9689846).

Webflow also hosts an [llms.txt file](https://help.webflow.com/hc/en-us/articles/43240104183315-Upload-an-llms-txt-file-to-your-site) (UTF-8, under 100 KB) on your custom domain, never on staging. What it does and doesn't do is in our [llms.txt guide](https://dardo.studio/en/blog/llms-txt/).

## Titles, descriptions, Open Graph and CMS templates

Webflow has **no site-wide default title or description**: each page gets its own in Page settings › SEO settings ([Webflow docs](https://help.webflow.com/hc/en-us/articles/33961237278611-Add-SEO-title-and-meta-description)). A page you forget ships without a meta description, so check every static page before launch.

On a Collection template, click **Add field** to build a pattern such as `{{Name}} | Blog`. [Open Graph](https://help.webflow.com/hc/en-us/articles/33961370297107-Control-the-look-of-social-shares-with-Open-Graph) works the same way, and the OG image must come from an Image field. Two details from the docs: every Open Graph image in a Collection must share the same dimensions, and the asset picker only offers JPG and PNG (paste a URL for WebP; AVIF isn't widely supported for previews).

What we set on every Collection that becomes pages:

| Field            | Type                               | Bound to                         |
| ---------------- | ---------------------------------- | -------------------------------- |
| SEO title        | Plain text, under 60 characters    | Title tag                        |
| Meta description | Plain text, 110–160 characters     | Meta description, OG description |
| Social image     | Image, 1200 × 630                  | Open Graph image                 |
| Image alt text   | Plain text                         | Alt of the main image            |
| Indexing         | The item's Sitemap indexing switch | Sitemap and noindex              |

Webflow AI can draft titles, descriptions, alt text and schema, but only in the primary locale; secondary locales are written by hand.

## Structured data

Each page, including Collection templates, has a **Schema markup** field in Page settings (paid plans), which Webflow AI can fill or you can write by hand ([schema docs](https://help.webflow.com/hc/en-us/articles/45766917223955-Add-schema-markup-in-Webflow-to-improve-SEO-and-AEO)). It goes in the `<head>`; code in the "before `</body>`" box lands at the end of the page. Use one place, not both, or you'll duplicate the markup.

The limit that bites: you can bind Plain text, Image, Link, Date/Time, Number, Option and a few other field types, but **not Reference, Multi-reference or Multi-image fields**, and Rich text isn't on the supported list. An article's author usually lives in a referenced Authors Collection, so add a plain-text "Author name" field to the post (or render the JSON-LD from a Code Embed with dynamic data). A minimal BlogPosting template, with each `{…}` replaced by a bound field:

```json
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "{Name}",
  "description": "{Meta description}",
  "image": "{Social image}",
  "datePublished": "{Published date}",
  "author": { "@type": "Person", "name": "{Author name}" }
}
```

Check it with Google's Rich Results Test after publishing. Valid markup makes a page eligible for rich results; it doesn't guarantee them.

## Images: alt text and responsive variants

Set alt text on the asset in the Assets panel and every use inherits it; override per instance, or bind a plain-text CMS field for Collection images ([alt text docs](https://help.webflow.com/hc/en-us/articles/33961330170643-Include-alt-text-on-images)). Mark purely decorative images as Decorative.

Webflow's [responsive images](https://help.webflow.com/hc/en-us/articles/33961378697107-Responsive-images) add `srcset` and `sizes` automatically, up to seven variants (500 to 3,200 px) for an upload wider than 3,200 px. Three cases get no variants: images in **rich text** elements, **background images**, and images that arrive by **CSV import or the API**. That last one catches almost every migration, since that's how bulk blog content usually gets in. Resize and compress those before import, or re-upload the heavy ones. Image uploads are capped at 4 MB, and the built-in tool converts JPG and PNG to WebP or AVIF in bulk.

## Localization: what Localize generates and what it costs

With [Localize](https://help.webflow.com/hc/en-us/articles/33961235675155-Localized-SEO-and-locale-routing), Webflow sets the `lang` attribute per locale, puts hreflang links in each page's `<head>` and in the auto sitemap, and serves each locale from a subdirectory (`/es/`). In the Localize panel's SEO settings you can turn the generated hreflang off or give it a custom base URL, which you need behind a reverse proxy.

Prices and the SEO features that differ, from the [pricing page](https://webflow.com/pricing) on 21 October 2026 (per locale, per month):

|                                            | Localize Essential   | Localize Advanced    |
| ------------------------------------------ | -------------------- | -------------------- |
| Price (billed yearly)                      | USD 9                | USD 29               |
| Price (billed monthly)                     | USD 12               | USD 35               |
| Locales                                    | Up to 3              | Up to 10             |
| AI translation                             | 10,000 words a month | 50,000 words a month |
| Localized SEO, hreflang, localized sitemap | Yes                  | Yes                  |
| Translated URLs (slugs)                    | No                   | Yes                  |
| Automatic visitor routing                  | No                   | Yes                  |

Four things the docs say that affect rankings:

- **Untranslated means duplicated.** A secondary locale inherits everything from the primary one; Webflow's [overview](https://help.webflow.com/hc/en-us/articles/33961240752147-Webflow-Localize-overview) says a locale you never customize serves identical content. Publish a locale only when it's translated, and keep it unpublished until then.
- **Slugs stay English on Essential.** Translated page slugs and Collection URLs (`/es/empleos` instead of `/es/careers`) are Advanced or Enterprise features ([Collection localization](https://help.webflow.com/hc/en-us/articles/33961252209171-Localize-Collection-content)).
- **Routing uses 302s.** Advanced and Enterprise send visitors to the homepage in their browser's language with a 302 you can't change. Google advises [against automatic redirects by language](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), and its crawler [sends no Accept-Language header](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages), so it sees the primary locale and finds the others through hreflang.
- **Slug clashes 404.** A page, folder or Collection that shares a locale's subdirectory slug returns "404 — Page not found" ([locale settings](https://help.webflow.com/hc/en-us/articles/53682971927571-Manage-your-site-s-locales)).

For the URL and hreflang decisions that come before any platform setting, see our [multilingual SEO guide](https://dardo.studio/en/blog/multilingual-seo/).

## Speed: how Webflow sites do with real users

Core Web Vitals come from real Chrome users. The HTTP Archive's [technology report](https://cdn.httparchive.org/v1/cwv?technology=Webflow&geo=ALL&rank=ALL&start=latest), built on the Chrome UX Report, shows the share of origins passing all three metrics on mobile in **September 2026**. "Country" means where the visitors are, not where the site is hosted.

| Visitors in   | Webflow sites passing | All sites passing | Webflow origins measured |
| ------------- | --------------------- | ----------------- | ------------------------ |
| Worldwide     | 71.3%                 | 52.8%             | 59,483                   |
| United States | 80.2%                 | 63.3%             | 16,374                   |
| Canada        | 80.8%                 | 67.4%             | 3,137                    |
| Spain         | 59.7%                 | 53.1%             | 1,470                    |
| Mexico        | 50.1%                 | 40.5%             | 1,852                    |
| Brazil        | 45.4%                 | 33.7%             | 3,292                    |
| Colombia      | 43.6%                 | 32.4%             | 754                      |

Webflow beats the average web in every country, and its worldwide pass rate rose from 64.0% in September 2025. It is weakest on slower Latin American mobile connections, where Largest Contentful Paint (54.6% good in Colombia, 58.7% in Brazil) and Interaction to Next Paint (57.9% and 61.9%) fail far more often than layout shift (above 91%). The HTTP Archive's [page-weight data](https://cdn.httparchive.org/v1/page-weight?technology=Webflow,ALL&geo=ALL&rank=ALL&start=latest) puts the median Webflow home page at 3.5 MB on mobile, with 926 KB of JavaScript, against 2.6 MB and 732 KB for all sites.

What usually moves the number: oversized images that skipped responsive variants (rich text, backgrounds, imports), interactions that animate the hero, third-party embeds, and scripts in the head. Compare platforms by country in our [platform speed report](https://dardo.studio/en/tools/website-platform-speed-report/), and work through the fixes in our [Core Web Vitals playbook](https://dardo.studio/en/blog/pass-core-web-vitals/).

## The common problems, and how to fix them

### The staging domain got indexed

Search `site:yoursite.webflow.io`. If pages show up, the site was shared or linked before Staging indexing was turned off (or was on a free plan, where you can't turn it off). Turn it off, keep the global canonical on your production domain, verify the subdomain in Search Console and request removals. Expect weeks, not days.

### Every Collection lives in a folder, and every Collection makes pages

Collection pages always sit under the Collection URL (`/post/your-post`); you can nest that under a parent folder (`/resources/blog/your-post`) but not put items at the root. Pick the folder name before launch: renaming it later means a wildcard redirect (`/posts/(.*)` → `/articles/%1`). Folders and Collections can't share a slug.

Webflow also creates a template page for every Collection, so a Testimonials, FAQ or Team Collection publishes one thin page per item, all in the sitemap. Turn Sitemap indexing off on each of those items (Premium), which adds noindex and takes them out of the sitemap. A redirect won't help while the items are published, because a live page beats a redirect rule.

### Pagination parameters

A paginated Collection list links to URLs like `/blog?7b68c208_page=2`, where the hex string identifies the list, so two paginated lists on one page create two parameter families. On one Webflow-built blog we checked on 21 October 2026, page 2 declared page 1 as its canonical, which is what the global canonical produces. Google says [don't use the first page of a paginated sequence as the canonical](https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading), and a list shows at most 100 items per page ([Webflow limits](https://help.webflow.com/hc/en-us/articles/33961370432275-Dynamic-content-limits)). The practical fix is to not depend on page 2 for discovery: category pages, "related posts" lists and the sitemap should link every item.

### Orphaned CMS items

Every published item gets a URL, but nothing links to it unless a Collection list or a link field does. Items beyond a list's limit, filtered out, or only reachable from page 3 of an archive are orphans with nothing but the sitemap pointing at them. Crawl the site, compare the crawl with `sitemap.xml`, and link whatever only the sitemap knows about.

### Slugs with accents and other alphabets

Webflow allows only lowercase `a–z` and `0–9` (with hyphens between words) in [page URLs](https://help.webflow.com/hc/en-us/articles/33961362705171-Page-URLs) and converts or strips anything else, so write localized slugs yourself (`diseno-web`, not whatever the converter makes of `diseño`).

## Webflow SEO checklist

1. Global canonical URL set: protocol, `www` if used, no trailing slash.
2. No second canonical from GTM or custom code.
3. Auto sitemap on, submitted in Search Console.
4. Staging indexing off (paid plan), before the link is shared.
5. Every static page has its own title (under 60 characters) and description (110–160).
6. Every Collection template binds title, description, OG image and alt text to fields.
7. Thin Collections (testimonials, team, FAQs) excluded with Sitemap indexing off, or redirected.
8. Utility pages (404, password, search, thank-you) set to Sitemap indexing off.
9. Schema in the Schema markup field or custom code, not both; validated.
10. Author and other referenced values copied to plain-text fields for schema.
11. Images over 1 MB compressed; imported and rich-text images resized.
12. OG images 1200 × 630, JPG or PNG, same size within each Collection.
13. Redirects exported to CSV before any import.
14. Every old URL with traffic or links redirected, including localized paths.
15. Collection URLs and folders final before launch.
16. Paginated archives backed by category pages and related-post links.
17. Locales published only when translated; slugs translated (Advanced) or accepted as English.
18. robots.txt reviewed, including the AI bot toggles and their trade-off.
19. llms.txt uploaded if you want one.
20. Mobile Core Web Vitals checked in Search Console after a month of traffic.

## What to do next

Run the checklist against your live site, then look up how Webflow compares with other platforms in your visitors' country in the [platform speed report](https://dardo.studio/en/tools/website-platform-speed-report/). If renewal costs are part of the decision, our [Webflow pricing guide](https://dardo.studio/en/blog/webflow-pricing-2026/) has the 2026 numbers. If you'd rather have Dardo set this up or audit an existing Webflow site, see our [Webflow development](https://dardo.studio/en/services/webflow-development/) and [technical SEO](https://dardo.studio/en/services/seo/) services.

## Common questions

**Is Webflow good for SEO?**

Webflow gives a marketing site the controls it needs: an automatic sitemap, per-page and per-template metadata, redirects, schema and hreflang. Rankings still depend on content, links and competition. Its gaps are bulk controls, such as excluding a whole Collection from the sitemap, and translated slugs on the cheaper Localize plan.

**Does Webflow create a sitemap automatically?**

Yes. Turn on Auto-generate sitemap in Site settings › SEO and Webflow rebuilds sitemap.xml on every publish, with a lastmod date per URL and hreflang entries when Localize is on. It also lists the sitemap in robots.txt. Submit it once in Google Search Console.

**How do I stop my webflow.io staging site from being indexed?**

Set Staging indexing to off in Site settings › SEO › Indexing and publish; this needs a paid Site plan or Workspace. Webflow then serves a Disallow robots.txt on the webflow.io subdomain only. If staging pages are already in Google, keep the global canonical on your domain, verify the subdomain in Search Console and request removals.

**Can Webflow translate URL slugs?**

Yes, on Localize Advanced (USD 29 a month per locale, billed yearly) or Enterprise, which include localized URLs for pages and Collections. On Localize Essential (USD 9) a Spanish page keeps the primary slug under its locale folder, such as /es/careers.

**Does Webflow add schema markup automatically?**

No. Each page has a Schema markup field where you paste JSON-LD or let Webflow AI draft it, on paid plans. On Collection templates you can bind plain text, image, date and similar fields, but not Reference, Multi-reference or Multi-image fields.

**Why do URLs ending in \_page=2 show up in Search Console?**

They come from paginated Collection lists; the code before \_page identifies the list. With a global canonical set, those pages declare page 1 as their canonical, which Google advises against. Link every item from category pages or related lists so discovery doesn't depend on deep pagination.

## Sources & further reading

Sources behind this page, with further detail from the original publishers.

- [Webflow: Pricing](https://webflow.com/pricing) · webflow.com
- [Webflow Help: Create a sitemap in Webflow](https://help.webflow.com/hc/en-us/articles/33961355371667-Create-a-sitemap-in-Webflow) · help.webflow.com
- [Webflow Help: Disable search engine indexing](https://help.webflow.com/hc/en-us/articles/33961368603539-Disable-search-engine-indexing) · help.webflow.com
- [Webflow Wishlist: Toggle to remove Sitemap Indexing on CMS Collection pages](https://wishlist.webflow.com/ideas/WEBFLOW-I-6584) · wishlist.webflow.com
- [Google Search Central: Build and submit a sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) · developers.google.com
- [Webflow Help: Set canonical tags to improve SEO](https://help.webflow.com/hc/en-us/articles/33961263684115-Set-canonical-tags-to-improve-SEO) · help.webflow.com
- [Google Search Central: How to specify a canonical URL](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) · developers.google.com
- [Webflow Help: How do I set up redirects in Webflow?](https://help.webflow.com/hc/en-us/articles/33961294898835-How-do-I-set-up-redirects-in-Webflow) · help.webflow.com
- [Webflow Help: Import/export 301 redirects](https://help.webflow.com/hc/en-us/articles/33961211526291-Import-export-301-redirects) · help.webflow.com
- [Webflow Help: Set robots.txt rules](https://help.webflow.com/hc/en-us/articles/41954080897683-Set-robots-txt-rules) · help.webflow.com
- [Google Search Central: Introduction to robots.txt](https://developers.google.com/search/docs/crawling-indexing/robots/intro) · developers.google.com
- [Webflow Help: Webflow staging subdomain](https://help.webflow.com/hc/en-us/articles/33961419650067-Webflow-staging-subdomain) · help.webflow.com
- [Google Search Console Help: Removals tool](https://support.google.com/webmasters/answer/9689846) · support.google.com
- [Webflow Help: Upload an llms.txt file to your site](https://help.webflow.com/hc/en-us/articles/43240104183315-Upload-an-llms-txt-file-to-your-site) · help.webflow.com
- [Webflow Help: Add SEO title and meta description](https://help.webflow.com/hc/en-us/articles/33961237278611-Add-SEO-title-and-meta-description) · help.webflow.com
- [Webflow Help: Control the look of social shares with Open Graph](https://help.webflow.com/hc/en-us/articles/33961370297107-Control-the-look-of-social-shares-with-Open-Graph) · help.webflow.com
- [Webflow Help: Add schema markup in Webflow to improve SEO and AEO](https://help.webflow.com/hc/en-us/articles/45766917223955-Add-schema-markup-in-Webflow-to-improve-SEO-and-AEO) · help.webflow.com
- [Webflow Help: Include alt text on images](https://help.webflow.com/hc/en-us/articles/33961330170643-Include-alt-text-on-images) · help.webflow.com
- [Webflow Help: Responsive images](https://help.webflow.com/hc/en-us/articles/33961378697107-Responsive-images) · help.webflow.com
- [Webflow Help: Localized SEO and locale routing](https://help.webflow.com/hc/en-us/articles/33961235675155-Localized-SEO-and-locale-routing) · help.webflow.com
- [Webflow Help: Webflow Localize overview](https://help.webflow.com/hc/en-us/articles/33961240752147-Webflow-Localize-overview) · help.webflow.com
- [Webflow Help: Localize Collection content](https://help.webflow.com/hc/en-us/articles/33961252209171-Localize-Collection-content) · help.webflow.com
- [Webflow Help: Manage your site's locales](https://help.webflow.com/hc/en-us/articles/53682971927571-Manage-your-site-s-locales) · help.webflow.com
- [Google Search Central: Managing multi-regional and multilingual sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites) · developers.google.com
- [Google Search Central: How Google crawls locale-adaptive pages](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages) · developers.google.com
- [HTTP Archive: Technology report API, Core Web Vitals for Webflow (September 2026)](https://cdn.httparchive.org/v1/cwv?technology=Webflow&geo=ALL&rank=ALL&start=latest) · cdn.httparchive.org
- [HTTP Archive: Technology report API, page weight (September 2026)](https://cdn.httparchive.org/v1/page-weight?technology=Webflow,ALL&geo=ALL&rank=ALL&start=latest) · cdn.httparchive.org
- [Google Search Central: Pagination and incremental page loading](https://developers.google.com/search/docs/specialty/ecommerce/pagination-and-incremental-page-loading) · developers.google.com
- [Webflow Help: Dynamic content limits](https://help.webflow.com/hc/en-us/articles/33961370432275-Dynamic-content-limits) · help.webflow.com
- [Webflow Help: Page URLs](https://help.webflow.com/hc/en-us/articles/33961362705171-Page-URLs) · help.webflow.com

[Nicolás Cerón](https://www.linkedin.com/in/nicoceron/)

Nicolás Cerón is the founder of Dardo, a brand, web design and development studio in Bogotá, Colombia.

## Related articles

- [**Webflow pricing 2026: what changes at renewal, what you'll pay and when to leave**Webflow merged its CMS and Business plans into Premium. What your site pays at renewal, with the math, and when staying beats moving to Framer or Astro.](https://dardo.studio/en/blog/webflow-pricing-2026/)
- [**Multilingual SEO: URL structure, hreflang without errors, and when a language isn't worth publishing**One URL per language, reciprocal hreflang with x-default, no redirects between versions, only languages you can review. Codes that fail, a checker, a checklist.](https://dardo.studio/en/blog/multilingual-seo/)
- [**Website migration SEO checklist: change platforms or domains without losing rankings**Rankings rarely drop because of the new platform; they drop because URLs that earned traffic stopped answering. A checklist from URL inventory to day 90.](https://dardo.studio/en/blog/website-migration-seo-checklist/)
- [**How to improve Core Web Vitals: a field-data-first playbook for marketing sites**Find the failing metric and template in Search Console, fix LCP, INP and CLS by their cause, then confirm the result in field data about 28 days later.](https://dardo.studio/en/blog/pass-core-web-vitals/)

## Keep exploring.

- [Service · **Webflow design and development for marketing teams**](https://dardo.studio/en/services/webflow-development/)

- [Your project · **Start a conversation**](https://dardo.studio/en/contact/)