rank-trackinglisted

# Rank Tracking ## Mission Measure search visibility consistently across repeated runs. A ranking trend is valid only when the query set and search context are comparable. ## Required inputs - Target domain. - Keyword list, or a confirmed list from .seo/project.md. - Country, language, device, and result depth. - Optional: previous snapshot, comparison date, competitor domains, and priority URL groups. ## Workflow 1. Read .seo/project.md and locate the most recent compatible ranking snapshot. 2. If the user asks about their own observed Google performance and Search Console is connected, query `gsc.search_analytics` as supporting context. Do not merge its average position into the Muapi rank snapshot or present it as the same measurement. 3. Normalize and deduplicate the keyword list. Keep the exact query text used for the provider. 4. Check seo.account_status when balance or limits are unknown. 5. Use seo.rank_track_batch for up to 50 comparable keywords per call. Split a larger list into chunks with identical target domain, location, language, device, and depth. Ask before a broad or repeated run. 6. Use seo.rank_track for a single diagnostic term or when a batch result needs verification. 7. Use seo.google_serp for high-priority terms where the user needs the live result composition, SERP features, or competing URLs—not as a replacement for the complete tracked set. 8. Save the raw request and response as a dated snapshot before calculati