Skip to main content
Gated Content Checker

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.

We read up to 25 public pages, try the usual members-area addresses, and report what we find. We never copy your content, only measure it.

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 Content

Middling

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 Content

Memberstack'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.”

Common Questions

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.

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.

See all free tools