Maeve Social

maevesocial.com

Social media scheduling and management platform for creators and teams

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

Maeve Social scores 91 of 100: 49 of the 50 base points, 43 of the 50 agent-layer points, no penalties.

Earned

49 of the 50 base points above the line, 43 of the 50 agent-layer points below it.

3 prompts away

Copy them below ↓

Taken back

Earned, then taken back by penalties.

Penalties0

How scoring works · current methodology →

Through a bot’s eyes

“Maeve Social is a social media management and project management platform that lets users schedule posts across nine platforms, manage comments and DMs, collect client approvals, and connect AI agents.”

Simulated from the response GoodForBotsBot received on 19 Oct 2026, not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns that Maeve Social is a social media scheduling and project management tool. The text covers features such as calendar management, multi-platform publishing, workbench planning spaces, a social inbox for auto-replies, analytics with PDF exports, an approval process workflow, and competitor tracking. The homepage outlines platform-specific controls for Instagram, Facebook, Threads, and TikTok. Provided auxiliary files add significant details: the llms.txt file provides links to documentation and developer guides, while the JSON-LD schema supplies concrete pricing tiers ranging from twenty-five to one hundred ninety-nine dollars per month, organizational details, and founder names. Contact information and developer endpoints are also explicitly documented in the provided files.

What is Maeve Social?

Maeve Social is a social media management software platform designed for creators, businesses, and agencies. It offers a centralized workspace to plan, write, schedule, and publish posts across nine platforms, including Instagram, Facebook, TikTok, YouTube, Threads, and LinkedIn.

The platform features a calendar, content planning tools, automated DMs and comment management, analytics exports, and a client approval portal that requires no logins. Additionally, Maeve Social supports AI agent integrations through an MCP server, CLI, and REST API, enabling users to manage workflows via tools like Claude, ChatGPT, and Cursor.

3 prompts, 9 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

State a position on AI crawlers

robots.txt names no AI crawlers, so every operator has to guess.

Read prompt

My website maevesocial.com scored 91/100 on Good for Bots (Excellent). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: state a position on AI crawlers in robots.txt.

The check it fails is "States a position on AI crawlers", worth 5 points. What the scanner saw: robots.txt names no AI crawlers, so every operator has to guess.

A `robots.txt` that says nothing about AI crawlers leaves every operator to guess what
this site wants, and they guess differently. The point of this task is to state a
position, whichever position that is.

The thing most people get wrong: the major operators run **separate crawlers for
separate purposes**, and blocking one does not block the others. OpenAI runs GPTBot for
training, OAI-SearchBot for search indexing, and ChatGPT-User for pages a user asks
about. Anthropic runs ClaudeBot, Claude-SearchBot and Claude-User for the same three
jobs. Decide about each job, not about the vendor.

A common and reasonable position is to refuse training while staying visible in AI
answers:

```
# Training: no
User-agent: GPTBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: CCBot
Disallow: /

# Search and user-requested fetches: yes
User-agent: OAI-SearchBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Claude-User
Allow: /
```

Work out what this project wants before copying that. Allowing everything is
equally valid and earns exactly as much here; what is being measured is whether there is
an explicit answer, not which answer it is.

Blocking a documented search or user-fetch control declares a refusal of that route.
Some user-triggered fetchers may still retrieve a page; do not promise complete invisibility.
Google-Extended also controls grounding, while CCBot publishes a reusable dataset.
Their training opt-outs remain neutral in our score.

Two things about how this is judged. The list of crawler tokens we recognise is a
snapshot of a moving target: operators add crawlers faster than any scanner tracks them.
A rule for a token we have not seen yet is a good rule that earns nothing here until we
catch up. And a position stated in a vocabulary rather than in rules, such as
`Content-Signal`, is a different check; this one is about the `User-agent` groups.

Use the operator sources in the report's crawler catalogue. Unconfirmed or retired names
do not count; aliases for one control count once. One mixed-use control still
counts as one engagement group.

The whole report, as markdown, is at https://goodforbots.com/r/maevesocial.com.md?scan=cmvezk3qr01o101qzwq8ccntc. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

+2.5

Declare AI usage preferences

No usage declaration found in robots.txt or the final successful homepage response header.

