New: Operator, the chat that answers questions about your site
RankMySEO home
Start for free
All skills
Report

Keep a change log and write owner and executive reports

Each change to a live site gets one row in the change log, so you can find it by date later. Reports stay short, use one set of numbers, and name the source and window for every figure.

Send feedbackConnect RankMySEO

Example

You ask

I changed the pricing page title and description this week. Log it, then write this week's report.

The assistant

Your assistant adds a change log row with the date, the reason, the expected effect on one metric, and a check date. Then it writes a one-page weekly report with the Search Console numbers, their window, and three actions.

Use it when

  • You changed a live page, template, or setting, and need a record of it.
  • It is time for the weekly or monthly owner report.
  • A manager or client needs a one-page executive summary, or a quarter is ending.

You give it

  • The changes made since the last report, with the date and reason for each.
  • The period's numbers from Search Console, GA4, and tracked ranks, each with its source and window.
  • Any decisions or approvals still waiting on you.

It returns

  • A change log with one row per change: date, page, what changed, reason, expected effect, metric, check date, and result.
  • A weekly or monthly owner report, under one page, in plain words.
  • A one-page executive summary with a scorecard of four to six numbers and the decisions a manager or client must make.

How the skill runs

  1. Log each change on the day

    Add one row for each change, on the day it is made. Record your own changes too, such as a new page you published or a setting you changed. Batch edits to one page on one day can share a row.

  2. Give each change a reason and metric

    Name the evidence for the reason, such as a number, an issue, or a request from you. Name one metric for the expected effect, and do not promise a rank.

  3. Write the weekly report

    Keep it under one page, in this order: summary, numbers, changes this week, three actions, and what waits on you. Explain each term the first time it appears.

  4. Write the monthly summary

    Use the same order over 28 days. Add the trend across the month, which of last month's actions had a result, and any change log row whose check date has passed.

  5. Write the executive summary

    One page, meant to be read in two minutes: headline, a scorecard of four to six numbers, what worked, what did not, risks, decisions needed, and next period priorities.

  6. Check every number's source

    Use the same metrics and definitions in the weekly and executive reports, with each value calculated and labeled for that report's own window. Leave out any metric without a source and a window, and write 'not reported' instead of a guess.

  7. Hold results until their check date

    Write a result only after its check date. Before you credit a number change to a page change, check the change log for that window.

Where it stops

  • Report no number without a source and a window, and report no result before its check date.
  • Average position from Search Console is reported as average position, never as a tracked rank.
  • Add no daily report unless GA4 or Search Console is connected. Expected effects name one metric, and no report promises a rank.

Questions before you install

Why does each change need a check date?

A check date falls at least two weekly checks after the change, or four weeks of Search Console data, whichever is later. The result stays blank until then, so no early outcome gets reported.

Can I credit a traffic change to a page change?

Only after checking the change log for that window, so the dates of the change and the drop in numbers can be compared.

When is the executive summary the right format?

Use it for a manager, a client, or the end of a quarter. It is one page, meant to be read in about two minutes, and it uses the same numbers as the weekly reports.

Other skills