Source links and contact details are small parts of a release, but they can determine whether the reader can use the announcement. A polished headline cannot compensate for an outdated address or an unexplained claim. Before submitting, review the material from the perspective of someone encountering the issuer for the first time. Give that reader a clear path to the underlying information.
Match the source to the statement
Use a source that directly supports the claim beside it. An organization’s homepage may establish its identity, but it may not establish a specific qualification, event date, partnership, or award. Where possible, link to the relevant detail page rather than expecting the reader to search an entire website.
Be careful when one source repeats another. Several pages carrying the same wording do not necessarily provide several independent confirmations. Identify the original announcement or record when that is available, and describe any uncertainty rather than making the statement stronger through repetition.
Check names, dates, and destinations
Confirm the spelling of people’s names, organization names, product names, and locations. Open each destination and make sure it is the page you intend to reference. A release about a new website should point to the actual launched domain, not an earlier naming idea or a staging address.
Dates deserve the same attention. Distinguish the publication date of the release from the date of an event, the launch of a resource, or a historical milestone. If those are different, make the distinction explicit. Do not backdate a release to make an announcement appear older or more established.
Use descriptive links
A useful link label tells the reader what they will find. A brand name, website name, document title, or plain destination can work well. Repeating a search phrase across several links rarely adds clarity. Links should serve the announcement and its sources, rather than become the main reason the text exists.
PRCurrent may qualify paid or promotional links where appropriate. A publication decision is not a promise that a link will pass search-ranking credit. Submitters should judge the release by the clarity of the announcement and the usefulness of the information it provides.
Choose an appropriate public contact
The public contact should be someone authorized to receive questions about the announcement. Obtain permission before publishing a personal email address or telephone number. A media team, agency contact, or clearly identified publication route may be more appropriate than a private individual’s details.
Do not assume that every contact channel serves the same purpose. A patient portal, customer support form, media address, and general publication inquiry form may reach different teams. Name the role so readers can decide whether the route matches their question.
Keep private submission details separate
The person sending a release may not be its public spokesperson. Make that distinction clear when submitting. PRCurrent’s launch form sends the proposed copy and sender information to the configured editorial recipient for manual review; it does not automatically create a public post.
Never use a release submission to send confidential records or sensitive information that is unrelated to the public announcement. If a claim cannot be supported without sharing private material, first discuss an appropriate way to verify it with the publication.
Make corrections traceable
Keep a copy of the version you submitted and the sources you used. If a factual detail changes, a short correction request identifying the exact statement and supporting source is easier to assess than a general request to rewrite the release. Use Contact for an existing publication or review the Editorial Policy before submitting new material.