Our other projects
The brief was to keep Webflow as the marketing site while adding more control over how search engines, AI systems, and monitoring scripts understand the domain.
Webflow can publish strong pages, but technical SEO and GEO often need extra control over redirects, discovery files, headers, cache behavior, and structured route lists.
Those details matter when a site wants to be clear to both search engines and answer engines.
The proxy had to preserve the Webflow editing workflow, avoid breaking live pages, support canonical host and URL cleanup, and keep generated or private routes out of public discovery surfaces.
SoFlow implemented a Cloudflare Worker that proxies the Webflow origin, redirects alternate hosts to the canonical domain, removes tracking parameters, serves robots.txt, sitemap.xml, llms.txt, and applies route-specific cache and SEO behavior.
Visitors request the public SoFlow domain. Cloudflare routes the request through the Worker, which handles canonical redirects and discovery files before proxying normal page requests to the Webflow origin.
- Canonical host redirects and URL cleanup
- Worker-served robots.txt and sitemap.xml
- llms.txt and ai.txt guidance for AI-search systems
- Cache behavior and purge endpoint ownership
- Live verification scripts for important public routes
The proxy gives SoFlow a stronger technical foundation for Webflow SEO, AI-search readiness, and ongoing site maintenance.
- Serves robots.txt, sitemap.xml, llms.txt, and ai.txt from the Worker
- Redirects www and Webflow-origin requests to the canonical host
- Removes common tracking parameters from canonical URLs
- Excludes private generated audit result routes from public discovery
Does Webflow need a proxy for SEO?
Not always. Many Webflow sites can perform well without one. A proxy becomes useful when a site needs extra control over discovery files, canonical behavior, cache rules, generated routes, or AI-search guidance.
What is llms.txt used for?
It gives AI systems a concise map of the company, topics, services, and preferred citation pages. It does not replace strong page content, but it can clarify the site structure.
Can this be added without rebuilding a Webflow site?
Yes. The point of the proxy pattern is to preserve Webflow as the editing surface while adding a controlled technical layer at the domain edge.
This implementation proves that SoFlow can keep Webflow flexible for marketers while adding the infrastructure-level controls needed for SEO, AI search, and reliable technical monitoring.
Does Webflow need a proxy for SEO?
Not always. Many Webflow sites can perform well without one. A proxy becomes useful when a site needs extra control over discovery files, canonical behavior, cache rules, generated routes, or AI-search guidance.
What is llms.txt used for?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Before the proxy, technical discovery behavior depended more heavily on the default Webflow surface and separate manual checks.
After the proxy, SoFlow could keep Webflow as the visual CMS while adding controlled discovery files, canonical behavior, route checks, and SEO-sensitive exclusions.
Webflow page settings alone cannot own every edge concern around robots.txt, sitemap.xml, llms.txt, canonical URL normalization, cache purge behavior, and route-level verification.
A proxy lets SoFlow add those controls without rebuilding the public site.
