Content Performance Review: A Weekly SEO Scorecard for WordPress

A content performance review connects what the team published to what happened next and decides what to do about it. The output is not a dashboard screenshot or a list of rankings. It is a short action register: the affected page or series, the observed evidence, the most likely constraint, the next test or correction, the owner, the due date, and the date the result will be reviewed.

Run a compact review every week to clear operational blockers and identify obvious discovery or tracking failures. Use monthly and quarterly comparisons for slower organic trends, refresh decisions, and strategy changes. A new page with three days of data should not be judged by the same standard as an established page with a year of history.

Start with five layers so the team does not use one number as a verdict. Discovery asks whether the canonical page is indexed and appearing for relevant searches. Acquisition asks which sources and campaigns created sessions. Engagement asks whether the landing experience helped visitors continue their task. Conversion asks whether qualified actions occurred. Editorial health asks whether the production system can reliably create, review, publish, and refresh the work.

A page can succeed at one layer and fail at the next. Impressions without clicks suggest a search-presentation or query-fit problem. Clicks without useful engagement suggest that the page did not meet the promise, attracted the wrong intent, or had an experience problem. Engagement without a next action suggests a weak conversion path. No impressions may indicate discovery, demand, authority, duplication, or content-quality constraints rather than a title problem.

• Discovery: indexation, impressions, queries, search appearance, and canonical URL.
• Acquisition: sessions by source, medium, campaign, and landing page.
• Engagement: engaged sessions, relevant page depth, resource use, and next-page actions.
• Conversion: trial starts, contacts, signups, assisted actions, or another qualified outcome.
• Editorial health: throughput, review time, acceptance, failures, corrections, and refresh debt.

Confirm that the live canonical URL is indexable, appears in the submitted sitemap, and is linked from another public page. Check that analytics loads only where intended, internal testing is excluded from the qualified-traffic definition, meaningful CTA events fire once, and distribution links carry consistent campaign parameters. A tracking gap can look like poor engagement, while bot or internal traffic can look like growth.

Record the measurement window and data freshness. Search Console and Google Analytics use different counting systems and should not be expected to match. Search Console measures Google Search visibility and clicks, while GA4 measures sessions and events observed on the site. Use each system for the question it answers instead of reconciling them into a false single total.

In the Search results Performance report, compare a useful period with the preceding equivalent period. For a new or low-volume site, twenty-eight days is usually more informative than a daily chart. Review pages by impressions and clicks, then open the queries for a specific page. Review queries by impressions, clicks, and click-through rate, then inspect which pages appeared for a specific query.

Google’s current guidance emphasizes trends in clicks and impressions over average position alone. Position is an aggregate that can change with query, location, device, and result type. Use it as supporting context. Prioritize pages with relevant impressions and clear actions over isolated position changes with no traffic or business meaning.

• New relevant impressions: discovery is beginning; confirm the page satisfies the emerging queries.
• High impressions and low CTR: test a clearer title, description, or query fit without exaggeration.
• Several pages for one query: inspect intent overlap and decide whether to clarify or consolidate.
• Declining clicks and impressions: check page changes, evidence freshness, competition, seasonality, and technical state.
• No impressions: verify discovery and usefulness, then consider distribution or a different page opportunity.

Use the Landing page report to see where sessions began, then add Session source / medium as a secondary dimension. Alternatively, use Traffic acquisition with Session source / medium and add Landing page + query string. This lets the team distinguish organic, referral, email, community, campaign, and direct sessions for each landing experience.

Choose engagement and conversion measures that match the page. A workflow template should record copy or download use and visits to the related guide or product path. An educational article should record meaningful internal navigation and relevant CTA actions. A product page should record trial or contact intent. Avoid treating every scroll, automatic event, or accidental click as a key outcome.

Keep user acquisition and traffic acquisition scopes straight. User acquisition describes how new users were first acquired, while traffic acquisition is session-scoped. For a weekly page review, session source and landing page are often the clearest operating view; use first-user dimensions when the question concerns original acquisition over a longer relationship.

