Write in Google Docs. Publish with Tenwrite.

Publish to WordPress or Blogger, manage updates, and track search performance.

Start free 5 free exports · No credit card required

Track a Blog Post’s Search Performance and Choose What to Fix

Abstract search, chart and checklist symbols representing a review of one post’s search results.

To track a blog post’s search performance, start with its published URL in Google Search Console. Record the page’s clicks, impressions, click-through rate and average position for two comparable periods. Then use those numbers together to decide whether to wait, investigate, change the post’s search presentation or improve the article itself.

The goal is not to react to one ranking number. It is to leave each review with a reproducible baseline, one documented next action and a date to check again.

Track one blog post’s search performance, not all traffic

Google Search Console provides reports for measuring a site’s Google Search traffic and performance. For this review, use the performance report to isolate the published page and compare its results across two periods.

That answers a different question from general blog analytics:

Your questionUseful measurement
Is the post appearing in Google Search results?Search impressions for the page
Are people clicking through from those results?Search clicks and click-through rate for the page
What do visitors do after arriving?On-site analytics, such as visits or a separately measured conversion

A search click counts the journey from a search result to the page; it does not tell you whether the visitor signed up, bought something or engaged with the article. Visits from other sources, such as email or social media, are a separate question from Google Search clicks. The review here stays with search exposure and clicks so that one post leads to one manageable editorial decision.

Read clicks, impressions, CTR and position together

These four measures answer different questions. None can explain the entire story by itself.

MetricWhat it tells youUseful questionLimit
ClicksClicks from Google Search results to the page in the selected context.Are more or fewer people reaching this post from Search?Clicks do not show whether visitors completed a task or prove that the article is good.
ImpressionsRecorded appearances of a link to the page in Search results.Is the page getting more or less search exposure?An impression does not establish that someone noticed or read the result.
Click-through rate (CTR)Clicks divided by impressions, expressed as a percentage.Of the recorded impressions, what share led to a click?CTR depends on the searches and results involved; one target will not suit every post.
Average positionAn aggregate measure of the page’s position in results where it appeared.Has reported position changed alongside the other metrics?It is not a live rank or a guaranteed position for every query or searcher.

Calculate CTR using matching clicks and impressions from the same page, period and filters:

CTR = clicks ÷ impressions × 100

For example, 100 clicks divided by 2,000 impressions, multiplied by 100, gives a 5% CTR. If impressions are zero, the calculation has no denominator; record CTR as not applicable rather than inventing a percentage.

Average position is most useful as context. A change in its overall value can reflect a different mix of searches, not necessarily a uniform move for every search. If clicks fall while position changes, look at the queries and reporting context before treating position as the explanation.

Percentage points are not the same as percent change

Suppose CTR falls from 5% to 3%. The difference is minus 2 percentage points: 3% − 5%. The relative change is minus 40%: (3 − 5) ÷ 5 × 100. Both describe the same movement, but they are not interchangeable.

For clicks and impressions, calculate relative change as:

(comparison value − baseline value) ÷ baseline value × 100

If the baseline value is zero, report the absolute difference and mark the relative change as not applicable. For example, a move from zero to 10 clicks is an increase of 10 clicks; it is not a calculable percentage increase under this formula.

Worked example: impressions rise while clicks fall

Consider a fictional garden-planning post. Both periods are complete 28-day windows, with the same page and filters. The example figures are invented to demonstrate the calculation.

MetricBaselineComparisonChange
Impressions2,0003,000+1,000; +50%
Clicks10090−10; −10%
CTR5%3%−2 percentage points, or −40% relative
Average position8.08.50.5 higher numerically; an aggregate, not a rank for every search

The calculations are straightforward:

  • Impressions: (3,000 − 2,000) ÷ 2,000 × 100 = 50%.
  • Clicks: (90 − 100) ÷ 100 × 100 = −10%.
  • CTR: 100 ÷ 2,000 × 100 = 5%, and 90 ÷ 3,000 × 100 = 3%.
  • CTR difference: 3% − 5% = −2 percentage points.

The observation is that the page received more recorded exposure but fewer search clicks. The numbers do not establish that its title failed. One possibility is that the page appeared for a broader or different set of queries, with a different likelihood of clicks. Changes in search demand or the results people saw could also be relevant. The aggregate position change alone does not identify the cause.

Before editing, check three things:

  1. Reporting context: Confirm that both periods use the same URL, search type and filters. Correct the comparison if, for example, one period includes a country filter and the other does not.
  2. Dates: Confirm that both periods are complete and equally long. Note whether a holiday, seasonal demand or a substantial site change makes them less comparable.
  3. Queries: Inspect the searches associated with the page in each period. Look for a change in the topics bringing impressions, then read the post and its title against those searches. Query data can offer clues, but it may not provide a complete explanation for the aggregate change.

