If a SaaS article is unpublished, keep its content behind access control or serve it only through an authorized preview. First open its intended URL as an ordinary visitor: if you can read the draft without signing in or enabling preview, so can someone with the link. Use noindex only when the page is deliberately public but should stay out of Google; it does not make the draft private.
Test the draft as someone outside your team
Use the exact intended article URL on the current deployed site, not an editor screen or local build. Open it in a fresh browser session without a login, preview cookie, or special link. Record the response and what actually renders. A 404, an access challenge, or a published page that does not contain the draft is different from a successful response showing the unpublished article. Do not assume that an unguessable slug is access control.
Then check whether the draft URL appears in your public sitemap, blog archive, navigation, related-post cards, or other published pages. Check any separate preview URL and content endpoint the page uses, too: hiding the article route is not enough if a public endpoint returns its text. A missing search result is not evidence of privacy; the visitor test answers whether the content is exposed now.
Choose privacy first—or indexing control if the page is public
Make the choice based on whether people outside the review team may read the article. Google distinguishes password protection, which limits access to authorized users, from noindex, which leaves a page accessible to visitors. If the text is confidential, fix public access rather than relying on a search directive.
| Approach | Can an ordinary visitor read the draft? | When to use it |
|---|---|---|
| Restricted access or authorized preview | No, if every route serving the draft enforces the restriction. | Choose this for unpublished content that must stay private. |
Public page with noindex | Yes. Google’s removal guidance says the directive does not restrict users. | Use only when public access is acceptable but Google indexing is not. |
robots.txt disallow alone | Yes; it controls crawler access, not visitor access. | Not a draft-hiding method: Google warns that a blocked URL can still appear in search. |
If the draft must be public, check the actual indexing directive
For a public review page, place noindex in its HTML robots meta tag or its X-Robots-Tag response header. Inspect the response or rendered HTML for the exact URL rather than assuming a site setting applied. Google must be able to crawl the page to see that directive, so do not combine this approach with a robots.txt block on the same URL. Remove the directive when the article is intentionally released for indexing, and check the deployed page again.
This is a visibility decision, not a safe way to circulate sensitive copy. If someone shares the public URL, anyone who opens it can still read the draft. For a private editorial handoff, choose the restricted route instead.
Hand off a private preview on a Next.js App Router site
Consider a fictional article intended for https://example.com/blog/new-guide. The editor needs to see its unpublished text; an ordinary visitor must not. Next.js Draft Mode lets an editor request fresh draft content while other visitors continue to see cached or prerendered content where such a page exists. Draft Mode is a preview mechanism, not by itself a complete access policy: the site still needs to control who can enter preview and ensure ordinary requests cannot fetch the draft.
Give the developer a concrete contract: the preview entry point accepts only an authorized editor and a validated article slug, then enables Draft Mode and sends that editor to the article path. Next.js documents a Route Handler that validates a shared preview secret and slug before setting the preview cookie; its draftMode API can check whether preview is enabled and disable it afterward. The article’s data lookup must return the unpublished version only to an authorized preview request. For everyone else, this fictional site should return a 404 at https://example.com/blog/new-guide until release, rather than rendering draft text or exposing it through another endpoint. (Next.js: draftMode API)
The handoff result is two observations, not merely a working editor screen: the authorized editor sees the new guide marked as a preview, and a fresh session without preview access cannot read it. Test both against the deployed site. Do not put a reusable preview secret in a public article or share a preview entry link as though it were a harmless public URL.
If the team creates articles with Ranks, keeping Autopilot off leaves generated articles as drafts for review; Daily generation is a separate control. That supports a person making each publication decision, but the website team must still establish and test its own preview boundary. Ranks’ draft status alone does not establish what a URL on the customer’s site serves. (Ranks public product reference)
Verify the boundary before release and after access changes
Before publication, repeat the fresh-session test on the exact deployed URL and any preview or content endpoints. Confirm that authorized preview still works, ordinary access does not reveal the text, and public navigation and sitemap entries do not point to the draft. If a preview session is disabled or its access is removed, test again in that browser and in a fresh session; the old preview should no longer reveal unpublished content.
If the draft already appeared in Google, first remove the exposure or put the appropriate lasting restriction in place. Google says its Removals tool can hide a result quickly, but the request lasts about six months; removing content, restricting access, or applying a crawlable noindex where public access is acceptable addresses the longer-term state. Check every URL variant that serves the same copy. After intentional publication, test the public article URL without preview access and confirm it serves the approved text; if that published URL returns 404, use the Next.js post 404 guide rather than reopening draft access as a workaround.
Sources
- Ranks public product referenceranks.so
- Next.js: How to preview content with Draft Modenextjs.org
- Next.js: draftMode APInextjs.org
- Google Search Central: Block search indexing with noindexdevelopers.google.com
- Google Search Central: Introduction to robots.txtdevelopers.google.com
- Google Search Central: Remove your site information from Googledevelopers.google.com



