Writing clear explanations
Explain what a thing is before telling someone how to apply it.
A definition identifies a thing and its boundaries. A process explains who acts, under which starting conditions, in what order and toward what result. Preserve negation, exceptions, time and quantity limits when changing prose into either form. Formatting must not change the rule.
Free learning from Semantec SEO.
Choose the answer structure from the question.
A definition answers what a term means and how it differs from the nearest confusion. A process answers how an actor carries out a task. A comparison helps choose between alternatives. A diagnostic route helps identify a cause or next check. These jobs can appear on one page, but they should remain recognizable.
Write the central relationship before choosing the component. If the content describes a condition, turning it into a numbered action can make it sound like something the reader should do. If it describes an optional action, turning it into a definition can make that action appear universally necessary.
A short opening can identify the concept and state when the process applies. The detailed sequence follows after the prerequisites. The reader should understand why the process is relevant rather than encounter an instruction list whose purpose is left implicit.
This editorial separation does not promise a particular search presentation. A list, table or definition paragraph is an answer format, not an entitlement to a snippet, ranking or external citation.
Build a definition with boundaries.
A useful definition names the term, gives its relevant type or role, states the defining relationship and includes the condition that limits it. It also distinguishes a common near miss when that confusion would affect the reader’s decision.
For the technical example on this page, a canonical URL is the URL selected as the representative of a group of duplicate or very similar pages. A publisher can indicate a preferred representative, but Google can select another URL. The canonical is not simply whichever URL an editor likes most.
The example follows Google’s canonicalization documentation. It does not imply that every page should point to one preferred page across an entire site. The group of equivalent content is part of the definition’s scope.
Keep the definition separate from installation details such as where a content management system exposes an annotation field. A person can understand the concept before knowing how a particular system implements it. The setup route must use the supported system and current source.
Turn procedural prose into steps without losing conditions.
Before writing steps, identify the actor, starting inputs, permission, scope, dependencies and intended output. Separate an unconditional action from a decision branch. Put a stop condition before the action it prohibits.
Preserve the original force of the statement. “May” describes permission or possibility; “must” describes a requirement. “Do not” is not a stylistic hedge. A rule that applies only after approval cannot become the first action in an unrestricted process.
Keep quantities, units and timing attached to the action they constrain. “At most 200 rows” includes the boundary of 200; “fewer than 200” does not. “Before export” and “within ten minutes after export” describe different timing. A format conversion must not silently change either relationship.
Use numbered steps when order is meaningful. Use a checklist for independent checks that do not form a necessary sequence. If the route branches, state the deciding condition and the next action for each supported case. Do not hide a branch inside a general heading such as “Continue.”
Worked example: separate a canonical definition from its decision route.
The following URL set is fictional: /workshop-room and /workshop-room?campaign=mail show the same room information. A separate page, /equipment-hire, describes another service. The example is for explaining answer structure; it is not a live site inspection.
Mixed draft: “A canonical URL is where you add a tag, pick the main page, change the sitemap and point other URLs to it so the right page ranks.” This mixes a concept with actions, omits the boundary of duplicate content and claims an outcome the annotation cannot guarantee.
Repaired definition: “A canonical URL represents a group of duplicate or very similar pages. For the fictional room pages, the publisher can indicate /workshop-room as the preferred representative; that preference does not guarantee Google’s selection.”
The editorial decision route is then separate: identify the URL set and its content; check that the proposed members are duplicate or very similar; choose the supported representative; use the appropriate canonicalization method in the supported system; and verify the emitted signal and the target. Follow the linked technical documentation for setting up the signal rather than treating this writing example as a complete deployment recipe.
The bridge between the blocks is explicit: apply the route only after identifying a suitable set of equivalent pages. If the equivalence check fails, stop that route and investigate the page’s distinct purpose. The process now follows a stated condition instead of implying a universal action.
Check the worked example.
| Element | Definition block | Process or exception block |
|---|---|---|
| Subject and scope | Representative of duplicate or very similar pages | Check equivalence before proceeding |
| Actor | Publisher indicates a preference; Google selects a canonical | Do not describe the preference as a guaranteed selection |
| Prerequisite | A suitable set of equivalent content exists | Stop when the proposed target has another purpose |
| Negation or exception | Not every preferred page is a canonical target | Different equipment-hire content fails the example test |
| Source and review | Current provider documentation | Verify the emitted signals in the supported system |
Show where the default route is inappropriate.
In the fictional set, /equipment-hire is not an appropriate canonical target for the room page merely because the publisher considers it more commercially useful. It describes different content. The counterexample makes the condition that pages are duplicate or very similar visible instead of allowing “preferred” to mean “most desirable.”
Canonicalization is also different from redirecting a visitor or removing a page. A reader who needs an unavailable URL moved elsewhere has a different technical question. Do not replace that question with an annotation instruction because the terms are often discussed together.
Language versions need their own review. Google documents localized alternatives separately. Do not treat a translation as disposable repetition simply because it covers the same topic; the intended audience and language relationship can change the appropriate technical setup.
An exception should identify the condition, the affected action and the next valid route. “There are exceptions” without an explanation does not help the reader decide. If an exception is outside the page’s supported scope, name the dependency and link to the source rather than inventing a workaround.
Test a conversion with time, quantity and an exception.
This additional review rule is fictional. It illustrates format preservation and is not a required Semantec SEO or external platform policy.
Original prose: “An editor may approve at most 10 definition records in one review batch, but only after a reviewer has checked each record’s sources within the previous 7 calendar days. The editor must not approve a record with an unresolved conflict. If a source changes after its review, hold the affected record for another review even when the 7-day condition is still met.”
- Confirm that a reviewer checked the sources for each proposed record no more than 7 calendar days before the approval decision. Hold any record that lacks that review.
- Limit the proposed review batch to at most 10 definition records. This limit is per batch, not per day or per editor.
- Check for unresolved conflicts and source changes after review. Hold each affected record; a source change requires another review even inside the 7-day period.
- The editor may approve the remaining eligible records. This permission does not require approval and does not authorize publication.
The converted list preserves the editor as approver and the reviewer as source checker. It keeps the inclusive limit of 10 records, the unit of calendar days, the timing relative to approval, the prohibition on unresolved conflicts and the exception for a changed source. “Approve 10 reviewed records” would lose nearly every one of those conditions.
Check the converted answer against its source.
Place the original passage and the formatted version side by side. List actors, actions, objects, prerequisites, negations, exception clauses, units and time limits. Check that each one is still present and still qualifies the same claim.
Test a normal case, a boundary case and a case that must stop. In the canonical example, the normal case is the duplicate room URL; the stop case is the different equipment-hire page. A page that is only superficially similar needs a content review rather than an automatic decision.
Then read the definition alone and the process alone. Each should state its scope without requiring an unsupported inference from the other. They can share a source and a link, but the process should not quietly broaden the definition.
Keep a format record with definition job, process job, shared evidence, bridge, scope and review owner. The record lets the next editor see what the definition means, when the process applies and which conditions need another check.
Sources and the next writing decision.
Read Google’s canonicalization overview, canonicalization methods and localized versions guidance. The worked examples and review records are Semantec SEO teaching material. They do not report a client outcome, live experiment or measured search effect.
Continue with opening answer and introduction. Return to the writing and content composition overview or the semantic SEO learning overview.