Suppose the additional exposure appears related to questions the article does not really answer. The proportionate next step is to investigate whether those questions fit the article’s purpose, not automatically promise an answer in the title. If the post does answer them but its title obscures that fact, a more accurate title might be worth considering. If the query evidence is sparse or inconclusive, save the observation and wait for another useful comparison.

For this example, the next action is investigate query mix and page relevance. No title change has been justified yet.

Prepare the URL and a comparable baseline

Open the public post and copy its current URL. Check that it leads to the intended article, not a draft, a category page or a different version. This applies whether the post is on WordPress, Blogger or another publishing platform.

Open the Search Console property that covers the page, then isolate the page in the search performance report. This guide assumes you already have the necessary access; setting it up is a separate task. Save enough context to find the same report again:

  • Published URL: Include the full address and note any known earlier URL.
  • Publication date: This helps distinguish a new post with little history from an established one.
  • Last substantial edit date: Note changes that could affect the reader’s experience or the page’s search presentation.
  • Reporting context: Record the search type and any country, device, query or other filters you apply.
  • Period dates: Write down both the start and end of each period, not just labels such as “last month.”
  • Known changes: Note events that might make the periods harder to compare, such as a URL move or a major rewrite.

For a starting comparison, use two consecutive, complete 28-day periods. For example, an illustrative baseline could run from April 1–28 and the comparison from April 29–May 26. Keep the same search type and filters in both. Equal-length periods make totals easier to compare; each 28-day window also contains four of every weekday.

This is an editorial starting point, not a universal rule. If the post receives very few impressions, a longer period may give you a more useful view. If its subject is seasonal, a comparison with the equivalent season in a previous year may be more meaningful. Record that choice and any differences in context rather than treating unequal or incomplete windows as equivalent.

A usable baseline is a saved snapshot of a defined page, period and reporting context. It does not need to be the post’s first month online. If a substantial edit happened halfway through a period, note it: some days in that period precede the edit and others follow it.

Build a one-post tracking worksheet

A spreadsheet is enough for this review. The following is a suggested editorial record, not an official Search Console template. Use one row for each review of one URL, and retain earlier rows so you can see what was measured and decided at the time.

Copy these headers into a spreadsheet. The baseline and comparison metric columns each hold the four figures for their stated period.

URL | Publication date | Last substantial edit | Baseline dates | Comparison dates | Search type and filters | Baseline clicks | Baseline impressions | Baseline CTR | Baseline average position | Comparison clicks | Comparison impressions | Comparison CTR | Comparison average position | Observations | Chosen action | Next review date

Here is one illustrative row for the garden-planning example. The URL, dates and figures are invented; they are not a customer result or a tested workflow.

https://example.com/blog/garden-planning/ | 2025-10-01 | 2025-11-15 | 2026-04-01 to 2026-04-28 | 2026-04-29 to 2026-05-26 | Web search; all countries and devices | 100 | 2000 | 5% | 8.0 | 90 | 3000 | 3% | 8.5 | More exposure, fewer clicks; cause unknown | Investigate query mix and page relevance | 2026-06-23

The row records a decision as well as numbers. Someone returning to it can identify the page, reconstruct the comparison and see why investigation came before an edit.

You can add columns for absolute and relative changes if you review posts regularly. Keep the raw values even if you do: a change from two clicks to four is a 100% increase, but the small counts tell you to be cautious. Keep a separate note of the specific edit and intended result if an action leads to a change; do not overwrite the earlier row.

Choose one next action from the evidence

Use the following table as a practical heuristic, not a diagnosis or a guarantee. A pattern suggests where to look; the check determines whether an edit is justified.

SignalCheck firstPossible actionWhen waiting makes sense
Very few impressions or clicksConfirm the correct page, filters and complete dates. Consider whether the post is recent.Gather a longer comparable period and record a review date.Counts are too small to distinguish a meaningful pattern from a few clicks changing.
Exposure fallsCheck consistent filters, comparable dates, seasonality and whether the URL changed. Inspect the queries that previously brought impressions.Investigate the change. If the article no longer helps with an identified reader task, plan a focused refresh.The periods are not comparable or the evidence does not identify a specific problem.
Exposure rises but CTR weakensCheck whether the query mix changed and whether the title and description accurately represent the page for relevant searches.Investigate first; consider a clearer search presentation only if it remains relevant and truthful.The extra exposure is poorly understood, or there is too little data to judge the change.
Clicks rise and the article remains usefulCheck that the periods and filters match, then read the page for any known factual or task-related gap.Record no change and schedule the next review.No specific problem is visible and the page still serves its intended reader.

