claude-plugin-wordpress-manager 2.3.1 → 2.6.0

package/skills/wp-search-console/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: wp-search-console
+description: This skill should be used when the user asks about "Google Search Console",
+  "GSC", "keyword tracking", "keyword rankings", "search analytics",
+  "indexing status", "URL inspection", "sitemap management",
+  "search performance", "SEO feedback", "content SEO",
+  "competitor gap analysis", "keyword gap", or mentions monitoring
+  WordPress site search performance.
+version: 1.0.0
+---
+
+# WordPress Search Console Skill
+
+## Overview
+
+Google Search Console connects WordPress content to Google Search data via 8 MCP tools. These tools enable keyword tracking, indexing management, sitemap operations, and search performance analysis directly from the WordPress authoring environment. By bridging GSC data with WordPress content, you can identify optimization opportunities, monitor indexing health, and build data-driven content strategies.
+
+## When to Use
+
+- User wants to check how their WordPress pages perform in Google Search
+- User needs to track keyword rankings and position changes over time
+- User asks about indexing status or why a page is not appearing in Google
+- User wants to submit or manage XML sitemaps
+- User needs search analytics data (clicks, impressions, CTR, average position)
+- User asks about content SEO improvements based on search data
+- User wants to identify keyword gaps or content opportunities
+- User needs to inspect a specific URL for crawl and indexing details
+
+## Decision Tree
+
+1. **What aspect of Search Console?**
+   - "setup" / "connect GSC" / "service account" / "verify site" → GSC setup (Section 1)
+   - "keyword tracking" / "rankings" / "position" / "top queries" → Keyword tracking (Section 2)
+   - "indexing" / "URL inspection" / "sitemap" / "crawl" / "not indexed" → Indexing management (Section 3)
+   - "content SEO" / "underperforming pages" / "content refresh" / "optimize title" → Content SEO feedback (Section 4)
+   - "competitor gap" / "keyword gap" / "content opportunities" / "missing keywords" → Competitor gap analysis (Section 5)
+
+2. **Run detection first:**
+   ```bash
+   node skills/wp-search-console/scripts/search_console_inspect.mjs [--cwd=/path/to/project]
+   ```
+   This identifies configured GSC credentials and verified sites.
+
+## Service Overview
+
+| Service | Tools | Auth Type | Use Case |
+|---------|-------|-----------|----------|
+| Google Search Console | 8 tools (`gsc_*`) | Service Account JSON | Search analytics, indexing, sitemaps |
+
+## Sections
+
+### Section 1: GSC Setup
+See `references/gsc-setup.md`
+- Service account creation in Google Cloud Console
+- JSON key file configuration
+- WP_SITES_CONFIG setup with gsc_service_account_key and gsc_site_url
+- Site verification and permissions
+
+### Section 2: Keyword Tracking
+See `references/keyword-tracking.md`
+- Using gsc_search_analytics and gsc_top_queries for keyword monitoring
+- Date range and dimension filters
+- Tracking position changes over time
+- Query-level analysis (clicks, impressions, CTR, average position)
+
+### Section 3: Indexing Management
+See `references/indexing-management.md`
+- Using gsc_inspect_url for indexing status checks
+- Sitemap operations (list, submit, delete)
+- Monitoring crawl coverage
+- Handling indexing issues and bulk URL inspection
+
+### Section 4: Content SEO Feedback
+See `references/content-seo-feedback.md`
+- Connecting search data to WordPress content strategy
+- Identifying underperforming pages with gsc_page_performance
+- Content refresh strategies based on declining metrics
+- Title and meta description optimization from search data
+
+### Section 5: Competitor Gap Analysis
+See `references/competitor-gap-analysis.md`
+- Identifying keyword gaps using search analytics data
+- Analyzing query coverage vs potential queries
+- Finding content opportunities from query data
+- Cross-referencing with WordPress content inventory
+
+## Reference Files
+
+| File | Content |
+|------|---------|
+| `references/gsc-setup.md` | Service account creation, JSON key config, site verification |
+| `references/keyword-tracking.md` | Search analytics queries, position monitoring, dashboards |
+| `references/indexing-management.md` | URL inspection, sitemap management, crawl coverage |
+| `references/content-seo-feedback.md` | Page performance, content refresh, title optimization |
+| `references/competitor-gap-analysis.md` | Keyword gaps, content opportunities, position strategies |
+
+## MCP Tools
+
+| Tool | Description |
+|------|-------------|
+| `gsc_list_sites` | List all verified sites in Google Search Console |
+| `gsc_search_analytics` | Query search analytics data with dimensions and filters |
+| `gsc_inspect_url` | Inspect a URL for indexing status and crawl details |
+| `gsc_list_sitemaps` | List submitted sitemaps and their status |
+| `gsc_submit_sitemap` | Submit a new sitemap URL to GSC |
+| `gsc_delete_sitemap` | Remove a sitemap from GSC |
+| `gsc_top_queries` | Get top search queries with clicks, impressions, CTR, position |
+| `gsc_page_performance` | Get page-level performance data with search metrics |
+
+## Recommended Agent
+
+Use the **`wp-content-strategist`** agent for SEO feedback loops and content optimization workflows that combine Search Console data with WordPress content management.
+
+## Related Skills
+
+- **`wp-programmatic-seo`** — generate SEO-optimized content at scale using search data
+- **`wp-content-attribution`** — track content sources and attribute search traffic
+- **`wp-monitoring`** — monitor site health metrics alongside search performance
+- **`wp-social-email`** — distribute optimized content across social and email channels
+- **`wp-content`** — create and manage WordPress content informed by search analytics
+- **`wp-content-optimization`** — use GSC data as input for AI-driven content optimization and triage

