All resources

What comes after view counts? A monthly review guide for your recruiting blog

How to look at traffic, read depth and clicks on hiring links, then decide what to improve next. A copy-ready monthly review sheet connects what you observe to what you do.

A candidate looking over hiring information outside a company

You're publishing steadily, but should you keep doing it the same way next month? Go one step beyond a report that only lists view counts and look at traffic, reading and next actions in turn. The goal isn't to assign a score. It's to choose what to work on next.

Before you look at the numbers, line up what you're comparing

First decide the question this review should answer. With a specific question, such as “Are role interviews carrying interest through to hiring information?”, it's easier to decide which posts and metrics to look at.

Record the period, the publish date and the distribution channels together. Cumulative views for a post that's been public all month and one published yesterday aren't on equal terms. If you ran ads for a post or linked to it from a job posting, note that too.

Teamblog statistics offer Yesterday, Last 7 days, Last 30 days and All time ranges. If your routine is to check the 30-day range on the same day each month, write the actual period you viewed in your notes so it isn't confused with the full previous calendar month. When a precise comparison is difficult, it's better to narrow the scope of your conclusion.

If views are low, look at distribution first

Low views don't necessarily mean a bad post. First check whether candidates had a chance to find it. Put the places you actually shared the link, such as job postings, your careers page and the team's social channels, side by side with your traffic records.

In Overview in Teamblog statistics, you can see the visit trend and traffic sources. Check whether the days you shared line up with the days visits rose, then go on to Content to see which posts were read. Without evidence that ties a channel to a post precisely, don't attribute the result to a particular channel.

An example of the visit trend and traffic sources on the Overview statistics screen with Last 30 days selected. Check the days visits rose against your distribution schedule.

The people, content and figures shown are fictional examples.

Keep the next action small. If a role post is hard to reach from the job posting, add a link; if your share copy only introduces the company, lead with what candidates will learn. You can check how a post gets discovered before rewriting the post itself.

Read depth is a cue to revisit the content

If a post gets plenty of visits but read depth is low, check whether the information the title promises appears in the opening, and whether it takes too long to reach the main point. An average alone can't tell you readers left at a particular sentence. Look at the post's length, its images and the number of readers together.

Content statistics in Teamblog show views and average read depth for each post. Read depth is measured from scrolling through the post body. It doesn't directly show whether readers understood the post or were satisfied by it. Rather than simply ranking posts on different topics, compare posts of similar length and purpose.

An example of comparing session views and average read for the same period in Content statistics. Average read is based on scrolling through the post body.

The people, content and figures shown are fictional examples.

If a role interview doesn't get to the core of the job until far down the page, try moving a summary up front. Record the date and what you changed, then watch a period of the same length afterward. The mix of visitors and the amount of distribution can change too, so don't conclude that a change in the numbers came from that one edit.

Separate clicks on hiring links from completed applications

Is it clear what readers should do after reading? Tell them where they're going: “View the product designer job posting” rather than “Learn more.” Also check that the link leads to a posting that's currently open.

Use the button block in the Teamblog editor to point to the next action, and check clicks on CTA buttons and external links in Conversion statistics, a paid feature. Looking at the number of clicks alongside the number of sessions with a click lets you tell repeat clicks apart from visits where interest occurred.

An example of CTA clicks and external link clicks in Conversion statistics. The 24 clicks occurred in 18 sessions and are not the number of completed applications.

The people, content and figures shown are fictional examples.

A click means someone moved on to the careers page, not that they submitted an application. Completed applications have to be confirmed separately in the hiring system you use. If people or sessions aren't linked between the two systems, don't report that “this post led to N applications.”

When clicks are low, pick one of the button copy, its position or the page it links to and improve that. If read depth is also low, look at the post's opening and the order of information before the button color. A single number can't settle whether low clicks mean a lack of interest or that readers never found the link.

End the report with one next action

In your monthly review, write down the observed facts, the possible explanations and the next action separately. Keeping them apart makes it less likely that a guess hardens into fact inside a performance report.

For example, “The role interview got visits, but few clicks on the hiring link” is an observation, and “The link sits too far below the description of the work” is a hypothesis. “Add hiring information right after the summary of the core work” becomes the next action. This is an example of how to keep the record, not a real customer's results.

Set an owner, the date the change goes in and the date you'll look again, and limit how many things you change at once. When visits are few, a handful of clicks can swing the ratios. If no stable pattern emerges, keep observing, or look at the questions candidates have asked you directly as well.

From what you reviewed in Teamblog to your team's next plan

Start in Overview with visits and traffic sources, move to Content for views and read depth by post, and, if you use Conversion statistics, continue through to clicks on hiring information. The reason to go through the screens in order is to choose which stage to improve first.

Use Save as Excel on the statistics screens to keep the metrics for the range you selected, and add your distribution activity and edits to the review sheet below. Exporting Conversion statistics is also a paid feature. View counts from different tools may be measured differently, so label the source when they appear in the same report.

You can plan the next interview for a role that drew interest, and an FAQ for a topic people keep asking about. Statistics won't pick your topics for you, but they add evidence to a next post you used to choose by instinct alone.

Capture this month's review on a single page

A sheet for recording everything together, from the period and distribution activity to observations, hypotheses and next actions. Leave any figure you can't verify blank and note why.

No login needed. Use it right away.

Show the monthly review sheet text