antigravity-seo-kit 2.0.0

package/.agent/skills/seo/references/maps-free-apis.md

@@ -0,0 +1,176 @@
+<!-- Updated: 2026-03-23 -->
+# Free Maps APIs for claude-seo
+
+## Source Key
+
+- **Docs**: Official API documentation for each service
+- **Policy**: Official usage policies and terms
+
+---
+
+## Overpass API (Best Free Option for Competitor Discovery)
+
+**Base URL:** `https://overpass-api.de/api/interpreter`
+**Docs:** https://wiki.openstreetmap.org/wiki/Overpass_API
+**License:** ODbL (attribution required: "Data from OpenStreetMap")
+
+### Rate Limits
+
+- Slot-based: ~2 concurrent queries per IP
+- Guideline: ~10,000 requests/day, ~1 GB/day download
+- Default timeout: 180 seconds, 512 MiB memory per query
+- Use `[timeout:25]` for lighter queries
+
+### Query Templates
+
+**Restaurants within 5km radius:**
+```bash
+curl -s "https://overpass-api.de/api/interpreter" \
+  --data-urlencode 'data=[out:json][timeout:25];(node["amenity"="restaurant"](around:5000,LAT,LNG);way["amenity"="restaurant"](around:5000,LAT,LNG););out body;>;out skel qt;'
+```
+
+**All businesses on a street:**
+```bash
+curl -s "https://overpass-api.de/api/interpreter" \
+  --data-urlencode 'data=[out:json][timeout:25];way["name"="STREET_NAME"]["addr:city"="CITY"];(._;>;);out body;'
+```
+
+**Competitor POIs by category in bounding box:**
+```bash
+curl -s "https://overpass-api.de/api/interpreter" \
+  --data-urlencode 'data=[out:json][timeout:25];(node["amenity"="dentist"](SOUTH,WEST,NORTH,EAST);way["amenity"="dentist"](SOUTH,WEST,NORTH,EAST););out body;>;out skel qt;'
+```
+
+### Key OSM Tags for Local SEO
+
+| Category | OSM Tag | Examples |
+|----------|---------|---------|
+| Food & Drink | `amenity=restaurant`, `amenity=cafe`, `amenity=fast_food` | Restaurants, cafes, takeaway |
+| Healthcare | `amenity=dentist`, `amenity=doctors`, `amenity=pharmacy` | Dental, medical, pharmacy |
+| Legal | `office=lawyer`, `office=notary` | Law firms, notaries |
+| Home Services | `craft=plumber`, `craft=electrician`, `craft=hvac` | Trades, contractors |
+| Retail | `shop=supermarket`, `shop=clothes`, `shop=car` | All retail types |
+| Automotive | `shop=car`, `shop=car_repair`, `amenity=fuel` | Dealers, repair, gas |
+| Hospitality | `tourism=hotel`, `tourism=motel`, `tourism=guest_house` | Accommodation |
+| Financial | `amenity=bank`, `office=insurance`, `office=accountant` | Banks, insurance, accounting |
+
+### Response Fields
+
+Each element returns: `id`, `lat`, `lon`, `tags` object containing `name`, `phone`, `website`, `opening_hours`, `addr:street`, `addr:housenumber`, `addr:city`, `addr:postcode`, `cuisine`, `brand`, etc.
+
+### Limitations
+
+- No reviews, ratings, or popularity data
+- No GBP-specific information
+- Data quality varies by region (excellent in Europe, inconsistent elsewhere)
+- Volunteer-contributed data; may be outdated
+- Interactive tester: https://overpass-turbo.eu/
+
+---
+
+## Geoapify Places API (Structured POI Search)
+
+**Base URL:** `https://api.geoapify.com/v2/places`
+**Docs:** https://apidocs.geoapify.com/docs/places/
+**Pricing:** https://www.geoapify.com/pricing
+
+### Free Tier
+
+- **3,000 credits/day** (1 credit = 20 places returned)
+- 5 requests/second
+- Requires API key (free registration, no credit card)
+- **Caching and storage explicitly permitted** (unlike Google)
+
+### Query Template
+
+```bash
+curl -s "https://api.geoapify.com/v2/places?categories=catering.restaurant&filter=circle:LNG,LAT,5000&limit=20&apiKey=YOUR_KEY"
+```
+
+### Category Hierarchy
+
+Uses dot-separated categories: `catering.restaurant`, `commercial.supermarket`, `healthcare.dentist`, `service.financial.accounting`, `commercial.vehicle.car_dealer`
+
+### Response Format
+
+GeoJSON FeatureCollection. Each feature has `properties`: `name`, `city`, `state`, `postcode`, `country`, `street`, `housenumber`, `phone`, `website`, `categories`, `lat`, `lon`, `place_id`, `formatted` (full address string)
+
+### Advantages Over Raw Overpass
+
+- Cleaner, structured responses
+- Aggregated data (OSM + OpenAddresses + WhosOnFirst + GeoNames)
+- Hierarchical category taxonomy
+- No rate limit surprises (clear credit system)
+
+---
+
+## Nominatim (Geocoding Only)
+
+**Base URL:** `https://nominatim.openstreetmap.org`
+**Docs:** https://nominatim.org/release-docs/latest/api/Overview/
+**Policy:** https://operations.osmfoundation.org/policies/nominatim/
+
+### Rate Limits (STRICT)
+
+- **1 request/second** (absolute)
+- Must include valid `User-Agent` header (stock library agents rejected)
+- Auto-complete queries **forbidden**
+- Bulk geocoding **forbidden** on public instance
+- Repeated identical queries trigger bans (cache results)
+
+### Forward Geocoding
+
+```bash
+curl -s "https://nominatim.openstreetmap.org/search?q=123+Main+St+Austin+TX&format=json&addressdetails=1" \
+  -H "User-Agent: claude-seo/1.7.0"
+```
+
+### Reverse Geocoding
+
+```bash
+curl -s "https://nominatim.openstreetmap.org/reverse?lat=40.7128&lon=-74.0060&format=json" \
+  -H "User-Agent: claude-seo/1.7.0"
+```
+
+### Response Fields
+
+`place_id`, `lat`, `lon`, `display_name`, `importance`, `category`, `type`, `address` object (house_number, road, city, state, postcode, country)
+
+### Best Use
+
+- Address-to-coordinates conversion for geo-grid center point
+- Reverse geocoding to validate business addresses
+- **NOT suitable** for business listing discovery (use Overpass or Geoapify)
+
+---
+
+## Rate Limit Enforcement Pattern
+
+```bash
+# Nominatim: enforce 1 req/sec with sleep
+for addr in "${addresses[@]}"; do
+  curl -s "https://nominatim.openstreetmap.org/search?q=${addr}&format=json" \
+    -H "User-Agent: claude-seo/1.7.0"
+  sleep 1.1
+done
+
+# Overpass: no explicit rate limit, but use reasonable timeouts
+# If HTTP 429 returned, implement exponential backoff
+
+# Geoapify: 5 req/sec on free tier, no explicit enforcement needed
+```
+
+---
+
+## Comparison Table
+
+| Feature | Overpass | Geoapify | Nominatim |
+|---------|---------|----------|-----------|
+| Business discovery | Yes (tags) | Yes (categories) | Limited |
+| Reviews/ratings | No | No | No |
+| Geocoding | No | Yes | **Best** |
+| Rate limit | ~10k/day | 3k credits/day | 1 req/sec |
+| Auth required | No | API key | No |
+| Caching allowed | Yes | **Explicitly** | **Required** |
+| Data quality | Regional | Aggregated | Regional |
+| Best for | Radius competitor search | Structured POI search | Address resolution |

