How to find and fix orphan pages on Webflow
Webflow orphan pages come from a different mechanism than most platforms. Webflow does not generate archives or automatic listings — a CMS item is only reachable if some Collection List somewhere renders a link to it, and Collection Lists have limits and filters. Set a list to show 6 items, and item 7 onward is orphaned the moment it is published. The page exists, it has a template, it is in the sitemap, and nothing on the site links to it.
Run the Orphan Page Checker on your site — free, no account.
How Webflow orphans pages
- Collection List limits. A list with a limit of 6 renders links to 6 items. Everything beyond that is unlinked until you add pagination or a full archive page.
- Collection List filters. Filtering by a switch field or a category means any item not matching the filter has no link anywhere.
- No archive page for a Collection. If a collection is only ever surfaced through a featured list on the homepage, most of it is orphaned by design.
- Static pages never linked. Webflow lets you create a page and publish it without adding it to navigation — campaign and legal pages routinely stay unlinked.
- Pagination not enabled. Webflow Collection Lists support pagination but it is off by default, so long collections stop at the limit.
- Items unpublished from a list but still published as pages, which happens when a switch field is toggled to hide something from a listing.
The template page trap Every Webflow Collection has a template page, so every item has a live URL whether or not anything links to it. The URL working is not evidence that the page is reachable — see what is an orphan page.
Finding them
- Crawl the published site from the homepage, following links only. The free Orphan Page Checker does this with no account.
- Fetch the Webflow-generated sitemap.xml, which lists every published item and static page.
- Diff them. Sitemap URLs the crawl never reached are your orphans.
- In the Designer, check each Collection List's limit and filter settings against the item count in the CMS. A collection with 80 items and a list limited to 9 tells you where 71 orphans came from.
Step 4 is the Webflow-specific one and usually explains most of the list in a couple of minutes. The orphans cluster by collection rather than scattering.
Fixing them
- Build a real archive page per Collection — a page whose Collection List has no limit and pagination enabled. This is the single fix that covers the most URLs.
- Enable pagination on any list that is meant to show everything. It is a checkbox in the Collection List settings and it is off by default.
- Link the archive pages from the main navigation or footer so the archive itself is reachable.
- Add related-item lists on the template page, filtered by a category reference field. This cross-links items within a collection and is the closest Webflow has to automatic internal linking.
- Link static pages from somewhere real. Publishing does not link.
- Add contextual links from rich-text content to the items it references — the links that carry actual topical meaning.
Step 4 deserves emphasis because it is cheap and it compounds: a related-items list on a template page gives every item in the collection several inbound links from topically similar pages, which is exactly the content cluster structure that internal linking is supposed to produce.
Keeping it fixed
- Treat any Collection List limit as a decision about indexability, not just layout. Every limit implies orphans unless an unlimited list exists somewhere.
- Re-crawl after publishing a batch of CMS items, since that is when a list's limit starts hiding things.
- Audit switch-field filters — a hidden-from-list toggle is easy to set and easy to forget.
- When you add a Collection, add its archive page in the same session.
Because Webflow orphans items in blocks rather than one at a time, the counts move sharply: a single limit change can orphan dozens of pages at once and a single archive page can reconnect all of them. How to fix orphan pages covers the general repair, and why internal links matter covers what those reconnected pages actually gain.
FAQ
Why are my Webflow CMS items not linked from anywhere?
Almost always a Collection List limit or filter. Webflow only renders links for the items a list actually outputs, so a list limited to 6 items leaves every other item in the collection with no inbound link, even though each has a live template URL.
Does Webflow create archive pages automatically?
No. Unlike blog platforms, Webflow does not generate category, tag or date archives. If you want every item in a Collection to be reachable, you have to build a page with an unlimited, paginated Collection List and link to it yourself.
Does enabling pagination on a Collection List fix orphans?
For that list, yes — pagination makes the remaining items reachable through crawlable page links. It is off by default in Webflow, which is why long collections silently stop at their limit.
Is a Webflow page orphaned if it is published but not in a menu?
Yes. Publishing gives a page a URL and puts it in the sitemap; it does not create any link to it. Campaign pages, landing pages and secondary legal pages commonly stay unlinked for years.
Will the Webflow sitemap stop items being orphaned?
No. The sitemap helps search engines discover a URL, but it passes no authority. An item that is in the sitemap and linked from nothing still receives nothing from the rest of the site.
What is the fastest fix for Webflow orphans?
Build one archive page per Collection with an unlimited, paginated Collection List, then link those archives from the navigation. That single change usually reconnects the majority of orphaned items, because Webflow orphans them in blocks rather than individually.
Put this into practice
Run the Orphan Page Checker to see this on your own site, or run the full structural audit for the complete picture — both free, no account required.