An SEO competitive analysis report turns research into a decision-ready deliverable: what changed, which search and content opportunities matter, how reliable the evidence is, and what the team should do next. Start with the structure below, then use the filled example and reusable template on this page.
The SEO competitive analysis guide covers how to do the research. This page covers how to present its result. Use the competitive intelligence report for a broader cross-functional briefing, and the startup SEO analysis record for the working evidence sheet.
What should an SEO competitive analysis report include?
Include the objective and period, the competitors analyzed, the evidence that changed the decision, findings with confidence and limits, prioritized recommendations, action owners and dates, and the next review. A useful report presents the result of the analysis; it does not repeat the entire research process or paste every tool export.
| Report section | What to present | Evidence or decision |
|---|---|---|
| Scope and objective | Audience, decision, market/device, period, and exclusions | What this report can and cannot answer |
| Executive summary | Three to five findings and the decision requested | The few changes that merit attention |
| Competitors analyzed | Domains, relevant pages, and reason for inclusion | Separate business competitors from search competitors |
| Search visibility | Query/page groups and comparable ranking observations | External SEO tools for competitors; Search Console for your own property |
| Keyword and content gaps | Relevant intents, existing coverage, and missing or weak answers | Demand evidence from external tools, with audience and product fit |
| Backlinks and technical observations | Relevant link evidence and verified technical issues | External backlink tools and permitted technical checks; label coverage limits |
| Publishing and important changes | Relevant new pages and observed changes since the previous review | Dated URLs and supported monitoring records |
| Findings and implications | Observed fact, bounded interpretation, confidence, and unresolved questions | Explain why the evidence matters without asserting competitor strategy |
| Recommendations and actions | Create, update, consolidate, investigate, monitor, or hold | Priority, owner, due date, and validation measure |
| Evidence and next review | Sources, collection dates, limitations, review date, and triggers | An inspectable appendix and accountable follow-up |
Set the scope before presenting the findings
Name the decision and its recipient. For example: “The content lead must decide which two onboarding articles to update this month for UK small-business buyers.” Set the reporting period and comparison period, geography, language, device, and relevant product or topic. Keep those definitions beside every search table. A report about one market should not silently mix global rankings into its conclusions.
List each competitor domain, the relevant section or pages, its relationship to the buyer, and why it is included. A marketplace may compete for search attention without being a product alternative. Keep excluded domains and the exclusion reason in the appendix so reviewers can challenge the set without reopening the whole analysis.
Present search, gap, backlink, and technical evidence separately
For search visibility, group queries by intent and map them to pages. Show the comparison window, external data provider, geography/device, and the changes that matter. Use Search Console impressions, clicks, CTR, and average position only for properties you can access. Third-party competitor rankings and traffic estimates are different measurements; do not present them as competitor Search Console or analytics data.
| Evidence family | Useful report entry | Limit to record |
|---|---|---|
| Search visibility and rankings | A relevant query group, competing pages, and matched-period movement from an external SEO platform | Provider coverage, location/device, freshness, and normal ranking volatility |
| Keyword and content gaps | A customer question, current owner URL, competing answers, and external demand evidence | A missing topic or a competitor publication is not proof of demand |
| Backlinks | Page-level referring domains or link gaps from an external backlink tool | Index coverage, collection date, relevance, and whether the links were checked |
| Technical SEO | A checked URL and observable status, canonical, indexability, internal-link, or performance issue from an external tool | Permitted scope, test conditions, and whether the observation was verified |
| Competitor publishing | Dated relevant URLs, source, detection time, and review state from supported monitoring or manual records | Discovery time may differ from publication time; coverage is bounded |
Include a backlink gap only when it changes the feasibility or promotion plan for a page. Include a technical observation only when you can state the affected URL, the observed behavior, and the scope checked. An inaccessible competitor page is unknown, not evidence of a technical fault. Keep detailed exports in a linked appendix rather than filling the main report with rows.
Turn important changes into bounded findings
Select changes that alter the agreed decision: a relevant topic expansion, a persistent visibility change, a gap in your existing answer, or a verified technical issue. Explain the selection criterion. A weekly one-position fluctuation or a large raw publishing count rarely earns a recommendation on its own.
| Layer | Example | Confidence and limit |
|---|---|---|
| Observed fact | A competitor published three onboarding guides during the reporting period; the URLs and dates are recorded | High confidence in the inspected pages; incomplete source coverage may miss other pages |
| Interpretation | The guides broaden coverage of onboarding questions relevant to our buyers | Medium confidence; the pages do not prove traffic, adoption, or a deliberate acquisition strategy |
| Implication | Our existing onboarding article may leave an important buyer question unanswered | Check the page and customer evidence before approving new content |
| Recommendation | Update the existing article with the missing answer and measure its relevant query group | Name an owner and review date; do not promise a ranking gain |
Use high confidence for a dated, reproducible observation; medium when evidence is consistent but incomplete; low when a finding rests on one source, a modeled estimate, or an unresolved inference. Confidence describes the support for a claim, not the probability of a promised outcome. Record evidence that would contradict the interpretation.
Prioritize recommendations and assign actions
Choose the smallest action that serves the intent. Update an existing owner when it can answer the question; create only when the job is distinct and current coverage cannot serve it. Consolidate genuine duplicates, investigate uncertain evidence, and explicitly hold low-value opportunities. A report should make these choices visible rather than turning every gap into an article brief.
| Priority | Use it when | Required action record |
|---|---|---|
| Do next | Evidence is strong, the buyer question matters, and the change is feasible | Action, existing/new owner URL, responsible person, due date, and validation measure |
| Investigate | The decision matters but demand, intent, data quality, or feasibility is unresolved | Exact missing evidence, who will check it, and a deadline |
| Monitor or hold | The sample is weak, the intent is already covered, or the work does not fit | Reason for holding and a specific trigger that would reopen the decision |
Define success against the decision: a clearer answer, resolved indexing issue, qualified brief, or sustained page/query improvement in comparable periods. Separate delivery dates from measurement dates, and preserve the baseline before making a change. Impressions, clicks, and business outcomes answer different questions.
Filled SEO competitive analysis report example
The following NorthstarFlow report is fictional. Its names, URLs, dates, and numbers illustrate the structure; they are not Content Radar results or evidence about real companies.
| Field | Filled example |
|---|---|
| Scope / objective | Monthly review, September 1–30 versus August 1–31, UK English desktop. The content lead will choose one onboarding refresh and decide whether a separate checklist article is warranted. |
| Competitors analyzed | CedarDesk and FlowHarbor are product alternatives; OpsLibrary is a search publisher. Three onboarding sections are in scope; pricing and recruitment pages are excluded. |
| Executive summary | Refresh the existing onboarding guide. Investigate link feasibility. Hold a new checklist URL because an existing page already owns that question. |
| Search visibility | Own Search Console: the guide earned 320 impressions and four clicks versus 280 and three. An external SEO platform observed CedarDesk among the first ten results for two relevant queries on matched dates; no competitor click data is available. |
| Keyword / content gap | CedarDesk explains first-week responsibilities; our guide lists setup tasks but not role ownership. An external keyword estimate is one demand input; two recent customer questions support relevance. |
| Backlink evidence | An external backlink index lists six relevant referring domains to the competing guide. Three links were checked manually; this is not an exhaustive link audit. |
| Technical observation | An authorized own-site crawler found an internal redirect on the onboarding hub. The browser check confirmed it. No full competitor technical crawl was performed. |
| Publishing changes | Three relevant competitor guides were recorded in September from supported feeds and manual review. Detection dates and page dates are stored separately; an unavailable source limits coverage. |
| Finding / implication | Competitor coverage includes a buyer question we answer weakly. That warrants a refresh, but publishing alone does not show competitor traffic or strategy. Confidence: medium. |
| Prioritized recommendations | Do next: add a first-week roles section to the existing guide. Investigate: review the three unchecked links. Hold: a separate onboarding checklist article. |
| Actions / owners / dates | Content lead: approve the refresh by October 5. Writer: deliver by October 9. SEO lead: check the hub link by October 6 and review comparable query performance on November 9. |
| Evidence / confidence | Appendix E1: own-property Search Console export. E2: dated external rank observations. E3: backlink export and checked links. E4: crawler finding. E5: publishing URLs and source-health notes. Observations high confidence; expected SEO benefit unproven. |
| Next review | November 9, or sooner if the guide stops indexing, the monitored sources fail, or a new validated buyer question changes the scope. |
The report produces one update, one investigation, and one deliberate hold. The small click counts do not justify a traffic-growth claim, and the customer question does not require another URL when an existing page can answer it.
Copy this reusable SEO competitive analysis report template
Use the outline below in a document or slide deck. Replace the prompts with findings and source references; omit a section only when you state why it is outside scope. Keep the template and filled example with this report guide rather than splitting the same reporting job across multiple pages.
- Report header: recipient, decision, reporting/comparison periods, market/device, author, and version.
- Executive summary: three to five material findings, confidence, and decision requested.
- Competitor set: domain, relevant pages, relationship, inclusion reason, and exclusions.
- Search evidence: query groups, page owners, comparable observations, external providers, and own-property Search Console results.
- Gap analysis: customer question, existing answer, competing evidence, external demand inputs, and product fit.
- Backlinks / technical observations: affected URLs, external tool, checked evidence, date, and scope limits.
- Publishing / important changes: relevant dated URLs, previous/current observations, monitoring source, and coverage gaps.
- Findings: fact, interpretation, implication, confidence, and unresolved or contradicting evidence.
- Recommendations: priority, create/update/consolidate/investigate/monitor/hold, owner URL, and reason.
- Action register: responsible person, delivery date, validation measure, measurement date, and current state.
- Evidence appendix: source/reference, collection date, method, market/device where relevant, and known limitations.
- Next review: calendar date, review owner, trigger conditions, and unresolved questions to revisit.
What to omit and when to review again
Move ungrouped keyword exports, isolated authority scores, routine ranking fluctuations, duplicate screenshots, and unrelated competitor news to the appendix or leave them out. Never omit contradictory evidence or source failures to make the summary look cleaner. If the sample is too small, say so and set a review trigger.
Use the cadence of the decision: a monthly report for an active content roadmap, a quarterly review for broader planning, or a short exception note for an important verified change. At the next review, check the previous action register before collecting another set of findings.
Where Content Radar contributes to the report
Content Radar can help discover and organize competitors, monitor supported public publishing sources and compatible public ecommerce stores, review observed changes, retain history, and surface in-app alerts. Publishing records and supported product events can contribute dated evidence to a report; reviewers decide whether that evidence belongs in the SEO scope.
Content Radar does not natively provide keyword rank tracking, backlink analysis, search-volume databases, traffic estimates, or full-site technical crawling. Use external SEO tools for those inputs and your own Search Console for property performance. The report document, example, and template here are an editorial workflow, not a promise of a native exported SEO report or automated competitor-strategy diagnosis.
Keep competitor publishing evidence ready for review
Use Content Radar for supported competitor discovery and monitoring, then combine reviewed observations with external SEO evidence in your report.