PI Definitions Cluster — Batch 2 Index, Internal-Link Map, and Publishing Schedule

Category: Insurance definitions · Reviewed by Matt Bartlett, Director · Founder · Last reviewed May 2026

This file is internal. It catalogues the 30 ultra-long-tail definition articles in article-drafts/definitions-batch-2/, the natural sequel to the 30-article cluster indexed in article-drafts/definitions/definitions-index.md.

Batch 2 deepens coverage of four areas the original cluster did not exhaust: legal-basis-of-liability concepts (tort vs contract, duty of care, joint and several, proportionate, contribution, economic loss, consequential loss, voluntary assumption), policy-mechanics and timing terms (policy trigger, notification deadline, ERP, indemnity period vs policy period, cancellation, deductible), specialist cover extensions (loss of fees, mitigation, rectification, restitution, investigation, cyber/PII), and market-structuring terms (tower, quota share, coinsurance, binders/coverholders, combined liability, worldwide jurisdiction, territory, wasted costs, quantum, loss adjuster vs claims handler).

All 30 files plus this index live in article-drafts/definitions-batch-2/. Each follows the format established for batch 1: YAML frontmatter (title, slug, focus_keyphrase, SEO title, meta description, og_image, category, tags, internal_links, last_reviewed), H1 matching the target query, 40–60-word featured-snippet opener, H2 sections (definition, how it works, worked UK example, when it matters, common variations, related concepts, FAQ), 6–8 FAQ pairs, three JSON-LD blocks (Article, DefinedTerm, FAQPage), E-E-A-T footer naming Apex Insurance Brokers Ltd (Bristol, FCA firm reference 724952, Companies House 07014570), and a “Related definitions” cross-link block.

How batch 2 fits the wider cluster and site

Batch 2 deepens the long-tail by addressing terms with even lower search volumes (commonly 10–80 queries/month) but cleaner, less competed SERPs. Where a batch-2 term overlaps a batch-1 term (e.g. deductible vs excess; indemnity period vs policy period; policy trigger vs claims-made vs occurrence), the batch-2 article treats the term as the lead concept, with a clear cross-link back to the batch-1 piece on the related concept. Cannibalisation risk is mitigated by:

• Each batch-2 article taking a distinct angle (deductible focuses on the specific question of fixed-sum self-insured retention; excess sits at a different attachment frame in batch 1).
• Strict one-term-per-page focus.
• Strong inter-article internal linking that signals the topical relationships.
• Schedule pacing that does not pair near-overlap terms in the same week.

Batch-2 articles link up to /glossary/, across to the most-related batch-1 definition where applicable, out to relevant pillar guides and sector pages, and inward to 3–5 batch-2 siblings.

The 30 articles

Volume bands are estimates based on UK Search Console patterns for similar long-tail B2B insurance queries and should be checked in Ahrefs or Semrush before publication.

Search-intent classification (consolidated)

• Informational — legal-basis-of-liability (8 articles): tort vs contract, voluntary assumption, proportionate, joint and several, contribution rights, breach of duty of care, economic loss, quantum.
• Informational — pure definition / policy mechanics (8 articles): combined liability policy, professional indemnity deductible, policy territory, policy trigger, indemnity period vs policy period, quota share, coinsurance, binders and coverholders.
• Informational — cover scope and extensions (7 articles): consequential loss, restitution, rectification cost, mitigation cost, loss of fees, investigation cost, wasted costs orders.
• Informational — claims process (1 article): loss adjuster vs claims handler.
• Commercial investigation (4 articles): worldwide jurisdiction, extended reporting period, tower program, cyber PII extension.
• Decision-stage / transactional (2 articles): notification deadline, cancellation clause.

Commercial-investigation and decision-stage pages should carry the heaviest internal-link weight from sector pages, pillar guides, and the contact CTA, because they sit closest to a quote enquiry or active claims event. The legal-basis-of-liability group should be heavily cross-linked internally because users searching one term are likely to search several.

Internal-link recommendations

Each article must link out to:

1. /glossary/ — anchor: “PI insurance glossary”
2. Relevant pillar guide (default: /the-ultimate-uk-professional-indemnity-insurance-guide-2026/)
3. Three to five sibling definition articles in batch 1 or batch 2 (via the “Related definitions” block)
4. At least one sector page where the term is most material
5. /contact/ — for users at decision stage (notification deadline, cancellation, tower, ERP, cyber)

