You finish a new page, copy the link and send it to a client. They get a sign-in screen. Or you publish it so they can see it, then discover the unfinished page is available to everyone.
Choose how the reviewer will get in before you send the link. A successful review needs the right page, the right access and a clear decision to make.
For a Scottsdale business using WordPress, this might be a partner checking an event announcement or a client approving a project description. Neither person necessarily needs an account that can edit the website.
Decide what the reviewer needs to see
Write a short brief for the review. Name the page, the person checking it and the parts that need approval. Separate factual corrections from design feedback so the response is easier to act on.
Imagine a Scottsdale studio preparing a joint workshop announcement. The guest instructor needs to confirm their biography, the session description and the date. They do not need to manage plugins or change the studio's other pages.
Choose the sharing method around that task. A simple draft review, an ongoing staff-only page and a confidential client workspace are different requirements. Ask your maintainer which arrangement the site actually supports.
- Page
- Which version should this person read?
- Decision
- Which facts or sections need their approval?
- Access
- How will they open it, and when does that route close?
- Response
- Where should they send corrections?
Keep material that needs stronger protection out of an ordinary preview until the access plan is verified. A password box on one page is not evidence that every image, download or connected tool has the same restriction.
Our website-editing guide covers routine staff updates. This guide focuses on the person outside that editing workflow who needs to review a page.
Separate page status from the sharing method
WordPress lists Draft, Pending, Private, Scheduled and Published among its page and post states. Pending marks content for review; it does not describe a complete client-sharing process. Read the page and post settings guide (new tab).
Keep the page in the state your publishing process requires. Do not turn an unfinished draft into a public page just to make a link open for someone else.
WordPress's visibility guidance distinguishes a password-protected page from private content that requires an appropriately authorized signed-in account. It also notes that a protected page's title remains visible with the password prompt. Review WordPress content visibility (new tab).
Ask who should be able to read the page and who should be able to change it. A recipient needing a quick read-through should not receive broad editing access as a convenience.
If someone does need a website account, use the editor-access checklist to agree on their tasks and test their permissions. For a one-time review, first consider whether the existing preview workflow can do the job.
Use a review link with a deliberate lifetime
Have the maintainer demonstrate the sharing option on your actual site. Copy the link intended for the reviewer, not merely the address currently open in the administrator's browser.
One available WordPress plugin, Public Post Preview, creates a link that lets someone without an account preview an unpublished post. Its documentation describes an expiring link and an option to disable the preview. It is a separate plugin, not a setting to assume every site already has. Read the plugin's documentation (new tab).
If your maintainer chooses that approach, confirm compatibility and the installed settings before using it. The documented default lifetime is 48 hours, but it can be changed. Tell the reviewer when the link should stop working and whom to contact if they miss the window. Check the expiration options (new tab).
Treat a link that works without sign-in as shareable. It does not establish the identity of the person opening it. If the material requires named access, tell your maintainer that requirement before choosing the tool.
Send one current review address with the requested decision and deadline. If you replace it, make clear which link the recipient should use. Avoid leaving several messages that appear to point to equally current versions.
Check what remains visible outside the page
If you choose native password protection, inspect the surrounding output too. WordPress warns that custom-field data can still display unless the theme handles protection explicitly. Read the password-protection limitations (new tab).
That matters on custom business pages. A project heading, client detail or price may be rendered separately from the main body. Have the maintainer inspect the actual output rather than judging protection from one paragraph behind a prompt.
Review the page title, navigation, search results and article listings while signed out. Check any linked file at its own address as a separate test. If it must be restricted, verify that restriction before uploading or sharing the material.
WordPress also documents that pages sharing the same password can be unlocked together in the reader's browser. Avoid reusing one review password across unrelated clients or projects. See the shared-password behavior (new tab).
- The page bodyWhat appears before and after the reviewer gets access?
- The surrounding siteWhat do titles, lists and custom page fields reveal?
- The linked filesDoes each file have the access restriction it needs?
Keep this review proportionate to the content. A public workshop description awaiting a date correction has different requirements from private customer records. When the requirement is confidential storage, ask for an appropriate restricted workspace instead of stretching a page preview into that role.
Test from the recipient's side
Open the exact link in a fresh browser session that is signed out of WordPress. Test on a phone and a desktop. Your normal browser may already have account access or a remembered page password.
Read the page as the recipient. Confirm that the latest saved wording appears, images load and the requested facts are easy to locate. Follow important links and check that they lead where the reviewer expects.
For a password-protected route, test before entering the password, with an incorrect password and with the correct one. After disabling a preview or changing its access, test again from a fresh session.
If a Public Post Preview link shows old content, its documentation identifies caching as a possible cause. Have the maintainer inspect the actual cache rules instead of repeatedly editing text that was already saved. Read the stale-preview troubleshooting note (new tab).
Do not ask the reviewer to submit a real payment or send a live enquiry just to inspect a page. Agree on a separate controlled test if forms or transactions are part of the project.
Record the URL tested, the date and what the reviewer should see. This gives your maintainer a useful starting point if the recipient reports a different result.
Close the review before the public release
Ask for an explicit decision tied to the version reviewed. A response such as “Looks good” can be ambiguous if you changed the page after sending the link. Confirm any important correction before handing the page to the publisher.
Apply agreed edits and recheck the affected sections. If you need to recover earlier wording, our page-revision guide explains how to do that without losing newer corrections.
Disable temporary review access when the review ends. Keep the approval record in your normal project notes and decide who is responsible for the final release.
Once the page is published, open its public address while signed out. Check that the approved content is there, the intended audience can reach it and temporary review wording has been removed. For a later release, follow the scheduled-announcement checks.
Your Scottsdale business website should make review and publication manageable without confusing the two. Our content management service can help set up the workflow. Talk to Brandon about sharing pages for review.
