Single Intent URL Mapping (SIUM-1) requires every indexable URL to be the exclusive canonical destination for exactly one primary search intent. The intent is not chosen by opinion. It is read off the top ten organic results for the target query, locked before the page is written, and everything the page cannot serve at that intent is moved to a different URL.
What Single Intent URL Mapping is
Single Intent URL Mapping is an architectural governance rule: one URL serves one primary search intent, and that intent is the only thing the URL competes for. Conventional search work dilutes topical relevance by blending conflicting reader goals into one page, most often an informational guide sharing a URL with a transactional checkout. SIUM-1 replaces that blending with intent locking, which raises signal density, removes keyword cannibalization inside a cluster, and gives an answer engine an unambiguous boundary for the passage it retrieves.
The specification states the chain in one line, and every rule below is a consequence of it:
Primary query cluster [intent lock]
--> 1 dedicated canonical URL [relevance anchor]
--> section isolation [secondary support]
--> Decision Ladder Navigation [stage alignment: Orient, Choose, Prove, Rate, Act]
--> GA4 and GSC conversion loop
Two things follow immediately. A URL that cannot name its one primary intent in a single sentence is not ready to be written. And a second URL that wants the same query cluster is not a second page, it is a consolidation task.
How the primary intent is decided, and which decision stage it belongs to
The primary intent of a URL is decided by SERP Dominance Analysis, not by judgement: a query belongs to the intent that at least 60 percent of the top ten organic results already serve. Below that level of agreement the query is genuinely mixed and falls under the exceptions in the next section. At or above it, the dominant intent is mapped to one stage of Decision Ladder Navigation, which then fixes the page format and the kind of supporting sections the page may carry.
| DLN decision stage | SERP archetype footprint | Primary page format | Allowable secondary sections |
|---|---|---|---|
| Orient (O), problem definition | Guides, how-tos, explanations, featured snippets. | Comprehensive article or tutorial hub. | Cost breakdowns, tool checklists, related FAQ. |
| Choose (C), solution comparison | Top ten lists, comparison tables, feature matrices. | Comparison matrix or listicle hub. | Where-to-buy links, selection criteria, proof stack. |
| Prove (P), trust validation | Case studies, testimonials, accreditation pages. | Case study or proof architecture page. | Methodology breakdown, client results, verification. |
| Rate (R), commercial evaluation | Pricing tables, calculator tools, quotation pages. | Pricing and commercial matrix page. | Return on investment calculator, service tiers, guarantee terms. |
| Act (A), direct conversion | Product pages, category filters, checkout forms. | Money landing page or product page. | FAQ, warranty policies, trust badges, lead form. |
Reading the table as a row rather than as a column is the point. A page whose format belongs to one row while its supporting sections are borrowed from another is misaligned, and the audit in this specification is built to catch exactly that.
The three controlled multi-intent exceptions
SIUM-1 allows a single URL to carry sub-intents in three named cases, and only when a structural boundary keeps the primary relevance signal intact. Outside these three, a second intent on a page is a second page. The exceptions exist because some query clusters genuinely have no dominant archetype, and forcing a split there would produce two thin URLs where one complete URL was correct.
- Mixed SERP queries, Choose plus Orient. When the top results consistently show a hybrid of comparison tables and tutorial guides, such as a query about selecting the best of a product category, the page may combine a selection guide with a soft comparison matrix.
- Topic navigation hubs. A category hub covers many child sub-intents, but its own primary intent is locked to navigational guidance, that is, steering the reader to the next stage. The detailed sub-topics stay on separate cluster URLs.
- Task-completion support sections. A secondary FAQ or pricing block may sit inside a guide only when it directly completes the primary task and occupies less than 20 percent of the visual weight of the page.
The Section Isolation Protocol and its weight control
The Section Isolation Protocol stops a secondary intent from hijacking the primary relevance signal, and it does so with four rules that can each be checked by looking at the rendered page. The protocol is what makes the exceptions above safe: a supporting section is permitted precisely because the protocol keeps it bounded, labelled and outweighed.
- Rule 1, primary-first layout. The answer that satisfies the primary intent appears above the fold or within the first two H2 sections, and primary content carries more than 80 percent of the total text weight of the document.
- Rule 2, heading task hierarchy. Every secondary intent sits inside its own H2 or H3 whose wording declares its scope, for example a pricing specification or a frequently asked questions block, so the boundary is readable by a machine and by a reader.
- Rule 3, jump-link anchors. A long multi-section page carries a table of contents with explicit anchor links, so a crawler and a reader can isolate one passage node instead of treating the page as one undivided block.
- Rule 4, contextual call-to-action placement. Conversion prompts follow the decision order, Orient to Choose to Prove to Rate to Act, and an informational page does not force a premature commercial prompt on a reader who has not reached that stage.
The 20-point technical audit
The audit is 20 checkpoints across five domains, four per domain, and each checkpoint names both what must be true and the instrument that proves it. Naming the instrument is what stops two auditors from reaching two different verdicts on the same URL, because the disagreement then has a place to go: they compare readings rather than opinions.
Domain 1, SERP intent lock
| Checkpoint | Mandatory requirement | Verification method |
|---|---|---|
| CHK-01 Query dominance | Lock one primary target query cluster per URL, based on at least 60 percent SERP agreement. | Manual SERP inspection and Search Console. |
| CHK-02 Format alignment | Page format matches the dominant top ten SERP type and its decision stage. | SERP archetype audit. |
| CHK-03 Secondary intent cap | Secondary intents stay supporting sub-tasks and do not change the role of the page. | Content brief review. |
| CHK-04 Intent definition | The primary intent is written out in one sentence inside the content brief. | Brief governance. |
Domain 2, cannibalization governance
| Checkpoint | Mandatory requirement | Verification method |
|---|---|---|
| CHK-05 One-to-one mapping | Zero keyword overlap across URLs in the same topic cluster. | Search Console query-to-URL matrix. |
| CHK-06 Canonical hygiene | Self-referencing canonical on the primary page, duplicate parameter URLs consolidated. | Crawler and rendered HTML inspection. |
| CHK-07 Redirect mapping | Legacy URLs sharing the identical primary intent redirect permanently into the master canonical. | Server response header audit. |
| CHK-08 Split URL consolidation | Competing thin pages ranking for one query cluster are merged into a single master page. | Impression split audit in Search Console. |
Domain 3, section isolation
| Checkpoint | Mandatory requirement | Verification method |
|---|---|---|
| CHK-09 Primary-first placement | The primary answer sits above the fold or within the first 20 percent of the document text. | Rendered height audit. |
| CHK-10 Heading task scope | Secondary intents are isolated in their own H2 or H3 with a descriptive task name. | Heading tree analysis. |
| CHK-11 Table of contents | A jump-link table of contents exists for any article over 1,200 words or four section blocks. | Anchor link test. |
| CHK-12 Weight governance | Primary intent text exceeds 80 percent of the document, secondary sections stay at or under 20 percent. | Word count and text ratio. |
Domain 4, internal links and decision flow
| Checkpoint | Mandatory requirement | Verification method |
|---|---|---|
| CHK-13 Anchor precision | Anchor text matches the primary entity or intent name of the target URL, never a generic phrase. | Internal link audit. |
| CHK-14 Decision flow alignment | Orient pages link to Choose comparisons, Choose links to Prove and Rate, Rate links to Act pages. | Decision flow inspection. |
| CHK-15 Unique anchor rule | The same anchor text never points at two different target URLs. | Crawl topology audit. |
| CHK-16 Contextual placement | Internal links sit directly after the paragraph where the reader intent actually shifts. | Link context audit. |
Domain 5, analytics and quality assurance
| Checkpoint | Mandatory requirement | Verification method |
|---|---|---|
| CHK-17 Key event tracking | Key events such as a form submission or a call click are mapped and active on the target URL. | Analytics debug view. |
| CHK-18 Query mix isolation | The primary query cluster accounts for at least 70 percent of the impressions of the URL. | Search Console performance export. |
| CHK-19 Click-through expectations | Where average position is three or better but click-through is under 3 percent, the title and H1 are rewritten to match the intent. | Click-through and position analysis. |
| CHK-20 Weekly change logging | Every change to URL structure, title or sections is recorded in the weekly engineering log. | Change log registry. |
The 100-point Definition of Done
A URL passes quality assurance at 90 points or more out of 100, scored across five domains of 20 points each. The rubric is applied before deployment rather than after a campaign underperforms, which is the only point at which the cost of a wrong intent lock is still one editing session instead of one rewrite plus one redirect.
| Evaluation domain | Weight | Pass criteria |
|---|---|---|
| Intent locking | 20 pts | One primary intent locked at 60 percent SERP agreement or better, and the format matches the dominant archetype. |
| Section isolation | 20 pts | Primary content holds at least 80 percent of document weight, secondary sections isolated in headings with a table of contents. |
| Cannibalization governance | 20 pts | Zero keyword overlap across cluster URLs, duplicate parameter URLs canonicalized. |
| Internal link precision | 20 pts | Anchor text matches the primary entity name of the target, and the decision flow from Orient to Act is enforced. |
| Analytics and retrieval readiness | 20 pts | Key events active, query mix at 70 percent primary or better, and the structured data graph matches the rendered text. |
The 30-day implementation roadmap
The specification schedules its own adoption over four sprints of roughly a week each, and the order is not interchangeable. Restructuring a page before its intent is locked produces a well-built page pointed at the wrong query, and consolidating URLs before the restructure means redirecting readers into a page that still fails the isolation rules.
| Sprint | Days | Work |
|---|---|---|
| 1. Intent audit and money page isolation | 1 to 7 | Run SERP analysis across the top twenty URLs in Search Console, lock the primary intent of each, then audit cannibalization and identify split URLs. |
| 2. Primary-first restructuring | 8 to 15 | Move the primary answer above the fold and isolate secondary FAQ and pricing blocks into declared headings with jump-link anchors. |
| 3. Canonical consolidation and link alignment | 16 to 23 | Redirect legacy duplicate URLs permanently, then rewrite internal anchors across the cluster to match target entities and decision stages. |
| 4. Key event assurance and review cycle | 24 to 30 | Verify key events on every money page, inspect the query mix ratios, and start the seven-day data review and backlog logging cycle. |
Declaring the locked intent to machines
SIUM-1 requires every URL to declare its primary intent and its entity binding in a structured data graph, and requires that graph to match the rendered text word for word. The parity rule is the part that matters. A declaration that describes a page the reader never sees is not a machine-readable summary, it is a second, competing version of the page, and an answer engine has no way to tell which one it was meant to quote.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://danhnolan.com/en/sium/#webpage",
"url": "https://danhnolan.com/en/sium/",
"name": "Single Intent URL Mapping (SIUM): Rules and Implementation Strategy",
"isPartOf": { "@id": "https://danhnolan.com/#website" },
"about": { "@id": "https://danhnolan.com/en/sium/#definedterm" }
},
{
"@type": "DefinedTerm",
"@id": "https://danhnolan.com/en/sium/#definedterm",
"name": "Single Intent URL Mapping (SIUM)",
"description": "A deterministic architectural specification mapping exactly 1 dedicated URL to 1 primary search intent to maximize relevance and eliminate keyword cannibalization.",
"inDefinedTermSet": "https://danhnolan.com/en/sium/"
}
]
}
Frequently asked questions about SIUM-1
These are the questions readers ask most often about the Single Intent URL Mapping Specification (SIUM-1). Each one is answered directly from the deposited specification, in a few sentences, so that the answer can be read, quoted and cited on its own without the rest of this page.
What does SIUM stand for?
SIUM stands for Single Intent URL Mapping, and SIUM-1 is the first version of the specification. Its rule is that every indexable URL is the exclusive canonical destination for exactly one primary search intent.
How much of a page can secondary sections take?
Secondary sections, such as FAQs or pricing blocks on a guide, may take no more than 20 percent of the page. Checkpoint CHK-12 requires the primary intent to hold more than 80 percent of the text, and this FAQ is sized to fit inside that limit.
When does a page need a table of contents?
A page needs a jump-link table of contents once it exceeds 1,200 words or four section blocks. Checkpoint CHK-11 requires it so that readers and crawlers can reach each section directly.
What share of impressions should come from the primary query cluster?
At least 70 percent of a URL's Search Console impressions should come from its primary query cluster. Checkpoint CHK-18 uses this ratio to show whether the page is really ranking for the intent it was locked to.
What CTR should trigger a title rewrite?
If a page ranks in position 3 or better but its CTR is below 3 percent, checkpoint CHK-19 asks you to rewrite the title and H1 to match the intent more closely.
Can the same anchor text link to two different pages?
No. Checkpoint CHK-15 forbids using one anchor text for two different target URLs, because the same words would then point machines at two different answers.
What score must a URL reach before release?
A URL must score at least 90 of 100 on the SIUM-1 Definition of Done before production deployment, across intent locking, section isolation, cannibalization governance, internal link precision, and analytics and GEO checks.
How are duplicate URLs with the same intent handled?
Legacy URLs that share the same primary intent are redirected with a 301 into the master canonical URL, and competing thin pages are consolidated into one. Checkpoints CHK-07 and CHK-08 audit both.
Why lock one intent per URL?
Locking one intent per URL concentrates the relevance signal, removes keyword cannibalization and gives AI search a clear boundary for the passage it retrieves. A page that blends a guide with a checkout answers neither well.
How should SIUM-1 be cited?
SIUM-1 should be cited by its DOI, 10.5281/zenodo.22892377, with Danh Nolan as author. It is published under CC BY 4.0, so it may be reused with credit.
Rights, reuse and how to cite this specification
Rights and reuse for this specification are governed by the Creative Commons Attribution 4.0 International licence attached to the Zenodo deposit. You may copy, redistribute, adapt and build on the material for any purpose, including commercially, provided you give appropriate credit, link to the licence and indicate whether changes were made.
Cite this specification as: Nolan, D. (2026). Single Intent URL Mapping Specification (SIUM-1): A Deterministic 1-Intent 1-URL Architecture Standard, SERP Dominance Analysis, Section Isolation Protocol, and Decision Ladder Navigation (DLN) Governance for AI Search Optimization. Technical Report, danhnolan.com Research Group. Zenodo. 10.5281/zenodo.22892377. ORCID: 0009-0007-7906-5091. Deposited 22 September 2026 under CC BY 4.0.
The deposit is the authoritative version. Where this page and the deposited document differ, the deposited document under the DOI is correct, because that is the version other people cite and the version that carries a fixed date.