Search visibility: responsibilities and practical exercise
SEO examines whether pages can be discovered and answer the searches they target. It connects content, structure, technical access and visibility observations. Recommendations should identify affected pages, expected effects and evidence for tracking changes without promising rankings.
These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.
Improve discovery and understanding of useful pages by search engines and visitors through technical diagnosis, search needs, answer quality and measurement.
Typical activities
Review crawling, indexing, URLs and internal links.
Identify missing or redundant answers from audience needs.
Prioritise corrections and interpret performance in context.
Responsibilities to agree with the team
SEO cannot guarantee rankings, traffic or AI citations. Work with development, writing and analysis to connect recommendations with usefulness and observations.
A first piece of work to demonstrate
Document an indexing or journey issue, propose a correction and explain its follow-up.
This is an editorial description of common activities. Job titles and scope vary across teams; it is not a certification framework.
Examine a family of pages whose titles and contents are very close.
Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.
Inventory URLs, their objectives and their exploration status.
Look for duplicates and pages that do not meet a separate need.
Prioritize corrections with one justification per page.
Define a measure that distinguishes observed change and assumed cause.
Deliverable and checks
Provide an inventory of similar pages, their intent, technical observations and consulted sources. For every proposed retention, merge or fix, state the problem, any destination and post-change check. Separate observed facts from causes still requiring testing.
Take a recommendation and verify that it identifies a URL and reproducible action. After the fix, check technical behaviour and then search observations within a comparable scope. A change in clicks alone does not establish its cause.
A ranking result alone does not prove the effect of an action. Do not announce a guaranteed position and document the context of the measurements.
Collaboration to explore: Web writing.
Fictional deliverable excerpt : A priority-page list connects the audience question, existing content, information to add and useful internal links. Recommendations promise neither rankings nor AI citations.
What passes between the roles : Share changed pages and their dates alongside measurement definitions. An observed increase alone does not establish the effect of an SEO action; other changes and data limitations need examination.
Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.
Sample excerpt
Fictional example: one page over a defined period.
Impressions: 1,200.
Clicks: 24.
Clicks / impressions: 2%.
Investigate: queries, relevance and contextual changes.
Another fictional record, same scope: 2,400 impressions and 36 clicks.
Result: 1.5%, down 0.5 percentage points, while clicks increase by 12.
What the author should be able to explain
The ratio concerns impressions in this record, not all internet users.
Use the same scope when comparing another period.
A change does not by itself establish the effect of an editorial revision.
Does this 2% rate show that the page is good?
This fictional figure supplies neither a market benchmark nor a quality score. Examine queries, intent, periods and useful actions after the click before recommending work. Show volumes alongside rates: 36 clicks versus 24 is a 50% increase, but clicks/impressions falls from 2% to 1.5%. This does not attribute the change to edited copy; also compare available queries, devices and periods.
Assess the quality of the work
For the exercise, a useful page has little visibility and someone proposes several near-identical variants. First distinguish technical access, indexability and content relevance. The deliverable should explain an observed problem on a precise URL and interpretation limits without promising a position from a wording change.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
Assess the quality of the work
Skill
Evidence to examine
Failure to spot
URL diagnosis
Identify the examined URL, HTTP status, crawling or indexing instructions and available observations. Distinguish direct findings from third-party tool estimates.
An inaccessible page receives only keyword advice, or an indexing instruction is treated as a guarantee of appearing in results.
Intent and distinct value
Connect the page with a real question, verifiable answer and next step. Compare existing content before proposing another address.
Near-identical pages target wording variants without adding information or addressing a distinct reader need.
Measurement
Metric, period and competing changes are recorded.
A third-party estimate is presented as actual received traffic.
Landing Page
Map a need to a useful URL, its evidence and the reader’s next action.
The recommendation distinguishes crawling, indexing and performance; it promises neither rich results nor rankings.
A focused next step
Take one URL and connect a recommendation with its supporting finding. Retain measurement context, then check access and content after correction. Interpret subsequent observations against period, queries and concurrent changes; an improved result alone does not establish that this change caused the entire effect.
Provide separate URLs per language and links for choosing an edition. Redirecting on an assumed language can prevent access to a version. Translating only navigation and footer does not translate the main content.
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
A review case to reproduce
The canonical targets another intent
Situation to examine
A distinct service page points its canonical to a different service while links and sitemap still present it as independent.
Proposed check
Inspect content, canonical URL, HTTP status and internal links together. Clarify each URL’s purpose before correcting. Check sitemap and language versions, then observe reports without promising immediate indexing.
Evidence to retain
An inventory connects useful pages with intent and the chosen canonical. Redirects and links do not contradict the decision.
Fictional finding example
/service-a/ describes a distinct service but its canonical points to /service-b/. Internal links and the sitemap still promote /service-a/.
Interpret this outcome
Document both pages’ purposes before deciding the canonical. Align signals afterwards; this guarantees neither Google’s final choice nor immediate indexing.
Three complementary checks
Fictional cases: adapt these expectations to your test contract and retain the limits of the check.
1Described intent
2Reconciled signals
3Observed selection
Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.
Scenario variations and expected evidence
Variation to test
Expected result in this case
Evidence to hand over
Two genuinely distinct services
Document each intent before choosing a canonical
Content-to-URL mapping
A copy has a campaign parameter
Examine equivalence with the reference page
Compared content and chosen canonical
Signals have been corrected
Align links, sitemap and language versions
Signal inventory and search-engine selection follow-up
Decision to hand over : Consistent signals guarantee neither Google’s canonical selection nor immediate indexing.
In-depth exercise: Audit a family of demo pages from its internal links to its rendering. Compare main topic, title, description, canonical URL and structured data. Test a moved page and a deliberately non-indexable page. For a multilingual site, check that the language alternatives correspond to the same subject. An optimization proposal should improve understanding or discovery of content; Do not announce a ranking gain that the exercise cannot measure.
What to deliver with your work
Inventory of URLs and expected statuses
Status of titles, descriptions and canonical links
Internal link controls and language variants
Recommendations with proof and method of verification
Acceptance criteria
These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.
The canonical URL designates an accessible and relevant page.
The title and description are specific to the topic of the sheet.
A redirection directly joins the useful destination.
Classify recommendations by observed impact and ease of verification. Give the URLs concerned as well as the proof of the defect, rather than a list of generic tips. After correction, retry status, render and links checks. Distinguish local measurements from engine-dependent indexing observations: A valid HTML does not prove that the page is indexed or better ranked.
Distinguish technical page discovery from content usefulness. Choose work according to the observed problem without promising rankings or inclusion in a generated answer.
Discovery and indexing corrections
When to choose it
Useful when status codes, links, canonical URLs or robots instructions conflict. First check which version should be accessible.
What to plan for
Record URLs and observed signals. Corrections support discovery without guaranteeing appearance in results.
Enrichment of a content collection
When to choose it
Suitable when pages fail to meet needs or duplicate each other. Map questions and available information before creating URLs.
What to plan for
Check sources, internal links and translations. Plan to merge or remove pages with no distinct purpose.
A risk to anticipate
An AI answer or search snippet varies with context. An isolated observation does not establish stable visibility or lasting attribution.
How to decide
Record a baseline and link each change to a hypothesis. Monitor effects and limitations without attributing every development to one action.
Compare pages, intentions and investigated problems using available data. Audit, implementation and content production are distinct services.
Recurring operation
Define monitoring and decisions attached to metrics. Separate delivered work from traffic changes; a fixed fee guarantees neither rankings nor AI citations.
Exit and handover
Request priorities, evidence and change history. Recover authorised access and monitoring methods without publishing keys; a keyword list does not restore the entire approach.
How can a fix be proposed without promising rankings?
Connect a URL to a question, an observed obstacle and a verifiable change: access, title, answer, link or canonical. Define the post-release check and monitoring limits. A technical fix can be verified without immediately attributing a traffic change to that action alone.
What if two pages answer the same intent?
Compare their answers, audiences and evidence before merging. A different keyword does not necessarily justify two pages. If they are merged, keep useful information, handle the old URL and update internal links to the final destination.
Is a page needed for every search variation?
A new page serves a distinct need with its own information. If variations lead to the same answer, a structured page may suffice. Avoid near-identical page series and focus links on genuinely useful content.