AI marketing agents you talk to, not tools you configure
Most SEO software hands you dashboards and leaves the work to you. IDMA gives you a manager agent and five specialists that do the work and report back in one conversation. Here is what each part actually does — the commands, the permissions they ask for, and the things they will never do without asking.
Everything on this page describes an SEO and content project — the three services that run today. The other project kind, a voice assistant, has no agents, connectors or automations, and does not answer calls yet. Social media management, cold marketing and ads campaigns are on the roadmap and are not built.
Your first project analyses itself
You don't start with an empty workspace and a blinking cursor. Creating a project starts the work — by the time it opens, IDMA has already been through your site.
Who you actually compete with
Your field of work and every seed keyword are searched separately, not mashed into one query — they turn up different sets, and a site that ranks for several of them is a competitor in a way one that ranks for a single term isn't. The top ten by Google rank are kept, each recorded with the query that found it and where it placed.
A technical audit of the whole site
Up to 100 pages crawled for indexing, metadata, headings, schema, images and speed, scored out of 100 and turned into a priority-ordered fix list. The full page inventory and every issue are downloadable as an Excel workbook, one sheet per kind of detail.
A content audit of what you've published
Your landing pages and blog read for E-E-A-T signals, grouped into topic clusters, and compared against the competitors above to find the subjects they cover and you don't.
None of it arrives as a wall of reports. The findings are stored, not posted, so your first conversation starts on a blank composer exactly as it would otherwise — the difference is that the manager has already read both audits, and answers “what's worst on my site right now?” from real findings instead of starting a five-minute job.
One thread, one manager
There is no dashboard to learn and no agent picker to get wrong. You open a project, describe what you want, and the DM Manager decides who does it.
Every project is one conversation. Ask in plain language — “why did traffic drop last week?” — and the DM Manager works out which specialists it needs, runs them, and answers in the same thread. Delegation is visible: you can always see which agent produced which answer, and say so if it picked wrong.
Work never blocks the chat. Long jobs come back as a “working” message and stream their results in when they finish, so a 40-page crawl doesn't freeze the window you're typing in.
Context stays in the project. The DM Manager remembers the audit it ran on Tuesday when you ask about rankings on Thursday, so you aren't re-explaining your site every time.
Start a project freeProject: acme-store
weekly report · Mondays 09:00Pulling Search Console for the last 60 days and re-auditing the pages that lost the most clicks. Two minutes.
Clicks are down 23%, and almost all of it is six product pages that fell from page one. They dropped the week your category template changed — their meta descriptions are now identical.
The Technical Fixer can rewrite those six descriptions, or the Content Writer can rework the pages properly. Which way do you want to go?
Slash commands: skip straight to a specialist
You never have to use these — plain sentences work everywhere. They just save a round-trip when you already know who you want.
| Command | Agent | What it does | Example |
|---|---|---|---|
/analyzeralso /audit, /technical-seo, /analyze | Technical SEO Analyzer | Crawls your site and scores its technical health — missing meta descriptions, duplicate H1s, Core Web Vitals, indexing — and hands back a priority-ordered fix list. | /analyzer max_pages=100 |
/content-analyzeralso /content-seo, /content | Content SEO Analyzer | Reads your published content for E-E-A-T signals, groups it into topic clusters, and finds the gaps competitors are covering and you aren't. | /content-analyzer |
/strategyalso /plan | Strategy Generator | Merges your latest technical and content audits into one plan: prioritised actions, a content calendar, and what each change is expected to move. | /strategy |
/fixeralso /fix | Technical Fixer | Applies the fixes it safely can through your WordPress connector, and writes step-by-step guidance for the ones that need a human. Previews by default — it never edits your live site unasked. | /fixer dry_run=true |
/writeralso /write, /draft | Content Writer | Turns a topic into an outline and a full draft shaped by your audits and business context — ready for your edit, not auto-published. | /writer topic="Best CRM for SMBs" type=blog |
Typing / in the composer opens the list with autocomplete, so you don't have to memorise any of it.
Connect your own data
Agents work with what your site actually reports, not with industry averages. Connectors are set up inside the project that uses them — not buried in an account settings page.
WordPress
- In WordPress, go to Users → Profile and scroll to Application Passwords.
- Type a name you'll recognise — “IDMA” — and click Add New Application Password.
- Copy the password WordPress shows you. It is displayed once and never again.
- In IDMA, open the project's Connectors panel and enter your site URL, your WordPress username, and that password.
- IDMA immediately checks the credential and tells you which role it has — an account that can't edit content is caught here, not mid-fix.
What it unlocks: The Technical Fixer applies fixes directly to your site, and drafts can be published to your CMS instead of copy-pasted.
An application password is revocable from WordPress at any time and never exposes your account password. IDMA needs an Editor or Administrator account to change content.
Google Search Console
- In Google Cloud Console, create (or pick) a project and enable the Search Console API.
- Go to IAM & Admin → Service Accounts, create one, then add a key of type JSON and download it.
- Open Search Console → Settings → Users and permissions, and add the service account's client_email as a user with Full permission.
- Paste the whole JSON key file into IDMA's Connectors panel.
- IDMA lists the properties that key can actually see — the most common mistake is a valid key that was never added to the property, and this catches it.
What it unlocks: Real impressions, clicks, positions and indexing status inside technical audits and reports — instead of estimates.
Read-only. IDMA requests the webmasters.readonly scope and cannot change anything in Search Console.
Semrush
- In Semrush, open Subscription info → API units and copy your API key.
- Paste it into the project's Connectors panel.
- IDMA runs one small query to confirm the key works and has units available.
What it unlocks: Backlink profile and domain-level competitive metrics in technical audits.
Bring your own key — IDMA uses your Semrush plan and its API units. Requires a plan that includes API access.
SerpAPI
- Copy your API key from the SerpAPI dashboard.
- Paste it into the project's Connectors panel — or leave it blank to use IDMA's own key where available.
- IDMA checks the key and reports how many searches remain on it.
What it unlocks: Competitor discovery — IDMA finds who actually ranks for your topics instead of relying on the competitors you already know about.
Optional. This is the one connector that falls back to IDMA's platform key when you don't set your own.
KWfinder
- In your Mangools account, open Settings → API and copy the access token.
- Paste it into the project's Connectors panel.
- IDMA runs one keyword lookup to confirm it works.
What it unlocks: Search volume and keyword difficulty scores, so the Strategy Generator ranks opportunities on real numbers.
Bring your own key. Requires a Mangools plan with API access.
Google Custom Search
- In Google Cloud Console, enable the Custom Search API and create an API key.
- At programmablesearchengine.google.com, create a search engine and copy its Search engine ID (the cx value).
- Paste both into the project's Connectors panel.
What it unlocks: Source and keyword discovery while setting up a project.
Read-only search. Google's free tier covers 100 queries per day.
Credentials are stored per project, so a client's Search Console access never leaks into another client's workspace. Disconnect one at any time and the agents that depend on it say so instead of quietly falling back to estimates. Full setup instructions are in the docs.
Put the repeat work on a schedule
Anything you can ask for once can run on a cron. The results land back in the project thread, where you review them like any other message.
Auto SEO Fixer
Weekly · Mondays 09:00- What triggers it
- Re-crawls the site on your schedule and diffs the result against the previous run.
- What you get
- One thread message: what regressed, what's newly broken, and what it can fix — each fix listed as an item you approve or skip.
It proposes changes. It never edits your site unprompted.
Auto Content Generator
Monthly · 1st at 08:00- What triggers it
- Takes the keyword gaps the Strategist found and turns the highest-opportunity ones into briefs.
- What you get
- Outlines and first drafts in the project thread, and optionally saved to your CMS.
It saves a draft. Nothing is published on your behalf.
Schedules are per project and editable at any time — change the cadence, pause one, or delete it. Every run is logged, so you can see what an automation did last Monday without taking its word for it.
Works with the tools you already use
IDMA connects through each vendor's own API using credentials you provide. No partnership or endorsement is implied.
- WordPressAt launch
- Google Search ConsoleAt launch
- Google Analytics 4At launch
- SemrushAt launch
- SerpAPIAt launch
See it on your own site
The free analyzer runs a dozen checks on your homepage without an account. Everything above starts once you create your first project.