A first-party source page is a permanent page on your own website that holds the fullest version of an announcement: every figure, the method behind it, images, quotes and links to related pages. The press release summarises the news and points to it. It matters because a syndicated release is a short copy on someone else's site, while the source page is the version you control, can update and can link to from the rest of your site.
Why not rely on the release alone?
A newswire release has limits. Wires cap the number of links, favour a set length and format, and publish your text on pages you cannot edit afterwards. Links in syndicated copies are nofollow as standard, so they are there for readers rather than to pass ranking value.
None of that makes a release less useful as a way to reach people and put a dated record on many sites. It does mean the release should not be the only place the full information exists. When a journalist wants the method behind a figure, when a customer wants the details, or when a search engine or AI assistant looks for the most complete answer, what they need is a page on your own domain.
What goes on a source page?
Everything the release had no room for. Use this as a checklist.
- A headline that states the news, matching or close to the release headline
- A one-paragraph summary answering who, what, where and when
- Publication date, and an update date whenever you change it
- The full details: every finding, specification, location or term that the release shortened
- Method or evidence: for data, the source, sample size, period, geography, exclusions and limitations
- Tables for figures, so they can be read and compared at a glance
- Original images or charts with descriptive captions and alternative text
- The quote, with the speaker's full name and title
- Links to related pages: the product or service page, earlier reports, the About page
- A contact for questions from journalists
Here is how a fictional research page might set out its key figures:
| Metric | Result |
|---|---|
| Residential emergency visits analysed | 4,812 |
| Visits involving flexible-hose failures | 31% |
| Visits involving water heaters | 22% |
| Period covered | January to December 2025 |
| Geography | Dubai |
The post on research and data press releases goes further into what a methodology section should include.
How do you choose the URL?
Pick an address that describes the content, sits in a sensible section of your site, and will not need to change.
| Type of announcement | Example URL |
|---|---|
| Research report | example.com/research/2026-dubai-water-damage-report |
| Product launch | example.com/products/acme-leak-sensor |
| New location | example.com/locations/abu-dhabi |
| Company news | example.com/news/acme-opens-abu-dhabi-operation |
A few rules of thumb:
- Use words, not ID numbers.
- Put the year in the URL for reports that will recur, so next year's edition gets its own page.
- Do not put a date in the URL for pages you will keep updating, such as a product or location page.
- Once published, do not move it. If you must, redirect the old address permanently to the new one, so links in releases already out keep working.
How does the release link to it?
The release should link to the source page once, with anchor text that says what the reader will find, such as "the full Dubai Residential Water Damage Report 2026" rather than "click here". On wires that limit links, a sensible set is the company name linked to your home page on first mention, and one link to the source page. The post on links in a press release covers this in detail.
Why does it matter for search and AI?
A source page gives search engines and AI assistants a complete, first-party answer to retrieve. Google says a page must be indexed and eligible to show in Search with a snippet to appear as a supporting link in AI Overviews and AI Mode, and that no special AI markup or file is required. The same basic conditions, being crawlable and indexed, apply to the other systems described in how AI assistants find and cite companies.
Original information is what makes the page worth citing. An assistant has little reason to cite a page that repeats what dozens of others already say. It has more reason to cite the page where a figure was first published, with its method alongside it. None of this guarantees a ranking or a citation; it makes your page a stronger candidate.
How do you make sure it can be found?
A source page that nothing links to is hard to find. Before the release goes out:
- Check the page loads normally and returns a successful response.
- Check it is not set to noindex and that robots.txt does not block it. See whether your site is readable by AI for the full checklist.
- Check the canonical tag points to the page itself.
- Add it to your XML sitemap.
- Link to it from your newsroom, the relevant product or service page and your About page where it fits.
Then keep it current. If a figure is corrected, a product is discontinued or a newer report replaces it, update the page, change the update date and link to the newer version.
Frequently asked questions
Can the source page be my existing product page?
Yes, for a product launch it often should be. Add the launch details, date and specifications to the product page rather than creating a separate page that competes with it. Use a separate news page when the announcement is an event rather than a lasting offering.
Should the source page copy the release word for word?
No. It should contain more than the release: the full data, method, images and context. Reusing the headline and opening facts is fine; the rest should add what the release left out.
What if I do not have a newsroom section?
Create a simple one: a page listing your announcements by date, each linking to its source page. It gives readers a dated history of the company and gives every source page at least one internal link.
media:on Editorial. Written and reviewed by the media:on editorial team, who edit every release before it files.