Read prompt

My website maevesocial.com scored 91/100 on Good for Bots (Excellent). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: declare the site's AI usage preferences in robots.txt or HTTP headers.

The check it fails is "Declares AI usage preferences", worth 2.5 points. What the scanner saw: No usage declaration found in robots.txt or the final successful homepage response header.

Blocking a crawler says who may fetch a page. This says what may be done with the
content afterwards (trained on, indexed, quoted in an answer), which is a different
question, and one a site can answer without blocking anybody.

There are two vocabularies for it and either is fine. Cloudflare's `Content-Signal` is
deployed at scale; the IETF AIPREF working group's `Content-Usage` is the standards-track
version. Pick one.

Cloudflare's, placed inside a user-agent group:

```
User-agent: *
Content-Signal: ai-train=no, search=yes, ai-input=yes
Allow: /
```

The three categories are `ai-train` (training or fine-tuning models), `search` (building
a search index that links back here) and `ai-input` (feeding the content to a model at
answer time, such as retrieval-augmented generation). Each takes `yes` or `no`.

The IETF version, with reversed naming for the training category and single-letter
values:

```
User-agent: *
Content-Usage: train-ai=n, search=y, ai-use=y
Allow: /
```

Alternatively, send the same IETF preference as an HTTP response header:

```http
Content-Usage: train-ai=n, search=y, ai-use=y
```

Configure it on the content responses it is meant to cover, including the final
homepage response after redirects. A header applies only to that response's content;
it is not a site-wide declaration. Do not put a robots.txt path prefix in it.
The scanner samples the final successful homepage response and awards this check
once even when both robots.txt and the header declare preferences.

Use lowercase category labels and the unquoted tokens `y` or `n`. Parameters are
ignored. Repeated HTTP fields form one dictionary: a duplicate category keeps its
last value. Keep that distinct from conflicts between separate applicable AIPREF
statements, where disallow takes precedence over allow by default. Keep the
carriers consistent with the intended policy; a header does not automatically
override robots.txt.

Decide what this project wants. A common position is to refuse training while
allowing search and grounding, so the site stays citable without feeding a model.
Omitting a category is allowed and means "unstated", not "allowed".

One caution: nothing compels a crawler to honour either directive. This is a stated
preference, not an enforcement mechanism. The standards-track vocabulary is also a draft
that can still change under you.

+1.3

Expose control roles, states and relationships

299 of 300 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Read prompt

My website maevesocial.com scored 91/100 on Good for Bots (Excellent). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: expose valid control roles, states and relationships.

The check it only partly passes is "Controls expose roles, states and relationships", with 1.32 points of it still on the table. What the scanner saw: 299 of 300 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Use native HTML controls when they implement the intended behaviour. Native
checkboxes, selects and range inputs already expose their corresponding semantics;
do not duplicate them with ARIA just to satisfy this check.

For custom widgets, choose a recognised non-abstract role and supply its required
states. Keep declared state values consistent with the widget. Resolve relationship
attributes such as aria-controls, aria-labelledby and aria-activedescendant to the
intended elements in the same document.

```html
<button type="button" aria-expanded="false" aria-controls="filters">Filters</button>
<div id="filters" hidden>
<label><input type="checkbox" name="available">Available only</label>
</div>
```

Update aria-expanded and the panel's visibility together in the event handler.
Do not treat this markup example as a working custom widget without implementing
its behaviour. For sliders, expose a current value within its bounds. Preserve
implicit defaults and native semantics instead of requiring every optional state.

Verify keyboard use, focus movement and state changes in the browser. This check
reads the collected HTML and checks a defined subset of ARIA; it cannot prove
that a declared state matches runtime behaviour or that the widget is accessible.

Pro

11 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for Maeve Social from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

All 36 checks

Evidence for each, in Markdown →

Select a check to see what we found and how it is graded.

Readable base

48.7 / 50

3.5 of 3.5 points.

robots.txt is valid, with 1 user-agent group.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

8.8 of 8.8 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, Person, ContactPoint in valid schema.org JSON-LD.

10.5 of 10.5 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

4.4 of 4.4 points.

282 of 282 assessed homepage links and buttons have a nonempty accessible name.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

1.3 of 2.6 points.

