How to Set Up Basic SEO Settings in Webflow

Setting up basic SEO in Webflow means configuring five built-in settings: meta title and description, image alt text, the XML sitemap, 301 redirects, and schema markup. Webflow handles all five natively, with no plugins required, though most sit behind a paid Site or Workspace plan. Doing them in order, meta fields and alt text once your content is finalised, then sitemap, redirects, and schema, covers the technical groundwork most Webflow sites are still missing. None of it guarantees a higher ranking on its own, but skipping it puts a site at a real disadvantage before it even competes.

What Do You Need Before You Start?

You'll need a paid Webflow Site plan or a paid Workspace, since the meta title and description fields, redirects, and schema markup all sit behind Webflow's free tier. Confirm your plan under Site settings before you start, so you're not halfway through a step when a field refuses to save.

• A paid Site plan or Workspace membership
• Finished page content and copy (SEO fields describe content that already exists, not a placeholder)
• Editor or Designer access to the site

That last point matters more than it looks. Meta titles and descriptions should describe what a page actually says, so writing them before the content is locked means rewriting them later anyway. Do the settings last, not first.

If you're still weighing whether Webflow's SEO tooling is worth relying on in the first place, that's covered separately in how Webflow gives Singapore businesses a real SEO advantage. This guide assumes you've already decided to build on Webflow and just want the settings done properly.

Where Each Setting Lives in Webflow

Before working through the steps, here's where each setting actually sits in the dashboard, useful to bookmark if you're doing this across several pages.

The Steps to Set Up SEO in Webflow

Step 1: Set Your Meta Title and Description

Every page's meta title and description live under Pages panel, then Page settings, then SEO settings. Keep the title under 60 characters and write the description to describe the page, not to stuff in keywords.

Here's the part most people get wrong. Google rewrites meta descriptions roughly 63 to 71 percent of the time, according to independent studies from Ahrefs and Portent. So the goal isn't crafting the perfect 155 characters Google will definitely show. The goal is writing something that matches the actual intent of the page, so when Google does rewrite it, the replacement still reflects what you meant.

I tell clients this directly: almost every title and description gets rewritten to match search intent anyway, so write for the content and the reader's intent first, not for an exact match you can't control.

You'll know it worked when the SEO settings panel shows both fields filled and the character counters sit in the green, no warning colour.

If the page is a CMS collection page rather than a static one, don't write each title and description by hand. Use Add field to pull in dynamic data straight from the collection, so every blog post or product page gets a consistent, unique pair without you touching a hundred pages one at a time.

Step 2: Add Alt Text to Every Image

Alt text lives on the image asset itself. Click any image on the canvas, open its settings, and add a plain description of what the image actually shows.

The rule I give every client is simple: describe the image, never stuff it with keywords. “Team reviewing a Webflow site layout on a laptop” is alt text. “Webflow web design agency Singapore UX UI” is not, and Google treats it as a spam signal, not SEO effort.

This is also the step clients most often skip once they start adding their own images after launch. If a client is uploading content themselves, make alt text part of their handover checklist, not an afterthought you catch in a later audit.

You'll know it worked when running Webflow's built-in SEO audit shows no missing alt text warnings.

Step 3: Turn On the XML Sitemap

Webflow generates your sitemap automatically. Go to Site settings, then the SEO tab, then toggle Auto-generate sitemap to yes, then publish.

Once it's live, it publishes at yourdomain.com/sitemap.xml, updates itself every time you publish changes, and Webflow adds it to your robots.txt file automatically. One thing worth knowing before you turn it on: once the sitemap page exists, you can't delete it, so there's no harm in enabling it early, even before the site is finished.

You'll know it worked when visiting yourdomain.com/sitemap.xml shows a list of your live pages rather than a 404.

Once it's live, submit it in Google Search Console under Sitemaps, pasting just sitemap.xml against your verified property. This doesn't speed up indexing on its own, but it gives Google a direct map of your site instead of relying purely on crawling links, which matters more on a newly launched site with few backlinks yet.

Step 4: Set Up 301 Redirects

Redirects live under Site settings, then Publishing, then 301 redirects. Enter the old path, enter where it should now point, and add the rule.

