Webflow SEO services

This is search work for a site built and hosted on Webflow. It is sold two ways.

An audit is a one-time job. We look at what a search engine meets when it comes to your site, write down what is in its way, fix what Webflow's settings let us fix, and test each fix again. A plan is hours each month, spent on a written list you have agreed to, with a report of what was done.

Either way you buy the work. Google's own page on hiring this kind of help says: "No one can guarantee a #1 ranking on Google." We do not promise one.

Webflow's help documents a setting for most of what an audit checks: the robots.txt rules, the sitemap, canonical tags, redirects, a switch that takes one page out of search, and code in the head of a page. So most findings on a Webflow site can be acted on. The ones that cannot are listed further down, each from Webflow's own help.

What Webflow does by itself

You are not sold any of this, because Webflow already does it.

• The certificate. Webflow's hosting includes SSL. Its help says a certificate renews automatically as long as the domain's DNS records point to Webflow and the site loads on its servers.
• The server. Webflow's help calls its hosting "a completely managed solution" and lists what you are spared: "scalability, site downtime, or applying security patches". That is why no upkeep is sold on this page.
• The sitemap, once it is switched on. With "Auto-generate sitemap" set to "Yes" under Site settings, the SEO tab, Sitemap, Webflow writes sitemap.xml and updates it each time the site is published, with the date each page was last published. It also adds the sitemap's address to robots.txt.
• One address for the site. Where more than one domain is connected, Webflow redirects the others to the one set as the default domain.
• A redirect when you rename a page. Change a page's slug with "Permanently redirect the old URL to this new one" checked, and Webflow makes the 301 redirect.
• Crawlers are let in. Webflow's help says traffic from search engine crawlers and AI bots is allowed by default.

What we look at

Each of these is a setting Webflow's help describes, so each can be read and, where it is wrong, changed.

• Where the site is published. To your own domain, or only to its webflow.io address, and which domain is the default. Webflow calls the webflow.io address the staging subdomain, and a setting named "Staging indexing" decides whether search engines are asked to ignore it.
• What robots.txt says. The rules live under Site settings, SEO, Indexing. The "Traffic control" toggles there write rules for a group of search engine crawlers or AI bots at once.
• Pages that ask to be left out. The "Sitemap indexing" toggle in a static page's SEO settings adds a noindex tag to that page and takes it out of the sitemap. An item in a CMS Collection has a toggle of its own under "Item details". A noindex can also sit in custom code.
• The address each page asks to be listed under. The "Global canonical tag URL" for the site, and the "Page canonical URL" on a static page.
• The sitemap. Whether it is the one Webflow generates or one that was pasted in by hand, and whether what it lists is what the site now has.
• Redirects. The list under Site settings, Publishing, 301 redirects, including the wildcard rules, and the order they run in. Webflow tries older rules first, so a broad rule added early can catch an address before a specific one does.
• What your pages say about themselves. The title tag and meta description of each page, the pattern a Collection template builds them from, alt text on images, and the "Schema markup" field.
• What the reports say. The page indexing and sitemap reports in Search Console, and Bing Webmaster Tools where it is set up.

Three of these you can check yourself, for free, whatever the site is built on: whether a page can be indexed, what your sitemap holds and what your robots.txt allows. If the site is missing from Google altogether, start with Webflow site not showing up on Google.

What Webflow does not let you change

The list is short. Each line is from Webflow's help center, read in October 2026.

