Have something to say?
Indexing via API/IDE: submit URLs and get per-URL status
Extend the Cromojo MCP connector (currently read-only, Page Performance tools) to cover Indexing, so developers and agencies can act on specific pages directly from their IDE or AI agent (Claude Code, Cursor, Codex, ChatGPT, etc.). What's being asked 1. Submit URLs for indexing from the IDE/agent (write access) A new MCP tool like submit-urls-for-indexing that respects the account's daily quota. Return which URLs were accepted vs. rejected (quota exhausted, invalid, etc.). 2. Per-URL indexing status (read access, more granular than bulk) Not just "X indexed / Y pending / Z not indexed" counters, but a URL-by-URL view returning for each URL: current indexing status, reason if not indexed, when last checked. Matches what the September 2026 Google Indexing rebuild already shows in the dashboard — just surfaced through the MCP so IDE workflows can read it. Why this matters Developers and agencies working on specific pages (new product launches, blog posts, pages fixed after a redirect) need to confirm indexing one URL at a time, inside their coding workflow — not by context-switching to the Cromojo dashboard. Bulk counters don't answer "is the page I just shipped actually indexed yet?" From a customer conversation (2026-10-09) "Feature request on this — be great if we can submit pages (within quota) via the IDE/agent.""Oh and URL by URL visibility of what's indexed and what isn't. That would make page work far more targeted and accurate rather than bulk numbers." Related existing work MCP Integration with Analytics — In Progress. The Indexing side is a parallel ask on the same MCP surface. Graph showing indexed/deindexed pages — In Progress, 39 upvotes. Overlaps on "better visibility into indexing state", but focuses on trend charting in the dashboard rather than per-URL + programmatic access. Google Indexing: rebuilt with per-page diagnostics (shipped Sept 2026) — already delivered per-URL visibility in the dashboard UI. This request extends the same data model to the MCP/API surface. Suggested scope Phase 1 (read): add get-url-indexing-status (single URL) and list-urls-indexing-status (per site, filtered) MCP tools. Phase 2 (write): add submit-urls-for-indexing MCP tool, quota-aware, with clear accept/reject feedback per URL.
Automated A/B testing
Test page changes and let Cromojo pick the winner based on revenue, not just clicks.
stop adding new owners without notice and or approval
I've been using Cromojo for a long time. I'm not sure I've added any domains or the associated cromojo emails as owners to GSC accounts since before the name change. Over the weekend, I started receiving emails from a number of my GSC domains/URL prefix properties that new emails were added as owners. One of those was bulkindexing@bulkindexing-3993tpcfak.iam.gserviceaccount.com which I've confirmed is in Cromojo. When did the service start adding new emails as owners? This is concerning because it was hard enough to have companies be okay with adding some ones, but every owner of the account was alerted by google of new emails being added as owners. This has caused stress with others on the teams at three companies and has reduced trust in both me and Cromojo with our team.
SEO Revenue
Most SEO tools tell you how much traffic you get from Google. Almost none tell you how much money it makes. The SEO Revenue tab answers one question: Which searches on Google actually earn us money — and which just look busy? A page can get 5,000 visits from Google and earn nothing. Another can get 80 visits and pay the rent. Traffic reports treat those two the same. This tab doesn’t.
Allow Users to Embed URL Monitor in Project Management Tasks
I have a workflow that involves checking the index status of my clients. I would like to embed URL Monitor directly into the task as I have with other apps. This integration would enhance my workflow's speed and efficiency.
Weekly Email Notifications contain Repeating Page Indexing Data
I’m encountering an issue with the weekly notifications regarding page indexing. Each week, the notification email reports a certain number of new pages indexed (e.g., "XX new pages indexed"), but the actual list of pages often includes ones that were already reported in previous weeks. This makes it confusing to accurately track the real progress of new page indexing. Additionally, when I attempt to verify or dig deeper using the reporting feature, I often encounter a "500 Internal Server Error," which further complicates tracking and validation efforts. Could you please look into: Why previously indexed pages are appearing repeatedly in the weekly notifications? What is causing the 500 errors in the reporting feature? I would appreciate any guidance on resolving these issues or an estimated timeline for a fix. Thank you!
No index Feature
Please add a feature where I can choose what pages to index and exclude the ones to not or an option to select the pages for "No index"
Sitemap manual upload/update
Your tool does not regularly update the site map on my site it hasnt updated since the 19th of March which is 3 days ago but ive included "Noindex" in 40 pages which your tool is not picking up which is annoying. Please add a feature where we can update the site map or re-upload in your tool daily or that it updates every day automatically
API Integration for Make.com
'- Submit Urls for Indexing via API integration Get list of submitted and indexed urls per domain maybe ability to retrive indexing statistics over all webpages
Crawl Pages to index based on RSS Feeds
Use RSS feeds instead of sitemaps to trigger the automatic indexing process.
Email Notifications for Secondary Search Console Accounts
Currently, all email notifications are sent to the primary Google account associated with the URLMonitor tool. I would like to request the ability to configure email notifications for additional websites linked to other Search Console accounts. Specifically, the notifications should be sent to the email address associated with the respective Search Console account instead of the primary account. This would improve tracking and communication for users managing multiple accounts.