package/.agent/skills/seo/references/maps-gbp-checklist.md

@@ -0,0 +1,150 @@
+<!-- Updated: 2026-03-23 -->
+# GBP Profile Completeness Checklist (Via API)
+
+This checklist scores a Google Business Profile using data retrieved from
+the DataForSEO My Business Info API. It measures profile completeness on
+the maps PLATFORM, not on-page signals (seo-local handles on-page).
+
+## Sources
+
+- Google official: https://support.google.com/business/answer/7091
+- Whitespark 2026 Local Search Ranking Factors (Study)
+- BrightLocal LCRS 2026 (Study)
+
+---
+
+## Scoring System
+
+Each field: **Present + Optimized = 2pts**, **Present = 1pt**, **Missing = 0pts**
+
+Total possible: 50 points. Normalize to 0-100 scale: `(score / 50) * 100`
+
+---
+
+## Critical Fields (Direct Ranking Impact)
+
+| # | Field | Points | Optimized Criteria |
+|---|-------|--------|-------------------|
+| 1 | **Primary category** | 2 | Most specific subtype for industry (e.g., "Cosmetic Dentist" not "Dentist") |
+| 2 | **Additional categories** | 2 | 3-5 relevant categories (optimal: 4 additional per BrightLocal) |
+| 3 | **Business name** | 2 | Matches real-world name exactly (no keyword stuffing) |
+| 4 | **Physical address** | 2 | Complete, matches website NAP |
+| 5 | **Phone number** | 2 | Local number (not toll-free), matches website |
+| 6 | **Website URL** | 2 | Points to correct page (not strongest page -- Diversity Update risk) |
+| 7 | **Business hours** | 2 | Complete with special/holiday hours. Open-at-search-time = factor #5 |
+| 8 | **Verified status** | 2 | Google Verified badge active |
+
+**Subtotal: 16 points (8 fields)**
+
+---
+
+## Important Fields (Significant Influence)
+
+| # | Field | Points | Optimized Criteria |
+|---|-------|--------|-------------------|
+| 9 | **Business description** | 2 | 250-750 chars, includes primary service + location keywords naturally |
+| 10 | **Services list** | 2 | All core services listed with descriptions |
+| 11 | **Products** | 2 | Key products/services with prices (if applicable) |
+| 12 | **Photos** | 2 | 10+ photos across types: logo, cover, interior, exterior, team, products |
+| 13 | **Photo recency** | 2 | Photos uploaded within last 30 days |
+| 14 | **Attributes** | 2 | Relevant attributes set (accessibility, payments, amenities, identity) |
+| 15 | **Service areas** | 2 | Defined for SABs, up to 20 areas (cities or zip codes) |
+| 16 | **Menu/services link** | 2 | Menu URL (restaurants) or services URL (others) |
+
+**Subtotal: 16 points (8 fields)**
+
+---
+
+## Supplementary Fields (Supporting Signals)
+
+| # | Field | Points | Optimized Criteria |
+|---|-------|--------|-------------------|
+| 17 | **Google Posts** | 2 | Active posting (1+/week). Types: update, offer, event, product |
+| 18 | **Post recency** | 2 | Post within last 7 days |
+| 19 | **Booking link** | 2 | Appointment/reservation URL configured |
+| 20 | **Social profiles** | 2 | Linked via `sameAs` or GBP social links |
+| 21 | **Logo** | 2 | High-quality square logo uploaded |
+| 22 | **Cover photo** | 2 | On-brand, high-resolution cover image |
+| 23 | **Videos** | 2 | At least 1 video uploaded |
+| 24 | **Owner responses** | 2 | Responding to reviews (target: 80%+ response rate) |
+| 25 | **Q&A engagement** | 2 | FAQ content on website (GBP Q&A deprecated Dec 2025) |
+
+**Subtotal: 18 points (9 fields)**
+
+---
+
+## Industry-Specific Weight Adjustments
+
+When scoring, apply multipliers to fields that matter more for specific industries:
+
+### Restaurant
+- Menu/services link: **x2** (critical for food-related searches)
+- Photos: **x1.5** (food photos drive engagement)
+- Booking link: **x1.5** (reservation systems expected)
+- Attributes: **x1.5** (dietary, dine-in/takeout/delivery critical)
+
+### Healthcare
+- Business hours: **x1.5** (patients need accurate hours)
+- Attributes: **x1.5** (insurance, accessibility, telehealth)
+- Services list: **x2** (insurance and procedure matching)
+
+### Legal
+- Business description: **x1.5** (practice area clarity)
+- Services list: **x2** (practice area matching drives visibility)
+- Photos: **x0.5** (less impactful for legal)
+
+### Home Services
+- Service areas: **x2** (SAB model depends on this)
+- Business hours: **x1.5** (emergency availability)
+- Photos: **x1.5** (before/after project photos)
+
+### Real Estate
+- Photos: **x2** (property photos critical)
+- Social profiles: **x1.5** (agent branding)
+- Posts: **x1.5** (listing updates)
+
+### Automotive
+- Products: **x2** (vehicle inventory)
+- Photos: **x2** (vehicle photos)
+- Services list: **x1.5** (sales + service departments)
+
+### Re-normalization After Multipliers
+
+After applying industry multipliers, re-normalize so the total remains 0-100:
+```
+final_score = (weighted_raw_score / max_possible_weighted_score) * 100
+```
+This ensures consistent scoring regardless of which industry multipliers are active.
+
+---
+
+## Score Interpretation
+
+| Score | Rating | Action |
+|-------|--------|--------|
+| 90-100 | Excellent | Maintain posting cadence and photo freshness |
+| 75-89 | Good | Fill remaining gaps in supplementary fields |
+| 50-74 | Needs Work | Missing important fields, address Critical + Important gaps |
+| 25-49 | Poor | Major profile gaps hurting visibility. Prioritize Critical fields |
+| 0-24 | Critical | Profile barely exists or unclaimed. Start with verification + Critical fields |
+
+---
+
+## Data Mapping (DataForSEO → Checklist)
+
+| Checklist Field | DataForSEO My Business Info Field |
+|----------------|----------------------------------|
+| Primary category | `category` |
+| Additional categories | `additional_categories` |
+| Business name | `title` |
+| Address | `address_info` |
+| Phone | `contact_info` (type: phone) |
+| Website | `domain`, `url` |
+| Hours | `work_hours` |
+| Description | `description` |
+| Services | (separate API or attributes) |
+| Photos | `photos_count`, `main_image` |
+| Attributes | `attributes` (grouped by type) |
+| Popular times | `popular_times` |
+| Posts | My Business Updates API |
+| Verified status | Not directly exposed — infer from profile completeness + Maps SERP presence, or flag as "Unknown (manual check required)" |

