Learn when pay-as-you-go URL indexing costs less than subscriptions or manual work, how to calculate effective cost and which billing details to verify before scaling.
Pay-as-you-go URL indexing lets a team buy balance and spend it only when it creates work, instead of committing to a monthly subscription. It is usually the clearest model for irregular campaigns, agencies with changing client volume and teams that want a visible per-URL cost. It is not automatically the cheapest model: the billing event, invalid URL policy, verification expense and unused balance determine the real cost.
Short answer: compare net spend per unique eligible URL, not the package headline. A transparent 2.50 TL submission can be cheaper than a low advertised token price if the competing workflow creates duplicate charges, expires credits or requires substantial manual reconciliation.
Four billing models you will encounter
| Model | When cost occurs | Main advantage | Main risk |
|---|---|---|---|
| Pay per submitted URL | When an eligible job is accepted | Predictable total before processing | Payment is for workflow execution, not guaranteed search inclusion |
| Pay per provider-confirmed result | After a later result check | Cost is tied to the provider's confirmation rule | Verification method and observation window may not equal Search Console data |
| Monthly subscription | Every billing period | Stable capacity for consistent volume | Paying for unused capacity in quiet months |
| Manual/free tools | No direct service fee | Strong official diagnostics for owned properties | Staff time, low throughput and fragmented records |
The label “pay as you go” is incomplete until the service names the charge event. Two services can use the same phrase while one charges on acceptance and the other after a seven-day check.
The three denominators that change the answer
Cost comparisons fail when they divide by the wrong URL count. Track these separately:
- Raw URLs: every line before cleaning.
- Unique eligible URLs: normalized, reachable URLs that pass the campaign's technical rules.
- Observed results: URLs found by the agreed verification method at the agreed checkpoint.
Then calculate:
preparation loss = 1 - (unique eligible URLs / raw URLs)
submission cost = net submission charge / unique accepted URLs
observed-result cost = total net cost / observed results
The first metric reveals list quality. The second measures the service contract. The third can support an experiment, but only when every group uses the same observation method.
A realistic agency example
An agency receives 2,000 placement URLs. After normalization it removes 120 duplicates, 40 malformed URLs, 25 login-protected pages and 15 noindex pages. The usable set is 1,800 URLs.
If the selected workflow costs 1.00 TL per accepted URL, the submission charge is 1,800 TL. If the team also buys a 1.00 TL result check for every URL, the combined maximum becomes 3,600 TL. The check should therefore be a business decision, not an automatic checkbox: checking a representative sample or only high-value placements may be more economical.
Now add labor. If manual preparation, submission and reporting takes six hours at a loaded cost of 400 TL per hour, labor adds 2,400 TL. A more expensive-looking automated workflow can still have the lower total cost when it removes several hours of work and preserves a reliable audit trail.
How Index Grab's model works
Index Grab uses a Turkish-lira balance and shows the unit price and calculated total before a URL job is confirmed. It does not require a monthly subscription. The service currently offers:
- Standard Index: 1.00 TL per URL for routine work, with a stated processing range of 3 hours to 7 days.
- High-Speed Index: 2.50 TL per URL for priority work, with a stated processing range of 5 to 10 minutes.
- URL result check: an optional 1.00 TL per URL beta service when live result data is available.
Prices above were reviewed on August 16, 2026 and can change. The live pricing and confirmation screens are authoritative.
The processing ranges describe Index Grab's service workflow. They do not guarantee that Google will crawl, index, rank or retain a URL. This distinction is essential when comparing a per-submission model with a provider-confirmed-result model.
When pay as you go is a good fit
Choose it when:
- campaign volume changes significantly from month to month;
- you want to start with a small representative test;
- different clients need separate job references and cost attribution;
- you prefer balance history over a recurring card charge;
- a standard and priority workflow should coexist in one account;
- sitemap additions create intermittent bursts rather than steady daily volume;
- an API integration needs deterministic price calculation before submission.
When a subscription may be better
A subscription can make sense when volume is stable, the included capacity closely matches use and overage rules are predictable. Calculate annual utilization rather than comparing one busy month.
capacity utilization = URLs actually used / URLs included
A cheap subscription at 35% utilization can cost more per useful URL than a higher visible pay-as-you-go rate. Also include cancellation, rollover, expiry and minimum-term rules.
When free tools are enough
For a small verified property, Search Console, internal links and a clean sitemap can be sufficient. IndexNow is useful for controlled URL changes sent to participating engines. These tools cost no submission fee and provide first-party or protocol-level information.
Their hidden cost is operational. They may not solve authorized third-party backlink lists, team wallet reconciliation, recurring client history or one API contract across many campaigns.
Avoid these seven cost traps
Duplicate billing
Normalize scheme, host casing, fragments and trailing-slash policy before creating a job. Use service idempotency or a stable client reference when retrying API requests.
Paying to submit ineligible URLs
Check HTTP status, noindex, robots rules, canonical target, redirects and authentication. A service cannot repair a blocked page by submitting it more often.
Treating all URLs as equally valuable
High-value editorial placements may justify priority processing and later verification. Low-value profile pages may not justify the same spend.
Checking too early
Verification timing should match the processing option and experiment design. An early miss can lead to unnecessary repeat checks.
Ignoring currency and tax
Dollar token packages, card conversion and taxes can change the effective local cost. Compare the amount that actually leaves the business account.
Confusing balance with bonus capacity
Some products sell tokens whose value changes by operation. Others load monetary balance. Record the conversion rule instead of comparing the labels.
Buying scale before validating quality
Run a small controlled sample first. A larger package does not fix noindex pages, weak content, canonical conflicts or an unreliable verification process.
A procurement checklist
- What exact event creates a debit?
- Is the displayed price tax-inclusive?
- Does balance expire?
- Are duplicates charged?
- Are invalid URLs rejected before debit?
- Can failed or interrupted jobs be reconciled without a second charge?
- Is result checking included, optional or unavailable?
- What does each status label mean?
- Can history be exported or queried through API?
- Does the API support idempotent retries?
- Is there a minimum purchase?
- Which refund rules apply to unused and consumed balance?
Primary sources and related guides
- Index Grab pricing
- Index Grab features
- Index Grab REST API
- Free vs paid URL indexing tools
- Best URL indexing tools in 2026
- Google recrawl documentation
Pricing statements were reviewed on August 16, 2026. Always use the live confirmation total for a current purchasing decision.
Frequently Asked Questions
What is pay-as-you-go URL indexing?
It is a billing model in which the customer purchases or holds balance and pays as individual URL jobs are accepted or results are confirmed, depending on the service contract. There is no mandatory monthly subscription.
Is pay as you go cheaper than a subscription?
It is often cheaper for irregular volume. A subscription may be cheaper at consistently high utilization. Compare annual net spend, eligible URLs, labor and unused capacity.
Should every submitted URL receive a paid result check?
Not necessarily. Check high-value URLs, contractual client deliverables or a statistically useful sample. Automatic checking of every low-value URL can double the workflow cost without changing the submission outcome.
Does a completed submission mean the URL is indexed?
No. Completion describes the service workflow. Indexing is a separate search-engine decision and should only be reported when an agreed observation actually finds the URL.
Can pay-as-you-go indexing be automated?
Yes, when the service provides a documented API. The integration should normalize URLs, calculate price, use stable references, respect rate limits and reconcile ambiguous timeouts before retrying.
This guide is written and reviewed by the Index Grab editorial team using publicly available search-engine documentation and practical technical SEO checks. Product capabilities and prices are verified against the current Index Grab interface before publication.
Primary references: Google Search Central · Sitemaps.org · Schema.org
