SeeMySaas documentation

When buyers ask ChatGPT, Claude, Perplexity or Gemini "what's the best tool for X", someone gets recommended. SeeMySaas finds the questions where that someone isn't you, puts a content crew on closing the gap, and tracks your visibility rising, engine by engine.

The product is built for founders, not SEO experts. Every number links to an action, every action tells you why it matters, and everything the crew produces waits for your approval before it touches your site or your name.

Getting started

  1. Sign up free, no card. Your first 7 days include the full platform, crew included. When the trial ends, your data stays saved and you subscribe to continue.
  2. Tell us your site. The crew scans it, builds your business profile, maps your competitors, and generates the buyer questions your customers ask AI.
  3. Run your first checks. Within the first day you'll have your AI visibility baseline (which engines know you, which recommend you) and your first site health scan.
  4. Work the loop. Open Discover to pick a gap, send it to the crew, approve what they make, and watch Progress move.

How it fits together: Find, Do, Track

1 · DiscoverFind the questions AI answers without you, the links worth earning, the competitors taking your spot, and the site issues holding you back.
2 · ActionsA short daily list of prepared moves: approve an article, paste a listing, send a pitch, apply a fix. Most take a few minutes because the crew did the prep.
3 · ProgressThe outcomes: your AI visibility score, wins as they land, engine-by-engine coverage, and every question the crew is working through.

The three nav items map exactly to this loop. Discover is where work starts, Actions is where it gets done, Progress is where you see it pay off.

Discover · Questions and the gap score

The Questions table with Easy win badges
The Questions table, best gaps first. The top rows carry an Easy win badge with the reason spelled out.

Every row is a real buyer question with four signals:

The table sorts by gap score by default: traffic times ease times how absent you are, divided by how crowded the question is. The top gaps get an Easy win badge with the correlation written out, for example "~613 visits/mo up for grabs, medium difficulty, you're absent on all 4 engines, only ConvertKit is cited". Click any column header to sort your own way instead.

The search box doubles as a question finder: type a topic and hit Find questions to discover new buyer questions around it, each arriving with real search volume and difficulty, deduplicated against the questions you already track.

The question workspace

The question workspace with keyword stages
One question, its target keywords, and where each one stands. Keywords already in motion can't be sent twice.

Click any question to open its workspace. From here:

The filter language

The Questions search box accepts plain text and typed filters, combined freely. Plain words match the question text; clauses filter the data:

FilterMeaningExample
difficultyDifficulty 0 to 100difficulty <= 25
trafficEstimated monthly traffictraffic > 500
volumeRaw search volumevolume >= 1000
intentBuyer intentintent = commercial
statusWhere you stand overallstatus = absent
competitorsRivals named on the questioncompetitors >= 2
claude chatgpt perplexity geminiYour status on one enginechatgpt = absent
nameQuestion text matchname = "email tool"

Status values are source (AI cites your content), mentioned (AI recommends you), absent, and unchecked. The engine cards on Progress deep-link into these filters, for example clicking the ChatGPT card opens chatgpt = absent.

The Links tab, ranked link opportunities
The links worth getting, ranked by value.

Two kinds of opportunities, ranked together:

Draft outreach hands the site to the crew: they prepare the pitch or listing and it appears in your Actions ready to send.

Discover · Competitors

A competitor detail page with the steal list
A competitor page. The steal list at the top shows the questions AI recommends them on and not you.

The list view benchmarks you against every rival on authority, backlinks, and AI share of voice (how often AI recommends them across your question set). Your own row is pinned on top for straight comparison. Add any competitor by name; the crew fetches and verifies their data.

The competitor benchmark list
The benchmark list, your row pinned on top.

Open a competitor to get:

Discover · Health: the whole-site scan

The site health scan with tiered findings
A real scan: score, then findings tiered into errors, warnings, and notices.

The crew crawls your sitemap and internal links (up to 200 pages) and checks everything that affects whether AI and search engines can read, trust, and cite your site. Findings come in three tiers:

