Work in progress · Documented plans
What we are building, testing and planning for Rank-in-Maps. Follow the work and help shape it. Completed features leave this list.
Evidence reviewed 2026-10-15
Working today. Included with a paid plan.
Gabriel reads your audit, picks the next fix, drafts it and waits for your OK in the approval queue. You learn as it goes.
Why a paid plan: Fixes change what Google shows on your profile, so they run through your approval queue on a paid plan. Nothing is published without your OK.
Chat with Gabriel about your business, with your audits and Second Brain within reach.
Why a paid plan: Beta on a paid plan. Live acceptance checks after the move to the new chat runtime are still open.
The knowledge graph of local SEO research behind Gabriel's advice. A public preview is open to everyone.
Why a paid plan: Beta on a paid plan. The full library inside the dashboard is included with it.
Implementation has started; these are the remaining steps.
Extend the browser extension's observed controls into evidence from the actual Google Business Profile on screen.
Why not yet: The extension's page-reading modules are not yet wired into the running extension, so what it shows is not yet a live observation of the profile.
Next: Extract displayed description and category values, produce evidence-backed findings, and verify switching between locations.
Real tools you can try, with specific limitations.
A working campaign planning and drafting workspace with saved business-specific drafts. A separate demo mode is used without a connected business.
Why not yet: The phone preview and the connected-business workflow have not been verified, so it stays an experiment.
Next: Complete the phone preview and verify the connected-business workflow. This does not promise publishing to every channel.
Documented work that is not available yet. No release dates are promised.
Turn saved website audit findings into reviewable code changes, starting with GitHub-connected sites.
Why not yet: Nothing edits a website yet. The audit hands findings off as issues only; the pull-request step and GitHub permissions are not built.
Next: Prepare the change, obtain owner approval, create a draft PR through an executor and record the result. WordPress follows later.
An owner-wide queue for reviews needing attention, with response-time targets and review alerts.
Why not yet: Reviews sync one location at a time, and there is no owner-wide queue or alert channel defined yet.
Next: Scope the queue, overdue views and alert channel. Assignment to multiple users is a separate capability.
Dated, versioned review records for comparing changes over time, beyond the existing sync and one-off CSV exports.
Why not yet: Review sync keeps the current state, not dated versions, and the snapshot contents and cadence are not decided.
Next: Set the snapshot contents, cadence and storage contract before building scheduled capture.
Build on the existing grid to show what changed, where and when, separating your visibility from competitor movement.
Why not yet: The grid stores dated scans, but nothing yet compares your movement with competitors and explains it.
Next: Connect dated grid evidence to a client-safe explanation that can accompany a report.
See where you show up in the map pack around your business, point by point.
Why not yet: Each scan buys live map data, so it is admin-only until usage limits and pricing are set.
Next: Open it to customers with limits and pricing in place.