package/.agent/skills/seo/references/maps-geo-grid.md

@@ -0,0 +1,154 @@
+<!-- Updated: 2026-03-23 -->
+# Geo-Grid Rank Tracking Algorithm
+
+## Concept
+
+Geo-grid rank tracking simulates Google Maps searches from multiple GPS
+coordinates around a business to show how rankings vary across a geographic
+area. The output is a heatmap revealing where the business ranks well (green)
+and where competitors dominate (red).
+
+---
+
+## Grid Generation (Haversine-Based)
+
+### Algorithm
+
+1. Take center coordinates (business location): `center_lat`, `center_lng`
+2. Define grid size (e.g., 7x7 = 49 points) and radius in km
+3. Calculate spacing: `step = (2 * radius_km) / (grid_size - 1)`
+4. Generate grid points using offset formula:
+
+```
+For each row i (0 to grid_size-1) and column j (0 to grid_size-1):
+  dy = (i - center_index) * step_km
+  dx = (j - center_index) * step_km
+  new_lat = center_lat + (dy / 111.32)
+  new_lng = center_lng + (dx / (111.32 * cos(center_lat * pi/180)))
+```
+
+Where `center_index = (grid_size - 1) / 2` and `111.32 km = 1 degree latitude`.
+
+### Grid Sizes and Use Cases
+
+| Grid | Points | Typical Radius | Best For | Est. Cost (Live) |
+|------|--------|---------------|----------|-----------------|
+| 3x3 | 9 | 2 km | Quick snapshot, low budget | $0.018/keyword |
+| 5x5 | 25 | 3 km | Standard urban audit | $0.050/keyword |
+| **7x7** | **49** | **5 km** | **Default. Best balance of coverage and cost** | **$0.098/keyword** |
+| 9x9 | 81 | 8 km | Suburban/wide service area | $0.162/keyword |
+| 13x13 | 169 | 15 km | Rural or large metro | $0.338/keyword |
+
+**Radius guidelines:** Urban dense = 2-5 km, suburban = 5-10 km, rural = 10-25 km.
+
+---
+
+## DataForSEO Integration
+
+Use the Google Maps SERP API with `location_coordinate` parameter:
+
+```json
+{
+  "keyword": "dentist",
+  "location_coordinate": "30.2672,-97.7431,15z",
+  "language_code": "en",
+  "device": "mobile",
+  "depth": 20
+}
+```
+
+For each grid point, fire one API call with the point's lat/lng. Parse the
+`items` array to find the target business rank (position in results).
+
+**Rate optimization:** DataForSEO allows up to 100 tasks per POST. For a 7x7
+grid, batch all 49 tasks into a single request to minimize HTTP overhead.
+
+---
+
+## Share of Local Voice (SoLV)
+
+Metric pioneered by Local Falcon. Measures visibility across the grid.
+
+### Calculation
+
+```
+SoLV = (points_in_top_3 / total_grid_points) * 100
+```
+
+### Interpretation
+
+| SoLV | Interpretation |
+|------|---------------|
+| 80-100% | Dominant. Business owns the local area. |
+| 60-79% | Strong. Visible in most of the service area. |
+| 40-59% | Moderate. Significant gaps in coverage. |
+| 20-39% | Weak. Competitors dominate most areas. |
+| 0-19% | Critical. Nearly invisible in maps results. |
+
+### Extended Metrics
+
+- **Average Rank**: Mean position across all grid points (lower = better)
+- **Visibility Score**: Weighted average where top 3 = 3pts, 4-10 = 1pt, 10+ = 0pts
+- **Worst Quadrant**: Identify which compass direction has weakest rankings
+
+---
+
+## ASCII Heatmap Rendering
+
+For terminal/Markdown output, render a grid using rank-position symbols:
+
+### Format
+
+```
+Geo-Grid: "dentist" (7x7, 5km radius, center: 30.267, -97.743)
+
+     W -------- E
+  N  1  1  2  3  5  8  -
+  |  1  1  1  2  3  6  9
+  |  2  1  [1] 1  2  4  7
+  |  3  2  1  1  1  3  5
+  |  5  3  2  1  2  4  8
+  |  8  5  3  2  3  6  -
+  S  -  8  5  4  5  9  -
+
+Legend: [1]=center, 1-3=top 3 (strong), 4-10=visible, -=not ranked
+SoLV: 57% (28/49 grid points in top 3)
+Avg Rank: 3.4 | Weakest: NE quadrant (avg rank 7.2)
+```
+
+### Color Mapping (for enhanced output)
+
+| Position | Symbol | Meaning |
+|----------|--------|---------|
+| 1 | `1` | #1 ranking (best) |
+| 2-3 | `2`, `3` | Top 3 (strong local presence) |
+| 4-10 | `4`-`9` | Visible but not dominant |
+| 11-20 | `+` | Buried in results |
+| Not found | `-` | Not ranking at this point |
+
+---
+
+## Multi-Keyword Grid
+
+For comprehensive analysis, scan 2-3 keywords on the same grid:
+
+1. Primary service keyword (e.g., "dentist")
+2. Brand + location (e.g., "Smith Dental Austin")
+3. Long-tail intent (e.g., "emergency dentist near me")
+
+**Cost for 3-keyword 7x7 scan:** 147 API calls = ~$0.29 (live) or ~$0.088 (standard)
+
+---
+
+## Cost Warning Template
+
+Before running a geo-grid scan, display:
+
+```
+Geo-Grid Scan Estimate:
+  Grid: 7x7 (49 points)
+  Keywords: 3
+  API calls: 147
+  Estimated cost: $0.09 (standard) - $0.29 (live)
+  Proceed? [DataForSEO credits will be consumed]
+```

