Understanding Credit Usage

Credit Model

Credits represent the unit cost of submitting URLs for indexing. In most plans, each successfully queued URL consumes one credit.

What Consumes Credits

• Single URL submissions accepted into the queue.
• Bulk submissions: one credit per valid row submitted.
• API-triggered submissions that pass validation.

What Does Not Consume Credits

• Validation failures prior to queueing (e.g., invalid URL).
• Automatic retries due to transient platform errors.
• Viewing reports, exports, and dashboard analytics.

Discounts & Bulk Efficiency

Certain plans may include discounted credit usage for large batches or monthly volume commitments. Check your plan details for specifics.

Monitoring Credits

1. Check remaining and consumed credits on your Dashboard.
2. Open Reports → Usage to view historical consumption by day and domain.
3. Set alerts to notify you when remaining credits drop below custom thresholds.

Rollover & Expiration

Standard plans reset credits at the start of each billing cycle with no rollover. Some premium plans may include partial rollover of unused credits—review your plan for exact terms.

Best Practices

• Group submissions into thoughtful batches to reduce overhead.
• Validate URLs ahead of time to avoid wasting attempts.
• Schedule large submissions during off-peak hours for faster throughput.

Who Is This Guide For?

This guide is ideal for marketers, SEO specialists, founders, and developers who want a reliable, repeatable process for understanding credit usage with minimal friction.

Prerequisites

• An active GetIndexedNow account
• A modern web browser (Chrome, Edge, Firefox, Safari)
• Owner or editor access to your website or CMS
• Basic familiarity with URLs and sitemaps

Detailed Steps

1. Open your GetIndexedNow dashboard and verify your project/website is selected.
2. Navigate to the relevant module for this task (Dashboard, URL Submitter, Sitemaps, or API).
3. Complete the input fields carefully—double‑check domain, protocol (http/https), and trailing slashes.
4. Click the primary action (Submit / Validate / Sync) and wait for a confirmation response.
5. Review status badges, logs, or activity feed to confirm successful processing.
6. If you see warnings, use the Troubleshooting section below to resolve them immediately.
7. Document your process so your team can repeat it consistently.

Best Practices

• Keep URLs clean, canonical, and accessible (no login walls for public pages).
• Use concise, descriptive titles and meta descriptions for faster search understanding.
• Batch similar actions (e.g., submit a set of new pages together).
• Avoid resubmitting unchanged URLs too frequently to prevent throttling.
• Maintain a changelog of edits and submissions to support audits.

Troubleshooting

• 403/401 errors: The destination blocks automated access—confirm robots and firewall settings.
• 404/410 errors: The URL doesn’t exist—fix the path or update internal links.
• 5xx errors: The site/server is unstable—retry after stabilizing hosting or CDN settings.
• Mixed content: Ensure all assets load over HTTPS to avoid blocked indexing.
• Slow responses: Optimize server performance or use a CDN to reduce TTFB.

FAQs

• How long does indexing take? It varies by search engine, crawl budget, and site authority. Many see results within hours to days.
• Can I undo a submission? No, but you can update or remove the page and submit changes.
• Is there a daily limit? Rate limits may apply—batch and prioritize important URLs.

Glossary

• Canonical URL: The preferred version of a page for indexing.
• Crawl Budget: The number of pages a crawler is willing to fetch on your site.
• Sitemap: A machine‑readable file listing URLs for discovery.