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

Category: Insurance definitions · Reviewed by Al Jabbar, Broker · Specialist Risks · Last reviewed May 2026

This file is internal. It catalogues the 30 ultra-long-tail definition articles drafted for the /learn/ or /glossary/<slug>/ URL tree, with target query, search-intent classification, the principal internal links each article should receive, and a paced publishing schedule (two per week for 15 weeks) designed to avoid duplicate-content / thin-content perception during indexing.

All 30 articles are stored as siblings of this file in article-drafts/definitions/.

How the cluster fits the wider site

These articles go deeper on a single term than the consolidated glossary page does. The glossary remains the hub; each of these is a spoke. To prevent self-cannibalisation:

• Each definition page links up to /glossary/ and to the relevant pillar (/the-ultimate-uk-professional-indemnity-insurance-guide-2026/, /the-ultimate-uk-solicitors-pi-guide-2026/, /the-ultimate-uk-architects-pi-guide-2026/, /the-ultimate-uk-accountants-pi-guide-2026/, /the-ultimate-uk-pi-claim-management-guide-2026/).
• The glossary entry for each term should carry a short 2–3 sentence summary and link down to the definition page with anchor text matching the page’s target query.
• Sector pages (/sectors/architects/, /sectors/accountants/, /sectors/solicitors/, /sectors/surveyors/, /sectors/consultants/) link across to the most-relevant 4–6 definitions in this set.

The 30 articles

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

Search-intent classification (consolidated)

• Informational — pure definition (16 articles): aggregate limit, each-and-every, retroactive date, policy period, civil liability extension, pollution exclusion, cyber exclusion, dishonesty extension, defamation extension, loss of documents, breach of contract, IP infringement, fines and penalties, contract works, aggregation of claims, utmost good faith.
• Commercial investigation (5 articles): run-off cover, claims-made vs occurrence, defence costs in/out of limit, excess vs deductible, following form excess layers.
• Regulatory / sector-specific (5 articles): Consumer Duty, SRA qualifying insurers, ARP, SRA MTC, FOS jurisdiction.
• Transactional / decision-stage (3 articles): mid-term adjustment, circumstance notification, renewal warranties.
• Regulatory / failure scenario (1 article): FSCS PI cover.

Commercial-investigation and decision-stage pages should carry the heaviest internal-link weight from sector pages, the pillar guides, and the contact CTA, because they sit closest to a quote enquiry.

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 this set (via the “Related definitions” block)
4. At least one sector page where the term is most material
5. /contact/ — for users at decision stage

Recommended inbound links (where the article should receive links from):

Tight internal-link clusters (group together)

• SRA / solicitors regulatory cluster: 24, 25, 26 (qualifying insurers, ARP, MTC) — these three should be heavily cross-linked because the queries overlap and a user searching one is likely to want the other two.
• Limits and money mechanics cluster: 1, 2, 6, 7 (aggregate, each-and-every, defence costs, excess) — cross-link aggressively; this is the foundational quartet.
• Trigger / time cluster: 3, 4, 5, 8 (retroactive date, run-off, claims-made vs occurrence, policy period) — these explain how PI responds to time, and cross-linking them keeps users in the cluster.
• Renewal & disclosure cluster: 29, 30, 21 (renewal warranties, utmost good faith, circumstance notification) — these reinforce the duty-of-disclosure story and should sit together in any renewal guide.
• Extensions cluster: 9, 11, 12, 13, 14, 16, 18 — these are all extension-style queries; sector pages that touch on creative/digital work should link to 11, 13, 16; sector pages that touch on construction should link to 9, 10, 18.

Suggested publishing schedule (2 per week × 15 weeks)

Schedule paces publication so Google indexes the cluster gradually, avoids two near-identical queries hitting the index in the same crawl window, and front-loads the highest-volume / commercial-intent terms.

Pacing principles applied

• No two articles from the same tight cluster published in the same week (e.g. aggregate limit + each-and-every would compete; instead they sit in weeks 2 and 3).
• High-volume / commercial-intent terms first (weeks 1–5) so the cluster’s top earners are indexed early and accumulate backlinks.
• Niche / lowest-volume terms last (weeks 13–15) because they benefit from the cluster’s accrued topical authority before publication.
• Regulatory cluster (SRA) spread across weeks 2, 4, 6 to avoid Google treating them as bulk-generated boilerplate.
• Renewal warranties + utmost good faith are deliberately separated (week 11 vs week 1) because they cover overlapping legal ground (Insurance Act 2015); pairing them risks duplicate-content perception.

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: check Search Console CTR per article at week 4 and week 12; rewrite SEO title and meta description on any page with impressions but CTR below ~3%.
3. Cannibalisation watch: monitor for ranking flips between a definition page and the corresponding glossary section. If they swap ranks repeatedly, consolidate the glossary entry into a 2–3 line summary and pass authority to the definition page via internal link.
4. Quarterly review: update the last_reviewed date in frontmatter every six months at minimum; faster if regulatory position changes (e.g. SRA MTC amendment, Consumer Duty closed-products rule changes, FOS award limit movements).
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 Apex’s Bristol address, FCA firm reference 724952, and Companies House number 07014570 render correctly on every page footer.

File inventory

All 30 article files plus this index live in article-drafts/definitions/. File-level word counts (including YAML frontmatter, JSON-LD blocks, and footer) range from approximately 2,476 to 3,138 words. Prose-only word counts sit in the briefed 1,500–1,800-word band per article. Each file contains:

• YAML frontmatter with title, slug, focus_keyphrase, seo_title (≤60 chars), meta_description (155–160 chars), og_image, category “definition”, tags, internal_links, last_reviewed “May 2026”.
• H1 closely matching the target query.
• A 40–60-word opening paragraph engineered for featured-snippet capture.
• Six to eight H2 sections (definition, how it works, worked example with realistic UK figures, when it matters most, common variations, related concepts, FAQ).
• Six to eight FAQ Q&A 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, contact email and phone.
• A “Related definitions” cross-link block.

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