package/.agent/skills/seo/references/quality-gates.md

@@ -0,0 +1,155 @@
+# Content Quality Gates
+
+## Minimum Word Counts by Page Type
+
+| Page Type | Min Words | Unique Content % | Notes |
+|-----------|-----------|-----------------|-------|
+| Homepage | 500 | 100% | Must clearly communicate value proposition |
+| Service / Feature Page | 800 | 100% | Detailed explanation of offering |
+| Location (Primary) | 600 | 60%+ | City headquarters or main service area |
+| Location (Secondary) | 500 | 40%+ | Satellite locations |
+| Blog Post | 1,500 | 100% | In-depth, valuable content |
+| Product Page | 400 | 80%+ | Unique descriptions, specs |
+| Category Page | 400 | 100% | Unique intro, not just product listings |
+| About Page | 400 | 100% | Company story, team, values |
+| Landing Page | 600 | 100% | Focused conversion content |
+| FAQ Page | 800 | 100% | Comprehensive Q&A |
+
+---
+
+## Location Page Thresholds
+
+### Warning Level (30+ pages)
+- ⚠️ **WARNING** at 30+ location pages
+- Enforce 60%+ unique content per page
+- Content must include:
+  - Unique local information (landmarks, neighborhoods)
+  - Location-specific services or offerings
+  - Local team or staff information
+  - Genuine customer testimonials from that area
+
+### Hard Stop (50+ pages)
+- 🛑 **HARD STOP** at 50+ location pages
+- Require explicit user justification
+- Must demonstrate:
+  - Legitimate business presence in each location
+  - Unique content strategy for each page
+  - Local signals (Google Business Profile, local reviews)
+
+### Why This Matters
+Google's doorway page algorithm penalizes programmatic location pages with thin/duplicate content. Signs of doorway pages:
+- Only city/state name changed between pages
+- No unique local information
+- No local business signals
+- Keyword-stuffed URLs
+
+---
+
+## Safe vs. Risky Programmatic Pages
+
+### Safe at Scale ✅
+| Page Type | Why It's Safe |
+|-----------|---------------|
+| Integration pages | Real setup documentation, unique technical content |
+| Template/tool pages | Downloadable assets, unique functionality |
+| Glossary pages | 200+ word unique definitions |
+| Product pages | Unique specs, images, reviews |
+| User profile pages | User-generated unique content |
+
+### Penalty Risk ❌
+| Page Type | Why It's Risky |
+|-----------|----------------|
+| Location pages with only city swapped | Duplicate content, doorway pages |
+| "Best [tool] for [industry]" | Often thin, no industry-specific value |
+| "[Competitor] alternative" | Requires genuine comparison data |
+| AI-generated mass content | No unique value, E-E-A-T failure |
+
+---
+
+## Title Tag Requirements
+
+| Aspect | Requirement |
+|--------|-------------|
+| Minimum length | 30 characters |
+| Maximum length | 60 characters (Google truncates ~60) |
+| Primary keyword | Near the beginning |
+| Brand name | At end (if included) |
+| Uniqueness | Each page must have unique title |
+
+### Good Examples
+- "Emergency Plumbing Services in Austin | ABC Plumbing"
+- "How to Fix a Leaky Faucet: Step-by-Step Guide"
+- "Enterprise SEO Software | Comprehensive Platform"
+
+### Bad Examples
+- "Home" (too short, not descriptive)
+- "Best Plumbing Services for All Your Plumbing Needs in Austin Texas and Surrounding Areas" (too long)
+- "ABC Plumbing - Plumbing - Plumber - Plumbing Services" (keyword stuffing)
+
+---
+
+## Meta Description Requirements
+
+| Aspect | Requirement |
+|--------|-------------|
+| Minimum length | 120 characters |
+| Maximum length | 160 characters (Google truncates ~155-160) |
+| Call-to-action | Include compelling CTA |
+| Primary keyword | Include naturally |
+| Uniqueness | Each page must have unique description |
+
+---
+
+## Image Alt Text Requirements
+
+| Aspect | Requirement |
+|--------|-------------|
+| Required on | All non-decorative images |
+| Length | 10-125 characters |
+| Content | Describe the image content, not "image" or filename |
+| Keywords | Include naturally where relevant |
+| Decorative images | Use `alt=""` or `role="presentation"` |
+
+### Good Examples
+- "Professional plumber repairing kitchen sink faucet"
+- "Red 2024 Toyota Camry sedan front view"
+- "Team meeting in modern office conference room"
+
+### Bad Examples
+- "image.jpg" (filename, not description)
+- "plumber plumbing plumber services" (keyword stuffing)
+- "Click here" (not descriptive)
+
+---
+
+## Internal Linking Guidelines
+
+| Page Type | Internal Links Target |
+|-----------|----------------------|
+| Blog post (1,500+ words) | 5-10 internal links |
+| Service page | 3-5 internal links |
+| Category page | Links to all child pages |
+| Product page | 2-4 internal links |
+
+### Anchor Text Rules
+- Use descriptive anchor text (not "click here")
+- Vary anchor text (don't always use exact match keywords)
+- Link to relevant, related content
+- Ensure no orphan pages (every page linked from at least one other page)
+
+---
+
+## Content Freshness Signals
+
+| Content Type | Update Frequency |
+|--------------|------------------|
+| News/current events | Within hours/days |
+| Blog posts (evergreen) | Review annually |
+| Product pages | When specs change |
+| Service pages | Review quarterly |
+| Company info | When changes occur |
+
+### Required Elements
+- Publication date visible (for articles/blogs)
+- Last updated date (if significantly revised)
+- Changelog for major updates (optional but good)