Use Search Console evidence to prioritise content
Decide what to improve, create, retain or investigate using Search Console evidence, website context and a worked fictional SaaS example.
Search Console can show where a website already receives search impressions and clicks. It does not decide whether another page should exist. Start with the reader’s need and the page that should answer it, then use the evidence to choose the work.
What evidence Rankvia actually uses
When connected to the matching website property, Rankvia can use query and page evidence with clicks, impressions, click-through rate (CTR) and average position. Its supported planning inputs include top queries, low-CTR candidates, queries near stronger visibility, query/page gaps, growing queries and declining-page signals. Country context and the snapshot’s date range help qualify those observations.
These inputs are bounded, selected evidence, not every Search Console row or a complete account audit. A connected property does not mean every existing calendar used its data. Check the current planning state and which evidence was available. Missing or unusable data is not zero demand.
Manually compare like-for-like periods, query/page scope, country and device where relevant in Search Console. Consider seasonality and changes to search results. CTR is clicks divided by impressions; average position is an aggregate, not a fixed rank for every buyer. A metric is a reason to investigate, not proof of a content defect.
Worked example: four decisions for HarborDesk
| Candidate and existing owner | Illustrative evidence: A → B | Decision and next check |
|---|---|---|
| Location rollout guide | Impressions 1,800 → 2,200; clicks 90 → 66; CTR 5% → 3%; average position 7.4 → 7.2. | Improve the current owner only after confirming its outdated permissions instructions. |
| Moving appointments between locations; only a generic product page answers | In B: 420 impressions, 8 clicks, average position 18 for the candidate query/page pair. No suitable use-case guide found in the assumed inventory. | Consider genuinely missing use-case coverage after checking intent and current results. |
| Buffer-time policy guide | Impressions 900 → 920; clicks 45 → 46; CTR 5% in both periods; average position 6.8 in both. | Retain the useful, accurate page. No substantive deficiency has been identified. |
| Calendar connection documentation | Impressions 120 → 300; clicks 12 → 6; average position 4 → 10. | Investigate query mix, demand, access and destination before changing the content. |
Improve: repair a verified deficiency, not a percentage
In this fictional inventory, the rollout guide still describes an old permission model. The product documentation now supports location-level permissions. Correcting that explanation and its next step would help the same reader. Keep the current URL as owner and link to the separate connection instructions. The CTR change alone would not justify this decision; a changed result layout could also affect clicks.
Create: prove the gap beyond the metric
The product overview is receiving a specific migration question but does not explain moving appointments between locations. Check the existing use-case pages and current search results manually. If no page serves the decision and the offer supports it, plan a distinct use-case page with prerequisites, limits and links to the product and documentation. Absence from an export alone does not prove a coverage gap.
Retain: useful coverage is already doing its job
The buffer-time guide still answers the question accurately and has an appropriate next step. Small changes do not create a reason to rewrite it. Leave the page unchanged and observe comparable evidence later. There is no universal traffic threshold or requirement to fill a calendar slot.
Investigate: diagnose before choosing a writing task
For the connection document, inspect which queries and pages changed, whether the selected property is correct and whether the public URL works. If access, redirects or canonical configuration might be involved, a site owner or technical specialist should verify them. This is a manual investigation, not a claim that Rankvia diagnoses or automatically fixes technical SEO. No rewrite is justified yet.
Investigate CTR before rewriting a title
| Query and page | Illustrative A → B | Investigation before editing |
|---|---|---|
| “Multi-location appointment booking” → product overview; desktop | 4,000 impressions in each period; clicks 80 → 60; CTR 2% → 1.5%; average position 5.2 → 5.3. | Check whether the overview actually answers this buyer need and whether its title/snippet accurately signal that answer. A lower CTR alone does not prove a wording defect. |
| Same query and page; mobile | 5,000 impressions in each period; clicks 50 → 45; CTR 1% → 0.9%; average position 8.4 → 8.6. | Compare within this device and market. Inspect the current result context manually; do not attribute the difference from desktop solely to the title. |
| “Appointment buffer examples” → existing explanation; desktop | Impressions 8 → 10; clicks 1 → 0; CTR 12.5% → 0%. | One click produces a dramatic percentage swing. Retain a sound page and gather more comparable evidence rather than treating this as a robust optimization result. |
Check relevance, result context and accuracy separately
- Query/page fit
- Read the actual query and destination together. Does the page help choose a booking product, explain a concept or provide setup instructions? A how-to page receiving a purchase query may be the wrong owner; changing its title to promise software does not fix that mismatch.
- Position and search-result context
- Inspect important queries manually for the relevant market and device. Look at the displayed title, snippet, result types and competing answers. Average position aggregates appearances; it does not describe one identical result screen. Distinguish branded and non-branded demand and account for seasonality.
- Title and snippet accuracy
- Compare the page title, main heading, visible content and the description shown in search. Correct misleading or obsolete promises, not every low percentage. Google can derive title links and snippets from several sources and may show different snippets for different searches. Your preferred metadata is not a guaranteed displayed result.
An editorial correction is a hypothesis, not a CTR win
Assume the fictional product overview already explains location permissions accurately but its title is vague. The following candidate makes that existing subject clearer; it does not add an unsupported capability.
- Illustrative existing title
- HarborDesk - scheduling for everyone
- Candidate title, only if the page supports it
- Multi-location appointment booking | HarborDesk
- Candidate description
- Evaluate appointment booking across service locations. Review local permission boundaries, setup requirements and current plan conditions.
Check that the page actually supplies every promised detail. Record the URL, query group, filters, edit and date when a real change is made. Compare a sufficiently useful later period and note other changes; a before/after pattern alone cannot establish causation. No universal “good CTR” applies, and a longer title or new description does not guarantee more clicks.
What Rankvia uses and what stays manual
The current GSC pipeline selects bounded query/page evidence with clicks, impressions, CTR, average position, country context and date ranges. Its position-based low-CTR heuristic flags candidates for planning; it is not a universal benchmark or an automatic instruction to rewrite. Missing evidence remains missing.
The device/market comparisons and result inspections above are manual Search Console and editorial work, not a claim that Rankvia performs an exhaustive device audit, runs title experiments, automatically optimizes CTR or diagnoses search-result changes. Optional GSC can inform an opportunity and Page Plan; it does not bypass Business Profile approval, trigger a calendar rebuild or guarantee a title change.
Official guidance reviewed on 15 October 2026. These are source definitions and manual review guidance, not a live HarborDesk assessment.
Choose the action after the investigation
What Rankvia takes on, and what you review
Rankvia is a website-growth autopilot. Optional GSC evidence joins the approved Business Profile, existing pages, search-opportunity research, available search evidence and compatible AI Visibility evidence where available. It can prioritise Create or Improve work, assess page ownership and move suitable opportunities through the dated Content Calendar, Page Plans, generation and eligible supported publication.
Review the selected opportunity and Page Plan before relying on the draft. Verify product facts, limitations, page ownership and internal links. A worthwhile decision can also be no additional page, monitoring, further investigation or skipping. This example does not load these numbers into Rankvia, force the four actions or promise a particular calendar mix.
The manual comparisons above are a method a reader can follow. They are not a promise of a full analytics dashboard, exhaustive historical/device analysis, URL Inspection, technical repairs or automated Search Console configuration.
Connect at the existing point in the journey
For a new general planning entry, enter your website, create an account or sign in, let website analysis finish and review and approve the Business Profile, including website language and market. The existing calendar continuation offers the optional GSC decision. You can continue without connecting.
To connect, use a Google account with access to the matching property, complete authorization and confirm that property for this Rankvia website. Existing users can also manage it in Settings → Integrations. Interface locale does not change approved publishing language or target market.
If a calendar already exists, connecting GSC does not silently replace it. Review the existing keep-current versus rebuild decision when offered. Rebuilding is a deliberate product action with existing eligibility rules, not something this guide or its CTA triggers.
Read the connection instructionsMetric definitions and reporting limits
APPLY THIS TO YOUR WEBSITE
Build a search plan for your website
Start with the existing website analysis and Business Profile review. Search Console can add evidence later; it is optional and no example topic is preselected.
Signup or login required. Existing eligibility and review steps apply.