A saved link once opened the equipment instructions. After a useful new chapter is inserted, it opens the eligibility rules instead. The page still loads, every chapter is present, and the reader has nevertheless been sent to the wrong explanation.
The short answer is to separate a section’s identity from its current position. A chapter number tells readers where something sits today. A maintained section identifier lets a bookmark continue to mean the same thing when the order changes. Both need checking against the actual published content.
This focused guide extends The Gold Standard of Websites. It uses an original fictional learning guide, not an audit of a real service. Its emphasis is the practical relationship between a reader’s saved destination and a changing long article.
For the wider failure patterns, use How Web Links Fail and How Redirect Chains Work. Connect the exercises with learning that transfers into life and How X Works.
eduKateSG · Websites
Find your next learning step
Choose the question closest to your task, or follow the expanded chapters in order.
Chapters 1–3 · Define the saved destination
Separate the reader’s purpose, page address and section identity.
Chapters 4–8 · Work through a reorder
Check inserted chapters, target meaning, contents and neighbour links.
Chapters 9–12 · Preserve meaningful continuity
Handle splits, withdrawals, arrival and interaction conditions.
Chapters 13–17 · Review and transfer
Keep descriptions accurate, verify saved results and solve a new case.
Chapters 18–20 · Practise and continue
Choose a learner route, review useful questions and follow specialist guides.
Chapter contents
Define the saved destination · Chapters 1–3
Work through a reorder · Chapters 4–8
- 4. Work through a chapter insertion before changing identifiers
- 5. Separate a missing target from a target with the wrong meaning
- 6. Inspect duplicate identifiers before trusting one successful jump
- 7. Keep the contents list connected to the current article
- 8. Rebuild previous and next links from the revised sequence
Preserve meaningful continuity · Chapters 9–12
Review and transfer · Chapters 13–17
Practise and continue · Chapters 18–20
CHAPTER 1 OF 20 · Define the saved destination
1. Begin with the reader's reason for saving a section
A reader rarely saves a section because its number is intrinsically interesting. They save the answer to a question: which materials to bring, how to check a result, what happens after a request, or where the exceptions are explained. That purpose is the meaning the link should preserve.
Imagine a fictional school exhibition guide. A learner saves its equipment section before leaving home. Another person shares the same destination in a planning message. A teacher prints a short reading route. These are three ways the section acquires an audience beyond the current contents list.
The editor later improves the article by moving equipment below a new introductory explanation. The improvement should remain possible. The maintenance question is how to preserve the route while changing the order, rather than treating every old reference as an obstacle to better writing.
Start a review with a plain sentence: this saved destination should still explain the equipment needed for the fictional exhibition. It should not merely open a related page or land near a plausible heading.
That sentence gives the check a useful standard. A loading page establishes reachability at one level. The reader’s intended explanation establishes success at another. Separating them helps an editor recognise a fault that an ordinary page-status check can miss.
CHAPTER 2 OF 20 · Define the saved destination
2. Distinguish the page address from the section destination
A web address can identify a page and include a fragment after a hash sign. In an ordinary HTML section link, that fragment can identify a particular part of the document. The browser’s handling depends on the relevant document and web-platform rules.
RFC 3986's fragment definition provides the general distinction between a primary resource and an identified secondary part. The HTML Standard's fragment navigation account provides the relevant HTML processing context. These are different layers of the explanation.
For this guide’s examples, imagine one page containing the section identifier equipment. A reference ending in #equipment asks for that identified part of the page. It is not the same destination as the page address without a fragment, even though both concern the same document.
This matters when recording a problem. Saying the article opens may be accurate but incomplete. Saying the equipment link opens at the article introduction identifies the lost section route more precisely.
Keep the complete tested address in a maintenance record where appropriate, including the fragment. A record containing only the page title cannot distinguish two bookmarks into different chapters. The exercise does not require a learner to memorise URL grammar; it requires them to preserve the part that identifies the question they intended to revisit.
CHAPTER 3 OF 20 · Define the saved destination
3. Give a section an identity that survives ordinary rearrangement
Consider three different descriptions of one fictional section: equipment instructions, chapter four, and the identifier equipment. They can refer to the same section today while serving different purposes.
The title explains the section to the reader. The number locates it within the current sequence. The identifier supplies a maintained target for a link. An editor can change one without automatically needing to change the others.
Suppose the title becomes Choosing and Checking Your Equipment. If the section still answers the same underlying question, its existing identifier may remain useful. Changing every address to match every wording improvement creates avoidable work for people who saved the earlier route.
This is an editorial design choice, not a guarantee that any identifier can remain meaningful forever. If the subject changes fundamentally, preserving the old target without explanation can also mislead. Stability should preserve a relationship, not freeze an inaccurate label around unrelated content.
A useful planning question is whether this identifier names the section’s purpose or merely its current position. Names such as equipment or interpreting-results can be easier to maintain than chapter-four when chapters are frequently inserted.
Do not treat a memorable name as automatic correctness. A well-named target can still be deleted, duplicated or attached to the wrong section. Identity needs both a considered initial choice and a check after the actual change.
CHAPTER 4 OF 20 · Work through a reorder
4. Work through a chapter insertion before changing identifiers
The fictional guide initially has six chapters. Equipment sits fourth, followed by booking and confirmation. The team inserts a new chapter on preparing a question before equipment, shifting three existing chapters down one place.
| Fictional section purpose | Earlier position | Revised position | Maintained identifier |
|---|---|---|---|
| Overview | 1 | 1 | overview |
| Eligibility | 2 | 2 | eligibility |
| Choosing a task | 3 | 3 | choosing-task |
| Preparing a question | Not present | 4 | preparing-question |
| Equipment | 4 | 5 | equipment |
| Booking | 5 | 6 | booking |
| Confirmation | 6 | 7 | confirmation |
The revised article now has seven chapters. Its contents, chapter labels and previous/next sequence need updating. The equipment identifier need not change simply because equipment moved from fourth to fifth.
Check the old bookmark against the revised page. If #equipment still identifies the equipment explanation, the reader’s saved purpose has survived the insertion. The new contents can display chapter five while linking to that same target.
Now contrast an automatically renumbered scheme. If the old fourth section used #chapter-4 and the editor assigns that identifier to the new fourth section, the old bookmark now opens Preparing a Question. Nothing is missing technically, yet the destination has changed meaning.
This example shows why a link test should ask both whether a target exists and what it now identifies. The distinction becomes particularly useful on long educational pages whose chapters grow as new explanations are added.
CHAPTER 5 OF 20 · Work through a reorder
5. Separate a missing target from a target with the wrong meaning
Two failures can look similar to the person seeking equipment instructions. In the first, the equipment identifier has disappeared. In the second, it exists but has been attached to eligibility. Both break the intended learning route, but the repair questions differ.
A missing target asks whether the section moved, was renamed, was merged or was deliberately removed. A wrong target asks why the maintained identifier now points to different content. Restoring an identifier mechanically without understanding the change can repeat the mistake.
For the fictional guide, compare three checks. Does an element with the intended identifier exist? Does it occur only once? Does its associated section answer the saved equipment question? These checks address existence, uniqueness and meaning.
A structural scan can help answer the first two. Reading the destination remains necessary for the third. The exact division between tools and editorial review can vary, but the questions should remain distinguishable in the record.
If the section was intentionally retired, the appropriate result may be an explanation rather than a recreated obsolete instruction. A reader should be told what changed and where the current relevant information can be found.
The existing link-failure guide supplies the wider distinction between a broken route and a working route to the wrong resource. Here the same distinction is applied inside one evolving article, where a successful page load can make the problem unusually easy to overlook.
CHAPTER 6 OF 20 · Work through a reorder
6. Inspect duplicate identifiers before trusting one successful jump
Suppose an editor copies a chapter panel as a starting point for the new section. The copied panel retains the identifier equipment. The original equipment section retains it too. The page now contains two identical identifiers.
A quick click may appear to work in one viewing situation. That observation does not make the document’s target identity unambiguous. The duplicate should be corrected, and the intended destination should be checked again after saving.
In this fictional case, the new question-preparation section needs its own identifier. Copying a visual component should not copy its identity into a second destination. The same reasoning applies to copied contents panels, question sections and repeated lesson templates.
Count identifier occurrences in the saved document, not merely in the editor’s visible outline. A heading might sit inside another element that also carries an identifier. The published structure is what the browser receives.
This is a good learner exercise because the fault is small and concrete. Supply a simplified list containing equipment twice and ask which section should retain it. The answer should refer to the section’s purpose, rather than choosing whichever occurrence appears first.
A uniqueness check can be systematic across the article. A meaning check can then focus on the changed sections and important saved routes. Passing one kind of check should not be reported as passing both. The final account should say what was inspected and what remains outside its scope.
CHAPTER 7 OF 20 · Work through a reorder
7. Keep the contents list connected to the current article
The contents list is a map of the article’s present structure. It should show the revised chapter order and point to the intended targets. A maintained old bookmark does not excuse leaving the contents in the old order.
In the fictional guide, Preparing a Question becomes chapter four, Equipment becomes five, Booking becomes six and Confirmation becomes seven. The displayed sequence changes while the existing purpose-based identifiers continue to serve their respective sections.
Check each contents entry as a pair: the words the reader sees and the section the link reaches. Equipment Instructions leading to the booking form is wrong even if the booking form is the next useful task. The link should accurately describe its own destination.
Grouped contents also need their chapter ranges reviewed. A group labelled Chapters Four to Six becomes misleading if it now contains four through seven. A small mismatch can make a long article harder to navigate even when every individual link works.
Use a deliberate reading test. Begin at the contents, choose Equipment, confirm the heading and explanation, then return. This verifies a useful round trip rather than merely confirming that the page scrolls somewhere.
The purpose is to lower the reader’s work. They should not need to infer that an outdated label probably means the new section beside it. A clear contents map is part of the teaching, especially when readers arrive with a specific difficulty and want one relevant route.
CHAPTER 8 OF 20 · Work through a reorder
8. Rebuild previous and next links from the revised sequence
Previous and next links describe an order. Their targets should follow the article’s current learning sequence, which can change even when individual section identities stay stable.
Before insertion, Choosing a Task leads next to Equipment. After insertion, it should lead to Preparing a Question. The new chapter leads back to Choosing a Task and onward to Equipment. Equipment’s previous destination changes, while its next destination remains Booking.
Those relationships are easy to miss if the editor only updates the new chapter. A neighbouring section can retain a perfectly functioning next link that skips the added explanation. The result is an incomplete route, not a missing page.
For a simple check, write the seven section identifiers in order. For each middle section, compare its previous and next links with the names immediately beside it. At the first and last sections, check the intended beginning or onward route separately.
This procedure tests sequence, not educational quality. The article may still need a better order or a clearer explanation. Once the editor chooses the order, however, the links should represent it faithfully.
A learner can practise with paper cards before touching a website. Insert one new card, then mark which neighbour relationships change. The exercise develops a useful general habit: a local addition can affect connections on both sides, even when most of the original material remains unchanged.
CHAPTER 9 OF 20 · Preserve meaningful continuity
9. Preserve old routes only where their meaning still fits
Sometimes an identifier must change. Perhaps a vague section has become two specific sections, or an earlier identifier was attached to the wrong concept. Keeping the old route can still be useful, but its destination needs thought.
Imagine Equipment is divided into Bringing Materials and Checking Shared Devices. The old equipment bookmark referred to both. Sending it directly to one half without explanation may hide the other half of the original question.
One possible editorial solution is a visible overview at the old target, explaining the split and offering both current routes. Whether and how to implement that depends on the site’s actual structure. The important point is that the old purpose receives a comprehensible continuation.
Do not create several elements with the same identifier as a substitute for such an explanation. Nor should an old label be attached to an unrelated paragraph simply to satisfy an existence check.
For the fictional guide, ask what a person with the old bookmark reasonably expected. Then decide whether the current article can still meet that expectation, needs a short transition, or should clearly explain that the instruction has been withdrawn.
This is maintenance through meaning. It allows a resource to evolve without pretending that every historical destination has an exact modern equivalent. The decision becomes reviewable when the record names the earlier purpose, the current destination and the explanation connecting them.
CHAPTER 10 OF 20 · Preserve meaningful continuity
10. Treat a merged section differently from a deleted instruction
A merge can preserve information while changing where it lives. A deletion can remove information because it is obsolete, outside scope or no longer supported. Both may remove a heading, but they should not automatically produce the same onward message.
Suppose the fictional guide merges Booking and Confirmation into Completing Your Request. The underlying reader tasks remain present. An old booking route can reasonably lead to the part explaining booking, with suitable context for the combined chapter.
Now suppose a previously described equipment loan is no longer offered in the fictional service. Redirecting that old instruction to a general welcome section may conceal the change. A clear statement that the loan instruction is no longer current can be more useful.
The maintenance record should therefore describe the content decision before the technical action. Was the material retained, moved, split, replaced or retired? What should a returning reader understand now?
This distinction also prevents accidental restoration of obsolete advice. A person repairing a link might otherwise recreate a removed instruction because an old worksheet still refers to it. The old reference is evidence of a reader route, not proof that the old instruction remains valid.
For a classroom task, supply one merge and one withdrawal. Ask learners to propose separate destination messages. The best answers preserve useful continuity while making substantive changes visible. Neither a silent disappearance nor an automatic jump to a broad introduction explains every kind of change adequately.
CHAPTER 11 OF 20 · Preserve meaningful continuity
11. Remember that a working address does not guarantee a usable arrival
A link can identify the intended section while the arrival remains difficult to use. A sticky header might cover its heading, the surrounding context might be unclear, or a control might hide the explanation the reader needs.
These are reasons to inspect the actual journey. They are not reasons to claim that one universal scroll adjustment solves every layout. Screen size, browser behaviour, page structure and interactive components can change the experience.
In the fictional guide, test a saved equipment destination from a fresh page opening as well as from the contents list. A return visit can differ from a route taken after several sections have already been opened or read.
If the content is behind a disclosure control, follow the relevant implementation guidance and evaluate the real result. Do not assume that a visual screenshot proves keyboard or assistive-technology access. The existing tabs and disclosure localisation guide examines control identity and state in its own specialist context.
Keep the test report proportionate. A check on one desktop browser is a check on that browser under those conditions. It does not establish every device experience or technical conformance.
The practical reader question remains simple: after using this saved destination, can the person recognise where they are and reach the intended explanation? That question connects structural correctness with the actual purpose of the article.
CHAPTER 12 OF 20 · Preserve meaningful continuity
12. Separate scrolling from keyboard focus and reading order
Moving the visible page and moving keyboard focus are related interface behaviours, but they should not be treated as identical observations. A section can appear on screen without every subsequent keyboard or assistive-technology action behaving as the reviewer expects.
For a meaningful evaluation, describe the task and interaction method. Start at a known place, activate the relevant link, observe the arrival and continue using the chosen method. Record what happened rather than inferring it from the amount of scrolling.
The HTML Standard provides detailed processing rules for fragment navigation. This article’s editorial exercises do not replace that implementation reference or a suitable accessibility evaluation. Their purpose is to help writers notice which part of the experience they actually checked.
In the fictional guide, a reviewer might confirm that the equipment heading is visible after the jump. Another check might examine how a keyboard user continues to the next useful control. Those are separate statements of evidence.
Avoid a vague pass labelled accessible because the link was clickable. Accessibility concerns a wider task and appropriate methods. The established digital accessibility testing guide provides the relevant broader route.
For learners, draw three columns: visible arrival, current interaction position and next useful action. Filling them from an observed or supplied fictional record teaches precision. It also prevents a common reporting shortcut in which one successful visible effect is allowed to stand for every part of the user’s journey.
CHAPTER 13 OF 20 · Review and transfer
13. Keep shared labels accurate when an explanation changes
A maintained identifier can keep a bookmark technically useful while the words surrounding an old link become outdated. The address and its description both deserve attention.
Imagine the fictional equipment section originally concerns materials visitors bring. It is later expanded to include shared devices and access arrangements. A current contents label can be updated easily. A printed worksheet or external message may still describe the earlier narrower purpose.
The article can help by making its current scope clear on arrival. If the older information remains relevant, the reader should be able to find it within the expanded explanation. If an instruction changed, identify that change where it affects the task.
This does not require rewriting every historical message. It does require avoiding a misleading current label on routes the site controls. Review the contents, nearby references and relevant connected articles when the section’s job changes materially.
A useful editing question is whether the link description remains true after the update. If it promises a worked example, does that example remain? If it promises a checklist, has the checklist become an essay without a practical equivalent?
The point is to preserve the reader’s expectation, not a particular wording forever. A section link is a small promise about the information ahead. Changes to the destination should trigger a review of that promise as well as a check that an identifier still exists.
A concise route record makes changes easier to review. It names the saved purpose, earlier target, current destination, content decision and observed result. It should be detailed enough that another person can repeat the important check.
For the fictional insertion, record that the equipment section moved from chapter four to chapter five, retained the identifier equipment and remained reachable from its saved destination. Separately record that neighbouring previous/next links and the contents order were updated.
| Fictional route check | Required comparison | What a pass establishes |
|---|---|---|
| Saved equipment destination | Old purpose against current section | Meaningful continuity for that route |
| Contents entry | Current label against target | Correct destination from the article map |
| Previous and next links | Revised order against neighbours | Correct sequence for checked chapters |
| Identifier scan | All identifiers against duplicates | Structural uniqueness in the checked document |
Do not turn this record into an unexplained list of ticks. Where a check fails, name the mismatch. Equipment opens eligibility is more useful than navigation issue.
Likewise, preserve scope. A review of four changed routes is not an audit of every reference ever made to the page. The record should identify what was tested, the page version or date where useful, and any important unresolved condition.
This is enough to make ordinary maintenance accountable without burdening a learner with a large technical system. The record connects an editorial change with the reader-facing consequence that justified the check.
CHAPTER 15 OF 20 · Review and transfer
15. Work through a split without inventing a perfect equivalence
Take a changed fictional case. The original section Preparing Your Display is divided into Planning the Explanation and Installing the Display. One concerns ideas and evidence; the other concerns arrangements handled under the school’s actual authorised process.
An old bookmark into the combined section has an ambiguous modern destination. A reader may want either half. Automatically choosing the first new section because it appears earlier would make the technical choice look more informed than it is.
A short visible transition at the old destination can explain that the chapter has become two routes. Give each route a descriptive label. The reader can then choose the question they actually brought.
Now add a further condition: the installation instructions are no longer current. The transition should not imply that both old halves remain available unchanged. It should distinguish the retained planning explanation from the retired instruction and identify the appropriate current information route.
Ask learners which facts the editor needs before deciding. They should request the old section’s scope, the present content, the reason for the change and the intended user task. An attractive destination alone is insufficient evidence of equivalence.
This example extends the earlier insertion rather than repeating it. A move can preserve one clear identity. A split can require a choice. A withdrawal can require an explanation of absence. Recognising the difference is the transferable reasoning skill behind the maintenance procedure.
CHAPTER 16 OF 20 · Review and transfer
16. Check the saved result after publication
An intended edit and the saved page can differ. A publishing system may generate an identifier from a heading, retain an old value, alter markup or present a different structure from the editor’s preview. The result needs checking where readers encounter it.
For the fictional guide, reopen the complete saved equipment destination. Confirm the intended section, its title and its explanation. Then use its contents and neighbour links. Check the saved identifier list for duplication or unexpected changes.
If a discrepancy appears, reconcile the saved state before attempting another broad change. Repeatedly pasting a whole earlier article can remove someone else’s later improvement. The safer editorial principle is to understand the current document and make the smallest relevant correction.
This guide does not prescribe one content-management workflow for every platform. It explains why saved-result verification belongs to the task. A correct plan in a notebook cannot establish what a reader now receives.
Keep the reference material unchanged when it is designated read-only. A learning example can inform a new article without becoming an invitation to revise the example itself. The scope of the edit should remain tied to the actual authorised resource.
A useful final question is what evidence would allow a colleague to distinguish intended behaviour from observed behaviour. The answer might be a saved content comparison, a repeated route check or a short result record. Choose the evidence that answers the specific uncertainty.
CHAPTER 17 OF 20 · Review and transfer
17. Practise with a new order and an old bookmark
Try this independent case before reading the explanation. A fictional article has Overview, Materials, Method, Results and Questions. Its purpose-based identifiers follow those names. A teacher has shared the Results destination with a class.
The editor inserts Checking Measurements before Results and changes the Results title to Interpreting the Findings. The substantive result explanation remains in that chapter. Which parts need review, and must the saved Results destination change?
The revised chapter count is six. The contents order, displayed numbers, affected chapter ranges and previous/next relationships need checking. The current title should accurately describe the chapter. The identifier results can remain if it still identifies the same underlying explanation.
The old saved destination should be tested against the renamed chapter. Its continued existence is necessary but insufficient: confirm that it still reaches the findings explanation, rather than a newly inserted measurement check.
Now change the case. The editor deletes the findings because the underlying dataset was withdrawn. Keeping the identifier results on a new unsupported conclusion would not preserve the old purpose honestly. The returning reader needs a clear account of the withdrawal and an appropriate current route.
The transfer check is whether the learner changes the repair when the content decision changes. A memorised rule saying never rename identifiers is too rigid. A rule saying always regenerate them is too careless. The useful principle is to maintain a truthful, recognisable destination through the actual kind of change.
CHAPTER 18 OF 20 · Practise and continue
18. Use a learning route matched to the first confusion
If a learner is struggling, begin with page versus section. Give them two supplied destinations into one fictional document and ask what each is intended to identify. Keep all content visible and avoid adding interactive complications immediately.
Once that distinction is stable, introduce an insertion. Let the learner keep purpose-based identifiers while updating chapter numbers and neighbour links. Ask them to explain why the saved route can remain the same although its position changes.
For extension, introduce a split, a merge and a withdrawal. Each needs a different judgement about continuity. Require a short reason for the chosen destination rather than accepting a technically working jump as the whole answer.
A practical evidence check has four questions. What did the reader expect? What does the saved target now identify? What changed in the article? What observation supports the claim that the route still works for that purpose?
These questions travel beyond websites. A textbook reference, numbered worksheet, shared presentation or revised procedure can also preserve a label while changing its meaning. The specific implementation differs, but the need to connect identity, position and purpose remains.
Progress appears when a student can inspect a new example, locate the exact mismatch and propose a proportionate repair. The aim is independent reasoning about a reader’s route, not memorisation of a particular publishing application’s buttons or an ever-longer maintenance checklist.
Must the section identifier match the visible title exactly?
No. They serve related but different purposes. A title can improve while an established identifier remains meaningful. The saved destination still needs checking against the current content and structure.
Is a purpose-based identifier always safe?
No. It can be duplicated, removed or reused for a different explanation. A sensible name makes maintenance easier; it does not replace maintenance or establish that the destination remains correct.
Does a successful page response prove that a chapter link works?
No. The page can load while the fragment is missing or identifies the wrong section. Verify the whole intended route, including the information the reader expected to find after arriving.
Should every old section be kept forever?
No. Obsolete or unsupported instructions may need withdrawal. Preserve useful continuity through a clear explanation where appropriate, rather than retaining inaccurate material simply because someone once linked to it.
Does a visible jump prove accessibility?
No. It establishes an observed visible effect under the tested conditions. Keyboard operation, reading order, hidden content and the broader task require suitable evaluation and appropriately bounded conclusions.
What is the quickest useful check after reordering?
Reopen an important old destination, confirm the section’s meaning and follow its contents and neighbour links. Pair that journey with a scan for missing or duplicate identifiers in the saved document. Record which routes and conditions were actually checked.
CHAPTER 20 OF 20 · Practise and continue
20. Continue through the relevant website guides
For the whole service journey, return to Websites. For page-level failures and the difference between reachability and meaning, follow How Web Links Fail. For a resource that moves between addresses, use How Redirect Chains Work.
For changes that affect interaction, use the tabs, accordions and disclosure localisation guide and Digital Accessibility Testing. For sustaining the result, continue through Accessible Website Maintenance and Content Accessibility Governance.
The primary technical reading is RFC 3986 and the HTML Standard's navigation and fragment processing, checked on 21 October 2026. They establish technical context; the fictional chapter maps, exercises and editorial decisions in this guide are original teaching material.
To practise the broader habit, choose one saved destination in a resource you are authorised to review. State its purpose before testing it, describe the current arrival and name one limit of your check. That is a small, concrete example of learning that transfers into life.