Our method / Built for local SEO work
Before analytics access, use the website, public business information and confirmed competitors to find problems worth discussing. Once Search Console and GA4 are connected, test the judgment, set priorities and prepare work the SEO can review and the client can understand.
From sale to delivery
Each stage starts with different information, but it keeps the problem, the reason and the next decision connected.
01 / Prospect
You getProspect Diagnosis + three priority actions
02 / Deliver
You getVerified Action Plan + completion criteria
03 / Review
You getClient-ready review + next-stage rationale
What you leave with
SearchTrust organizes the evidence and working detail. You keep the final professional judgment.
Specific findings, traceable public evidence and three actions for the first client conversation.
Judgments tested against eligible client data, with targets, priority rationale and completion criteria.
A clear account of the work, material changes, remaining limits and the next decision.
A business-specific finding and a conditional first action.
PUBLIC OBSERVATIONProspect / Before analytics access
Start with the prospect’s services, target locations and website. Use public business information and confirmed competitors to examine how the business serves search demand and explains its offering. Identify problems worth addressing in the first phase of work.
Finding another website in the industry is not enough. First confirm whether the client and competitor share a relevant service, location and search context.
Keep the query and location attached to the observation, and distinguish organic search from local results. Competitors provide market context—not proof that copying their pages will improve rankings.
The eight-layer trust model helps diagnose page content and credibility. It is one part of the method; business context, competition and subsequent performance data also inform the judgment.
Connect the specific target, observed evidence, judgment and recommendation. Keep the conditions that need client confirmation visible, rather than turning every apparent gap into an execution task.
Method example · Not a real client result
Get findings specific to this business, traceable observations and three priority actions. Explain which pages or business details need attention, why the work is worth doing and which conditions still need client confirmation.
Once the client connects analytics, test these judgments further and adjust the priorities.
Public evidence supports a proposal. It does not establish the client’s private traffic, lead quality or revenue.
View a sample reportCheck for an existing page before recommending a new one.
A more specific action candidate linked to the confirmed page.
JUDGMENT REVISEDVerified / From diagnosis to action
The prospect diagnosis helps you raise evidence-backed problems and opportunities. Once the client connects Search Console and GA4, combine actual performance with the relevant pages, business information and competitive context. Confirm or revise the initial judgments and establish clearer action priorities.
Not a few more charts in the report. A move from “what deserves investigation” to “what should we do now, and why?”
Method example · Not a real client result
01 / From the prospect diagnosis
Is a dedicated service page actually missing?
Within the pages checked, information about one core service was mainly scattered across general pages. A confirmed competitor used a dedicated page to explain that service.
Not yet established. Confirm existing pages before proposing another one.
02 / After client data is connected
Has the content been shown to cause too few enquiries? Not yet. Event measurement, visit intent and other possible factors still need checking.
04 / Final work decision
Keep the confirmed page. Improve its service information and contact path; check relevant key events. Compare its priority with the other action candidates.
01
Public website and competitor information can reveal specific problems, but may not explain their significance for current performance. Separate observed facts from judgments that still need support from client data.
Stage output
The judgments to test, tied to specific pages or analysis targets.
02
Use comparable client data to examine how people discover the relevant page and what happens after they arrive. Read performance evidence alongside page checks, rather than choosing a direction from one metric alone.
Stage output
Evidence that supports the initial judgment, conflicts with it or remains inconclusive.
03
Reassess the recommendations against new evidence. Confirm problems worth addressing, revise inaccurate assumptions and bring better-supported priorities to the front.
Stage output
Specific targets, reasons for action and a clear order of priority.
Combine the public diagnosis with actual client performance to produce evidence-supported problem assessments and three priority actions. Explain to the client why these come first, then hand specific requirements to the delivery team.
Review the full reasoning before delivering clear recommendations to the client. Where evidence is insufficient, keep the open checks visible rather than filling uncertainty with confident language.
View a sample reportInvestigate improving the existing page before creating a possible duplicate.
A recommendation with an impact direction, target, rationale and dependencies.
ACTION CANDIDATEPrioritization / Your plan, your decision
SearchTrust brings together expected outcome impact, business value, problem severity and supporting evidence to propose priority actions. Review the reasoning, adjust the order and edit the details around your client’s goals and delivery constraints to build your own work plan.
Every recommendation explains what it aims to improve, why it deserves attention now and how to validate it later.
The controls below change only this fictional example. In the report workspace, you can reorder the three generated actions and save edits to their work fields as a versioned plan. The five considerations here explain professional review; they are not a published numerical scoring formula.
Interactive demo · Changes do not affect real reports
These illustrative actions are not real client findings. Their starting order is for demonstration, not a fixed priority for every client. Nothing is sent to a report, and no sign-in, analysis or credits are required.
Drag using the handle on desktop, or use Move up / Move down on any device.
Target: The confirmed service page
Original recommendation: Relevant demand already exists, and there are specific information gaps.
Original suggested content · Initial position 1
Target: The website and public business information
Original recommendation: An information conflict needs client confirmation.
Original suggested content · Initial position 2
Target: The corresponding service page
Original recommendation: Specific content gaps need supporting business material.
Original suggested content · Initial position 3
Saved plans exist only in this page’s demo. Refreshing or leaving the page resets them.
Demo plan not saved.
Business priorities, team capacity, redesign plans and project progress also affect the order of delivery. Keep the original reasoning while adjusting the action order and content to turn the analysis into a practical plan.
For example, if the service page will be updated in next week’s redesign, you could bring forward the business information correction that can be completed this week.
What should this work improve? How directly does it connect to rankings, traffic or enquiry goals?
Distinguish whether an action primarily addresses search visibility, page competitiveness, click acquisition or the contact path after arrival. Explain the part of the journey it aims to improve, rather than describing every change as ‘improving rankings’.
These are impact directions, not proof that an outcome has been achieved.
Which pages and services are affected? Do they matter to the client’s current business priorities?
The same problem can have different value on a secondary page and a core service page. Use the analysis scope and known business context to understand whether it affects one page, several targets or an important service need.
The SEO can add the client’s business priorities and adjust the suggested order.
Is this a clear obstacle, a performance weakness or a general improvement opportunity?
Distinguish problems that prevent normal use, business information that needs correcting and content that could be improved. Not every finding belongs on an urgent task list.
How much support is there for the expected value? Which parts remain assumptions?
Check for direct observations, supporting client data and whether the evidence refers to the same target. Separate well-supported judgments from opportunities that still need validation.
An important-looking problem does not prove its impact. Strong evidence does not automatically make a task urgent.
Does other work need to happen first so this improvement can be implemented or reliably evaluated?
Identify prerequisites such as business confirmation, restoring page access or checking measurement. Some work does not directly increase traffic, but provides the necessary foundation for what follows.
Method example · Not a real client result
Expected value helps plan the work. It is not a guarantee of higher rankings or more traffic.
You do not have to accept every suggestion or start from scratch. Review the evidence, adjust the order and edit the details to turn the suggested actions into a plan you stand behind.
Consider improving this page for the top-three plan; the SEO sets the final order.
An editable working brief and review checklist—not a claim that work is complete.
WORK PREPAREDExecution support / From recommendation to review
See how a recommendation could become a working brief, a reviewed content draft and a later check of the same page. The SEO confirms the business details, implements the work and decides what the follow-up evidence supports.
This is an isolated website demonstration. Real reports provide action steps and review guidance, but do not yet save content drafts, confirmed implementation records or implementation-aligned before/after comparisons. Nothing here runs analysis, publishes a page or uses credits.
01 / Execution steps selected.
Specify the location, sequence, required materials and completion criteria. Hand the reviewed brief to the content team, developer or client contact.
Step 02 / Working brief
Explain who the service is for, which problems it covers and its service area.
Use confirmed business information and specific findings. Leave missing information marked for completion rather than inventing it.
Editable demo · Fictional business
Bracketed text marks information to confirm. These changes stay in this demo and do not edit a real report or publish a page.
Draft contains information still to fill in. It is not a final, publish-ready version.
Air conditioning repair | [Service area] | [Business name]
[Business name] provides [Confirmed repair services] in [Service area]. When contacting us, describe the equipment type, fault symptoms and your location so we can confirm whether your request is within our service scope and discuss the next steps.
We can provide: • [Confirmed repair service one] • [Confirmed repair service two] • [Confirmed repair service three] Service area: [Confirmed service area]. If you are unsure whether your equipment or problem is covered, please check through [Enquiry channel] first.
Confirm the following process against the business’s actual way of working: 1. Submit equipment and fault details. 2. Confirm the service scope and next steps. 3. Inspect and address the issue as appropriate. 4. Explain the outcome and any follow-up advice. [Confirm the actual service process with the client]
Need to check your repair requirements? Tell us about your equipment and location through [Phone number or enquiry channel].
Compare content and data for the same page. Separate whether work is complete, whether performance changed and whether the evidence supports the next decision.
Comparison demo · Simulated data, not a client result
Changed sections are shown below. This is a fixed illustration—not a published version of your edited demo draft.
Before
A general description of the service.
After · Illustrated change
Confirmed services and service areas are explained.
Before
No explanation of what happens after contact.
After · Illustrated change
A client-confirmed service process is included.
Before
The next step is unclear.
After · Illustrated change
The information to provide and the enquiry route are explained.
The service-page heading is unchanged. Bracketed fields in the example copy still represent client-confirmed information to insert; no real business details or publication are implied.
Air conditioning repair We provide air conditioning repair services. Contact us for more information.
Air conditioning repair
Suggested page title Air conditioning repair | [Service area] | [Business name] Service introduction [Business name] provides [Confirmed repair services] in [Service area]. When contacting us, describe the equipment type, fault symptoms and your location so we can confirm whether your request is within our service scope and discuss the next steps. Service scope We can provide: • [Confirmed repair service one] • [Confirmed repair service two] • [Confirmed repair service three] Service area: [Confirmed service area]. If you are unsure whether your equipment or problem is covered, please check through [Enquiry channel] first. Service process Confirm the following process against the business’s actual way of working: 1. Submit equipment and fault details. 2. Confirm the service scope and next steps. 3. Inspect and address the issue as appropriate. 4. Explain the outcome and any follow-up advice. [Confirm the actual service process with the client] Contact guidance Need to check your repair requirements? Tell us about your equipment and location through [Phone number or enquiry channel].
Simulated data · Air conditioning repair service page
Metric scope
Demo scenario
Each metric has its own zero-based scale. Compare the two periods within a metric, not across different metrics. Exact values are in the table.
| Metric | Before | After | Change |
|---|---|---|---|
| Impressions | 6,000 | 6,250 | +4.2% |
| Clicks | 120 | 150 | +25% |
| CTR | 2.0% | 2.4% | +0.4 percentage points |
Positive change
Relevant metrics move in the expected direction, supporting further review of the current approach. Interpret this alongside demand changes, other work during the period and measurement conditions.
The comparison describes changes. It does not establish that this page edit caused them. Scenario switches use local simulated data and do not call a live data source.
Prepare page changes for SEO and client review before implementation.
A review trail and next-decision criteria. No result is claimed for this fictional case.
REVIEW CONDITIONSReview / From work record to next decision
A work brief is not proof of implementation, and a later metric change is not proof of cause. Follow the same page and the same decision from original evidence through the work record and a suitably comparable result check. Keep, adjust or investigate the direction on that basis.
Record the live page, exact changes and date before describing the work as complete.
Review the same page, relevant queries and eligible on-site data against a suitable baseline.
Separate the effect of the work from seasonality, measurement changes and other explanations.
Inspect the full reasoning trail behind a defensible review.
The examples below trace Google’s public principles, SEO judgment, analysis rules, project evidence, action and result review. They show what a real project must document; they are not completed client case studies.
Google’s public principles
Use documented guidance on local search, search performance and measurement to identify relevant factors, comparable data and limits on a conclusion.
View principle sourcesSEO experience and data validation
Start with business and competition context, then investigate possible causes. A real project record should show the initial idea, important trade-offs and the subsequent checks—not an unsupported experience claim.
View the judgment and required recordsSearchTrust’s analysis rules
Organize evidence, object matching, condition checks and action briefs, separating system analysis from manual verification. L1–L8 is one page-diagnosis tool within this wider method. The SEO reviews the final judgment.
View conditions and scopeMethod examples, not verified client case studies. No authorized project evidence has been supplied for these examples. The cases show the investigation process and the records needed—not completed work, growth results or measured time savings.
Selected method example 1: Impressions look steady. Why are clicks falling?. No verified project results.
Method example · Not a real client result
Narrow a site-wide change to specific pages and queries before rewriting titles.
No verified project outcome or implementation record is available. This is one possible reasoning branch, not a finding about a real site. Search presentation or a narrower page problem would require its own evidence.
Investigate affected pages, queries and possible causes before choosing a response to a search traffic change. A site-wide total alone does not identify what to fix.
Google: Debugging drops in Search traffic (opens in a new tab)Public guidance, not a Google endorsement or validation of SearchTrust.
Fewer clicks do not, by themselves, mean that a title has become less appealing. First find where the change occurred and what else changed around it.
Illustrated investigation approach—not a named practitioner’s project record or a claim of years of experience.
Analysis conditions illustrated in this method
Manual verification
The SEO reviews the live result context, query intent and alternative explanations. A trend alone does not establish the cause or justify a rewrite.
Website method preview: this checklist is not a record of a completed system run. Actual automated coverage and manual checks must be identified in the report; product alignment is pending.
A real case needs page/query-level exports, comparable periods, relevant search and page captures, and the SEO’s investigation notes. None have been supplied for this example.
No original evidence attached · Required record structure
Only publish authorized, anonymized materials. Preserve relevant business context, sources and observation times; do not expose private client information.
Conditional reasoning · Not a verified finding
If the evidence shows a shift toward queries with a different click-through pattern, revise the title hypothesis first. That would support investigating the query mix, not a blanket title rewrite.
This is one possible reasoning branch, not a finding about a real site. Search presentation or a narrower page problem would require its own evidence.
Proposed approach · No implementation recorded
Why not the obvious alternative? Do not rewrite every title solely because aggregate clicks fell. Unaffected pages and alternative explanations must remain distinguishable.
No work or implementation date verified · Records needed
Revisit clicks, CTR, impressions and average position for the same page/query scope. Read the change alongside the implementation date and other influences, rather than treating it as automatic proof of impact.
Validation not completed
No verified before/after results, implementation date or comparison periods are available. Missing data is not zero, and no simulated outcome is substituted.
Other influences to investigate: Search demand, query mix, ranking changes and other page or search-result changes have not been investigated in this example.
Inspect the public basis, the reasoning and the project evidence behind each recommendation. Understand why the action was chosen, review what changed after implementation and decide what comes next.
Credibility comes from judgments that can be verified and revised—not from every case showing growth.
View a method exampleCheck completion first; then examine performance and competing explanations before keeping or changing the plan.
A clear proposal or follow-up report, contingent on SEO approval.
READY FOR SEO REVIEWReport expression example - Not a real client result
Same case, finding and action. Switching views changes the explanation, not its certainty.
Client report view / Website example 01
Local air conditioning repair - Existing core service page
Service-stage illustration, after access to client data. The evidence below is an example assumption, not collected client evidence.
This page is already attracting relevant search visits, but its explanation of service coverage, the service process and how to get in touch is not clear enough. We suggest improving the existing page so visitors can better understand the business and their next step.
Illustrative evidence only. Source snapshots, observation times and comparison periods have not been supplied.
Client report view selected. The same evidence, pending conditions and work status are retained.
Behind the client’s clear explanation is the full reasoning you can inspect.
SEO working view
Inspect the evidence, adjust the plan and prepare for the questions the client may ask.
Client report view
Help the client understand why the work matters, what is proposed and how to contribute.
A client view is not a way to hide problems or show only good results. Missing data, pending confirmations and important limits stay visible, expressed in language the client can use.
Prospect proposal
Illustrative report excerpt · Not a client result
Within the publicly checked pages, the core repair service and the route to contact are not explained clearly. Confirm the intended service page and business details before agreeing on the scope of work.
Page observation: the checked content leaves service coverage and process unclear.
Page observation: the checked contact guidance does not clearly explain the next step.
Confirm the service coverage, existing page and accurate business materials. Treat the three actions as a proposed discussion scope, not a fixed ranking for every client.
Still to verify: Public evidence does not establish private search traffic, lead quality or revenue. Relevant search demand and the effect on enquiries still need to be checked after access.
Discuss this business's actual issues and the first engagement scope, not a checklist that could apply to any business.
Service delivery and review
Illustrative report excerpt · Not a client result
Review the existing core service page as an action candidate: it has relevant search visits, a client-confirmed business priority and an identifiable information gap in this illustration.
Review basis: the page, supporting evidence and limits stay attached to the proposed action.
Confirm the business materials, concurrent page changes and measurement conditions. An SEO-approved plan and real implementation records would be required for an actual delivery.
Actual status: In this example, work is proposed only: implementation is not recorded and results have not been reviewed. No comparison values or measured improvement are claimed.
Help the client see how work follows from a judgment, rather than sending an unexplained set of changing numbers.
01
Check evidence, conclusions and pending conditions. Keep the report within what the available materials can support.
02
Review the action order, execution scope and client contributions, following the plan-adjustment approach in module 4.
03
Inspect the report the client will actually see. Confirm that its wording is accurate before sharing or exporting.
The delivery must match the final reviewed plan. A later plan edit should not silently change an already approved client version. This website demo does not save approval, send reports or change a real plan.
Method references
These sources explain the underlying practice. They are not an endorsement of SearchTrust or a validation of its proprietary model.
Search performance, on-site behavior and why the totals can differ.
Consider technical issues, demand, seasonality and ranking changes.
Relevance, distance and prominence provide essential local context.
The workflow follows evidence-led SEO practice: inspect the market and site, check data quality, compare relevant signals, prioritize work and review the outcome. SearchTrust organizes this into traceable reports. Its L1–L8 model is one proprietary page-diagnosis tool within that workflow, not a claim about Google's internal algorithm.
It can document checked website and public Business Profile issues, compare confirmed competitors and recommend work supported by those observations. It cannot establish the client's private search traffic, conversions or the revenue impact of a proposed change.
Connected Search Console and GA4 data add performance evidence to the same Case. Healthy evidence that matches the relevant page, query or supported scope can strengthen or reduce an action's priority. Conflicting signals can call for measurement review. Verified describes the evidence used; it does not mean an SEO outcome is guaranteed.
No. Period comparisons and agreement between sources can support a judgment, but do not isolate the effect of one change. Advisors should consider timing, demand, seasonality and other work before drawing a causal conclusion. The report provides action baselines, validation criteria and review dates to support that review.
Official GBP account access is not required for the core workflow. Confirmed public Business Profile evidence is used alongside the website. Verified requires the relevant GSC and GA4 connections; official GBP Performance can provide additional evidence when available and enabled. Public profile observations are not private GBP performance metrics.
No. The report states the sources and pages checked. The wider diagnostic method also includes advisor checks such as seasonal demand, algorithm-update timing, tracking configuration and implementation history. SearchTrust does not claim exhaustive technical, backlink or local rank-grid coverage.
New evidence may support an earlier finding, reduce its urgency or reveal a measurement issue that needs attention first. Performance growth does not erase a directly observed problem such as an explicit noindex directive. Changes are explained against the earlier report; unchanged evidence does not need a change label.
Begin with the website and business confirmation, then move into analysis. Review the initial work direction and test it further when the client connects their data.
Website entry and business confirmation are free. New accounts receive 5 permanent credits; starting a Prospect analysis or generating a Verified Action Plan uses 1 credit. This button opens the entry flow; it does not start paid generation.
