Monthly runbook
Check New Backlinks After a Placement Goes Live
The article is published, the client wants proof, and the link graph has not caught up. Here is the routine we would follow instead of refreshing a dashboard.

Our index refreshes about once a month. A link published on the 3rd can be invisible for weeks. Absence in the data is not proof the link is gone. Google's own Search Console shows links it knows about, but it also lags, and we cannot see inside it.
Write the dates down before anyone asks
Logs settle disputes. Before the article goes live, write down the planned date, the date you first saw the page and the date of each data pull, since those three answer most questions a client asks in the first month.
A check is only as good as its log. A log helps only when every row has the same fields. Use one column order everywhere. Then any date filter works across the whole year.
A quick test helps here. If a stranger could find the placement from your row alone, the row is complete. If they would have to message you first, a field is missing, and that field belongs in the log before the next placement starts.
The live page is the proof while the index waits
Until the index catches up, the only evidence that a link exists is the page itself. Save a dated screenshot and the full address, then keep the view-source extract that shows the anchor and the rel attribute.
Keep that screenshot beside the CRM row, so the proof and the record stay together. A reviewer who opens one and finds the other rarely needs to ask a second question. Name the file with the publisher and the date, not the client's name alone, because a screenshot pulled from a shared drive months later is much easier to find that way.
Record the anchor exactly as it appears
Editors often shorten an anchor, reword it or link a phrase other than the one in the brief. Copy what is live, not what was agreed, and mark any difference in the row. A changed anchor is an ordinary edit. A silent one is the problem. Two anchors that differ by a single word are still two rows, so write both down.
When the difference matters for a campaign, raise it at the next check rather than in the final report, while there is still time to talk about it.
Test the URL before you blame the index
Confirm the page returns a normal response and is reachable without a login. A redirect chain or a block in the page setup can complicate the picture, and it is cheaper to find that on day zero than in week four.
If the page is healthy, the cause is almost always timing. Note the refresh you are waiting for, and move on to the next placement on the list.
Run the same check on a second browser session if the first one is logged in. A page can look different to the person who manages the site, so compare what a plain visitor sees.
Runbook
Day 0: verify by hand
Open the live page, view source and confirm the anchor, the href and whether rel says nofollow, sponsored or ugc. Screenshot it with the date.
Day 0: log the target
Write the referring URL, anchor text and your own target page into the CRM row as expected.
Day 7: spot check
Call refdomains for the target and look for the new domain. Seeing it early is a bonus, not a requirement.
After the monthly refresh
Run backlinks for the target and tick the row as indexed once the new URL appears. Compare it with your import rules.
Day 60: close or chase
If the page still shows nothing, test that the URL returns 200 and is not blocked, then ask the publisher.
Why a good link looks missing, and what to do
| Symptom | Likely cause | Action |
|---|---|---|
| Domain absent a week after publishing | Index not refreshed yet | Wait for the next cycle |
| Domain present, page absent | Link sits on a deep page the crawl has not reached | Check toppages later; do not panic |
| Link vanished from the live page | Editor removed or rewrote the paragraph | Email the editor with the dated screenshot |
| Anchor differs from the brief | Editor reworded it | Record the real anchor; fix the report |
| Link present but marked nofollow or sponsored | Publisher policy | Tell the client early, not at the monthly review |

How long a placement takes to show up in the data
The index refreshes roughly once a month, so a placement can be real and still missing from every call. Waiting is not the question. Phrasing the wait is, and so is the evidence you show while you do it.
Plan for one refresh cycle, not for a fixed number of days. Nothing in the product promises that a link shows sooner, so a schedule built on that promise will break.
Set the reminder for the refresh, not for the calendar date you guessed. The refresh is what changes the data, so the reminder should follow it, and a reminder that fires early only tells you what you already knew.
Two rows that answer the same question should carry the same note, so nobody reconciles them twice in a month.
What to report on the first refresh
Once the next refresh lands, run backlinks for the target and compare the result with your log. A row that now shows the link can be ticked as indexed, with the month it first appeared. A row that still shows nothing stays pending.
Say you had 12 placements in a month and 9 appear after the refresh. Report 9 as indexed, 3 as pending, and attach the dated screenshots to the three. The client report layout has a row for exactly that status.
When a month passes and the link is still missing
Two refreshes without a match is a signal to look harder, not a reason to panic. Check that the referring page is still live, that the linked address is unchanged and that the publisher did not restructure the site.
After that, a short note to the publisher is reasonable. Keep it factual, with the address and the screenshot, and ask about the link itself rather than about the outlet's judgment.
Keep the file open for that placement until the link appears, or until the publisher confirms it is gone. Whichever comes first closes the row, and the note records which one it was.
Four kinds of question and the evidence for each
When a client or a colleague asks whether a placement counts, the question usually falls into one of four groups. Each group has its own evidence, and mixing them up is how a simple question turns into an argument. Name the question first, then pick the evidence, and the discussion stays short.
Is the link live?
Answer with the dated screenshot and the view-source extract. The data tool has no say on this one, so do not quote it.
Is it in the index?
Answer with the refresh month and the
backlinksresult. Say pending until the row appears, and do not round that up.Does the rel attribute allow it?
Read the rel value from the source. A nofollow or sponsored placement is still a real placement, so report the attribute rather than a ranking claim.
Did it hold?
Recheck the live page at each refresh. A link that has vanished gets logged with the date it was last seen, not deleted from the sheet.
What to tell a client while you wait
Give them the screenshot, the URL and the date. Say the data tool updates monthly. Done.
A line such as "live since 3 November, expected in the index by the next refresh" is honest and specific. It is also far easier to defend than a screenshot of an empty report in the third week. Once the sheet is in order, the DR cutoff table tells you which publisher to approach next. Say it plainly.
Pull the newest links to one page
The backlinks action costs 2 credits per call and returns up to 1,000 rows. Page through with page and per, and reorder with sort and order if you need a different view.
curl "https://linkfluence.app/api.php?action=backlinks&q=example-client.com&per=100&key=sk_live_..."
Placement questions
How long until I can check new backlinks in the data?
Plan for up to one refresh cycle, which is roughly a month. A link may appear earlier, but nothing in the product promises it. Verify the live page by hand on day zero and treat the index as a later confirmation step.
Is Search Console enough on its own?
It is a useful second source for your own site, since you see links Google reports for it. It does not cover other people's sites, so for prospect and competitor work you still need a link index like ours or Ahrefs.
What if the link is nofollow?
It can still bring readers and brand mentions, so it is not worthless. Record the rel attribute in the CRM and say so in the report. Do not describe it as a ranking boost.
Do not do these
- Do not re-run the same query daily; the data moves monthly
- Do not mark a placement failed before one full refresh has passed
- Do not change the anchor in the CRM to match what you hoped for
- Do not report a nofollow link as a ranking boost