Everything from installing the plugin to reading every number in the dashboard — and setting up the indexing widget that actually gets your pages indexed.
indexfixer-pro-x.x.x.zip from your account panel.A new IndexFixer item appears in the left admin menu.
Two one-click steps, no license keys and no Google Cloud setup:
After connecting you'll see a short "Collecting data" screen. The first scan usually takes a few minutes; big sites can take longer (Google allows up to 2,000 URL inspections per day per site). The dashboard unlocks automatically.
| Card | Meaning |
|---|---|
| TOTAL | All published URLs IndexFixer tracks (per the post types you selected in Settings). |
| CHECKED | How many of them already have a result from Google's URL Inspection. Fresh installs start at 0% and climb as the daily budget is used. |
| INDEXED | Pages confirmed in Google's index. This is the number you want to grow. |
| NOT INDEXED | Google knows the page (usually crawled it) but decided not to index it — typically a content-quality signal. These are the pages the widget works on. |
| DISCOVERED | Google has seen the URL (e.g. in your sitemap) but hasn't crawled it yet. |
| EXCLUDED | Technically blocked or excluded: redirects, 404s, noindex, robots.txt, canonicals pointing elsewhere. |
| UNKNOWN | Google has never heard of this URL at all — common for brand-new posts. |
The same data grouped by Google's own coverage labels (e.g. "Submitted and indexed", "Crawled — currently not indexed", "URL is unknown to Google"). This is exactly what Search Console would tell you — for every URL at once.
When Googlebot last visited your pages. Healthy, active sites keep most pages in the ≤ 30 days bucket. If a large share of pages hasn't been crawled for 90+ days, Google is losing interest — the widget (below) is the fix.
| Column | Meaning |
|---|---|
| VERDICT | Google's overall verdict for the URL: PASS indexed / indexable, NEUTRAL excluded by design, FAIL blocked or error. INDEXING_ALLOWED underneath confirms nothing blocks indexing. |
| COVERAGE STATE | Google's detailed label — same wording as Search Console ("Submitted and indexed", "Crawled — currently not indexed"…). |
| ROBOTS.TXT | Whether your robots.txt allows Google to crawl this URL. |
| LAST CRAWL | When Googlebot last fetched the page. This date comes from Google and can be weeks old. |
| LAST API CHECK | When IndexFixer last asked Google about this URL. Don't confuse the two: a check from 5 minutes ago can still report a crawl from last month. |
| ACTIONS | ↻ re-check the URL now · Copy the URL · GSC ↗ open this exact URL in Search Console's inspection view. |
Use the filters on top (status, robots, type, crawl age) and Export to CSV for offline analysis.
Most plugins stop at reporting. IndexFixer ships a front-end widget that lists your not-indexed posts as real internal links. Googlebot finds those links on pages it already crawls and follows them straight to the pages it's been missing. Once a page turns indexed, it drops out of the widget automatically and the next not-indexed page takes its place. URLs shown in the widget are also checked with priority, so the loop keeps turning.
Static internal linking gives every article the same links forever. The widget is dynamic — it always points at the pages that need discovery most right now:
today: every page → /article-8472/ (Googlebot has never crawled it) tomorrow: every page → /article-9211/ (not crawled for 94 days) after it indexes: every page → /article-10482/ (next in line)
Ordering is by neglect: pages Googlebot has never crawled come first, then the ones it hasn't visited longest — and only live, published pages ever make the list. Google's own documentation says internal links are the primary way it discovers a site's pages; the widget simply makes sure those links always point where they're currently needed.
Google separates crawling from indexing: after crawling a page it still decides whether to index it (quality, uniqueness, canonicals). The loop removes the discovery bottleneck — "Google can't find this URL, or won't come back to it". It cannot fix "Google saw this page and judged it thin or duplicate". IndexFixer tells you which case you're in:
| Setting | What it does |
|---|---|
| Post types to check | Which content types IndexFixer tracks (posts, pages, media, any custom post type). Un-ticking a type removes its URLs from tracking. |
| Check interval (hours) | How often the plugin refreshes data. 24 h is the sweet spot — Google's own data doesn't move faster. |
| Max URLs per check | Batch size per refresh cycle. |
| Automatic refresh | Auto-reloads dashboard numbers every 5 minutes while you watch. |
| Debug mode | Verbose logging for troubleshooting. Leave off. |
The Diagnostics tab shows system health: PHP/WordPress versions, Search Console connection status, and the plugin's database tables. If anything ever looks wrong, this is the screenshot to send us.
IndexFixer makes Google find your un-indexed pages (widget) and tells you the moment status changes. New posts are checked right after publishing. Indexing itself is Google's decision — for "Crawled — currently not indexed" pages, improving the content is usually part of the fix.
Google's URL Inspection API allows up to 2,000 checks per day per site. Large sites simply need a few days for the first full pass. Widget URLs and new posts always jump the queue.
No. You grant read-only Search Console access with two clicks; our servers handle the rest.
Email [email protected] — attach a screenshot of your Diagnostics tab if you can.