A content performance audit helps you decide which pages deserve attention first. This practical template combines Google Search Console, GA4, and editorial judgment so you can identify declining pages, separate real problems from reporting noise, and maintain a prioritized refresh backlog.
Overview
Not every page with lower traffic needs an update. A decline may reflect seasonality, a change in search demand, stronger competition, a tracking problem, or a page that no longer matches the visitor’s intent. Conversely, a page can retain steady traffic while losing valuable conversions or attracting visitors who do not progress beyond the landing page.
A useful content performance audit evaluates three questions:
- Is the page still visible? Review organic clicks, impressions, click-through rate, and average position in Search Console.
- Does it satisfy visitors? Review GA4 landing-page engagement, engaged sessions, key events, and funnel progression.
- Is it worth improving? Consider business value, search intent, strategic importance, freshness, and the effort required.
Use the audit as a recurring decision system, not a one-time list of URLs. Compare a recent period with a suitable previous period, record the date and data sources, and avoid changing several important variables without documenting what changed.
What to track
Create one spreadsheet row for each important landing page. The following columns provide a practical starting point for a content refresh template:
- URL and page type: Record the canonical URL, content format, topic, author or owner, and whether the page is a guide, product page, comparison, template, or support resource.
- Last meaningful update: Note the date of the last substantial change, not merely a revised publication date. Include what changed if the information is available.
- Search Console clicks and impressions: Compare the latest period with a previous period of equal length. Add queries or query groups when they clarify the page’s search intent.
- Click-through rate and average position: Use these together. A lower click-through rate with stable impressions can suggest a title, snippet, or intent mismatch. Average position is directional and should not be treated as a complete ranking diagnosis.
- GA4 landing-page sessions: Use a consistent landing-page dimension and date range. Make sure the page path, hostname, and query-string handling do not split one page into misleading rows.
- Engagement indicators: Track engaged sessions, engagement rate, average engagement time, scroll or interaction events where they are intentionally implemented, and exits from the next important step. These metrics need context; no single engagement metric proves content quality.
- Conversions and key events: Record leads, purchases, sign-ups, downloads, or another defined business action. Document the event definition and attribution setting. Conversion numbers can differ between GA4, advertising platforms, and CRM systems.
- Assisted value: If your reporting supports it, note whether the page appears earlier in journeys that later produce a conversion. Treat assisted conversions as directional evidence rather than proof that the page caused the outcome.
- Intent match and business value: Score whether the page answers the query clearly and whether the topic supports a meaningful business objective.
- Recommended action: Use one of five controlled outcomes: refresh, expand, merge, redirect, or leave unchanged.
For reliable GA4 content analysis, confirm that page views, landing pages, key events, and form tracking are implemented consistently. The GA4 Analytics Audit Checklist can help identify missing or broken data before you treat a decline as an editorial problem. If you use Google Tag Manager, document changes and QA results using the GTM governance guide.
A spreadsheet-ready scoring model
Add a score from 0 to 3 for each factor below. Keep the definitions stable between audits so that the score remains comparable:
| Factor | 0 points | 1 point | 2 points | 3 points |
|---|---|---|---|---|
| Traffic or clicks trend | Stable or improving | Small decline | Moderate decline | Large or sustained decline |
| Search visibility | Stable demand and position | Minor loss | Clear loss | Major loss or relevant queries missing |
| Conversion opportunity | Low business relevance | Some relevance | Meaningful opportunity | Directly supports a primary goal |
| Intent or content gap | Strong match | Minor gap | Several gaps | Page no longer answers the intent |
| Freshness risk | Current and durable | Minor dated details | Outdated examples or sections | Important information requires review |
| Update feasibility | High effort, low confidence | Complex | Manageable | Clear, practical improvement |
Sum the points, then add a separate priority modifier for strategic importance: 0 for low importance, 1 for useful support content, and 2 for a page tied closely to an important product, audience, or conversion path. A high total identifies an investigation candidate, not an automatic rewrite. Read the page and its queries before deciding.
Cadence and checkpoints
Use a monthly review for a small set of priority pages and a quarterly review for the broader library. Monthly checks are best for detecting sharp changes, broken tracking, campaign effects, and pages affected by a recent update. Quarterly reviews provide enough context for slower-moving organic performance and editorial planning.
At each checkpoint:
- Export or record the same GA4 and Search Console fields used in the previous review.
- Use comparable date ranges and annotate seasonality, promotions, site changes, migrations, and tracking releases.
- Flag pages with declines across more than one signal. A traffic decline alone is weaker evidence than simultaneous losses in clicks, relevant impressions, engagement, and conversions.
- Review the top queries, landing-page experience, internal links, technical status, and competing results for flagged pages.
- Assign an owner, action, expected outcome, and review date in the editorial backlog.
Do not compare reports built from different event definitions without recording the change. If key events, consent settings, or attribution configurations changed, mark the affected period. The consent and analytics troubleshooting checklist is useful when GA4 or advertising conversions appear to change without a corresponding business explanation.
How to interpret changes
Use the pattern across metrics to choose an action:
| Observed pattern | Likely investigation | Recommended action |
|---|---|---|
| Impressions and clicks fall, but intent remains valid | Demand, competition, ranking, or coverage changed | Refresh and expand the page; validate target queries and internal links |
| Impressions remain stable while clicks fall | Search-result presentation or intent alignment may be weaker | Review the title, description, introduction, and query-to-page match |
| Traffic is stable but conversions fall | Offer, form, CTA, tracking, or visitor mix may have changed | Check the conversion path before rewriting the article |
| Two pages target the same intent and both weaken | Topic overlap or diluted internal signals | Merge into the stronger page, redirect where appropriate, and update links |
| Page has little visibility, weak intent, and low business value | Limited opportunity or obsolete purpose | Leave unchanged only if useful, otherwise consider consolidation or removal |
| GA4 declines but Search Console is stable | Tracking, consent, referral, or implementation issue | Audit measurement before making editorial decisions |
For pages supporting ecommerce decisions, compare content performance with product views, cart actions, checkout steps, and purchases using a consistent tracking plan. For lead-generation pages, inspect form starts, submissions, validation errors, and downstream qualified outcomes rather than relying on sessions alone. Funnel context is available in the marketing funnel analysis template.
After a refresh, record the change date and preserve the pre-update baseline. Recheck early for implementation problems, but judge organic performance over a reasonable observation period rather than reacting to a few days of movement. If the page was part of an experiment, use a documented testing process and avoid declaring a winner from an incomplete comparison; see the A/B test measurement checklist for a structured review.
When to revisit
Return to this audit monthly for priority pages and at least quarterly for the complete content inventory. Revisit sooner when a page loses an important query, a conversion path changes, a tracking implementation is released, a site migration occurs, or a page depends on information that may become dated.
At the end of each quarter, archive the previous scores and compare them with the current set. Look for recurring patterns: the same topic losing visibility, repeated form-tracking gaps, pages that improve after refreshes, or high-value content that receives traffic but no meaningful next step. Use those patterns to refine your content plan and measurement setup.
To put the process into practice, create the spreadsheet with the fields above, choose a fixed review date, and begin with your most important landing pages. Score no more than the team can investigate, assign each flagged URL one action, and schedule a follow-up measurement date. A reusable marketing KPI dashboard can centralize recurring reporting, while the KPI definitions guide helps keep metric meanings consistent as the audit becomes part of your regular editorial workflow.