Webflow User Accounts / Memberships

Customizing Webflow Site Search for User Accounts

Overview
Getting Started with User Accounts
000
User Accounts Current Features
001
User Accounts v. Memberstack
001
User Accounts Roadmap
002
Use Cases & Key Limitations
003
Customizing Membership UI
Building a Custom Login/Logout Button
8:50
110
Combining Log In / Sign Up into a Single Tabbed Page
8:41
111
Conditional Element Display, on Log-in State
7:34
112
Access-Group-Specific Sign-Up Forms
113
Customizing Membership Flow
Redirect Users to a Specific Page after Login
4:11
201
Redirect Users to a Specific Page after Registration
202
Log Out User
202
Getting Member Data
Getting the Logged-In User's Info
10:18
401
Getting the User's Webflow User ID
4:11
402
Customizing the Member UX
Customizing Webflow Site Search for User Accounts
601
SEO & Content Preview Approaches
602
Addendum
Other Membership Solutions
901
Memberships Loader
902
User-Specific Data
903
No items found.
Published
January 21, 2023
Updated
in lightbox

What happens with Webflow's Site search, and memberships?

UPDATE Apr-2023: "Site Search will not be able to index pages restricted with a password or to logged-in users only."
Webflow has made the decision to exclude all gated content from site search, which means site search is no longer useful with Webflow Memberships content.

Alternatives

Well, virtually none. Webflow has no server-side mechanic for installing a search solution that could index that secured content.

All external solutions are blocked from seeing that content.

Consequence;

  • No ability for your User Accounts users to use site search to navigate the content they've purchased. If it's in CMS collections, you can use a solution like Finsweet's CMS filter instead.
  • No ability for Google to SEO any aspect of your content for marketing purposes, as it's blocked at the page level.
If Webflow has fixed it, you may be able to use access-group conditional visibility to build those pages with some portion of the content secured, and some portion not secured.

Original Article Content

This is mostly obsolete based on the changed described above.

In general there are three categories of users who will be using your Webflow-Memberships-based site;

  • Public users, who are not logged in, aka "Anonymous" users.
  • Logged-in users, regardless of the access groups they have access to
  • Access-group users, who have specific access-group permissions

As of Dec-2022, there is no difference in the search results experience between what these three user groups can see. If all 3 users do the same search, they'll all get the same results, including private pages. What they won't

So far, we've used three approaches, for different clients.

Approach #1 - Show no results at all

Just disable site search.

While this isn't the ideal solution for many clients, in case where privacy needs are high, and/or most of your site is private anyway, it might be the best approach.

Unfortunately there currently is no way to restrict the site search page to logged-in users only.

Approach #2 - Show all results to everyone

This is ideal if you have a paid membership site which has a content-driven marketing strategy. Those results are part of your marketing strategy, and you want people to click them and encounter the paywall.

Users will see those results but be confronted with a log-in / sign-up screen when they try to access it.

If you want to improve that UX, you can mark gated content specially in the results.

Approach #3 - Hide member-only results for everyone

This is good if the gated content is "private" and you don't want the public to even see the page titles.

Yes, this makes search useless for logged in users but you can build other good dynamic views for them.

Approach #4 - Hide sensitive member-only results

Webflow allows you to include/exclude specific pages and collection pages from site search results.

Remember, Site search does have the ability to index and excerpt your secure pages, so there's a chance those results could be shown in search results.

If you have highly sensitive pages, that you cannot risk people seeing, simply exclude those collection pages completely.

Approach #5 - Build dynamic "smart" results

This is the hardest approach to setup, but arguably the coolest.

You can determine log-in/log-out state using Webflow's conditional visibility feature on your HTML Code Embed, or if that's problematic, use Sygnal's Current User Info library.

Then, use custom code to examine the URLs paths of the pages in your results, and show only the ones the current user should see.

Conveniently, Webflow has a very strict URL architecture;

  • Up to 100 static pages
  • Up to 20 collection-list pags, which are identifiable by /collection-slug/

Yes this means maintaining a list in code, but unless you're changing your site's security setup often, it should be relatively stable.

Google Search

Keep in mind this same problem appears with the sitemap.xml,

If you're using Webflow's automatic sitemap generation, it includes the path of every page on your site, including your private, gated pages.

This is safe. Unlike Site Search, Google cannot access the content of your pages, so page titles, text and META tags will not be exposed in Google's SERPs.

However, make sure that your URLs do not themselves contain sensitive content like email addresses or ID's.

Videos
No items found.
Table of Contents
Comments
Did we just make your life better?
Passion drives our long hours and late nights supporting the Webflow community. Click the button to show your love.