299 of 300 assessed homepage controls and role declarations meet the static role, state and relationship checks.

1.8 of 1.8 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

0.9 of 0.9 points.

All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.

Agent layer

42.5 / 50

11.3 of 11.3 points.

/llms.txt is well formed: 9 links across 3 sections.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

12.5 of 12.5 points.

llms.txt points at 7 markdown versions of pages.

10 of 10 points.

All 4 pages read pass. The homepage serves markdown on `Accept: text/markdown`.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

1.3 of 1.3 points.

All 4 pages read pass. The homepage points at a markdown version of itself through the page markup.

Penalties

− 0

Penalty: 0 of 15 points.

Penalty: 0 of 20 points.

Penalty: 0 of 25 points.

Penalty: 0 of 10 points.

Penalty: 0 of 3 points.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Adds +1 to the badge when found.

What we found

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

Passes: Homepage
The homepage marks its content root, its heading outline and its landmarks.
Passes: /social-media-management-software-for-agencies
The page at /social-media-management-software-for-agencies marks its content root, its heading outline and its landmarks.
Passes: /features/analytics-reports
The page at /features/analytics-reports marks its content root, its heading outline and its landmarks.
Passes: /docs/authentication
The page at /docs/authentication marks its content root, its heading outline and its landmarks.

Extracted words: 1,378
Headings: 33
H1 headings: 1

Content and navigation

Share of extracted homepage words by marked region. Navigation inside a header, footer or main region is counted once, under navigation.

Extracted words and their share by page region
Region	Words	Share
Main region	1,163	84.4%
Navigation	162	11.76%
Page header	4	0.29%
Page footer	49	3.56%
Other text	0	0%

70 words appear before the first main-region text in HTML order.

Diagnostic only; it does not affect the score. Recognised hidden text and script payloads are excluded. Stylesheet visibility and repetition across pages are unknown. A large menu is not necessarily a problem.

Heading outline · first 4

H1The Social Media Scheduler Project Management Platform
H2Save yourself hours scheduling
H2Like Notion, Miro and Monday, built in
H2Automatic replies & Social inbox

29 more headings recorded

Page landmarks

banner
contentinfo
navigation
region

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "gaps": [],
  "pages": [
    {
      "url": "https://maevesocial.com/",
      "reason": "structured",
      "status": "pass",
      "summary": "The homepage marks its content root, its heading outline and its landmarks.",
      "homepage": true
    },
    {
      "url": "https://maevesocial.com/social-media-management-software-for-agencies",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /social-media-management-software-for-agencies marks its content root, its heading outline and its landmarks.",
      "homepage": false
    },
    {
      "url": "https://maevesocial.com/features/analytics-reports",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /features/analytics-reports marks its content root, its heading outline and its landmarks.",
      "homepage": false
    },
    {
      "url": "https://maevesocial.com/docs/authentication",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /docs/authentication marks its content root, its heading outline and its landmarks.",
      "homepage": false
    }
  ],
  "roots": [
    {
      "words": 1964,
      "source": "element",
      "hierarchicallyCorrect": true
    }
  ],
  "reason": "structured",
  "h1Count": 1,
  "headings": [
    {
      "text": "The Social Media Scheduler Project Management Platform",
      "empty": false,
      "level": 1
    },
    {
      "text": "Save yourself hours scheduling",
      "empty": false,
      "level": 2
    },
    {
      "text": "Like Notion, Miro and Monday, built in",
      "empty": false,
      "level": 2
    },
    {
      "text": "Automatic replies & Social inbox",
      "empty": false,
      "level": 2
    },
    {
      "text": "Analytics that are actually useful",
      "empty": false,
      "level": 2
    },
    {
      "text": "The Approval Process",
      "empty": false,
      "level": 2
    },
    {
      "text": "Competitor Analysis",
      "empty": false,
      "level": 2
    },
    {
      "text": "Post to all your social channels from your AI agent",
      "empty": false,
      "level": 2
    },
    {
      "text": "Maeve Social on Your iPhone and Mac",
      "empty": false,
      "level": 2
    },
    {
      "text": "So Who Is It Made For?",
      "empty": false,
      "level": 2
    },
    {
      "text": "Creators & Founders",
      "empty": false,
      "level": 3
    },
    {
      "text": "Businesses",
      "empty": false,
      "level": 3
    },
    "… 21 more items"
  ],
  "bodyWords": 2187,
  "landmarks": [
    {
      "role": "banner",
      "named": false,
      "source": "native",
      "element": "header"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "contentinfo",
      "named": false,
      "source": "native",
      "element": "footer"
    },
    "… 6 more items"
  ],
  "textRatio": 0.0217,
  "truncated": false,
  "articleCount": 10,
  "contentWords": 1964,
  "headingCount": 33,
  "headingSkips": [],
  "requirements": {
    "landmarks": true,
    "contentRoot": true,
    "headingOutline": true
  },
  "landmarkRoles": [
    "banner",
    "contentinfo",
    "navigation",
    "region"
  ],
  "hiddenMainCount": 0,
  "textComposition": {
    "words": {
      "main": 1163,
      "other": 0,
      "footer": 49,
      "header": 4,
      "navigation": 162
    },
    "shares": {
      "main": 0.8439767779390421,
      "other": 0,
      "footer": 0.03555878084179971,
      "header": 0.002902757619738752,
      "navigation": 0.11756168359941944
    },
    "version": 1,
    "truncated": false,
    "totalWords": 1378,
    "analysisLimited": false,
    "mainRegionCount": 1,
    "wordsBeforeMain": 70
  },
  "emptyHeadingCount": 0,
  "misnestedMainCount": 0
}

