Commercial Keyword Knowledge Base — Internal Link Rules defines how the SN Engineering portal should connect technical, commercial, regional and procurement content into a coherent knowledge system.
Primary Objective
The objective is to help users and search engines understand the relationship between lightning protection concepts, products, applications, industries, government departments, locations, standards, FAQs, comparisons, calculators, resources, case studies and tenders.
Entity Layer
Products, systems, standards, applications, industries, departments, locations and services.
Intent Layer
Informational, comparison, commercial, local, tender, troubleshooting and maintenance intent.
Link Layer
Parent-child links, related-topic links, product-application links, location-service links and FAQ support links.
Quality Layer
Uniqueness, accuracy, evidence, crawlability, schema, freshness, conversion and review status.
Recommended Internal Link Rules
- Every detail page should link to one primary parent hub.
- Every pillar page should link to relevant products, applications and FAQs.
- Product pages should link to applications, industries, comparisons and tender resources.
- Location pages should link to actual services and regionally relevant applications.
- Government pages should link to tender, BOQ, product and application pages.
- Standards pages should link to technical guides without reproducing copyrighted text.
- FAQ pages should support a pillar or product page rather than remain isolated.
- Pages with no meaningful unique value should not be indexed only to increase count.
Suggested Data Fields
| Field | Purpose | Example Use |
|---|---|---|
| Page Type | Classify the URL | Pillar, product, city, FAQ or tender |
| Primary Entity | Identify the main subject | Type 1 SPD or airport |
| Primary Intent | Match the user need | Price, design, comparison or tender |
| Parent Hub | Maintain hierarchy | Products or applications |
| Related Entities | Generate contextual links | SPD, panel, earthing and data lines |
| Review Status | Control publication | Draft, reviewed, published or hold |
Quality-Control Checklist
- Unique title, meta description, H1 and canonical.
- No empty or misleading pages.
- No unsupported project, approval or certification claims.
- Clear parent hub and relevant contextual links.
- Valid sitemap entry and crawlable navigation.
- Useful content that matches the stated search intent.
- Original evidence added to priority pages.
- Search Console performance reviewed after publication.
Measurement Framework
Track index status, impressions, clicks, click-through rate, average position, enquiries, assisted conversions, orphan pages, crawl depth, broken links, duplicate intent and content freshness.
Target Keywords
Frequently Asked Questions
Should every generated page be indexed?
No. Only pages with useful, distinct and reviewed content should be indexed.
How many internal links should a page contain?
There is no fixed number. Links should be relevant, contextual and helpful to users.
Can AI-generated structure replace technical review?
No. Engineering accuracy, evidence and project-specific review remain necessary.
Related Knowledge Pages
Master Portal Optimisation
Use the manifest and link map to connect reviewed pages during the final merge.