Every reviewed page should leave the meeting with one primary action or an explicit decision to observe. Choosing several speculative changes at once makes the result difficult to interpret. Write the evidence before the diagnosis, and write the diagnosis before the action. If the evidence is too thin, define what will make it sufficient and when to look again.

• Keep: the page serves its intended job; continue distribution and watch the agreed measure.
• Improve search presentation: relevant impressions exist but the result earns weak clicks.
• Improve the answer: visitors arrive for the intended task but engagement or feedback shows a gap.
• Strengthen the path: the page helps readers but has no clear relevant resource or conversion step.
• Expand: real queries or questions reveal a distinct supporting task the page should answer.
• Consolidate: multiple pages serve the same intent or divide useful evidence.
• Refresh: facts, screenshots, product behavior, links, or recommendations are stale.
• Repair measurement: canonical, indexation, analytics, event, or campaign evidence is unreliable.
• Retire: the page no longer serves an audience or business purpose and has a safe removal plan.

Traffic reports cannot explain why a publishing system is stalled. Review the number of approved briefs, drafts awaiting review, average time in each status, WordPress failures, corrections after publication, and refresh items without owners. Compare planned cadence with actual editorial capacity. A backlog of unreviewed AI drafts is not productive output.

Connect quality signals to the series and prompt that produced the work. Repeated missing evidence calls for a better brief or source process. Repeated voice edits call for clearer examples and editorial rules. Publishing failures call for connection and permission checks. Low acceptance calls for less generation, not more. The goal is to improve the system that creates useful pages.

Prepare the scorecard before the meeting and spend the time making decisions. First, verify incidents and tracking. Second, inspect the largest relevant changes in Search Console and GA4. Third, review pages that crossed a pre-agreed threshold. Fourth, clear the oldest pipeline blockers. Finally, assign no more than a small number of actions that the team can complete before the next review.

Do not narrate every chart. Escalate only evidence that can change a page, series, distribution action, workflow, or measurement rule. Keep a dated decision log so later comparisons show when a title, content section, link path, campaign, or tracking configuration changed.

Use one row per page or series that needs a decision. Keep totals in a separate summary so the operating list stays actionable. Add the previous-period value beside each current measure and annotate releases, campaigns, outages, or major edits that affect interpretation.

• Canonical page or series and accountable owner:
• Published, updated, and last-reviewed dates:
• Indexation and sitemap state:
• Search impressions, clicks, CTR, top relevant queries, and comparison period:
• Sessions by source / medium, campaign, and landing page:
• Engaged sessions and page-specific useful actions:
• Qualified CTA events, trials, contacts, and assisted outcomes:
• Editorial status, review age, publish failures, and correction count:
• Observed evidence, diagnosis, chosen action, due date, and review date:

A monthly review can compare pages and series over a stable window, examine non-branded discovery, identify low-CTR opportunities, assess distribution quality, and choose refresh or consolidation work. A quarterly review can revisit audience fit, topic boundaries, series economics, conversion paths, and the balance between production and maintenance.

Treat causal claims carefully. A page change followed by growth is evidence worth investigating, not proof that one edit caused the outcome. Compare similar periods, annotate changes, account for launches and seasonality, and prefer repeated patterns across pages. The best review leaves the team with a smaller number of better-supported decisions.

Feed the actions back into strategy, series, briefs, templates, review checklists, distribution, and WordPress QA. A new query can become an expansion section or a distinct article. Weak CTA engagement can produce a better resource. Repeated review failures can change the brief. A declining cluster can trigger consolidation and refresh work before the team creates more pages.

PostMynd is designed to keep these operating layers connected: site context, strategy, series, approved ideas, article versions, scheduling, WordPress handoff, and visible status. The traffic number matters, but the durable advantage is a system that can explain why it changed and decide what to do next.