Webflow recommends keeping redirects to roughly 1,000 as best practice, since each one adds to the site's manifest file. In practice, this is one of the more foolproof parts of Webflow's dashboard. Try to redirect a URL that's still a live page, and Webflow throws an error rather than letting you create a broken rule. That's exactly why I'll often let a client handle simple redirects themselves once I've shown them the panel once. There's very little room to break it.

You'll know it worked when visiting the old URL in an incognito window lands you on the new page.

Two smaller things worth knowing. Redirects run in the order you added them, so a specific rule should sit above a broader wildcard one, not after it. And Webflow strips trailing slashes before a query string, so a path like /page/?ref=email needs the slash and question mark escaped rather than typed plainly.

Step 5: Add Schema Markup

Schema markup now has its own native field in Webflow, no custom code required. Open the page, go to Page settings, and scroll to the Schema markup section, where you can either write it manually or click Generate schema markup to have Webflow AI draft it.

I've used the AI-generated version on live projects, and it's a reasonable starting point, not a finished job. It tends to miss nuance a page actually needs, so I generate it first, then refine it by hand afterwards rather than publishing it as is.

Two mistakes to watch for here specifically. The first is generic Organisation schema copied onto every page of a site, when only the homepage or about page usually needs it. The second, and the one I check for on every audit, is duplicated pages quietly carrying over the original page's schema. Duplicate a service page to build a new one, and the schema comes along with it unless you update it manually.

Which schema type to use on which page, and the fuller case for why it's worth doing at all, is covered in how schema markup improves CTR and search visibility. Short version here: the evidence on payoff is genuinely mixed. One controlled test found a 9 percent uplift in organic traffic after adding FAQ schema, while a separate test on switching markup formats found no measurable difference at all.

You'll know it worked when Google's Rich Results Test recognises your markup without errors.

What Mistakes Should You Check For?

Four mistakes show up repeatedly on the Webflow sites I audit, and all four are quick to check once you know to look.

• Generic Organisation schema pasted onto every page instead of just the homepage or about page
• Meta titles and descriptions with no real connection to the page's actual keywords or intent
• Alt text stuffed with keyword phrases instead of describing what the image shows
• Schema left unchecked after duplicating a page, so old markup describes the wrong content

How to fix it: work through each page individually rather than assuming settings copied across correctly. Treating every duplicated page as a fresh page that needs its own settings is a habit worth building into how we approach SEO audits for clients, and it costs nothing to apply to your own site.

What Won't This Setup Do for You?

Filling in every field correctly still doesn't mean Google will automatically rank the page. These settings remove technical barriers and make a page eligible for better results, they don't replace the content, backlinks, and relevance that actually decide where a page lands.

Think of this guide as clearing the path, not winning the race. A page with strong content with non-optimal SEO settings will usually still outrank a page with perfect settings and thin content.

This is worth saying plainly to a client before they see the invoice for a settings clean-up and expect a ranking jump the following week. Set expectations first, then do the work, and nobody feels misled by a genuinely useful technical fix.

Frequently Asked Questions

Which of these settings are free, and which need a paid plan?

The XML sitemap and image alt text work on Webflow's free plan. It's the meta title and description fields, 301 redirects, and schema markup that sit behind a paid Site or Workspace plan, so a brand-new free-tier site can still handle two of the five before upgrading.

Does Webflow's native schema markup replace the need for custom code?

It replaces the need for most sites, but not the need for a second look. Webflow's AI-generated schema is a genuine starting point, and existing custom-code JSON-LD embeds still work. Running both at once risks duplicate structured data, so pick one approach per page rather than layering them.

Do I need any SEO plugins to do this in Webflow?

No. Everything in this guide, meta fields, alt text, the sitemap, redirects, and schema, is a native Webflow setting, not a third-party app. That's different from WordPress, where most of this needs a plugin like Yoast, so there's nothing extra to install here.

Conclusion

Work through these five settings once, page by page, and most of Webflow's technical SEO groundwork is done. The habit worth keeping afterwards is checking new and duplicated pages against the same list, since that's where settings quietly go stale.

Once your settings are in place, the next thing worth locking down is keeping the site itself healthy over time, covered in how to maintain your Webflow website.

{{build-better-experience="/directory"}}