TASK REPORT – JKRS ALIGNMENT TO MASTER (v2)

CORE RULE (NON-NEGOTIABLE)

• DO NOT change URL structure
• All improvements must work within existing live URLs

🎯 OBJECTIVE

Align current JKRS Jekyll project with Master Report best practices without affecting live URL structure.

🔍 GAP ANALYSIS → TASKS

1. CONTENT QUALITY & UNIQUENESS

Issue - Potential duplication across location pages - Generic blocks reused

Tasks - [ ] Ensure each location page has unique intro (town-specific) - [ ] Inject location-specific signals (nearby areas, landmarks) - [ ] Remove/avoid repeated boilerplate blocks

2. PAGE STRUCTURE (SEO)

Issue - Possible multiple H1s / inconsistent headings

Tasks - [ ] Enforce exactly ONE H1 per page - [ ] Standardise H2/H3 hierarchy - [ ] Ensure titles are 50–60 characters

3. INTERNAL LINKING

Issue - Inconsistent or weak internal linking

Tasks - [ ] Add contextual internal links between nearby locations - [ ] Ensure all links are relative (Jekyll-safe) - [ ] Remove broken links - [ ] Standardise anchor text (natural, not spammy)

4. DETERMINISTIC GENERATION

Issue - Potential randomness in page generation order

Tasks - [ ] Sort all location inputs before generation - [ ] Ensure consistent ordering of: - Nearby locations - Services - [ ] Prevent content shuffling between builds

5. DATA-DRIVEN STRUCTURE

Issue - Hardcoded content limits scalability

Tasks - [ ] Move location data into structured data files (_data/*.yml or .json) - [ ] Refactor templates to consume data - [ ] Eliminate duplicated template logic

6. BUILD STABILITY

Issue - Risk of inconsistent outputs between builds

Tasks - [ ] Ensure idempotent builds (same input = same output) - [ ] Remove any time-based or random functions - [ ] Validate full rebuild produces identical files

7. SCHEMA & METADATA

Issue - Missing or inconsistent structured data

Tasks - [ ] Add LocalBusiness schema per page - [ ] Ensure all schema is valid (no errors) - [ ] Align metadata with page content

8. QA VALIDATION SYSTEM

Issue - No enforced validation step

Tasks - [ ] Create validation checklist script or manual process: - One H1 check - Title length check - Broken link scan - Duplicate content scan - [ ] Run QA before deployment

🚀 EXECUTION ORDER (IMPORTANT)

1. Deterministic generation
2. Data structure refactor
3. Content improvements
4. Internal linking
5. Schema
6. QA system

✅ SUCCESS CRITERIA

• All pages keep existing URLs
• Each page is unique and location-relevant
• Build output is identical across reruns
• No broken links
• SEO structure consistent across all pages

STATUS

Not Started

🔥 CRITICAL MISSING BEST PRACTICES

9. CANONICAL & DUPLICATION CONTROL

Issue - Risk of duplicate URLs or parameter variants

Tasks - [ ] Add canonical tag on every page - [ ] Ensure canonical matches live URL exactly - [ ] Prevent duplicate paths (trailing slash consistency)

10. XML SITEMAP & INDEXING

Issue - Weak crawl signals if not controlled

Tasks - [ ] Generate sitemap.xml automatically - [ ] Include ONLY live URLs - [ ] Ensure correct lastmod dates (deterministic if possible) - [ ] Submit to Google Search Console

11. ROBOTS & CRAWL CONTROL

Tasks - [ ] Validate robots.txt - [ ] Ensure no important pages are blocked - [ ] Block irrelevant paths (if any)

12. PAGE SPEED / CORE WEB VITALS

Issue - Jekyll sites often ignore performance optimisation

Tasks - [ ] Compress and optimise images - [ ] Use responsive images (srcset) - [ ] Minify HTML output - [ ] Defer non-critical JS - [ ] Avoid render-blocking assets

13. TEMPLATE CONSISTENCY (Jekyll Best Practice)

Issue - Risk of template drift across pages

Tasks - [ ] Use a single layout for location pages - [ ] Extract reusable components into includes - [ ] Eliminate duplicated HTML across files

14. PERMALINK CONSISTENCY

Issue - Jekyll can accidentally change URL output

Tasks - [ ] Explicitly define permalinks in front matter - [ ] Ensure they EXACTLY match live site URLs - [ ] Prevent Jekyll default permalink behaviour

15. INTERNAL LINK DEPTH (SERP FACTOR)

Issue - Pages too deep = weaker ranking

Tasks - [ ] Ensure every location page is reachable within 2–3 clicks - [ ] Add hub or regional linking if needed - [ ] Strengthen links from high-authority pages

16. TOPICAL COVERAGE (REAL RANKING FACTOR)

Issue - Not enough supporting content

Tasks - [ ] Ensure service pages support location pages - [ ] Interlink services ↔ locations - [ ] Add supporting informational content if missing

17. ANCHOR TEXT NATURALITY

Issue - Over-optimised anchors can hurt rankings

Tasks - [ ] Vary anchor text naturally - [ ] Avoid repeating exact-match anchors excessively

18. BUILD OUTPUT CLEANLINESS

Issue - Hidden junk can affect crawlability

Tasks - [ ] Remove unused files from _site - [ ] Ensure no orphan pages - [ ] Ensure clean HTML (no debug remnants)

19. 404 & ERROR HANDLING

Tasks - [ ] Create custom 404 page - [ ] Ensure broken URLs return proper 404 status - [ ] Redirect any known legacy URLs if needed

20. VERSION CONTROL SAFETY

Tasks - [ ] Ensure full backup before major refactor - [ ] Use branches for each task implementation - [ ] Validate before merging to main

✅ FINAL STANDARD

To be considered complete, the project must:

• Match ALL existing live URLs exactly
• Produce identical builds every time
• Have zero duplicate content
• Have strong internal linking structure
• Pass technical SEO checks (sitemap, canonical, robots)
• Be fully scalable via data-driven Jekyll architecture