FindingTierWhy it matters
Pages blocked by noindexErrorNo AI or search engine can see these pages at all.
Noindex pages in the sitemapErrorThe sitemap invites crawlers to pages that refuse them. Contradictory signals erode crawl trust.
Broken pages linked internallyErrorInternal links point at error pages. Crawlers waste budget, users hit dead ends.
Redirect chainsErrorTwo or more hops before the final page leak crawl budget and slow users down.
Indexable pages missing from the sitemapWarningThese pages exist but the sitemap never tells crawlers about them.
Thin pages (under 300 words)WarningAI engines cite substance. Pages this thin rarely get pulled into an answer.
No H1 / multiple H1sWarningThe H1 tells engines what the page is about. Zero means they guess, several dilutes the signal.
Missing title / meta descriptionWarningThe title is the strongest on-page signal; without a description, engines invent your pitch.
Slow pagesWarningPages over 3 seconds get crawled less and ranked lower.
Oversized imagesWarningHeavy images drag load time past the threshold where ranking suffers.
Title / description lengthNoticeToo short wastes the signal, too long gets truncated in results.
Nofollow pagesNoticeLink equity stops dead. Fine if intentional, costly if not.
A finding's ready-to-run fix prompt
Every finding carries a ready-to-run prompt with your affected pages baked in.

The crew can't edit your code, so it does the next best thing: Get the fix opens a prompt written for your coding agent (Claude Code, Cursor, or any other) with the exact affected URLs included. Copy, paste into your agent, done. Or add it to your Actions to handle later. The health score is the share of your pages affected, weighted by severity, and you can re-scan after every deploy.

Page health and "Fix this page"

A single page's health checks with the fix CTA
One page: performance, health checks, and the fix button when checks fail.

The Pages sub-view lists every published page with its Google rank, clicks, and indexation. Open one for its health checks: indexed in Google, enough depth to get cited (900+ words), and updated recently enough to stay the current answer.

When a page fails fixable checks, Fix this page puts the crew on it: the page gets expanded to fully answer its question and refreshed with current information. You approve the result before the live page changes, always.

Do · Your daily actions

The daily Actions list
The Daily list: one Do-this-first card, then everything else, filterable by type.

Actions is your working list. The crew prepares each item as far as it can, then hands you the last step, usually a paste, a click, or an approval. The header estimates total time so you know what you're committing to. The Sprint tab holds bigger, less frequent pushes; Daily is the routine.

Why the last step is yours: replies, listings and outreach go out under your name, on platforms that ban automation, to people who can tell. You stay the sender; the crew stays the writer. That's what keeps it authentic and safe.

Every action type

ActionWhat the crew preparedWhat you do
Approve an articleA full draft written for one of your target questions, reviewed by the crew's editor first.Read it, edit anything inline, approve. It publishes on your content schedule.
Fix a site issueThe exact change plus a ready-to-run prompt for your coding agent.Copy the prompt into Claude Code or Cursor, or apply the steps by hand.
Reply on RedditA relevant thread where buyers are asking, and a genuinely helpful drafted reply that mentions you where it fits.Review, adjust to taste, post it from your account.
Answer on QuoraA high-traffic question and a thorough drafted answer that positions you among the real options.Review and post.
Comment on LinkedIn / Reply on XA drafted reply to a relevant conversation.Review and post from your account.
Send an emailAn outreach pitch, for example to a roundup that ranks for your question but doesn't list you yet.Send it from your inbox.
Get listed / List on a directoryThe listing fields written out: name, tagline, description, ready to paste.Open the directory, paste each field, submit.
Repurpose to LinkedIn / Import to Medium / Post on social / Pin on PinterestYour published article reshaped for the channel, first line tuned as the hook.Post it.
Ask for a reviewA review request for the comparison sites AI cites.Send it to a happy customer.
Set upA connection or configuration step the crew needs, for example connecting Google Search Console.Follow the steps once.

