# Changelog of Google Autocomplete Scraper & Rank Change Monitor (`automa-flow/google-autocomplete-rank-change-monitor`) Actor

- **URL**: https://apify.com/automa-flow/google-autocomplete-rank-change-monitor/changelog.md
- **Full Actor documentation**: https://apify.com/automa-flow/google-autocomplete-rank-change-monitor.md

## Changelog

### 0.1 - 2026-09-09

Monitor Google Autocomplete prefixes by country, language and search type:
Web, YouTube, Shopping or News. Results include current suggestions and
`NEW_SUGGESTION`, `LOST_SUGGESTION`, `RANK_CHANGED` and `METADATA_CHANGED` events.

- Confirm new and missing suggestions across successful checks. A failed
  request keeps the previous observation and cannot report a lost suggestion.
- Each input has an outcome, including unchanged checks and duplicates. Use
  the default view for suggestions and statuses, and the changes view for events.
- Changing confirmation or relevance settings starts a new comparison baseline.
  Below-threshold suggestions still returned by Google do not produce loss events.
- The query echo is checked against the requested prefix. Incomplete or mismatched
  responses are reported as failures; a failure across the whole source fails the run.
- Spending limits preserve comparison state. Interrupted delivery is checked
  before resuming to avoid repeating rows or charges.
- Five saved examples cover keyword research, market comparisons and monitoring.
  The webhook example uses `clean=true` to omit empty change projections.
- Google relevance scores appear in the output but do not trigger change events.
  Autocomplete positions do not measure search volume or website rankings.

Pay per successful prefix check. Retries, failed checks and duplicate scopes
are not charged. Access errors such as 401, 403 and 451 remain source failures,
so they do not imply that a keyword has no suggestions.