A live guest post proves that a page was delivered. It does not prove that readers visited your site or became customers. To judge that part of the work, agree on a measurement plan before the publisher adds your link.
Start with one goal. If the placement should bring enquiries, track the path from the article to a useful landing page, then to a clearly defined enquiry. Keep that result separate from any claim about search rankings.
Choose the result before you choose a tracking code
Write the goal in plain language: “Help relevant readers reach our service page and ask for a suitable quote.” That gives you something to review. A promise of more traffic does not explain which visitors would be useful.
Use the guest-post topic-fit checklist to check the reader and landing page first. Tracking cannot fix a placement aimed at the wrong audience.
Decide what counts as a qualified enquiry. For example, an agency might require a real business, a relevant service need and a usable contact method. Those are proposed criteria, not RankPulse campaign results.
Agree on the link with the publisher
If the publisher accepts campaign tags, send one final destination URL for approval. Save the untagged address too. This makes it easier to check where the link should lead.
Google Analytics supports UTM parameters on external campaign links. Its documentation describes utm_source, utm_medium and utm_campaign as fields for identifying the source, channel and campaign. Use consistent values; capitalization matters.
https://example.com/service?utm_source=publisher-a&utm_medium=referral&utm_campaign=autumn-guideThis is an illustrative URL, not a live RankPulse campaign. Here, publisher-a names the source and autumn-guide names the campaign. Agree on your own naming rules before you send the link to several publishers.
Keep personal details out. A campaign tag should not contain a person's email, phone number or customer record. Ask whoever owns your analytics setup to check the site's privacy and consent requirements before collection starts.
Tracking tags do not replace paid-link qualification. Google recommends rel="sponsored" for paid placements and accepts nofollow; our paid-link guide explains the distinction. Neither tags nor payment guarantee ranking value.
Test the path before reviewing results
Open the published link. Check that it reaches the intended page and that any redirects preserve the agreed campaign parameters. A neat spreadsheet cannot tell you whether the destination is broken.
Then run a clearly labelled test enquiry through your normal workflow. Ask the site owner to confirm that it arrived and can be distinguished from real customer requests. Do not count your test as a lead.
Check the page on a phone as well as a laptop. The next action should be easy to find, and any form should explain what the reader will receive after submitting it.
For the placement itself, use our post-publication verification checklist. Link delivery and visitor response are related, but they need different evidence.
Keep a small results record
Choose a review window before launch. Four weeks is a possible planning interval, not a promise that the placement will generate enough data. Record when the page first went live and when the tracking path was tested.
| Field | What to record | Why keep it separate? |
|---|---|---|
| Delivery | Publisher URL, link destination and live date | A delivered page may send no measurable visits |
| Recorded visits | Same date range, source and campaign filters | Visits are not people asking to buy |
| Enquiries | Real requests received, excluding test submissions | A request may not fit your service |
| Qualified enquiries | Requests that meet the criteria agreed before launch | Qualification should not change to flatter the result |
| Cost and limits | Placement spend, content cost and tracking gaps | A low headline price may hide extra work or incomplete data |
In Google Analytics, the Traffic acquisition report can show session source, medium and campaign. Save the property, date range and filters alongside your exported figures. Compare like with like.
Do not turn a small sample into a big promise
Suppose a fictional campaign costs £300 and produces three qualified enquiries under your agreed definition. The recorded cost per qualified enquiry is £100. That is arithmetic, not proof that the next placement will repeat the result.
With no qualified enquiries, report zero enquiries rather than a useful-looking cost-per-lead figure. Review audience fit, the landing page and the tracking test. Check more than one possible cause.
Analytics is not a complete account of every reader. Consent choices, blocked measurement and a later visit through another route can leave gaps. Those limits matter. Treat recorded campaign activity as evidence with limits, not a full causal claim about sales.
Make the renewal decision explicit
Choose whether to repeat, revise or stop the placement. State the reason. A relevant article with useful enquiries supports a different decision from a delivered page that nobody can find or act on.
If you change the offer, landing page and publisher at once, keep a note of all three changes. A later difference cannot fairly be assigned to one of them without more evidence.
Use the same reporting rules for the next trial. Over time, a consistent record can support buying decisions better than a list of publisher logos or a promise that every paid link improves rankings.
Sources and disclosure
Technical references: Google Analytics campaign URL guidance, Traffic acquisition report guidance, Google Analytics guidance on personal information in URLs, and Google's paid-link qualification guidance. Checked September 13, 2026.
Disclosure: RankPulse sells guest-post placements. This is a proposed reporting workflow, not a report of measured RankPulse client outcomes. Ask for a placement proposal with clear delivery and reporting terms.
