Documentation

Every screen in SEOLinkMap has a page here. If the account is new, start with Getting Started with Your Dashboard. If it is already set up and you are looking at it wondering which button matters, start with What Do I Do Next.

The guides fall into three groups. Product mechanics cover projects, pages, keywords, and the page relationships that build a LinkMap. Agency operation covers team roles and permissions, sharing, client communication, and the calendar and reminders the whole team can see. The MCP guides connect Claude or another chat tool straight to your project data, which is where most of the work happens once setup is done.

Guides to the Paid Work

The work you pay for is documented before you buy it, so nothing arrives as a surprise. Backlink Prospector screens the pages ranking for a keyword and hands back only the domains worth writing to, priced per keyword. Competitor Research is priced per keyword too and measures what the pages beating you have in common.

AI Visibility tracks which sites the AI answer engines cite for your questions, every day. The AI Visibility Methodology is the long one, and the one to read before trusting any citation number, ours included. It names every statistic behind the panel, including the tests that stop a lucky week from reading as progress.

Where to Start Reading

Reading order beats reading everything. Connect a chat tool with How to Connect to MCP Servers, then run the master workflow once end to end on a single project.

That one pass touches most of the product: a crawl, a look at site structure, the visualization, and a report you can hand to somebody. The rest of these pages are there for the day you need one screen in detail.

Two MCP Servers, Not One

The public server answers questions about SEOLinkMap and needs no account, which is what makes it useful for testing whether your client speaks the protocol at all. The private server is the one that reaches your projects, your crawls and your purchased research.

Private MCP and Agentic SEO Workflows covers the part where an agent queues work rather than just reading, and the approval API closes that loop without a person clicking approve.

Where a guide and the app disagree, the app is right and the guide is stale. Tell us and we will fix the page.