Meo audit guides · Meo Advisors
Search Visibility Audit: Rankings and Traffic Estimates
Audit branded and non-branded search visibility, page coverage, and technical access. Learn what modeled traffic can and cannot tell you.
Published · Reviewed
Overview
A search visibility audit checks whether your business appears for relevant searches and whether useful pages support those results. Separate searches for your name from searches for a service. Public rankings are sampled observations, while third-party traffic totals are modeled estimates. Neither establishes your actual organic enquiries or revenue.
Decide which searches matter to the business
Start with the services and markets you intend to serve. Write queries that reflect a buyer's task, such as finding a provider, comparing approaches, or checking whether a company offers a service in a location. Keep these groups separate in the review.
Branded queries contain your business name or a recognizable variation. They assess whether someone who already knows you can reach the right public information. Non-branded queries describe a need without naming your business. They explore discovery among people who may not know you yet.
Document geography, language, device, source, and collection date. Without those conditions, "you rank below a competitor" is too vague to reproduce or turn into a useful decision.
Review the branded result as a visitor would
Search for your business with appropriate location context. Check the website destination, business identity, and other official public results. A similarly named company or an old domain can complicate the picture.
Look at the title and description people may see. Does the result identify the business and relevant service? Is it sending a visitor to the current site? Google generates title links from several sources, so your page title influences the result without giving you complete control. Source: Google title-link guidance. Sources: [1] influencing-title-links-in-google-search
Record the actual result rather than assuming the source-code title is displayed verbatim. When the result seems misleading, compare it with the visible page content before proposing a change.
Review non-branded visibility by intent
Group queries by the buyer question they represent. A list of loosely related keywords can inflate apparent coverage while telling you little about the services you want to sell.
Inspect the kinds of results that appear. If the query returns directories and explanatory guides, a short sales page may not answer the same intent. If it returns local providers, a generic national overview may be too broad. Treat this as a content and market question before prescribing more pages.
Mark whether the observation came from a live query sample or a vendor's keyword database. A query checked today and a historical database record can both help, but they carry different dates and coverage limits.
Review which pages carry the visibility
Identify whether search appearances lead to the homepage, service pages, location pages, or educational content. The destination should give a visitor a useful next step that fits the question.
A broad article can attract relevant research interest without serving the same role as a service page. Keep that distinction when evaluating traffic. Do not remove useful educational content solely because it does not immediately produce enquiries.
For a multi-location business, inspect the sampled location page itself. A group homepage cannot answer every local question, and a combined domain estimate should not be presented as the performance of an individual office.
What to check
Use a scoped search register rather than an unfiltered keyword export:
- Confirm the current domain, business name, and relevant market.
- Separate branded queries from service and comparison queries.
- Record language, location, device, collection date, and source.
- Match each query group to an actual business service.
- Review result types and the likely question behind the search.
- Check the destination page for relevance and a useful next step.
- Inspect titles and main headings on sampled pages.
- Check public crawl and indexing signals without assuming index status.
- Review whether important pages have relevant internal links.
- Compare peers using the same provider, geography, and period.
- Keep estimated traffic separate from account-reported clicks.
- Describe unknown keyword coverage as unknown.
Keep the scope manageable enough that someone can inspect the pages behind the findings. A keyword list without destination review can create a content plan that repeats existing material.
Check technical access without overstating it
A public technical review can inspect response status, robots rules, indexing directives, and canonical references. These signals help identify questions for your developer. They do not prove how Google indexed every page.
A robots.txt restriction manages crawling. It is not a reliable way to remove a URL from search results, as Google explains in its robots.txt introduction. Keep crawl permission and indexing instructions separate in the report. Sources: [1] introduction-to-robots-txt
Canonical references also need context. They signal a preferred version among duplicate or similar URLs. A reference to another URL may be deliberate, and Google can choose a different canonical. Review the implementation against Google's canonical guidance before calling it a defect. Sources: [1] how-to-specify-a-canonical-url
A site: search can provide a public clue, but it is not a complete inventory of indexed pages. Google documents the operator's limits in its site-search guidance. Account-level inspection is the next step when you need a definitive diagnosis of a particular page. Sources: [1] how-to-use-the-site-search-operator
Modeled traffic is an estimate of search opportunity
Third-party organic traffic estimates typically combine a tracked keyword set, estimated search volumes, and assumptions about clicks at different positions. DataForSEO describes its estimated traffic volume calculation in the domain overview documentation. Sources: [1] domain-rank-overview-api
That modeled number is not a count from your website. It can miss searches outside the provider's database or differ from the behavior of actual searchers. Label the provider and tracked scope rather than presenting a precise estimate as a known visitor total.
Use a consistent source to compare relative footprints. Do not add totals from separate vendors or treat their disagreement as a measured traffic change. Their datasets and models may differ.
Keyword counts need an intent check
A larger keyword footprint can include irrelevant markets, informational topics, and name variations. Read the query mix before deciding whether the business is reaching the right audience.
An empty dataset also needs interpretation. Was the domain matched correctly? Does the provider cover the geography and language? Was the request successful? "No covered records returned" is a narrower statement than "no organic traffic."
A ranking observation deserves the same care. Record the result in the tested conditions. Avoid converting a sampled position into a claim about what every prospective buyer sees.
Owner reporting answers a different question
Google Search Console reports clicks, impressions, click-through rate, and average position for the property's search performance. It requires authorized access and is outside a public audit's evidence boundary. Source: Search Console Performance report. Sources: [1] performance-report-search-results
Your team can use it to check whether public findings align with observed search activity. Keep its definitions intact when comparing with analytics sessions or sales enquiries. Those systems describe different stages and can use different attribution rules.
Choose the next action from the evidence
If the page exists but answers a different question, revise the content around the relevant buyer need. If it is technically restricted, confirm the restriction's purpose before editing it. If the keyword database is sparse, gather a clearer query sample before commissioning a large content program.
Assign the action to the cause. A domain migration issue belongs with the technical owner. Missing service explanations belong with the content owner and service team. A poor competitor match belongs in the audit methodology, not on the website backlog.
Define how the change will be checked. Confirm publication and technical access, then review relevant search evidence over a suitable period. Avoid promising a ranking position or an exact traffic gain.
Common mistakes: combining branded and discovery traffic
Brand demand can make an organic footprint look strong even when category discovery remains narrow. Report them separately so your team can distinguish existing awareness from visibility for a new buyer's service question.
Common mistakes: publishing every keyword variation as a separate page
Closely related searches may be answered by the same useful page. Review intent and existing coverage before expanding the site. A page count is not a strategy or evidence of market relevance.
Common mistakes: comparing unrelated businesses
Common mistakes: calling every missing result a technical failure
A page can be absent from a sample for several reasons. Inspect public signals, verify the query conditions, and ask for account-level evidence when needed. Do not assume a penalty, indexing failure, or lost traffic without support.
Keep the tracked scope visible
Show the number of tracked keywords alongside modeled organic visibility. A provider dataset is a sample of searches, not a census of demand. Separate the observed rank from estimated clicks, and compare the target and peers within the same instrument, geography, language, and period.
A completed, covered dataset can support an observed zero. An unknown tracked universe or an uncovered geography remains unavailable. Missing records alone cannot establish that nobody searches for or visits the business.
How the free Meo audit checks this
The free Meo audit examines branded results, tracked non-brand keywords, sampled page coverage, and modeled organic visibility. It shows source dates and available coverage rather than treating a traffic model as observed website visits.
The search comparison uses matched geography, period, and instrument. A domain-wide model does not become an individual office result. Missing source coverage stays unavailable, and a public access check cannot certify that every page is indexed.
The full report adds deeper query and page evidence and competitor context up to its funded scope. Search Console, actual enquiries, and revenue still require authorized first-party evidence. The full report is free with email and phone; automated calls and texts are optional.
Read the audit methodology for the scoring rules, coverage requirements, source policy, and limits.
Related guides
Frequently asked questions
Does ranking for your name mean your SEO is strong?
It confirms a useful part of the journey for people who already know the name. It does not establish discovery for service searches. Review relevant non-branded query groups and their destinations before judging the broader search position.
Are estimated organic visits accurate enough to use?
They can support directional comparisons when the source and scope are consistent. Treat them as models with coverage limits. Use authorized first-party reporting when you need observed clicks or website activity for business planning.
Can a public audit confirm an indexing problem?
It can identify signals that warrant investigation, such as an unexpected indexing directive. Confirm the intended setup and inspect the affected URL through authorized search tools before claiming a site-wide indexing diagnosis.
Should you target the competitor's highest-volume keyword?
Only if it matches your service, market, and buyer question. A high-volume informational term may be a poor fit for a local sales objective. Review commercial relevance before allocating writing or advertising effort.
How should you review progress?
Keep the query groups, geography, source, and definitions stable. Record site changes and campaign context alongside the next observation. Separate technical verification from later visibility changes so the report does not imply results before they are measured.
Sources and review dates
- Influencing Title Links in Google Search (https://developers.google.com/search/docs/appearance/title-link) — checked · Claims: review-the-branded-result-as-a-visitor-would-2
- Introduction to robots.txt (https://developers.google.com/search/docs/crawling-indexing/robots/intro) — checked · Claims: check-technical-access-without-overstating-it-2
- How to Specify a Canonical URL (https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) — checked · Claims: check-technical-access-without-overstating-it-3
- How To Use the Site Search Operator (https://developers.google.com/search/docs/monitor-debug/search-operators/all-search-site) — checked · Claims: check-technical-access-without-overstating-it-4
- Performance report: Search results (https://support.google.com/webmasters/answer/7576553?hl=en) — checked · Claims: owner-reporting-answers-a-different-question-1
- Domain Rank Overview API (https://docs.dataforseo.com/v3/dataforseo_labs-google-domain_rank_overview-live/) — checked · Claims: modeled-traffic-is-an-estimate-of-search-opportunity-1