There is not much point collecting useful information if the person making the decision never sees it.
In August 2026 I added a small search-performance panel beside the WordPress editor. It used the existing Search Console connection and fetched the current page’s recent impressions, clicks, click-through rate, average position and leading queries. The aim was context for the article being edited, not a miniature copy of an analytics product.
Make the next decision easier
If a page is being shown for a query the article barely answers, that is a reason to read the page again. Perhaps the introduction is vague. Perhaps the page covers a different need. Perhaps a clearer title would help people recognise what is there.
A low click-through rate does not identify the cause on its own. Search appearance, query intent, position and the mix of searches all matter. I use the figures to choose what to investigate, then look at the actual results and the page.
Keep the period visible
The first panel used a recent 28-day window. That makes it manageable, but it also gives the numbers a boundary. A seasonal page can be useful even when that particular window is quiet.
For comparisons I want equivalent periods where practical, with any unusual event or seasonal change noted. An average position is an aggregate, not a promise that everyone sees the page in the same slot. Google’s Search Console performance-report help explains how its measurements should be read.
Do not let reporting break editing
The panel loaded its information separately from the editor’s initial render. It only appeared when the necessary connection and a published page address were available. If the external service failed, editing and the existing SEO tools still worked.
I also kept credentials on the server. A browser needs the relevant report, not the account token used to fetch it. Reusing an existing connection avoids asking an editor to manage another set of credentials for the same service.
The workflow I want
- Read what the page currently promises.
- Look at the searches bringing it into view.
- Choose one useful change and record why.
- Publish it, then review a suitable later period.
- Keep the result in context rather than crediting every movement to that one edit.
Good reporting should make a sensible editorial decision easier. It should not turn a noisy metric into another score someone feels obliged to chase.