Skip to content
Find, fix and prove

Impact Reports: How to Build and Send One

5 min read · Updated Nov 22, 2026

One page for 28, 90 or 180 days: search clicks against the days before and a year ago, the fixes a crawl confirmed, rewritten pages with clicks before and after, and what to do next. PDF or Excel on every plan.

Impact Reports put what shipped on one site and what search did beside it on one page you can read or download as PDF or Excel. One report covers 28, 90 or 180 days. It shows the site's search clicks against the days before and a year ago, the site's Google Analytics sessions and key events beside them, the fixes a crawl confirmed, the rewritten pages with their clicks before and after, what the crawls saw change, and the biggest open fixes. It lists what changed and what the numbers did. It makes no claim about why they moved.

What it needs

  • Crawls of the site, for the fixes and the crawl block. See Fixes: what to fix first.
  • Search Console linked to the site, with the workspace owner's permission to read Search Console data (in Settings, under Integrations), for the search numbers and the rewritten pages. Without it those blocks say what is missing, and the rest of the report still works. See Connect Google Search Console.
  • Google Analytics linked to the site, for the sessions and key events. Without it that block says what is missing. See Connect Google Analytics.
  • Suggestions from the AI Page Rewriter that went live, for the rewritten pages block.

Open it

  1. Open Impact Reports in the site menu, under This site, and pick the site.
  2. Pick the period: 28 days, 90 days or 180 days. The report opens on 90 days.

The period ends 3 days back, because Search Console's final data trails by about that much. Data to shows the last day it covers. The report is made fresh from stored data every time you open it, and Made on shows the day.

The summary

One sentence at the top says, for the period, how many fixes a crawl confirmed and across how many pages, how many rewritten pages went live, how many crawls finished, and the site's Search Console clicks against the same number of days before, then its Analytics sessions when Analytics is linked. A page that is part of two fixes is counted once for each fix.

Did the site's search clicks go up or down?

Three numbers of Search Console clicks: This period, The 90 days before (or 28 or 180, matching the period) and Same days a year ago, the same span 52 weeks earlier so the weekdays match. When a period has no clicks for every day, or the site's history does not reach back a year, the block says so instead of showing a number.

Did the site's sessions and key events go up or down?

The site's Google Analytics sessions and key events, for the same days as the clicks: three numbers each, for this period, the days before and the same days a year ago, each with its change when there is one. Key events is Google Analytics' own name for the actions you marked as important there. Analytics sends no row for a day with no sessions, so a span with such a day shows no total, and the block says so. Without Analytics linked to the site, the block says what is missing. The report does not read revenue.

What was fixed, and did a crawl confirm it?

  • Confirmed by a crawl: fixes closed in the period that are still closed.
  • Came back: fixes a crawl found open again in the period.
  • Open now: fixes open today.

The table Fixes a crawl confirmed in this period lists each Fix, its Pages, How it was confirmed (Confirmed by a crawl, Confirmed by Check if fixed, or Confirmed by an accessibility run) and the day it was Confirmed on. Fixes marked done by hand are counted apart, in the line Marked done by hand, not checked by a crawl:, because no crawl checked them. A fix closed in the period that is open again now is not in the count.

How did each rewritten page do in search, against the site?

  • Went live: suggestions a crawl saw on the page in the period.
  • With a result, Waiting for data and Not measurable: where those pages stand.
  • Accepted, not live yet: suggestions marked as used that no crawl has seen on the page yet.

The table lists each Page with Clicks, before to after, Page change, Site change, Position, before to after and Result. Clicks are for the 28 days before and the 28 days after the page went live, and the site's change is for the same days. A result is Waiting until those days have final data, Too few clicks when both windows are under 20 clicks, Measured, or Not measurable when the title changed again or Search Console did not list the page. A line above the table counts how many of the compared pages gained more clicks than the site did over the same days, and says that this count is not proof about the rewrite.

When the site's Analytics numbers show, the table adds Sessions, before to after and Key events, before to after, for the same days as the clicks, and a second line counts how many pages with Analytics numbers for both windows had more key events after the change than before. That count is not proof about the rewrite either. A page's Analytics numbers are read at the next Analytics refresh after its days have final data.

What did the crawls see change on the site?

Crawls finished in the period, then the First crawl and the Last crawl, each with its kind (Fast crawl or Full crawl), Pages, SEO issues and Open this crawl. Under The last crawl compared with the one before it: New broken links, Fixed broken links, New pages, Pages gone and Pages changed. Check if fixed crawls are not counted. Page changes are compared only when the last crawl read page content.

What should happen next?

The biggest open fixes, by score: up to 5, each with a link, and Open Fix Planner for the rest.

How to read it

  • A dash means the number is not measured. It is never shown as 0.
  • Each block names what it left out, such as fixes with no recorded page count or crawls with no stored comparison.
  • The screen shows up to 50 fixes and 50 rewritten pages. The file holds up to 500 of each. A period with more crawls counts the newest 400.
  • Every report ends with this note: "Search Console and Analytics numbers are Google's, for the days shown, final data only. Search and traffic move for many reasons (seasons, Google updates, other changes to the site). This report lists what was changed and what the numbers did, and makes no claim about why they moved."

When nothing happened in the period, the report says Nothing has shipped in this period yet. and offers the next step: Run a crawl, Connect Search Console to see search numbers or Open Fix Planner.

Download

Press Download for a PDF or an Excel file of the period on screen. The Excel file has the sheets Summary, Fixes, Pages, Crawls and Next. The Pages sheet holds each page's sessions and key events before and after, beside its clicks. On Starter and up, both carry the name, color and logo you set in Settings, under Branding, instead of PerfBee's; on Free they carry the PerfBee logo. A site that shows sample search data gets no file. The download is on every plan. Viewers can download too.

What it does not do

  • It does not say a fix or a rewrite caused a change in clicks. It puts them side by side, with the site's own change next to each page.
  • It has no share link. Send the PDF or the Excel file.
  • It covers 28, 90 or 180 days ending 3 days back. It does not take custom dates.
  • It changes nothing on your site and does not promise rankings or traffic.

Plans

Impact Reports are on every plan. The PDF and Excel download is on every plan; your own logo on it comes with Starter and up.