Share Work Before It Is Ready to Publish

• A client may need to check a landing page's copy and layout before it goes live, or an editor may want feedback from someone who does not normally work in WordPress. Publishing early is not a good substitute for a review process, while creating an account solely for one view can add unnecessary administration. A draft-preview link offers a narrower way to share the work.
• WP PowerSuite generates a URL tied to the selected draft so the reviewer can open it directly. The content remains a draft, but the valid preview request can render it as a viewable page. This is useful when the reviewer needs to see the page rather than edit it. It does not create a client portal, track approval, or replace the team's feedback process; it provides the access needed for that conversation to happen before publication.

Keep Preview Access Separate From WordPress Accounts

Use the Preview Controls in Your Publishing Workflow

• The module adds a Public preview action to supported content lists and provides copy/open controls in the Classic editor's publishing area, alongside Block Editor support. This keeps link creation close to the item being reviewed instead of asking editors to assemble preview parameters manually. Posts and Pages are the default supported types, with settings for the existing types you want to enable.
• Authorized integrations can also obtain a link through the module's REST endpoint when the requesting user can edit the post. The permission requirement applies to generating that access link; a reviewer opening the resulting valid URL does not need the same editor capability. This distinction lets content managers remain responsible for what is shared while keeping the recipient's experience straightforward.

Understand the Validity Window and Draft-Only Scope

• The validity setting ranges from one to thirty days and defaults to three. Token validation uses a WordPress-style two-tick time window rather than a separate exact-expiry timer for every recipient. Treat the setting as the module's configurable validity policy, not a guarantee that every copied link stops at a precisely measured number of hours after it was sent.
• The content must also be a draft for this preview workflow. Pending review, private, and scheduled items are not interchangeable with drafts, and the module does not open them through the same draft-link mechanism. If an item later becomes published or private, the preview request is redirected to its real permalink; that redirect is not permission to read private content. This keeps temporary draft viewing separate from the content's later visibility rules.

Keep Preview Responses Out of Normal Public Presentation

• Preview pages receive no-cache headers and noindex/nofollow instructions through both response headers and WordPress robots handling. Comments and pings are forced closed for the preview request, so a draft review does not become a public discussion thread. For multi-page content, supported pagination retains the token rather than losing preview access when the reviewer moves to another part of the draft.
• These measures support a temporary review workflow, but noindex is not the same as recipient authentication or a guarantee that shared content remains confidential. The token-bearing URL remains the access mechanism. Failed token attempts are rate-limited per post and IP, with excessive invalid requests receiving a 429 response. That safeguard discourages repeated bad preview attempts without turning the module into a general firewall for the website.

Review Retained Drafts Without Reopening Publication