01 / Review signal
↳ /pricing
- Impressions
- 4,300
- Clicks
- 41
Average position 4.2 · 29 eligible peer pages. A signal to investigate, not a diagnosis.
What could explain the difference? Review the page and its search context before considering an edit.
Search and AI visibility, with evidence
Connect search performance, website facts and AI answers. Get a specific plan for what to change, with the sources behind every recommendation.
Your evidence. A clear next step.You review the proposed work before anything is published.
01 / Review signal
↳ /pricing
Average position 4.2 · 29 eligible peer pages. A signal to investigate, not a diagnosis.
What could explain the difference? Review the page and its search context before considering an edit.
One finding. Its source. Your next decision.
Synthetic data · not customer results
This fictional page has a lower click-through rate than its comparison group. That gives us a question to investigate. It does not establish the cause or justify a change on its own.
A closer look at the sample
A useful report takes you from a number to a question, then back to the source. You can see what was observed and what still needs to be checked.
Specific proposals. Your approval. Measured follow-up.
01 The signal
example.com/pricing41 clicks from 4,300 impressions. In this fictional comparison, the page’s click-through rate is less than half the peer median.
The comparison opens the review. It does not explain the difference.
02 The next question
Read the page and its search context. Check the title, the visible answer and the path to a useful next step.
Confirm the reporting period, filters, page intent and comparison group. Separate page and query exports do not establish which queries led to this page; use a joined query–page report for that decision.
03 The evidence you keep
A report carries the observation, its scope and the next check. A proposed change follows only when the evidence supports it.
Follow a finding through to an exact proposed editA focused review of your business
Website pages, search data and saved AI answers work together. The review connects what we can verify to work you can approve.
Review the website, agreed exports and business facts. Keep the dates, source and limits with every finding.
A baseline you can inspectConnect related facts and pages. Turn supported findings into specific copy, link or technical proposals.
The proposed edit and its reasonYou review the work before publication. Compare later observations with the baseline and decide what to test next.
Search, answers and visits measured separatelyFictional sample walkthrough
See how pages, topics, searches and source records can connect. The illustration and findings are synthetic; they are not customer results.
A visual map of the relationships in a fictional site review.
Selected page: /servicesSelected page: /pricingSelected page: /glossary
Heuristic order, not a forecast. Select a finding to follow its evidence.
The traffic and lab records give this page context. Capture the page and inspect its canonical URL before confirming a conflict or proposing a correction.
Check whether a useful, sourced answer belongs on the page. An impression or citation alone does not prove what caused it.
Review a relevant source page, destination and link text before recommending an internal link.
Find relevant relationships between topics and pages. Review the source, destination and link text together.
Explore the link exampleKeep business facts and structured data consistent with the visible website and the sources behind it.
Explore the markup exampleSave the answer, question and cited sources. Keep a mention, a citation and an actual website visit distinct.
See how AI search is reviewedFrom evidence to an exact edit
Fictional exampleQuillfield Physical Therapy
Synthetic records, not client results.
Location page review
quillfield.example/clinics/wexley-falls
01 Page capture
The Wexley Falls page declares /clinics/east-mere as its canonical.
02 Separate inspection
The inspection record also names East Mere as the selected canonical.
Captured value
<link rel="canonical"
href="/clinics/east-mere">
Proposed value
<link rel="canonical"
href="https://quillfield.example/clinics/wexley-falls">
Owner decision
Confirm that Wexley Falls and East Mere are distinct clinics before approving this edit.
Awaiting confirmationAfter owner approval and publication, check the page response and rendered canonical.
Save the prior value. Restore it if the edit is wrong.
Request a fresh inspection through the owner’s agreed process. Revisit the selected canonical and comparable search periods after enough new observations.
The records support reviewing the signal; they do not establish the cause of a traffic change. No indexing or ranking outcome is guaranteed.
Read the sample auditOne connected program
Sourcewave is an operator-run service for search and AI visibility. We review the pages, business facts and saved answers in your agreed scope, prepare supported changes and report what happens after approved work.
Explore the programWebsite search AI answer observations Business information
A possible first 90 days
Agree the questions, access and approval responsibilities. Record the starting evidence and prioritize supported fixes.
Prepare the agreed page, link and business-information changes for your review.
Compare available observations with the baseline, resolve open decisions and agree the next priorities.
Work and timing are agreed before starting. Search and AI outcomes follow their own schedules.
The monthly record
See what was completed, what needs a decision and what comes next. Search clicks, saved AI answers and identifiable referral visits each keep their own place in the report.
Monthly report
Quillfield Physical Therapy
The current period, with each measurement kept separate.
saved answers cited the site.
A citation in a saved answer and a referral visit are separate observations.
Service-page title clarified
Completed after owner approval.
Service-description change
Awaiting clinical review.
Recheck the approved page
Then compare the next full reporting period.
Independently authored synthetic records for explanation only. These are not client results.
Read the complete sample reportClear from the start
The evidence should be easy to question, as well as easy to see.
Meet the Sourcewave approachYour website and a business question are enough to define the scope. Search Console and Analytics exports can add evidence. We agree access and reporting periods with you first.
What to prepare →You can provide exports or invite the Sourcewave account with read-only permissions for the agreed properties. You keep control and can revoke access. We explain the access and data scope before starting.
Review the access options →You receive the proposed changes and the reason for each. Publication requires your approval. The report records what was published, held and checked afterward.
Follow an approved change →No. Search rankings and AI answers depend on systems we do not control. We improve what the evidence supports and report search visibility, saved answer observations and visits separately.
How results are measured →The process is repeatable across fields: establish the facts, inspect the evidence, prepare changes and measure follow-up. Your audience, terminology and review requirements determine the work. Specialist claims stay with the appropriate reviewers.
Explore the program →Discuss your business question, agree the scope and decide what evidence is needed.