$100 free credit on sign-up, then $0.10 per 1,000 calls

Report layout

Ahrefs Backlinks Client Report Layout for a PR Team

Clients ask for a screenshot from a famous tool. If you build the report from our API, say so and keep the numbers consistent from month to month.

Craftsman sorting premium blocks from generic rubble on a workbench

Mistakes in client reports, and the repair

MistakeWhy the client noticesRepair
Mixing Ahrefs screenshots and our DR in one chartTwo scales appear on one axisPick one source per chart and label it
Quoting a DR with no dateThe figure looks arbitraryAdd the month of the index refresh
Counting nofollow placements as ranking gainsSearch does not move and the account manager has no answerReport coverage and links as separate lines
Hiding placements that vanishedThe client finds out from their own auditList them with the editor's reply
Reporting live links before the index shows themThe data tool says zeroAttach the dated page screenshot as the proof

Who this is for

You run PR for clients and you need a monthly document. Ahrefs, Semrush and Moz are common, and many clients have their own seat. Fine.

Our API is the cheaper way to fill a template yourself: DR, referring-domain counts and anchors for each placement, pulled by script. It is not a replacement for keyword and ranking sections, where Ahrefs or Semrush remain fuller. For deciding which outlets to chase in the first place, see the DR cutoff table. Keep that split.

One-page layout we would use

  • Top line: new placements this month, with live URLs
  • Table: outlet, DR with the refresh month, anchor, rel attribute
  • Chart: referring domains of the client's site, month on month
  • Short list of pitches sent, replies, and the reason for each decline
  • Next month's ten targets, with the cutoff that selected them
Simple architectural model standing clear against a complex maze background

Decide what the report is for before the layout

A short layout saves time. Every extra section is one more thing to rebuild each month. A layout you can refresh in an hour beats a deep one you rebuild for a full day.

Reports that try to answer every question answer none of them well. Name one decision first. Before you pick a layout, write down what the reader has to decide after reading. For most PR teams that decision is whether to keep an outlet in the plan or swap it for another.

An Ahrefs backlinks client report usually runs long, and this one does not need to. Clients stop early. The first page carries the decision, so give it the space. The placement check routine explains what goes into the pending column.

Who reads the first page

The account lead wants proof that the month was productive. The client's marketing head wants to know which outlets are worth another round. A third reader, often the founder, only wants the headline and whether it moved.

Design the top of the page for those three readers, in that order. A single line with the count of new placements, the count indexed so far and the refresh month does most of the work.

Keep outlets that the client has not approved off the first page. A draft list reads as a commitment, and the client may remember it that way at the review.

Why the refresh month belongs on the page

Our index refreshes roughly once a month, so every DR figure in the report is a snapshot. Printing the refresh month beside the numbers tells the reader that the snapshot has a date. That is the honest way to present it.

A pull made at the start of a month and a pull made at the end can differ for the same site. Pick one rule, such as the last refresh before the report date, and state it in the footer.

Print the refresh month in the header as well as the footer. A reader who skims the top should not have to scroll down to learn when the numbers were taken.

If the refresh lands after the report date, say so in one line and carry the older figures forward with that label. The reader sees the gap and the reason for it in the same place.

What to leave out of a link report

A link report does not need every referring domain the client has. Twenty well-chosen rows and a total count are easier to read than a list of several hundred. Keep the full export in a separate file for anyone who asks for it.

Leave out any figure you cannot reproduce. If a number cannot be pulled again from a dated call, it does not belong on the page, however impressive it looks.

A total that matches the export is worth more than a long table nobody can reconcile. Say how many rows the export holds, so the reader knows the count is complete.

Include the count of rows you left out as well, so a reader can see that the cut was deliberate rather than accidental.

Keep the layout identical every month

A client who sees the same layout twice starts to read the changes rather than the layout. Keep the section order, the column names and the footer wording fixed, and let only the numbers move.

When you must change a column, say so on the page and keep the old column for one cycle. That way the trend line does not break without an explanation, and the reader can follow the change.

Test the template on last month's numbers before the new data arrives. A gap in the layout shows up quickly when the figures are familiar, and that is far easier to fix than in front of a client.

Run the monthly pull in four steps

01

Pull the placements

Start from the sheet of live URLs, one row per placement, with the date each one went live.

02

Check the headline counts

Call overview for the client domain. It is free, and it gives the counts that open the report.

03

Fetch the referring domains

Call refdomains for the client at 2 credits per call, up to 1,000 rows, then filter the new domains in your script.

04

Write the refresh note

Add the refresh month and the rule used to choose the pull date to the footer before anything is sent.

Worked example (hypothetical, numbers invented)

A boutique agency reports for a travel-booking startup. In October it landed 6 articles. After the refresh, the data shows 4 of the 6 domains as new referring domains for the client.

The report says exactly that: 6 live, 4 indexed so far, 2 expected next cycle. Cost to pull it: 6 backlinks or refdomains calls at 2 credits is 12 credits, about a tenth of a cent. No drama in the review meeting. The wait is explained in the placement check routine.

Pull referring domains for the report table

Page through results with page if the client has more than 500.

bash
curl "https://linkfluence.app/api.php?action=refdomains&q=client-site.com&per=500&key=sk_live_..."
Balance scale weighing a single stone against a bundle of twigs

Reporting questions

Can I put our DR in a report that normally shows Ahrefs?

Yes, if you label it. Use a column header such as Linkfluence DR and a footnote with the refresh month. Never place it on the same axis as an Ahrefs figure, since the two formulas differ and clients will notice.

How many API calls does a monthly report need?

For a client with 20 placements, roughly 20 to 40 calls at 2 credits, so 40 to 80 credits, under a cent. Free overview calls cover the headline counters. Bulk work like a prospect list belongs in the import job instead.

Do I still need Semrush or Ahrefs for the report?

For keyword positions and traffic estimates, yes. Our data covers links only. Many agencies keep one seat for those sections and use our per-call pricing for the link tables.

What should I do if a placement is not in the data yet?

List it as live with the dated screenshot and mark the index status as pending. Data refreshes about monthly, so check again after the next refresh in November or December and update the row.

How do I explain a placement that never appears in the data?

Say it is live, show the dated page and mark the index status as pending. Pending is an accurate label, not a failure. Recheck the row at the next refresh, then update it, and keep the first screenshot in the file as the record.

Our view

Label the source, always

The report that survives a skeptical client states where each number came from. Linkfluence DR and Ahrefs DR are different scales. Put the name in the column header and the argument never starts.

  • Our graph: 2,774,625,913 domain-to-domain links
  • Refresh about monthly, so month-end snapshots work best

Questions a client asks about a number, and the answer

Most objections to a link report are about one of four numbers. Each one has a plain answer, and the answer is easier to give when the report already contains it. Give the answer in the report itself, because a reader who has to ask a second time has lost some trust already.

  • Why is this different from the figure I know?

    Because it comes from a different index. Label the figure, state its formula in one line and keep it on the same scale from month to month.

  • Why does this month look smaller?

    Often the refresh has not caught up with recent placements yet. Show the pending rows and their screenshots instead of removing them from the total.

  • Does this link help search rankings?

    Do not promise that. State that the link is live and what its rel value is, then leave search effects out of the claim entirely.

  • Can I see the raw data?

    Yes, share the dated export. A tidy extract with the call date is more useful to a reviewer than a screenshot of a dashboard.