Before changing the search presentation

A lower CTR can invite a quick title rewrite, but first compare the searches with what the article actually delivers. Ask: would a reader using a relevant query recognize that this post answers their question? Does the page fulfil the promise made by its title and description?

If the answer is yes and the data is inconclusive, wait or investigate further. If the page genuinely covers the task but the wording makes that hard to recognize, consider a clearer, accurate title or description. Do not add a promise the article cannot keep. Also remember that the presentation Google displays may differ from the wording you supplied, so an edit to your preferred text is not a guarantee of what a searcher will see.

Before refreshing the article

A substantive refresh should address a real gap, not merely a disappointing number. Read the live post alongside the relevant searches and identify the missing or outdated part of the reader’s task. For the fictional garden-planning article, that might mean discovering that the post discusses choosing plants but never explains how to turn those choices into a planting schedule. That is an illustrative gap, not a conclusion from the example metrics.

Write down the specific proposed improvement: “Add a practical planting-schedule example,” rather than “improve SEO.” If you cannot identify a task the article fails to help with, investigate or wait. More words alone are not a useful success criterion.

A valid decision may be to leave the post unchanged. The worksheet can say “No edit: relevant queries still match the article; check again on the next review date.” That preserves the reasoning without manufacturing work.

Review the result after an edit

When you do make a change, add the edit date, what changed and the intended result to the record. For example: “June 2: clarified the title to describe the planting schedule already in the article; intended result: make the page’s purpose clearer for relevant searches.” Record other substantial changes made at the same time. If several things change together, it becomes harder to interpret a later difference.

Preserve the pre-edit figures. Then choose a subsequent, complete comparison period and use the same URL, search type and filters. Two 28-day windows can again be a starting point, but use a period appropriate to the volume and seasonality of the post. Avoid mixing pre-edit and post-edit days in a period you intend to call “after.”

At the follow-up, calculate the same changes and inspect the same four metrics. Then revisit the reason for the edit:

  • If the title was clarified, check whether the page still matches the relevant queries and whether CTR and clicks changed in context with impressions and position.
  • If the article was refreshed, verify that the published page contains the intended improvement. Search numbers alone cannot confirm that the reader-task gap was fixed.
  • If the figures moved but query mix, demand or other circumstances also changed, note those differences before deciding what they mean.

You can keep a clear, accurate edit because it helps readers even if the search numbers are inconclusive. You can also reconsider an edit if the live page no longer describes its content accurately. A before-and-after comparison is an observation, not proof that the edit caused the movement. Add a new worksheet row instead of replacing the original baseline.

Troubleshoot missing or confusing data

No visible report data is a reason to check the context, not proof that the page is absent from Google’s index. Work through the simplest explanations first:

  1. Wrong property or URL: Open the public page again and compare its full address with the page you isolated. Make sure the selected property covers that address. If the URL changed, note both versions and the date of the move; do not silently compare one address before the move with another afterward.
  2. Filters exclude the activity: Check the search type and any page, country, device or query filters. Remove an unintended restriction, then restore the intended consistent context before saving the comparison.
  3. Incomplete or mismatched dates: Check the start and end of each period. If one window is still in progress or covers fewer days, select complete comparable windows instead.
  4. Recent publication or sparse exposure: A new or infrequently seen page may not yet have enough visible data for a useful comparison. Record what you checked and revisit later; there is no fixed period that guarantees meaningful results for every post.
  5. Changes within the period: A rewrite or URL move can make a total difficult to interpret. Note the date and, where practical, choose periods that do not straddle the change.

If the report remains empty after these checks, leave the metric fields blank or mark them as unavailable rather than entering zero unless the report actually establishes zero. Investigating access or indexing issues may be a separate task; the absence of a visible performance row does not settle either question by itself.

For the next review, use this short checklist:

  • The public URL and property are the ones intended.
  • Both periods are complete, suitable for the post and recorded with their dates.
  • Search type and filters match, or any differences are explained.
  • Clicks, impressions, CTR and average position are saved for both periods.
  • Any edit date, intended result and other known changes are recorded.
  • The decision is proportionate to the evidence, with a next review date.

Choose one published post, complete the worksheet for two comparable periods and save one next action with its review date. The immediate result is a baseline you can reproduce and a decision you can explain—not an instant increase in rankings.