Bing, YouTube, and Amazon tracking

Non-Google engines use the same add-keyword flow with an engine picker. Rank history is engine-tagged, and the history view carries a URL-backed engine filter.

<!-- docs-truth: metric=alt_engine_checks; unit=one-keyword-one-engine-check; cache-hits=count; refund=provider-failure-zero-retained; cadence=weekly; estimates=provider-observation -->

How each engine is matched

Bing is matched the same way as Google: by host equality against your site domain. A result whose normalized host equals yours is your result.

YouTube is matched by an exact channel handle and Amazon by an exact ASIN. Every result URL on those platforms lives on the platform domain, so a host match would be meaningless and no fuzzy brand match is attempted.

Cadence and units

Non-Google targets are checked once per week regardless of the cadence configured for the site. Each keyword-and-engine check reserves one alternative-engine unit before the request is made.

Cached results still count toward your allowance. If the provider fails, nothing is retained and the unit is returned.

Honest limits

Without an exact channel handle or ASIN, RankMeFast will not guess. A missing token means the keyword cannot be tracked on that engine rather than tracked approximately.

An Amazon position is a position within the provider’s returned product index, not a live shelf position, and sponsored blocks are dropped before ranking. Positions are observations on a stated date, never a forecast.

Plans and availability

Monthly allowances by plan are Free 0, Starter 0, Pro 20, and Agency 240. A one-time credit pack can top the allowance up when a plan runs out.

The surface is gated by the ALT_ENGINE_TRACKING_ENABLED rollout flag: when an operator turns it off, new runs are refused with a localized message while stored results stay readable.

For units and plan limits, see Pricing.

Before acting, compare this guide with the stored evidence and status shown in RankMeFast.

Back to the docs index