package/skills/wp-search-console/references/competitor-gap-analysis.md

@@ -0,0 +1,226 @@
+# Competitor Gap Analysis
+
+## Overview
+
+Competitor gap analysis uses Google Search Console data to identify keyword opportunities your WordPress site is missing. By analyzing your query coverage, position distribution, and content inventory, you can find topics where you have search visibility but no dedicated content, or where competitors likely rank for queries you do not yet target.
+
+## Identifying Keyword Gaps
+
+### Step 1: Export your full query coverage
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query"]
+  row_limit: 5000
+Returns: Array of all queries with clicks, impressions, ctr, position
+```
+
+This gives you every query Google associates with your site. Sort by impressions to see which topics generate the most search visibility.
+
+### Step 2: Map queries to content
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 5000
+```
+
+This maps each query to the page that ranks for it. Look for:
+- **Queries without a dedicated page** — a query matches a generic page rather than a focused article
+- **Multiple queries pointing to one page** — the page may be covering too many topics and could be split
+- **Queries with position > 20** — you appear in results but have no strong content to compete
+
+### Step 3: Identify content gaps
+
+Cross-reference your queries with your WordPress content inventory:
+
+```
+# Get all published content
+Step 1: wp_list_posts status="publish" per_page=100 → Array of posts with titles and URLs
+
+# Get all queries with page mapping
+Step 2: gsc_search_analytics dimensions=["query", "page"] row_limit=5000
+
+# Compare: queries that map to pages not optimized for them = content gaps
+```
+
+## Analyzing Query Coverage
+
+### Position distribution analysis
+
+Categorize your queries by position to understand coverage quality:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query"]
+  row_limit: 5000
+```
+
+Group results by position ranges:
+
+| Position Range | Category | Strategy |
+|----------------|----------|----------|
+| 1-3 | Dominant | Protect — monitor and update regularly |
+| 4-10 | Competitive | Optimize — content refresh, internal links, backlinks |
+| 11-20 | Striking distance | Target — create supporting content, build topic clusters |
+| 21-50 | Weak presence | Evaluate — is the content worth investing in? |
+| 50+ | Minimal visibility | Decide — create new dedicated content or abandon |
+
+### Topic cluster gaps
+
+Group related queries into topic clusters to find areas where your coverage is incomplete:
+
+1. Export all queries with `gsc_search_analytics`
+2. Group queries by root topic (e.g., "wordpress seo", "wordpress performance", "wordpress security")
+3. Count unique queries per topic and average position per topic
+4. Topics with few queries or high average position are underserved
+
+## Finding Content Opportunities
+
+### High-impression, no-click queries
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 1000
+```
+
+Filter for queries where `impressions > 100` and `clicks == 0`. These are searches where Google shows your site but users never click — likely because:
+- Your page does not match the query intent
+- Your title and description are not compelling for that query
+- You rank too low (position > 20) for the query to generate clicks
+
+For each opportunity, decide whether to:
+- **Optimize the existing page** for that query (if the topic is related)
+- **Create a new dedicated page** targeting that query (if the topic is distinct)
+
+### Question-based queries
+
+Filter queries that start with question words (what, how, why, when, where, which, can, does, is):
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query"]
+  dimension_filter_groups:
+    - filters:
+        - dimension: "query"
+          operator: "contains"
+          expression: "how to"
+  row_limit: 200
+```
+
+Question queries map directly to FAQ content, how-to guides, and tutorial posts. If you appear for these queries but don't have dedicated content, create:
+- FAQ sections on existing pages
+- Standalone how-to articles
+- Comprehensive guides that answer multiple related questions
+
+### Long-tail opportunities
+
+Queries with 4+ words are typically long-tail keywords with lower competition:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query"]
+  row_limit: 2000
+```
+
+Filter for queries containing 4+ words with `impressions > 20`. Long-tail keywords often have:
+- Higher conversion intent
+- Lower competition
+- More specific content requirements
+
+Create focused content addressing the exact long-tail query.
+
+## Position Improvement Strategies
+
+### Strategy 1: Topic clusters
+
+For queries where you rank 11-20, build topic clusters:
+
+1. Identify the core topic from your query data
+2. Create a **pillar page** — comprehensive guide covering the broad topic
+3. Create **cluster pages** — focused articles on subtopics
+4. **Interlink** all cluster pages to the pillar and vice versa
+5. Monitor position changes with `gsc_search_analytics` over 4-8 weeks
+
+### Strategy 2: Content depth expansion
+
+For queries where you rank 4-10 but cannot break into top 3:
+
+1. Analyze the query with `gsc_search_analytics` filtered by the specific query
+2. Fetch the ranking page with `wp_get_post`
+3. Expand the content:
+   - Add 500-1000 words of additional depth
+   - Include data, statistics, or original research
+   - Add images, tables, or diagrams
+   - Add expert quotes or citations
+4. Update via `wp_update_post`
+
+### Strategy 3: Internal link building
+
+Boost underperforming pages with strategic internal links:
+
+1. Identify pages ranking 11-30 for valuable queries
+2. Find high-authority pages on your site (top performers from `gsc_page_performance`)
+3. Add contextual internal links from high-authority pages to underperforming pages
+4. Use the target query as anchor text (naturally, not forced)
+
+## Cross-Referencing with WordPress Content
+
+### Audit workflow
+
+Complete gap analysis workflow combining GSC and WordPress data:
+
+1. **Export all queries**: `gsc_search_analytics` with `dimensions: ["query"]`, `row_limit: 5000`
+2. **Export all pages**: `gsc_page_performance` with `row_limit: 500`
+3. **List WordPress content**: `wp_list_posts` with `status: "publish"`
+4. **Map coverage**: For each WordPress post, check if it has GSC data
+5. **Find orphans**: WordPress posts with no GSC impressions may have indexing or quality issues
+6. **Find gaps**: Queries without a dedicated WordPress post are content opportunities
+
+### Priority scoring
+
+Score content opportunities by potential impact:
+
+| Factor | Weight | Measurement |
+|--------|--------|-------------|
+| Impressions | High | More impressions = more potential traffic |
+| Current position | Medium | Closer to page 1 = easier to improve |
+| CTR gap | Medium | Low CTR vs expected = quick win with title optimization |
+| Competition | Low | Long-tail queries typically have less competition |
+| Business relevance | High | Queries related to products/services have higher value |
+
+## Best Practices
+
+- **Regular cadence**: Run gap analysis monthly to catch new opportunities as query landscape evolves
+- **Focus on intent**: Not all queries are worth targeting; prioritize queries that align with your content goals and business objectives
+- **Quality over quantity**: One comprehensive article targeting a cluster of related queries outperforms five thin articles each targeting a single query
+- **Track outcomes**: After creating content for identified gaps, monitor its performance in GSC after 4-8 weeks
+- **Avoid keyword cannibalization**: Before creating new content, check if an existing page already targets the same query cluster
+- **Use search data directionally**: GSC data shows what Google associates with your site, not what your competitors rank for; use it as a map of your current footprint and expand from there
+- **Combine with external tools**: For true competitive analysis (what competitors rank for that you do not), supplement GSC data with third-party tools like Ahrefs, SEMrush, or Moz
+- **Content calendar integration**: Feed identified opportunities into your WordPress editorial calendar for systematic execution

