What Is a Good Share of Voice Percentage? How to Measure and Improve It

What is a good share of voice percentage? There is no universal target. A useful percentage depends on the keyword set, competitors, country, device, search features, date range, and visibility formula you choose. Measure the same market consistently, separate branded from non-branded queries, and set a directional target based on commercial intent.

What is share of voice in SEO?

SEO share of voice is the percentage of organic search visibility your site receives across a defined keyword set compared with the visibility received by tracked competitors. It is a market-specific measurement, not a permanent score attached to your domain.

A site can rank for thousands of low-demand queries and still capture little search visibility. A smaller site can own a valuable group of commercial searches while appearing modest in total keyword counts. Semrush describes share of voice as a comparison of estimated organic traffic across a defined keyword set, while Ahrefs describes its Rank Tracker version as the percentage of clicks received against the clicks available across the SERP. The methodology changes the result, so record it beside every report.

Metric	What it tells you	What it misses
Ranking position	Where one URL appears for one query	Total market visibility
Impressions	How often your result appeared in Search	Competitor visibility across the same set
Organic traffic	Visits attributed to search	Demand you did not capture
Share of voice	Your proportion of tracked visibility	Queries outside the selected set

Fix the denominator before comparing two reports. Store the country, language, device, date range, search type, keyword intent, competitor list, and treatment of featured snippets or other search features. A desktop report for US non-branded software terms cannot be compared fairly with a mobile report for worldwide branded terms.

Share of voice becomes useful only when the keyword set and visibility method stay stable between measurements.

What is a good share of voice percentage?

A good share of voice percentage is one that supports your business goal and improves against a clearly defined competitor set. A percentage that looks strong across branded queries may hide weak coverage for new-customer searches. A lower percentage across a broad category may still produce valuable leads if your tracked terms have high purchase intent.

Start with a baseline. Export the current visibility score for a fixed set, then split the set into branded, non-branded informational, commercial, and transactional terms. Compare your result with direct competitors that sell to the same audience. Do not use a large publisher or a marketplace as a competitor unless its search role matches yours.

Set a directional target after that comparison. For example, a developer-tool company might keep a separate target for searches such as “coding agent SEO” and another for its brand name. The first group measures acquisition reach. The second measures existing demand. A target to increase non-branded visibility within the next reporting period is more defensible than claiming that every site should reach a fixed percentage.

Branded terms deserve their own view. Include them if you want to measure total visibility, then report a second, non-branded view for acquisition analysis. Market share and SEO share of voice also answer different questions. Market share concerns business sales or users; share of voice concerns visibility within the search set you defined.

When not to use a share-of-voice target

• Do not set a target before you have a stable keyword set.
• Do not compare reports that use different countries, devices, or search features.
• Do not judge a new site against an established competitor without separating brand demand.
• Do not treat a score as a ranking guarantee or a substitute for conversions.

The practical answer to “what is a good share of voice percentage” is therefore conditional. Use the baseline, competitor comparison, intent split, and business value to choose the target.

How to calculate SEO share of voice

Choose one visibility score and apply it to every tracked domain. A simple calculation is:

Share of voice (%) = your site visibility / total tracked visibility × 100

“Visibility” can mean estimated clicks, impressions, a position-weighted score, or another documented value. Semrush’s position-tracking documentation describes visibility as a click-through-rate-based metric for the tracked campaign, with 0% representing no top-100 rankings and 100% representing first position for every tracked keyword. Your report should name the method rather than presenting the percentage as an objective market fact.

Illustrative example: A fictional keyword set gives Product A a visibility score of 240, Product B 360, and Product C 400. Total visibility equals 1,000. Product A’s share is 240 / 1,000 × 100, or 24%. This example says nothing about a real market. It only shows the calculation.

Weight priority terms when every query should not count equally. Assign a business-value weight to each keyword, multiply each site’s visibility by that weight, and divide your weighted site score by the weighted total. A high-intent query can receive a larger weight than a broad informational query, provided you document the rule and keep it unchanged.

A share-of-voice percentage is comparable across time only when the scoring formula, keyword set, and competitor set remain unchanged.

How to measure share of voice with your SEO data

Build a small, repeatable dataset before opening a dashboard. For each keyword and measurement date, store the query, intent, country, device, your URL, position, impressions, clicks, and competitor observations. Add the visibility score and its formula. A CSV, database table, or versioned JSON file works if the fields remain consistent.

• Use rank data to see where each domain appears.
• Use Google Search Console to validate your site’s impressions, clicks, queries, and pages.
• Use analytics to connect organic visits with engagement or conversions.
• Use competitor observations to calculate the comparison set.
• Use a backlink tracking tool to inspect authority and referring pages behind a visibility gap.

