Is your members-only content actually hidden?
Memberstack hides content in the browser. We fetch your pages the way a logged-out visitor does, with no account and no JavaScript, and show you what comes back.
The short answer
How do you keep gated content out of the page source?
Use Hosted Content. Page gating and data-ms-content attributes hide content in the browser, so it still arrives in the page's HTML. Hosted Content is stored inside Memberstack and delivered only after access is checked, so it never appears in your page source.
Three ways to gate, three outcomes.
All three are legitimate. They just protect different amounts, and it's worth knowing which one you picked.
Weakest
Page & folder gating
Set in the dashboard under Restricted URLs. Memberstack's script redirects visitors who shouldn't be there, but the server still sends the page, so the content is in the response either way.
Dashboard → Gated ContentMiddling
Element attributes
data-ms-content hides an element after the script runs. Pair it with data-ms-bind:style so it starts hidden, or it's briefly visible to everyone and permanently visible in view-source.
data-ms-content="members"Strongest
Hosted Content
The HTML or link lives inside Memberstack and is delivered only once a member's access has been checked. It is never in your page source, so there is nothing to find.
Dashboard → Hosted ContentMemberstack's own docs put it plainly: front-end gating “isn't a fully secure solution. If Memberstack fails to load and a visitor knows the exact URL of your content, they will be able to access it.”
Questions about gating content
What this checker looks at, what it can't see from outside, and what to do with what it finds.
It fetches your pages the way a logged-out visitor would, with no account, no cookies, and crucially no JavaScript. Memberstack hides content in the browser, so anything that arrives in that raw response is content a visitor could read without logging in. The checker reports what came back and how it was gated, reading up to 25 pages found via your sitemap or homepage links, plus a handful of conventional members-area addresses that nothing links to.
Yes, for pages it finds on its own. Nothing verifies that the person running a check owns the site, so ignoring robots.txt would make this a crawler anyone could aim at anyone. The one exception is paths you type in yourself: a members area is exactly what a sensible robots.txt disallows, so honouring it there would make the tool useless for its main job. Any path your robots.txt covers is offered back as a suggestion you can confirm in a click.
No. It measures what it finds, counting the words, links, images and media inside a gated element, and reports those counts. It never returns the content itself and nothing is stored after the scan finishes. A tool that echoed the text back would be a working paywall bypass for any URL someone pasted in, which would be the opposite of the point.
Usually, yes. Page and folder gating is a redirect that happens in the browser, so the page itself looks identical whether it is gated or not. But Memberstack's script loads your page-gating settings in every visitor's browser, and the checker reads them the same way, so it can mark which pages they cover. If it can't read them, the result says so. Either way you can paste the paths you have gated, and it fetches those logged out to show what a visitor gets if the redirect never runs.
Because data-ms-content hides elements after Memberstack's script runs, which means the content was in the HTML before it ran. Memberstack documents this directly: front-end gating "isn't a fully secure solution. If Memberstack fails to load and a visitor knows the exact URL of your content, they will be able to access it." View-source, a disabled-JavaScript browser, or a plain HTTP request all bypass it.
It depends which mechanism you use. Page gating and data-ms-content are front-end authorization: excellent for shaping what members see, but the content still reaches the browser. Hosted Content is different. The HTML or link is stored inside Memberstack and delivered only after access has been checked, so it never appears in your page source at all. For anything you genuinely cannot afford to leak, that is the one to use.
It measures how much of Memberstack's own gating checklist your site follows: default-hidden elements, no public links to gated URLs, gated pages kept out of the sitemap, and a noscript fallback. It is deliberately not called a security score, because a site can follow every item and still have content in its HTML by design. If the checker found no gating at all there is no score, since there would be nothing to measure.
No. It means there was nothing to judge, which is a different thing. A members area is usually absent from the sitemap and unlinked from any public page, so a crawl can easily miss it entirely. If the result says no gating was found, add the paths you have gated and run it again so the checker looks in the right place.
Some sites, single-page apps and certain site builders among them, return a rendered page for any URL at all rather than a 404. The checker tests this by asking for an address nobody could have created. When that comes back as a page, a successful response stops meaning anything, so the checker relies only on what is actually in each response and skips guessing at members-area addresses. It is not a problem to fix; it just limits what a status code can tell you.
Yes, and it is worth knowing rather than panicking about. Most Memberstack sites gate previews, upsells and member-only sections of otherwise public pages, where a determined reader getting in costs nothing. The result matters when what is behind the gate is the product: a course, a report, a download. That is the content to move into Hosted Content.
Set the element to display:none in your styles, then add data-ms-bind:style="display:block" alongside data-ms-content. Memberstack sets it back to visible once it has confirmed access, so the content is never briefly on screen for a visitor who should not see it. It does remain in the page source. That step closes the flash, not the source.
Remove them. A sitemap is a public, machine-readable list of your URLs, so gated pages in it both invite indexing and hand anyone curious a map of what sits behind the gate. In Webflow this is the per-page SEO setting; on a custom sitemap, exclude the gated paths when you generate it.
Nothing is gated at all. Memberstack's script never runs, so no elements are hidden and no redirect fires. Memberstack's checklist recommends a noscript meta-refresh in your site header, which sends those visitors somewhere harmless before they can read anything.
Lock down what actually matters.
Most gated content doesn't need to be airtight. A preview that leaks is a marketing problem, not a breach. For the things that do, Hosted Content keeps them out of the page entirely.
Keep reading
More free tools.
No signup, no catch. Each one answers a question builders keep asking about their membership.
Membership X-ray
How is that membership site actually built?
Paste any membership or paywalled site. We read the page a logged-out visitor gets and show the membership platform, payments, login flow, pricing tiers and gated content behind it, plus how you'd rebuild it on Memberstack.
- Free
- No signup
- Any site
Membership Tool Detector
Which membership tool does that site use?
Paste a URL and we read the page's HTML for the traces membership and login tools leave behind. See which tool it runs, how sure we are, and the exact snippet that gave it away.
- Free
- No signup
- Reads one page
Sitemap Leak Checker
Can search engines find your members-only pages?
Your sitemap and robots.txt tell Google where to look. We check which members-only pages they list, which ones only robots.txt is hiding, and which have no noindex.
- Free
- No signup
- Checks up to 25 pages