Track · The Progress page

The Progress dashboard
Score, recent progress as a timeline, your next best gap, and visibility by engine.

Progress answers one question: are AIs recommending you yet?

The full wins history page
The full progress history behind Show all.

Track · Questions in progress

The tracking view with per-keyword stages
Every committed question, its keywords, and each keyword's execution stage.

The second tab on Progress is the worklist: every question you've sent to the crew, sorted with the most work remaining first. Each keyword moves through three stages:

The percentage on each card is coverage: how much of that pipeline is done across the question's keywords. Click any question to open its workspace.

Connect your blog · the publishing endpoint (for developers)

If you'd rather build the endpoint yourself than paste our AI prompt, here is the whole contract. SeeMySaas publishes by sending one HTTP request per article to a URL you provide in Settings → Publishing.

The request. POST to your endpoint with Content-Type: application/json. If you set an auth header in Settings we send it verbatim (either as Header-Name: value, or a bare token which we send as Authorization: Bearer <token>). The body:

{
  "title": "The 7 best Semrush alternatives, tested",
  "slug": "best-semrush-alternatives",
  "body_md": "Full article as Markdown…",
  "meta_description": "150-char summary for the page's meta tag",
  "byline": "your brand",
  "hero_image_url": "https://…jpg or null",
  "published_at": "2026-07-29T12:00:00Z"
}

Your endpoint must:

That's the whole integration: one route, JSON in, page out. Test it from Settings → Publishing with the validate button, it sends the probe and shows you exactly what came back.

Connecting Google (Search Console + Analytics)

Connecting Google turns estimated numbers into real ones: your actual rankings, clicks and index status from Search Console, and your real visitors from Analytics. The crew also reads both to learn which articles convert and double down.

One connection, two pickers. In Settings → Google you sign in once with the Google account that owns your site's data, then pick your Search Console site and your Analytics property. If your own site is in the list, we select and save it for you automatically. Changes save as you pick them.

If your site is not in the Search Console list: it is not verified in that Google account yet. Open Search Console, choose Add property, enter your domain and verify via the DNS record it gives you. Then return to Settings and refresh the list.

If the Analytics list is empty: the account has no GA4 property for your product yet. Two steps:

Data starts flowing within a day. Search Console history backfills on its own; Analytics counts from the day the tag went live.

Behind the scenes · Your AI agents

LeadIris runs the room: reviews every draft against your brief before you ever see it, and routes work between the others.
StrategyAster researches questions and keywords, briefs every article, verifies competitor claims from their own pages, and runs your audits.
WriterWren writes the articles: answer-first openings, verified numbers only, built to be the source AI cites.
DesignLuma creates the hero and body images for every article.
CommunityEcho finds the Reddit threads and Quora questions worth answering, and drafts the replies.
DistributionDex reshapes published articles for LinkedIn, Medium, social and Pinterest, and prepares listings and outreach.

How an article ships

1 · BriefAster researches the question and writes the brief, fetching competitor pages so every number is verified at the source.
2 · DraftWren writes from the brief. Specific claims must come from verified facts; invented numbers are forbidden.
3 · ReviewIris reviews against the brief and the verified facts. If something's off, it goes back for a revision round, not to you.
4 · Your approvalYou get the finished piece in Actions. Edit inline if you want, approve, and it publishes. Nothing goes live without you.

If a draft fails review, the crew fixes it itself: the brief is re-verified against live sources and the article rewritten, up to two full rounds. You only see a flagged draft when two grounded rounds genuinely couldn't settle it, with the objections listed so you can decide.

The same gate applies to refreshes: when a page is expanded or updated, the new version goes through review and then your approval before the live page changes in place.

Trial and billing

Getting help

The fastest way to reach us is the Need help? DM me link in the app sidebar, which goes straight to the founder. Every screen also carries small info marks next to numbers and columns; hover or tap them for a plain-language explanation of exactly what you're looking at.

Back to top ↑