Google Analytics cannot calculate competitor share of voice by itself. It measures behavior on your site. Search Console provides first-party search performance for your property, while a rank source supplies the competitor observations needed for the denominator. Treat “seo optimization google analytics” as a measurement workflow that joins tools, not as a single Google Analytics report.

A backlink tracking tool helps diagnose why a competitor page may outrank a comparable URL, but links do not prove that a ranking change will follow. Google’s Search Console Links report also says its link data is a sample rather than a complete list, so use it as supporting evidence rather than a full backlink inventory.

Keep the collection schedule consistent. A weekly or monthly review can work; the correct choice depends on search volume and the pace of your publishing. Record the owner, extraction date, source, filters, and any keyword additions. Adding new terms mid-period changes the denominator and breaks the comparison.

What to do when your share of voice is low

A low score becomes actionable when you connect each missing visibility point to a query, competitor URL, and change you can review. Export the terms where a competitor ranks above your relevant page. Group them by intent and existing URL before writing anything.

1. Find the gap. Filter for high-intent queries where your site ranks outside the visible results or where a competitor owns a stronger position.
2. Choose the page. Map each query to the best existing URL. Create a page only when the repository has no suitable destination and the intent deserves separate coverage.
3. Fix relevance. Rewrite the title, description, headings, examples, and body sections so the page answers the query directly. Add missing subtopics rather than repeating the keyword.
4. Connect related pages. Build contextual internal links and organize adjacent terms through topic clusters for organizing keyword coverage.
5. Check technical signals. Review canonical tags, indexability, sitemap entries, robots rules, rendering, and structured data.
6. Measure one hypothesis. Record the proposed file change, expected query group, owner, and next measurement date.

For example, if a product page ranks for a commercial query but the supporting comparison page has no internal link, add the link and improve the comparison page’s evidence before rewriting the entire site. Small diffs make approval and later diagnosis easier.

Prioritize pages with existing relevance and demand before creating new content for every missing keyword.

A coding-agent workflow for share-of-voice improvements

SEOAgent fits teams that keep their site in a repository and work through a coding agent. Its free Skill and local seoagent CLI run on the user’s own model inside a compatible coding agent. The workflow audits files, proposes changes, or writes approved changes directly into the repository. You review the diff and ship it yourself.

That mechanism matters for SEO work. A proposed title belongs in the page metadata file, an internal link belongs in the relevant Markdown or component, and a sitemap adjustment belongs in the configuration that generates it. The change stays visible in version control instead of becoming a dashboard task that someone must manually translate into code.

1. Run the SEOAgent skill or local CLI against the repository.
2. Inspect the audit findings for the pages connected to the low-visibility queries.
3. Ask your coding agent to propose a narrow change and state the target keyword group.
4. Review the diff, test the site, and approve only the files you want to keep.
5. Measure the same keyword set after the change reaches production.

SEOAgent requires a coding agent, so it does not suit a dashboard-only workflow. Google Search Console analysis, keyword research, and competitor research belong to its optional paid cloud tier. The product does not publish to a CMS or ship changes without approval.

Teams searching for the best claude keyword rank tracker software should separate two use cases. A conventional rank tracker provides a hosted interface. SEOAgent for Claude Code puts the audit and implementation step inside the repository workflow, using the user’s own model. The SEOAgent vs Semrush comparison is useful when deciding whether repository changes or dashboard reporting better matches the team’s process.

The same distinction applies to “seo optimization google analytics.” Analytics can validate behavior after a change, while SEOAgent can inspect and modify the site files that define the page.

Share of voice measurement checklist

Copy this checklist into a repository issue or measurement document before the next review.

• Define the market, language, country, device, search type, and date range.
• List every tracked keyword and label its intent.
• Separate branded, non-branded, informational, commercial, and transactional groups.
• Record direct competitors and the URLs observed for each keyword.
• Document the visibility formula, weights, search features, and missing-data rules.
• Store positions, impressions, clicks, landing URLs, and competitor observations.
• Record the source tool and extraction date.
• Assign an owner and a fixed review schedule.
• Write one hypothesis for each approved page or technical change.
• Keep the approved implementation diff with the report.

For repository-based teams, pair the measurement document with the SEO optimization workflow. Developers using Claude Code can review the SEOAgent for Claude Code workflow before choosing the implementation path. Review the score only after the keyword set and formula match the prior report.

References

• How to measure SEO share of voice using Semrush
• Position Tracking Overview
• Links report, Search Console Help
• How to check my website’s SEO visibility?