Semrush report: the reporting add ons, what to put in a client pack, and how to schedule it
The two things people mean by a Semrush report, the add ons as published on 9 October 2026, and the five source reports worth including.
Published by AI Knows Us · Updated 12 October 2026
A Semrush report is one of two things, and knowing which one you want saves an hour and sometimes a subscription. Either you want a single tool's output pulled out as a PDF or CSV, which every plan can do, or you want a scheduled multi tool pack that lands in an inbox on the first of the month, which is sold as a separate add on. On the Semrush pricing page, checked on 9 October 2026, the reporting add ons are listed as a Base Report at $10 a month and a Pro Report at $20 a month. Below is what each one includes as published, the five underlying reports worth putting in a monthly pack, and the one page summary that decides whether anybody reads it.
The two meanings of "Semrush report"
- A tool export. You ran Site Audit, Organic Research, Position Tracking or Backlink Analytics and you want the result out of the browser. Every report has an export control, usually CSV or XLSX for the data and PDF for the view. This is the right route for a one off question, a slide, or handing a developer a list of broken links.
- A built report. A template that pulls widgets from several tools plus connected Google data into one document, on a schedule, branded, and delivered to a list of people. This is the right route for a monthly client pack or an internal board page, and it is the part that sits behind the report add ons.
Most frustration with Semrush reporting comes from trying to make the first thing do the job of the second. If you are rebuilding the same five exports into a deck every month, the add on is cheaper than your time.
What the report add ons include, as published on 9 October 2026
| Add on | Listed price | Listed contents |
|---|---|---|
| Base Report | $10 a month | Data from 20+ Semrush tools, Google Analytics and Google Search Console integrations, monthly, weekly or daily scheduling, PDF export, sharing with Semrush users |
| Pro Report | $20 a month | All Base Report features, plus 20+ external integrations, delivery at a specific time, branding and white labelling, AI generated summaries, sharing by link |
Two details in that table do most of the work for an agency. "Sharing by link" means a client reads the report without a Semrush login, which removes the most common complaint about platform reporting. "Branding and white labelling" is what lets the pack go out under your own logo. If neither matters to you, the base add on covers scheduling and PDF.
Prices and plan contents in this category change, so treat the figures above as a dated snapshot and open the Semrush pricing page before you buy. For how the add ons sit against the subscription tiers and their limits, see our dated breakdown of Semrush pricing.
The five reports worth putting in a monthly pack
A report people read answers five questions in a fixed order. Build the template once with these widgets and you never redesign it again.
| Order | Source report | The question it answers |
|---|---|---|
| 1 | Position Tracking | Did we move on the queries we agreed to care about? |
| 2 | Search Console widget | What did Google actually record: impressions, clicks, average position, by page and query? |
| 3 | Organic Research, Pages tab | Which pages are carrying the gains, and which lost ground? |
| 4 | Site Audit | What broke since the last deployment, and what is blocking indexing? |
| 5 | Backlink Analytics | What new referring domains arrived, and is anything pointing at us a problem? |
Put Position Tracking first because it is the only number the reader already agreed to. Put Site Audit fourth because it is a work list, not a result. Our page on running the five reports in the order that makes them useful covers the analysis sequence behind this pack.
The one page summary that decides whether it gets read
Page one is not a dashboard. It is five lines, written by a person, in this shape:
- What changed. One sentence with a direction and a number, taken from Search Console clicks rather than an estimate.
- Why. The cause you are confident about, named: a page shipped, a fix landed, a competitor moved, a seasonal swing.
- What we did. Three bullets of work completed, each tied to a page or a template rather than a task name.
- What we are doing next. Three bullets, in priority order, with the reason each one is above the next.
- What we need from you. The decision or the developer time that is blocking the next item.
Everything else in the pack is evidence for those five lines. A client who reads page one and approves the last bullet has got full value from the report, and that is the test to design it against.
Measured numbers and modelled numbers, labelled
Semrush traffic estimates, keyword volumes and authority style scores are modelled from its own index, which is exactly what you want for competitor comparison because you have no other way to see a competitor's performance. Search Console clicks, impressions and average position are measured for your own site. Put the measured numbers in the results section and the modelled numbers in the competitive section, label each table with its source, and nobody argues about the figures in the meeting. Our Search Console guide covers what each of those numbers measures.
Scheduling and delivery, set once
- Pick the day the data is complete. Search Console data settles a couple of days behind, so a report scheduled for the 1st is reading an incomplete last day. The 3rd or 4th of the month is a calmer choice.
- One recipient list per client, not per person. Adding people one at a time is how a report quietly stops reaching the decision maker.
- Keep the template, change the commentary. A pack whose layout moves every month cannot be compared month to month, which is the only thing a monthly report is for.
- Keep an archive. Save every PDF in a dated folder. Twelve of them side by side is the strongest renewal document you will ever produce.
Where to use an export instead
Four jobs are faster as a raw export than as a built report: handing a developer the Site Audit issue list filtered to blocking errors, giving a writer the Organic Research positions four to twenty list sorted by volume, giving a disavow decision the backlink export, and giving finance a keyword list with volumes. Export those as CSV and skip the PDF entirely. For the tracking side of the pack, our page on what a position really measures and how to build a ranking report goes deeper.
This page covers Semrush reporting: the add ons, the pack, the schedule. For choosing a subscription tier and its limits, see the pricing breakdown linked above. For the analysis that produces the findings, see the five reports page.
What gets asked about semrush report
Can I build a report on the free plan?
The free plan is limited to a small number of tool requests a day and one demo project, so it suits a one off export rather than a scheduled pack. Run the tool, export the view, and build the document yourself. When you are rebuilding the same document monthly, that is the signal to buy the add on.
Do I need the Pro Report add on or the Base Report?
Decide on two questions. Does the report need your logo rather than Semrush branding, and does the reader need to open it without a Semrush account? If the answer to either is yes, the Pro Report is the one that lists branding, white labelling and sharing by link. If you only need a scheduled PDF to colleagues who already have logins, the Base Report covers it.
Can a Semrush report include Google Analytics and Search Console data?
Yes. Both integrations are listed as part of the Base Report add on, which means your measured click and session data can sit in the same document as the platform's competitive estimates. Connect both properties before you build the template so the widgets have data to draw.
How often should a client report go out?
Monthly for the pack, with a short written note after anything significant ships or after a volatile week in the search results. Weekly packs invite people to read noise as a trend. Daily reporting is useful during a migration or a recovery, and worth switching off again afterwards.
What should I leave out of the report?
Leave out the overall site health score, any metric nobody agreed to at the start, and every screenshot that needs a paragraph to explain. A report earns its length by helping somebody decide something, so each page should end with either a number the client chose or an action you are asking for.
The question this pack does not cover yet
There is now a sixth question a client asks in the same meeting: when a buyer types our category question into an assistant, does it name us? That answer is generated per prompt, it is not a position in a list, and the reports above were built for a world of ten blue links, so they do not carry it. Tracking it means choosing the prompts buyers actually use, running them on a schedule across the assistants, and recording which sources the answer drew from. AI Knows Us does that part and runs a free scan with no account, at aiknowsus.com, and it belongs beside the pack above rather than instead of it.