Webflow does a lot of SEO work automatically. It generates a sitemap.xml, sets canonical URLs, lets you control meta titles and descriptions per page, and renders content server-side so crawlers see real HTML. What it doesn't do is help you with the highest-leverage on-page SEO work most Webflow sites actually need: internal linking.
There's no Webflow equivalent of Link Whisper (the popular WordPress plugin), no built-in orphan-page detector, no inbound-link counter per CMS item. This guide covers the Webflow-specific internal linking checks that matter, how to run them without leaving the platform, and where dedicated tooling earns its keep on larger Webflow sites.
What Webflow handles automatically
Worth knowing what you don't need to fix:
- Sitemap.xml. Webflow generates one automatically and updates it whenever you publish. Includes static pages and Collection items by default.
- Canonical tags. Each page gets a canonical URL automatically. You can override at the page level if needed.
- Server-side rendering. Pages render real HTML, not React-injected DOM. Crawlers see the content without executing JavaScript.
- Robots.txt. Generated automatically, with options to hide specific pages or sections.
That covers the technical SEO baseline. Everything below is about the editorial layer Webflow doesn't touch.
What Webflow doesn't do (and what to do about it)
1. No internal link suggestions while you write
When you're drafting a blog post in the Webflow Designer or Editor, there's no panel saying “hey, you mentioned content marketing and you have a great page about that, want to link it?” You have to remember every relevant target page manually.
Practical fix: Maintain a one-sheet keyword map outside Webflow. One row per published page: target URL, primary topic, three or four phrases that should anchor-link to it. Before publishing any new post, scan the new post for mentions of those phrases and link them. Five minutes of discipline per post, no tooling.
2. No way to see inbound internal links per page
Webflow doesn't expose a count of how many other pages link to each page. You have no idea whether your priority pages (homepage, money pages, pillar content) actually have the inbound link distribution they deserve.
Practical fix:Site-search Webflow's editor for the slug of each priority page; the search hits show you where each link lives. Tedious past a dozen pages. This is where dedicated tooling starts to pay back.
3. No orphan-page detection
A Webflow Collection item with no inbound internal links is an orphan. It's in your sitemap so Google can discover it, but it won't rank well or get recrawled often. Webflow has no view that surfaces orphan items.
Practical fix:Export your sitemap.xml, get the URL list, then run a crawler over your live site to extract every link on every page. URLs in the sitemap but missing from the crawl's link list are orphans. Doable by hand or with an internal linking tool that crawls any stack.
4. CMS Collection links are easy to forget
When you build a blog template page in Webflow, you set up links between the post and its tags or categories. Those are usually fine. The mistakes happen on Collection-driven elements elsewhere: a “Related posts” component, a “Featured product” carousel, an author archive. Each of these can become a stale or empty Collection list if the underlying CMS data changes, breaking internal links you never noticed.
Practical fix: Periodic crawl-based audits catch these instantly because the broken or empty Collection list shows up as either a missing element or a redirect to something else.
5. Body links in Rich Text fields are uncrawled until publish
If you embed internal links inside Rich Text fields (the way most CMS blog posts are written), those links don't exist in the published HTML until the page is republished. This means you can update a target URL and forget to republish posts that linked to the old URL, ending up with internal redirects or 404s.
Practical fix:Any time you change a URL (rename a Collection item slug, change a static page path), republish the entire site. Webflow does this in seconds. It's a one-click habit, not a code change.
The 5-minute Webflow internal linking sanity check
If you're doing this manually, here's a sequence that catches the most common issues on a small to medium Webflow site:
- Open your live sitemap.xml. Copy the URL list to a sheet.
- Use Webflow's site search (the search inside the Designer, not Google) to count where each priority URL is linked from. Anything under three inbound internal links is likely under-linked.
- Visit any “Related” or Collection-driven sectionson a sample of templates. Confirm they're populating and that the links go somewhere useful.
- Click through your blog from oldest to newest. Spot-check internal links in the body. Anything that 404s or redirects is a republish problem (see fix 5 above).
- Repeat quarterly or after any URL structure change.
On a site with under 50 pages this is enough. Past that, the sheet starts to fight back.
Webflow-friendly internal linking tools
Most internal linking tools are WordPress plugins. The short list that actually works on Webflow:
- InterlinkTool. Hosted, crawls Webflow sites directly (no install), surfaces orphan Collection items, inbound and outbound link counts per URL, and broken internal links. Designed specifically for non-WordPress stacks.
- Screaming Frog SEO Spider. The veteran crawler. Works on any site including Webflow. Desktop app, 10-minute install, dated UI. Gives you the raw data and expects you to do the analysis.
- Sitebulb. Modern crawler with built-in visualizations. Strong on internal linking specifically. Cloud or desktop options.
- LinkStorm. Hosted, focused on internal linking suggestions and audits. Works on any stack.
For Webflow specifically, the criteria that matter: it has to crawl arbitrary HTML (not require a plugin install), it has to handle Webflow's CDN reliably, and it should surface orphans from Collection items, not just static pages. All four tools above handle this.
Audit your Webflow site in minutes
If you're tired of the manual sheet-and-site-search workflow, InterlinkTool crawls Webflow sites in a couple of minutes, identifies orphan Collection items, ranks pages by inbound link count, surfaces broken internal links, and prioritizes the fix list by SEO impact. No plugin, no install, no WordPress. Free to try.
Frequently asked questions
Does Webflow have a built-in internal linking tool?
No. Webflow handles the technical SEO baseline (sitemap, canonical tags, server-side rendering) but doesn't include suggestion features, inbound-link counters, or orphan-page detection. For internal linking analysis on a Webflow site you need a third-party tool or a manual workflow.
Can I use Link Whisper on Webflow?
No. Link Whisper is a WordPress plugin only and doesn't ship in a hosted form. For Webflow you need a crawler-based tool (InterlinkTool, Screaming Frog, Sitebulb) or a hosted link-suggestion tool that works via a script tag like InLinks.
How do I find orphan pages on a Webflow site?
Compare your sitemap.xml URL list against a crawl of your site. Any URL that appears in the sitemap but does not show up as an internal link target anywhere in the crawl is an orphan. Doing this manually is tedious; dedicated internal linking tools surface orphans automatically.
Does Webflow generate a sitemap automatically?
Yes. Webflow generates and updates sitemap.xml automatically whenever you publish. It includes both static pages and CMS Collection items by default. You can override specific items to be excluded from the sitemap in the Collection settings.
How many internal links should a Webflow blog post have?
There's no fixed number, but most blog posts benefit from three to seven contextual internal links to related content. That's enough to help readers and Google's crawler without diluting the link equity passed by each individual link. Avoid stuffing 20+ links into the body just to hit a count; concentrate on the most relevant targets.