Recommended inbound link sources

Tight internal-link clusters (group together)

• Legal-basis-of-liability cluster: 2, 6, 11, 12, 13, 14, 15 — the lattice of how liability arises and is shared. These should be heavily cross-linked because users searching one are likely to want several. Group 12 (joint and several) and 11 (proportionate) at the top of the cluster as the central conceptual pair.
• Money mechanics cluster: 3, 16, 24, 25 — deductible, consequential loss, restitution, indemnity period. Cross-link with batch-1’s “Limits and money mechanics” cluster (aggregate, each-and-every, defence costs, excess).
• Cover scope and extensions cluster: 16, 24, 26, 27, 28, 29 — what the policy positively responds to beyond simple defence/indemnity. Cross-link with batch-1 extensions (civil liability, dishonesty, defamation, loss of documents, IP, contract works).
• Market structuring cluster: 1, 17, 18, 19, 20, 21 — combined liability, ERP, tower, quota share, coinsurance, binders. Cross-link with batch-1’s following-form excess layers and FSCS.
• Notification and process cluster: 9, 10, 22, 23 — loss adjuster vs claims handler, notification deadline, cancellation, policy trigger. Cross-link with batch-1’s circumstance notification, MTA, utmost good faith, renewal warranties.
• Cyber cluster: 30 plus batch-1’s cyber exclusion — pair on every page that discusses cyber.

Suggested publishing schedule (2 per week × 15 weeks)

Pacing front-loads the highest-volume commercial-intent and decision-stage terms, splits same-cluster terms across weeks to avoid duplicate-content perception, and reserves the lowest-volume niche terms for later weeks when the cluster has accumulated topical authority.

Pacing principles applied

• No two articles from the same tight cluster published in the same week, except weeks 11 (territory + worldwide jurisdiction, which together form a coherent decision pair and should be indexed together to support each other’s ranking).
• Highest-volume / commercial-intent terms first (weeks 1–6).
• Legal-basis-of-liability spread across weeks 1, 2, 3, 7, 8, 9 so the cluster builds organically without bulk-publication risk.
• Cover-scope / extension terms spread across weeks 4, 6, 7, 9, 10, 12 so they reach a common conceptual hub but do not flood any one renewal cycle.
• Most niche / lowest-volume terms last (weeks 13–15) to benefit from cluster authority.

Post-publication checks

1. Indexation: confirm each article is indexed within 14 days via Google Search Console URL inspection. If not, request indexing.
2. CTR monitoring: at week 4 and week 12, check Search Console CTR per article and rewrite SEO title and meta description on any page with impressions but CTR below ~3%.
3. Cannibalisation watch: the highest cannibalisation risks in batch 2 are (a) professional indemnity deductible vs batch 1’s excess vs deductible, (b) PI policy trigger vs batch 1’s claims-made vs occurrence, (c) PI indemnity period vs policy period vs batch 1’s policy period, (d) cyber PII extension vs batch 1’s cyber exclusion, (e) notification deadline vs batch 1’s circumstance notification. Monitor ranking flips and consolidate or pass authority through internal linking if any pair swaps ranks repeatedly.
4. Quarterly review: update last_reviewed in frontmatter every six months, faster if a regulatory position changes (Building Safety Act 2022 amendments, FCA Section 166 procedural changes, SRA MTC amendments, UK GDPR amendments).
5. Schema validation: run each page through Google’s Rich Results Test for FAQPage and Article. DefinedTerm is not a Rich Results type but is a valid schema.org type and helps semantic search.
6. E-E-A-T audit: confirm Bristol address, FCA firm reference 724952, and Companies House number 07014570 render correctly on every page footer.
7. Inter-batch link audit: every batch-2 page that overlaps a batch-1 term must carry a forward link to the relevant batch-1 piece (and vice versa). A spreadsheet should track these and be checked after each weekly publication.

File inventory

All 30 article files plus this index live in article-drafts/definitions-batch-2/. Each file follows the format established for batch 1, with one-term-per-page focus, plain-English UK PI explanation, worked UK examples where appropriate, six-to-eight FAQ pairs, three JSON-LD blocks (Article, DefinedTerm, FAQPage), and the standard E-E-A-T footer naming Apex Insurance Brokers Ltd, Bristol, FCA firm reference 724952, Companies House 07014570.

Document owner: Apex Insurance Brokers Ltd Last reviewed: May 2026