Skip to main content

What is IndexCheckr and how does it work?

What is IndexCheckr and how does it work?

IndexCheckr is a tool that checks whether your web pages are indexed by Google. It helps you track indexing status at scale, monitor changes over time, and take action on non-indexed pages using external indexer tools.

Checking pages

There are two ways to check pages:

  • Projects, to monitor pages over time. You can add pages manually or via CSV, or by importing from a sitemap. Pages are organized into projects so you can monitor indexing by site, campaign, or client, and you can label them with tags to filter and act on groups of pages.

  • Quick Check, to check a list of up to 1,000 URLs once, without creating a project.

Each indexing check consumes one credit. In projects, you can recheck pages manually or set up automatic rechecks (daily, weekly, biweekly, or monthly). There's also an option to stop rechecking a page automatically once it's indexed (see Setting up your first project).

Monitoring and acting on results

IndexCheckr shows detailed stats for each project in the Projects Overview, lets you drill down into individual Pages Reports, tracks every change in the Changelog, and can email you when statuses change.

You can connect your account to supported indexer tools to try to get non-indexed pages indexed (see Submitting pages to an indexer).

Chrome extension, API and team

  • The Chrome extension checks the page you are on, its outbound links, a list of URLs, or a site's sitemap, right from your browser.

  • The API lets you automate checks and feed indexing data into your own tools. It is available to all accounts.

  • The Team feature lets you invite colleagues to work on your projects.

Credits

IndexCheckr is entirely credit-based. There are no subscriptions, and credits never expire. New accounts get 50 free credits to try the tool (see Buy credits, top-up and invoices and the FAQ).


Summary

IndexCheckr makes it easy to track which pages are indexed and helps you take action when they’re not, at scale and with automation.

Did this answer your question?