• The sitemap's address, once it exists. "It isn't possible to delete the /sitemap.xml page once you've created your sitemap and published your site." You choose between the generated file and one you paste in. You do not choose where it lives.
• Whether there is a robots.txt. "Once the robots.txt has been created, it can't be completely removed." Its rules can be replaced with ones that allow everything.
• What robots.txt covers. Files you upload are served from Webflow's own network of servers and not from your domain, so Webflow says it is not possible to use robots.txt to keep those files from being indexed.
• The certificate. "You cannot disable SSL on Webflow-hosted sites."
• One title or description for the whole site. "You can't set SEO settings globally." Each page carries its own, and a Collection template sets a pattern for its items. Webflow's help also says it does not support SEO meta keywords, because most major search engines do not use them.
• Some addresses. The password page, the 404 page and the search results page have slugs that cannot be edited. A slug takes lowercase Latin letters and numbers. Other characters are converted or removed. On a site with Ecommerce, /product and /category are reserved.
• Where code can run. The custom code sections take HTML, CSS and JavaScript, up to 50,000 characters each. Webflow's help says you cannot integrate a server-side language in any of them, and that its support team does not help with custom code.
• The per-page switch without Webflow's own sitemap. Webflow says you can only disable indexing with the "Sitemap indexing" toggle if the auto-generated sitemap is enabled. With a sitemap pasted in by hand, a page is taken out of search another way, such as a tag in custom code.
• Some fields in structured data. Reference, Multi-reference and Multi-image Collection fields are not supported in the "Schema markup" field.

When an audit finds something that falls on this list, the report says so in those words: a finding you cannot act on from inside Webflow. It then says what, if anything, can be done beside it. We do not sell a fix for it.

Some settings are there but belong to a paid plan. Webflow's help says a site needs a paid Site plan, or a place in a Workspace on a paid plan, to add a robots.txt file, to add 301 redirects and to switch "Staging indexing" off. Publishing to your own domain needs a paid Site plan, and so does the indexing toggle on a CMS item. Where a finding depends on your plan, the report says which.

What you get

From an audit:

• A written report. Each finding says what we saw, where, and why it matters, and names the page of Google's, Bing's or Webflow's documentation it rests on. Google's advice to anyone buying this work is to ask whether the recommendations cite its official documentation as evidence. Ours do.
• The fixes, done. What Webflow's settings allow is put right as part of the job, up to the hours the price includes.
• Each fix tested again. After a change is published we ask for the page the way a crawler would and record what it answers now.
• A list of what is left. Anything that needs more time or a decision from you, and anything Webflow does not let you change, marked as that.

From a plan:

• The hours, spent on the list. In the order agreed, usually from an audit.
• A report every month. What was done, what was tested, and what Google's and Bing's own reports show, each figure with the day it was read.
• An honest end. When the list has nothing left on it that is worth your money, we say so. Plans are month to month.

The prices and the hours each includes are on this page.

How it works

What we need

• Read access to Search Console. Google's advice to site owners about an audit is to "only grant read access to Search Console". You add us as a user under Settings, Users and permissions, and you stay the owner. One thing stays yours: Google says only an owner can submit a sitemap in the Sitemaps report. Webflow already lists the sitemap in robots.txt.
• A place in your Webflow Workspace. Webflow has a guest role for this, made for agencies and freelancers. Its help says a client keeps ownership of the Workspace and invites an agency or freelancer in, with "No need to share passwords or transfer sites back and forth". You choose the roles we may hold, and on some Workspace plans whether we can publish. Webflow's help gives the Site manager role as the one that manages all site settings, which is where robots.txt, the sitemap and redirects are. Webflow's help says a guest must hold a Freelancer or Agency Workspace plan, and we hold an Agency Workspace. When the job is done you remove us with "Remove from Workspace".
• If Search Console was never set up, we walk you through it in your own Google account. Webflow has a field for Google's verification ID under Site settings, the SEO tab.

We never ask for the password to your Webflow account or your Google account.

What it does not cover

• A ranking, a position or a figure for traffic.
• Links, reviews written or rewarded, articles by volume, listings in bulk. We do not sell them. Each is against a search engine's published policy or the FTC's rule on reviews, or is something no search engine documents as working. Google's advice is blunt about the first: "You should never have to link to an SEO." WordPress SEO services gives the source for each.
• Ads. This is work on what a search engine finds without being paid.
• Design work beyond what a fix needs. If the structure of the site is the problem, the report says so, and that work is quoted on its own.
• Upkeep. Webflow runs its own hosting, certificate and security patches. There is nothing there for us to look after, and we do not sell a plan for it.

The same audit and the same hours are sold for a site on any platform: see SEO services.