Skip to main content
Sitemap Leak Checker

Can search engines find your members-only pages?

Your sitemap tells Google which pages matter. We check which members pages it lists, which ones only robots.txt is hiding, and which have no noindex.

The short answer

Can search engines find your members-only pages?

They can if your sitemap lists them or nothing tells search engines not to index them. A members-only page should be left out of your sitemap and carry a noindex, in a robots meta tag or an X-Robots-Tag header; a robots.txt block stops crawling, not indexing. The checker reads your sitemap and robots.txt and checks up to 25 members-only pages, logged out, for all three.

Common Questions

Questions about sitemaps and members pages

What this checker looks at, what it can't see from outside, and how to fix what it finds in Webflow.

It reads your robots.txt and your sitemap, then works out which of the listed pages are members-only. If your homepage loads Memberstack, it reads the page and folder gating rules from your Memberstack app, the same rules Memberstack's script uses in a visitor's browser. You can also type in paths or folders you've gated. Each members-only page is then checked three ways: is it in your sitemap, does robots.txt block Googlebot from it, and does it carry a noindex in a robots meta tag or an X-Robots-Tag header. It fetches up to 25 of those pages, logged out.

Yes, for pages it finds in your sitemap. If your robots.txt asks crawlers like ours to stay out, we don't fetch those pages and say so in the report. Paths you type in yourself are fetched regardless, because a members area is exactly what robots.txt tends to disallow. The checker reads robots.txt a second time as Googlebot, to report what Google is told.

No. That's between your site and Google, and we can't see it from the outside. This checker reports what your site tells search engines: which members pages your sitemap lists, which ones robots.txt blocks, and which ones ask not to be indexed.