package/skills/wp-search-console/references/content-seo-feedback.md

@@ -0,0 +1,181 @@
+# Content SEO Feedback
+
+## Overview
+
+Content SEO feedback connects Google Search Console performance data to WordPress content strategy. By analyzing page-level metrics (clicks, impressions, CTR, position), you can identify underperforming content, discover optimization opportunities, and make data-driven decisions about content refreshes, title rewrites, and new content creation.
+
+## Identifying Underperforming Pages
+
+### Get page-level performance data
+
+```
+Tool: gsc_page_performance
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  row_limit: 200
+Returns: Array of pages with clicks, impressions, ctr, position
+```
+
+### Detect declining pages
+
+Compare two periods to find pages with declining performance:
+
+```
+# Previous period
+Tool: gsc_page_performance
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-01-01"
+  end_date: "2026-01-31"
+  row_limit: 200
+
+# Current period
+Tool: gsc_page_performance
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  row_limit: 200
+```
+
+Compare results to identify:
+- **Click decline > 20%** — high priority for content refresh
+- **Impression decline > 30%** — content may be losing relevance or competitors have overtaken
+- **Position increase > 3 positions** (lower is better) — content is dropping in rankings
+
+### Categorize pages by performance
+
+| Category | Criteria | Action |
+|----------|----------|--------|
+| High performers | Top 10% by clicks | Protect and expand — add internal links, update regularly |
+| Declining stars | Previously top, now dropping | Content refresh — update data, add sections, improve media |
+| Hidden gems | High impressions, low CTR | Title/meta optimization — rewrite to improve click-through |
+| Dead weight | Low impressions, low clicks | Evaluate for removal, consolidation, or major rewrite |
+| Rising pages | Increasing impressions and clicks | Accelerate — build more internal links, add supporting content |
+
+## Content Refresh Strategies
+
+### Strategy 1: Refresh based on declining clicks
+
+1. **Identify declining pages** using period comparison (see above)
+2. **Fetch the WordPress content** using `wp_get_post` with the page URL
+3. **Analyze queries** driving traffic to the page using `gsc_search_analytics` with `dimensions: ["query"]` filtered by the page URL
+4. **Update the content** to better address the top queries:
+   - Add missing subtopics that queries suggest users are looking for
+   - Update outdated statistics, dates, and references
+   - Expand thin sections with more depth
+   - Add FAQ sections based on question-type queries
+
+```
+# Find queries for a specific declining page
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query"]
+  dimension_filter_groups:
+    - filters:
+        - dimension: "page"
+          operator: "equals"
+          expression: "https://example.com/blog/wordpress-performance/"
+  row_limit: 50
+```
+
+### Strategy 2: New content from high-impression queries
+
+Queries with high impressions but low or zero clicks on your pages represent untapped opportunities:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 500
+```
+
+Filter for queries where:
+- `impressions > 200` and `clicks < 5` — your page appears but users do not click
+- `position > 10` — you rank on page 2+ and need a dedicated, optimized page
+
+These queries can inform new blog post topics or dedicated landing pages.
+
+### Strategy 3: Content consolidation
+
+Multiple pages ranking for the same query cannibalize each other:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 1000
+```
+
+Look for queries that appear with 2+ different pages. When multiple pages compete:
+1. Choose the strongest page (most clicks/best position)
+2. Merge content from the weaker page into the stronger one
+3. Redirect the weaker URL to the stronger page
+4. Update internal links to point to the consolidated page
+
+## Title and Meta Description Optimization
+
+### Find CTR optimization opportunities
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 200
+```
+
+Target pages where:
+- `position < 5` and `ctr < 0.05` — ranking well but not getting clicks (expected CTR for top 5 is 5-15%)
+- `position < 3` and `ctr < 0.10` — top 3 positions should have 10%+ CTR
+
+### Title tag optimization guidelines
+
+Based on search data patterns:
+- **Include the primary query** in the title — queries that appear verbatim in titles get higher CTR
+- **Front-load keywords** — the first 60 characters are visible in SERPs
+- **Add power words** — "Guide", "2026", "Complete", "Best" boost CTR by 5-15%
+- **Use numbers** — "10 Tips", "5 Steps" increase CTR by 10-20% vs generic titles
+- **Match intent** — if queries are questions, use question format in title
+
+### Meta description optimization
+
+- **Include target query** — Google bolds matching terms in descriptions
+- **Add a CTA** — "Learn more", "Get started", "Read the full guide"
+- **Stay under 155 characters** — longer descriptions get truncated
+- **Differentiate from competitors** — include unique value propositions
+
+## WordPress Integration Workflow
+
+Complete content optimization loop using GSC data and WordPress tools:
+
+1. **Pull page performance**: `gsc_page_performance` for all pages
+2. **Identify targets**: Filter for declining or underperforming pages
+3. **Get query context**: `gsc_search_analytics` filtered by target page URL
+4. **Fetch WordPress content**: `wp_get_post` to get current content
+5. **Update content**: `wp_update_post` with improved title, content, and meta
+6. **Monitor results**: Re-check `gsc_page_performance` after 2-4 weeks
+
+## Best Practices
+
+- **Refresh cadence**: Review page performance monthly; refresh declining content quarterly
+- **Data threshold**: Only act on pages with 100+ impressions — below that, data is statistically unreliable
+- **Patience after changes**: Wait 2-4 weeks after content changes before measuring impact; Google needs time to re-crawl and re-evaluate
+- **Track changes**: Note the date and nature of each content update so you can correlate with performance changes
+- **Prioritize by impact**: Focus on pages with the highest impression volume first — small CTR improvements on high-impression pages yield more clicks than large improvements on low-impression pages
+- **Seasonal awareness**: Some traffic drops are seasonal, not quality-related; compare year-over-year when possible
+- **Avoid over-optimization**: Do not stuff keywords into titles or content; natural language performs better in modern search
+- **Internal linking**: After refreshing content, add internal links from other relevant pages to boost crawl priority

package/skills/wp-search-console/references/gsc-setup.md

@@ -0,0 +1,110 @@
+# GSC Setup
+
+## Overview
+
+Google Search Console integration requires a Google Cloud service account with Search Console API access. The service account's JSON key file is configured in `WP_SITES_CONFIG`, enabling all 8 GSC MCP tools to authenticate and query search data for your WordPress site.
+
+## Setup
+
+### Step 1: Create a Google Cloud Project
+
+1. Go to [Google Cloud Console](https://console.cloud.google.com/)
+2. Create a new project or select an existing one
+3. Enable the **Google Search Console API** (also called "Search Console API" or "Webmasters API") under APIs & Services → Library
+
+### Step 2: Create a Service Account
+
+1. Navigate to IAM & Admin → Service Accounts
+2. Click **Create Service Account**
+3. Name it (e.g., `wp-search-console`) and add a description
+4. No additional roles are needed at the project level
+5. Click **Done**
+
+### Step 3: Generate JSON Key File
+
+1. Click on the newly created service account
+2. Go to the **Keys** tab
+3. Click **Add Key** → **Create new key** → **JSON**
+4. Download the JSON key file and store it securely
+
+The JSON key file contains:
+
+```json
+{
+  "type": "service_account",
+  "project_id": "your-project-id",
+  "private_key_id": "key-id",
+  "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
+  "client_email": "wp-search-console@your-project.iam.gserviceaccount.com",
+  "client_id": "123456789",
+  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
+  "token_uri": "https://oauth2.googleapis.com/token"
+}
+```
+
+### Step 4: Grant Search Console Access
+
+1. Go to [Google Search Console](https://search.google.com/search-console)
+2. Select your property (site)
+3. Navigate to **Settings** → **Users and permissions**
+4. Click **Add user**
+5. Enter the service account email (e.g., `wp-search-console@your-project.iam.gserviceaccount.com`)
+6. Set permission to **Full** (for read access and sitemap management) or **Restricted** (read-only)
+
+### Step 5: Configure WP_SITES_CONFIG
+
+Add GSC credentials to your site configuration:
+
+```json
+{
+  "sites": [{
+    "name": "my-site",
+    "url": "https://example.com",
+    "gsc": {
+      "gsc_service_account_key": "/path/to/service-account-key.json",
+      "gsc_site_url": "https://example.com/"
+    }
+  }]
+}
+```
+
+**Important notes on `gsc_site_url`:**
+- Use the exact property URL as it appears in Search Console
+- For domain properties, use `sc-domain:example.com`
+- For URL-prefix properties, use the full URL with trailing slash: `https://example.com/`
+- The value must match exactly — a mismatch will result in 403 errors
+
+## Verification
+
+After configuration, verify the setup works:
+
+```
+Tool: gsc_list_sites
+Returns: Array of verified sites with siteUrl, permissionLevel
+```
+
+You should see your site listed with `permissionLevel` of `siteOwner` or `siteFullUser`.
+
+## Permissions and Scopes
+
+The service account requires the following OAuth scope:
+
+- `https://www.googleapis.com/auth/webmasters.readonly` — for read-only access (search analytics, URL inspection, sitemap listing)
+- `https://www.googleapis.com/auth/webmasters` — for full access (includes sitemap submission and deletion)
+
+The MCP tools automatically request the appropriate scope based on the operation.
+
+## Troubleshooting
+
+- **403 Forbidden**: The service account email has not been added to Search Console, or `gsc_site_url` does not match the property URL
+- **404 Not Found**: The site URL format is incorrect (missing trailing slash or wrong protocol)
+- **Authentication errors**: The JSON key file path is invalid or the file is malformed
+- **No data returned**: The site may be newly verified; Search Console data takes 24-48 hours to populate
+
+## Best Practices
+
+- **Key file security**: Store the JSON key file outside the project directory; never commit it to version control
+- **Least privilege**: Use **Restricted** permission if you only need read access (search analytics, URL inspection)
+- **Separate accounts**: Use a dedicated service account per project to isolate access
+- **Key rotation**: Rotate service account keys periodically (every 90 days recommended)
+- **Domain property**: Prefer domain-level properties (`sc-domain:example.com`) over URL-prefix properties for complete data coverage