SEO reporting: which pages moved, for which searches, and what they sold.

A sitewide traffic loss can come from blog searches nobody buys from while the pages that sell hold. A traffic gain can come from pages that never produce an enquiry or a sale. So an SEO report reads the affected pages and their searches before the total.

The SEO strategy says what the work was meant to change, and technical SEO confirms what went live. Without those two, SEO reporting from an analytics dashboard describes movement and cannot say whether the work succeeded.

Search Console can show a page collecting impressions for a relevant search while it earns no clicks far from page one. It shows which searches Google connects to the page, and it asks three questions: is this the page that should own the search, is its canonical stable, and does it answer the search?

Fifty impressions around position 85 mean Google has found the page for those searches, and page one is still far. Read them against the release and crawl dates and against the few weeks a rewritten page takes to show, and improve the page that owns the search rather than creating a new one for a different wording.

The report records the release date and the exact pages, templates and markets it touched, then compares them with the period before and with pages the change did not touch, checking season, demand, the results page and measurement. What the data shows and what the explanation infers are written apart.

It ends in a decision: keep the work, change it, investigate a contradiction, or stop. On an SEO retainer, each month's report names the change and what it moved.

For a store's category page, that is revenue from organic visits. For a service business, it is enquiries, sorted by the ones that turned into work. A page can gain traffic from people the business cannot serve, and another can lose informational clicks while its buying searches hold.