Open each important profile link in a browsing context that does not carry your owner session. Confirm the final page, access requirements, content and intended action. Test the exact shared address, including redirects and downloads. Record what you observed; a successful public page check does not by itself prove form delivery or search indexing.
Build a list from actual sharing locations
Collect the links people genuinely encounter: your email signature, social biography, proposal, event listing, portfolio cards and downloadable introduction. Copy the exact addresses rather than reconstructing what you think they should be. An old document may contain a temporary preview link while the website uses a correct public path. Testing only the newest page can miss the address most often shared.
For each link, write down the expected destination and action. A service overview, case-study PDF and enquiry form require different checks. Include the label visible to the reader. If the label says “view selected work,” a sign-in screen or general application dashboard does not fulfill it even when the server responds normally. The acceptance criterion comes from the promised experience.
Remove the owner-session advantage
Use a separate browser profile or private browsing context without the relevant account session. Verify that the test is actually signed out of the service rather than assuming a new tab removes access. Some organizational environments provide access through other mechanisms. The goal is to approximate the intended public reader, and the environment should be recorded honestly if that cannot be fully achieved.
Paste the exact shared address and follow redirects. Check the final host and page identity before interacting. A management or invitation URL may expose a different experience from the public page. If the destination unexpectedly asks for credentials, stop treating it as publicly readable and record the issue. Do not bypass access controls or publish private material simply to make the test pass.
Inspect content and actions separately
Confirm that the page contains the intended professional name, current service and expected evidence. Open important downloads and check their actual contents, not just the filename. A file may load yet contain outdated contact details, private notes or a broken internal link. Check a small-screen view when the link is likely to be shared through messaging or a QR code.
Follow the contact route far enough to understand its behavior. A form loading, a submit confirmation and a message reaching the intended recipient are separate observations. Any authorized submission test should use harmless test data and a known route. Do not claim completed delivery merely because a button responds, and do not send an unsolicited test to another person’s inbox.
Record defects in a way someone can fix
Write the original address, final destination, test date, browsing context and observed issue. Identify where the faulty link appears and who controls it. For an inaccessible example, the fix may be a permitted public replacement rather than changing the private document’s permissions. For a retired page, choose an honest replacement and update the surrounding label when the purpose changes.
Retest the exact shared link after correction, including any redirect. Keep unresolved external listings visible in the record instead of calling the whole distribution complete. W3C’s link-purpose guidance supports meaningful labels; it does not verify your destinations. Your evidence is the observed reader journey, with explicit limits around permissions, delivery and any environments that were not tested.
Fictional example: a proposal links to an owner preview
A fictional independent editor tests the profile address embedded in an older proposal. It works in her normal browser, but a separate signed-out context reaches the website builder’s login page. Her current email signature uses a different public address, so checking only the signature would have missed the problem.
She updates the proposal template to the public profile, checks its final destination and records that already-sent copies may still contain the old link. A private project document remains private; she does not change its permissions as a shortcut. Her review establishes public access for the replacement address, while enquiry delivery and search appearance remain separate tasks. No unrelated recipient receives a test message.
A checklist for your next step
- Collect exact shared addresses.
- Define each expected destination.
- Use an independent signed-out context.
- Check downloads and redirects.
- Separate access from message delivery.
Common questions
Is a new browser tab enough to test public access?
Usually it shares the same session. Use a context without the relevant account access and verify that assumption before recording a public check.
Does a working contact form prove email receipt?
No. Loading, submission acknowledgement and actual delivery are separate stages requiring appropriate evidence and authorized test data.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.