How to Earn Journalist Backlinks With a 7-Step Workflow

Only 21.9% of the relevant journalist requests in one two-month study explicitly promised a follow link.

That makes filtering more important than writing faster.

This guide shows the seven-step workflow I use to find useful requests, reject weak ones, prepare evidence, and send answers a reporter can actually quote.

If you want one place to research the evidence, build source pages, and manage outreach, try Distribb.

1. Connect the journalist request sources

Reporters post source requests when they need a quote, example, or expert explanation for an article. If they use your answer, they may name you and link to your site.

The requests are spread across services such as HARO, Qwoted, Connectively, Featured, SOS, and MentionMatch. Some appear in web dashboards. Others arrive by email.

Use one separate inbox for the email digests. Pull every request into one list with the platform, request ID, full brief, outlet, deadline, and time remaining.

For dashboard-based services, sign in yourself and use a secure saved session. Check that the session still works each morning because it can expire.

The services do not show the same opportunities. In the source study, only 17% of news sites appeared on more than one platform.

The overlap changed by pair:

• HARO and Qwoted: 35%
• HARO and SOS: 31%
• Qwoted and SOS: 25%
• X and LinkedIn: 82%

Using several request services increases coverage. Using both X and LinkedIn adds less because their lists overlap heavily.

2. Write a specific expert bio

A reporter should understand your experience in 30 seconds.

Your bio needs three simple parts:

1. Your name, role, company, and what the company does.
2. Five topics you can discuss from direct experience.
3. Topics or roles you cannot speak about.

That final limit matters. It stops irrelevant requests from reaching the writing stage.

Check the website URL carefully. That is usually the link a reporter will use if the quote is accepted.

3. Collect new requests three times a day

Good requests can close quickly. I check all sources three times a day and place every new request into one file.

Sort by time remaining. Keep the source, request ID, title, full brief, outlet, Domain Rating, and deadline together.

Domain Rating, or DR, is Ahrefs' 0 to 100 estimate of a website's backlink strength. It is useful for comparison, but it should never decide the pitch on its own.

The source study found that 70.3% of Qwoted requests came from sites at DR 70 or above. On HARO, 38% came from sites at DR 9 or below.

The quality mix changes by platform. Pulling every request into one list makes the difference easy to see.

4. Score every request before writing

This is the most important step.

One team sent more than 1,000 pitches in a year and earned 143 mentions. They said rejecting 70% of the requests was the biggest change they made.

Use the same score every day:

• Add 3 if the brief asks for statistics, data, or research.
• Add 2 if the topic matches one of your five expert topics.
• Add 2 if the outlet is DR 70 or above.
• Add 1 if the request explicitly promises a link or credit.
• Subtract 3 if the topic falls outside your five topics.
• Subtract 3 if fewer than four hours remain.
• Subtract 3 if the request asks for a role you do not hold.
• Subtract 2 if there is an appearance fee.

Keep requests scoring 3 or more. Log one reason for every rejection so you can improve the rule after a week.

Here is how the rule handled five requests from my account:

• Bulldog Digital Media, DR 58, asked about link building after AI. Score: +6. Answer.
• BacklinkBuilding, DR 19, asked what decides whether you pursue a backlink. Score: +2. Answer only if time allows.
• Ping Media asked for an AI tool used after an AI marketing course. Score: -1. Skip.
• GavelGrow, DR 36, asked law firm partners and CMOs about AI search. Score: -3. Skip because I hold neither role.
• TechRound, DR 77, offered a paid Startup of the Week advertorial. Score: -5. Skip.

The highest-DR opportunity was still the wrong one. The scoring rule caught that before I spent time writing.

5. Build one statistics page for each expert topic

A statistics page collects 50 to 80 verified numbers about one subject. Every number should name its original source.

Reporters search for these pages while writing. One useful page can earn links for months without a direct pitch.

Build one page per expert topic, not one page per request. Prefer government data, industry reports, and platform data. Drop any number whose original source you cannot open and verify.

Keep a complete source list for your own checking. Never let a writing tool invent a statistic. One bad number can end the relationship with a reporter.

6. Answer with one number nobody else has

Reporters can receive 50 to 200 replies to one request. Most answers lead with credentials and then give a general opinion.

Open with the answer.

Then include one verified number from your own logs or a sourced statistics page. Read the reporter's last three articles and match the length of the quotes they normally publish.

One real answer from this workflow used these figures from our own systems:

• 34 search-result queries per listicle discovery run
• About 1,264 listicle-shaped results
• About 33 targets left after vetting
• Around $0.03 in search-result API costs per run
• Distribb at DR 51 after 12 months using this mix

Write at least two sentences the reporter can paste without editing. Use one supporting link. Three or more links can make the answer look promotional.

Some journalist platforms show reporters an AI-likelihood score. One team only reached an 18% to 20% acceptance rate after rewriting each draft three times to remove obvious generated patterns.

Use a writing tool for sorting, research, and the first draft. Add your own sentences before anything leaves your account.

7. Save the draft, review it, then send

Save every answer as a draft first. Read the brief again. Check the number, the credit line, and the single link.

After approval, log the request ID, platform, outlet, date, and statistics page used. Refuse any request ID already in the log.

That log prevents duplicate pitches. After three months, it also shows which topics earn the most placements.

Free plans can be tight. In the source article, Connectively allowed three answers, while Qwoted allowed two pitches a month and delayed new requests by two hours. Check the current limits before choosing a paid plan.

Speed helps. One source said the first 10 responders roughly tripled their odds. But the team that measured the full process ranked speed behind choosing the right request. A fixed morning schedule handles the speed without lowering the quality bar.

The complete workflow

1. Connect several journalist request sources.
2. Define five topics you can prove from experience.
3. Pull new requests into one list three times a day.
4. Reject weak or irrelevant requests before writing.
5. Build one sourced statistics page per topic.
6. Write each answer around one verified number.
7. Review, send, and record every request ID.

Which part takes you the most time today: finding requests, rejecting them, gathering proof, or writing the answer?

If you want Distribb to help with the research, source pages, and outreach workflow, try Distribb.