Related checks

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://maevesocial.com/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules

Declared allow · Scan admission
- GoodForBotsBot/1.0 (+https://goodforbots.com/bot)
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://maevesocial.com/
robots.txt is present and valid
Declared allow · robots.txt
- goodforbotsbot (Site diagnostics)
- * (Default robots group)
- oai-searchbot (ai-search)
- claude-searchbot (ai-search)
- perplexitybot (ai-search)
- mistralai-index (ai-search)
- kimi-searchbot (ai-search)
- amzn-searchbot (ai-search)
- meta-webindexer (ai-search)
- exasearchbot (ai-search)
- aiwebindex (ai-search)
- duckassistbot (ai-search)
- shapbot (ai-search)
- yandexadditional (ai-search)
- yandexadditionalbot (ai-search)
- gptbot (ai-training)
- claudebot (ai-training)
- mistralai-training (ai-training)
- kimibot (ai-training)
- ai2bot (Unknown)
- applebot-extended (ai-training)
- webzio-extended (ai-training)
- chatgpt-user (user-fetch)
- claude-user (user-fetch)
- perplexity-user (user-fetch)
- mistralai-user (user-fetch)
- kimi-user (user-fetch)
- amzn-user (user-fetch)
- diffbot-user (user-fetch)
- firecrawlagent (extraction)
- webzio (extraction)
- meta-externalfetcher (user-fetch, agent)
- google-extended (ai-training, grounding)
- meta-externalagent (ai-training, product-improvement)
- amazonbot (ai-training, product-improvement)
- ccbot (open-dataset, ai-training)
- googlebot (search)
- bingbot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://maevesocial.com/
https://maevesocial.com/robots.txt
```
User-agent: *
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access

Observed · Direct request
- GoodForBotsBot/1.0 (+https://goodforbots.com/bot)
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://maevesocial.com
```
HTTP 200
```
Serves the homepage over HTTPS with HTTP 200
Observed · Final homepage response
- GoodForBotsBot/1.0 (+https://goodforbots.com/bot)
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://maevesocial.com/
```
HTTP 200
Transport: direct
```
Serves the homepage over HTTPS with HTTP 200 Serves our crawler without a challenge

Indexing directives

No indexing restriction was observed in the supported homepage directives.

Sources and scope: indexing directives

Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://maevesocial.com/
The homepage does not block indexing or snippets

Search snippets

Scoped instructions were recorded; see their values and recipient support below.

Sources and scope: search snippets

Observed · Meta robots
- googlebot (search)
This declares a snippet instruction for the named recipients. The value is not a claim about citation by every AI operator.
This response only
https://maevesocial.com/
```
max-snippet: -1
```
The homepage does not block indexing or snippets

Search usage

No applicable preference for this use was established.

Sources and scope: search usage

Unstated · AIPREF Content-Usage
- goodforbotsbot (Site diagnostics)
- * (Default robots group)
- oai-searchbot (ai-search)
- claude-searchbot (ai-search)
- perplexitybot (ai-search)
- mistralai-index (ai-search)
- kimi-searchbot (ai-search)
- amzn-searchbot (ai-search)
- meta-webindexer (ai-search)
- exasearchbot (ai-search)
- aiwebindex (ai-search)
- duckassistbot (ai-search)
- shapbot (ai-search)
- yandexadditional (ai-search)
- yandexadditionalbot (ai-search)
- gptbot (ai-training)
- claudebot (ai-training)
- mistralai-training (ai-training)
- kimibot (ai-training)
- ai2bot (Unknown)
- applebot-extended (ai-training)
- webzio-extended (ai-training)
- chatgpt-user (user-fetch)
- claude-user (user-fetch)
- perplexity-user (user-fetch)
- mistralai-user (user-fetch)
- kimi-user (user-fetch)
- amzn-user (user-fetch)
- diffbot-user (user-fetch)
- firecrawlagent (extraction)
- webzio (extraction)
- meta-externalfetcher (user-fetch, agent)
- google-extended (ai-training, grounding)
- meta-externalagent (ai-training, product-improvement)
- amazonbot (ai-training, product-improvement)
- ccbot (open-dataset, ai-training)
- googlebot (search)
- bingbot (search)
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://maevesocial.com/
Declares AI usage preferences

Coverage and interpretation

Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
This explanation adds no points or penalties. Any score effects belong to the linked checks.
AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

3rd of 51 in SaaS & Web Apps

Whole category →

1Appnaryappnary.com
2BulkSharebulkshare.cloud
3Maeve Social · this reportmaevesocial.com

The prompts above would take Maeve Social to 100, first in its category.

To the prompts ↑

Category average 57. The percentile appears once the catalogue holds a few hundred sites.

Scanned: 19 Oct 2026
Category: SaaS & Web Apps
Tags: MarketingProduct ManagementDevelopers

Site profile

Login: Detected; A sign-in or sign-up link
API: Not established
Commerce: Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Read this report as Markdown

Removing it is free. Remove →

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned: 19 Oct 2026
Rubric: 0.9.0
Requests: 23
Fetched: 2.4 MB
Took: 27.8 s
Homepage: 147 ms · direct
Pages read: 4
robots.txt: allowed

Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

Homepagealways read
/social-media-management-software-for-agenciesarticle · linked from the homepage · from the sitemap · read
/features/analytics-reportsservice · linked from the homepage · from the sitemap · read
/docs/authenticationdocumentation · from the sitemap · read

Similar reports

The whole directory →

More like Maeve Social:SaaS & Web Apps Marketing Product Management Developers

Also Excellent

Good for Bots

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

Same category

angles.video

Turn product pages and screen recordings into editable launch videos with scripts and captions

Same category

PepVault: Peptide Tracker App

peptidetracks.com

Free peptide tracker app for logging doses, vials, injection sites and schedules

Same category

Mantis Ai

mantisai.in

Local lead intelligence and website gap detection for agencies and sales teams

Same category

Allwebforms

allwebforms.com

No-code online form builder with AI generation, visitor analytics, and integrations

Same category

SoftSync

softsync.ai

Flexible B2B CRM for startups with meeting notes and automated follow-ups

Maeve Social

Changed your site? Run a new scan.

Maeve Social scores 91 of 100: 49 of the 50 base points, 43 of the 50 agent-layer points, no penalties.

Through a bot’s eyes

What a bot can read

What is Maeve Social?

3 prompts, 9 points

State a position on AI crawlers

Declare AI usage preferences

Expose control roles, states and relationships

11 more prompts in Pro

Ready-made files

A ready-made llms.txt and robots.txt

All 36 checks

Who can read this page, and for what purpose?

Declared crawling rules

Observed access

Indexing directives

Search snippets

Search usage

AI input and use

AI training

3rd of 51 in SaaS & Web Apps

Site profile

Scan details

Similar reports

Good for Bots

angles.video

PepVault: Peptide Tracker App

Mantis Ai

Allwebforms

SoftSync