How to Set Up a Webflow Docs Site at /docs on Your Custom Domain

Webflow has become a strong option for documentation and knowledge base sites. The editor is clean, CMS collections are flexible, and the reading experience can be dialed in without custom code.

The problem: Webflow's native custom domain setup gives you docs.yourcompany.com — a subdomain. For SEO and domain cohesion, yourcompany.com/docs is meaningfully better. Webflow doesn't support subfolder routing natively, so you need a routing layer in front.

This guide covers the complete setup — including canonical URL configuration, link rewriting for docs sites, and the search indexing considerations that matter for technical SEO.

Why /docs instead of docs.yourcompany.com

Documentation pages accumulate a specific kind of high-quality backlinks: developer blogs, Stack Overflow answers, GitHub READMEs, and technical tutorials all link to specific documentation pages when referencing an API or feature.

These are among the most valuable backlinks a developer tool can earn — they come from trusted, authoritative sources, and they're contextually relevant. If those links go to docs.yourcompany.com, their PageRank benefits the subdomain. If they go to yourcompany.com/docs, they directly strengthen your main domain's authority.

For developer tools specifically, documentation is often the highest-trafficked section of the site. Getting that traffic — and those backlinks — on the main domain is the single highest-ROI SEO change most developer tools can make.

Webflow hosting options

Webflow sites can be published in two common ways:

For the purposes of this guide: your Webflow site is published and accessible at youraccount.webflow.io. Furl will route yourcompany.com/docs to that origin.

If you've already set up Webflow's native custom domain (pointing to docs.yourcompany.com), you have two options: either route through Furl from yourcompany.com/docs → docs.yourcompany.com (two-hop), or point Furl directly to the youraccount.webflow.io origin (recommended — cleaner).

Step 1: Publish your Webflow site

In Webflow, make sure your site is publicly published:

1. Open your site in Webflow Designer
2. Click Publish
3. Select your staging domain
4. Publish the site

Test it: open youraccount.webflow.io in a browser. Your docs should load.

Step 2: DNS records

In your DNS provider, add:

Type    Name    Value                  TTL
CNAME/ALIAS @    proxy.usefurl.com     Auto
CNAME   www     proxy.usefurl.com      Auto

If using Cloudflare: set the CNAME to DNS-only (grey cloud). Orange proxy cloud will interfere with Furl's SSL certificate provisioning.

Step 3: Add domain to Furl and verify

In your Furl dashboard:

1. Sites → New Site → enter yourcompany.com
2. Wait for DNS propagation (2–10 min on Cloudflare, up to 60 min elsewhere)
3. Furl shows green Verified status
4. SSL provisions automatically within 3–5 minutes

Step 4: Create the /docs route

New route in Furl:

• Path: /docs
• Destination: youraccount.webflow.io
• Platform: Webflow (enables Webflow-specific rewriting)
• Link rewriting: Enabled

Save. Open https://yourcompany.com/docs in an incognito window — your Webflow docs should load.

Step 5: Configure Webflow's custom domain (optional)

This step is optional but helpful for canonical correctness. Webflow lets you set a custom domain for the site, which influences canonical tags and internal link generation.

In Webflow: Site Settings → Publishing → Custom Domains

If you already control docs.yourcompany.com, you can add it here. You do not need to point DNS at Webflow — Furl still owns routing. This is purely for canonical/URL generation.

If you prefer to keep things simple, leave the site on youraccount.webflow.io and rely on Furl's link rewriting. That is usually sufficient.

How link rewriting works for Webflow

Webflow generates its pages as server-rendered HTML. When a user requests yourcompany.com/docs/getting-started, Furl:

1. Receives the request at the nearest edge node
2. Forwards it to youraccount.webflow.io/docs/getting-started
3. Webflow returns HTML with internal links pointing to youraccount.webflow.io
4. Furl's link rewriter replaces youraccount.webflow.io with yourcompany.com in the response body
5. Rewrites the <link rel="canonical"> tag to yourcompany.com/docs/getting-started
6. Rewrites og:url and any other absolute internal references
7. Returns the rewritten HTML to the user

What gets rewritten:

What is not rewritten (intentionally):

• Webflow's static asset CDN (images, fonts, scripts served from assets.website-files.com)
• External links in your documentation content — these are correct as-is
• Webflow's API endpoints used for search and content loading

Webflow's built-in search

Webflow's search is a runtime feature — it loads content from Webflow's API when a user types in the search box. After setting up Furl routing, search queries are issued to Webflow's backend and results should link to yourcompany.com/docs/... paths.

If you notice search results still linking to youraccount.webflow.io after setup, check that:

1. Your Webflow site is published and the custom domain (if used) is set correctly
2. Internal links in your Webflow content are relative or point to the production domain

Sitemap and Search Console

Webflow generates a sitemap at youraccount.webflow.io/sitemap.xml. After your custom domain is verified in Webflow, this sitemap updates to use your production domain.

Access it via Furl's routing at https://yourcompany.com/docs/sitemap.xml and submit it in Google Search Console.

In Search Console:

1. Ensure yourcompany.com is a verified property (root domain)
2. Submit https://yourcompany.com/docs/sitemap.xml under Sitemaps
3. Optionally add a URL prefix property for https://yourcompany.com/docs/ to track docs traffic separately

Technical SEO specifics for documentation sites

Documentation sites have a different SEO profile from marketing blogs:

Keyword targeting is implicit, not explicit. Docs pages rank for long-tail queries like "how to authenticate Webflow API" or "Webflow webhook setup" — queries where the user wants exactly what the documentation contains. You don't need to optimise title tags aggressively; you need the content to be accurate and well-structured.

Heading structure matters more than usual. Googlebot uses heading hierarchy to understand document structure. Webflow renders clean heading hierarchies from your Markdown/WYSIWYG content. Make sure each page has a logical H1 → H2 → H3 structure.

Duplicate content from versioning. If you maintain multiple Webflow projects for different doc versions, consider noindexing older versions or canonicalizing to the latest version to avoid duplication.

Internal linking between docs and marketing content. After consolidating docs to yourcompany.com/docs, internal links from your blog (yourcompany.com/blog) to your docs (yourcompany.com/docs/api-reference) are true internal links. These links pass PageRank between your content and your docs, strengthening both.

Verification checklist

Common issues

Internal Webflow navigation links still showing youraccount.webflow.io The most common issue. Usually means the Webflow site wasn't republished after changes, or internal links are absolute to the staging domain. Republishing and using relative links typically resolves this.

Search not working after routing Webflow's search JS makes API calls to Webflow's backend. If Furl's link rewriter is intercepting the search API responses (it shouldn't, since they are external), check your Furl rewriting configuration. API endpoints from external domains are never rewritten.

404 on some docs pages but not others Webflow uses clean URLs without trailing slashes by default. If Furl is configured to add or strip trailing slashes inconsistently, some pages will 404. Leave trailing slash handling at Furl's default (preserve as sent) for Webflow.