AmazingPlugins

amazingplugins.com

Free WooCommerce plugins for accessibility fixes, shipping checks, and order cleanup

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

AmazingPlugins scores 89 of 100: the whole readable base, 39 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 39 of the 50 agent-layer points below it.

2 prompts away

Copy them below ↓

Penalties0

How scoring works · current methodology →

Through a bot’s eyes

“AmazingPlugins offers free WooCommerce plugins for storefront accessibility fixes, shipping rule checks, and stale order cleanup.”

Simulated from the response GoodForBotsBot received on 13 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 AmazingPlugins offers a catalog of free WooCommerce tools. The homepage and the provided llms.txt file outline specific plugins including AP Accessibility Fixer, Shipping Rules Tester, Stale Order Cleaner, and an in-development Amazing Security plugin. The text explains the scope and limitations of each tool, such as read-only shipping checks and permanent order deletion processes. The provided llms.txt file adds a comprehensive list of guides, blog posts, documentation links, and references to other products from the same team. The embedded JSON-LD schema confirms the organization name and includes frequently asked questions regarding plugin installation and requirements. Contact details are referenced through support links and contact paths.

What is AmazingPlugins?

AmazingPlugins provides free tools for everyday WooCommerce store management. It offers specific utility plugins designed to address common storefront challenges, such as fixing accessibility markup issues, investigating shipping rules and zone rates, and cleaning up stale or abandoned orders.

The site is intended for WooCommerce store administrators and developers who need targeted solutions for maintenance and compliance tasks.

3 prompts, 11 points

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

+10

Serve Markdown when asked for it

Asking the homepage for markdown still returns text/html.

Read prompt

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

I need you to: serve markdown through content negotiation on all public HTML routes.

The check it fails is "Serves markdown when asked for it", worth 10 points. What the scanner saw: Asking the homepage for markdown still returns text/html.

Implement content negotiation across all public HTML routes, including page types
outside the scan's sample. Put it in the shared response handling or the handlers
for each page type, so new pages receive it too. Agents need the content of any
page they follow, including pages the report did not name.

When a request arrives with `text/markdown` in its `Accept` header, the same URL that
serves HTML to a browser should return a markdown rendering of that page's content.
Requests without that header must keep getting the HTML exactly as they do now.

The response must:

- set `Content-Type: text/markdown; charset=utf-8`;
- include `Accept` in the `Vary` header, so shared caches never serve the markdown to a
  browser or the HTML to an agent (RFC 9110 says a server SHOULD send `Vary` whenever
  the representation depends on a request header);
- contain real markdown, not HTML with a different header on it;
- drop `ETag` and `Last-Modified` for the converted response, since a conditional request
  cannot be honoured against a body generated on the fly.

Work out how to do this in whatever stack this project uses. If the site is behind
Cloudflare on a paid plan, the "Markdown for Agents" zone setting does all of the above
and is the least invasive option. Otherwise implement it in the framework: middleware
inspecting the `Accept` header, a route handler that returns the markdown source, or
whatever fits the architecture here.

Strip navigation, headers, footers and cookie banners from the markdown. The point is the
content, without the page furniture around it.

Verify HTML and Markdown responses for each public page type, including URLs
outside the reported sample. Check that each Markdown response contains that
page's content and that ordinary browser requests still receive HTML.

The whole report, as markdown, is at https://goodforbots.com/r/amazingplugins.com.md?scan=cmv6r9ot300gx01qzsjxpk4d9. 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.

+1.3

Advertise machine-readable resources with typed links

Neither page read passes. The homepage's links are all ordinary page furniture; none point an agent anywhere.

Read prompt

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

I need you to: advertise machine-readable resources with typed web links.

The check it fails is "Advertises machine-readable resources with typed links", worth 1.25 points. What the scanner saw: Neither page read passes. The homepage's links are all ordinary page furniture; none point an agent anywhere.

The scan checked a sample of 2 pages. It does not establish which other pages have the same issues. Use the findings below to locate the responsible templates, components or configuration, and apply the fix wherever the same issue occurs. Pages in the sample with findings:
- https://amazingplugins.com/: The homepage's links are all ordinary page furniture; none point an agent anywhere.
- https://amazingplugins.com/blog/10-common-accessibility-issues-on-e-commerce-sites/: The page at /blog/10-common-accessibility-issues-on-e-commerce-sites/'s links are all ordinary page furniture; none point an agent anywhere.

Add typed discovery links through the site's shared response handling or page
templates. Review all public page types, including those outside the reported
sample, and advertise the resources that apply to each page. Verify the links on
a page from each template and check that their targets exist.

Typed links let an agent find a page's Markdown twin or an index describing it
from the response, without guessing at paths.

Follow RFC 8288. Add these either as `<link>` elements in the document head or as an HTTP
`Link` response header; both are equally valid, and the header also works for responses
that are not HTML.

The two that matter most, named by the llms.txt v2 specification:

```
Link: </page.md>; rel="alternate"; type="text/markdown",
</llms.txt>; rel="describedby"
```

- `rel="alternate"` with `type="text/markdown"` points at the markdown version of the
current page. Emit it per page, pointing at that page's own markdown twin, not at a
single site-wide file.
- `rel="describedby"` points at the `llms.txt` that covers the page.

If this project also exposes any of the following, advertise them the same way: an
OpenAPI description with `rel="service-desc"`, human documentation with
`rel="service-doc"`, an API catalog with `rel="api-catalog"`.

Two rules to respect. A relative URI is resolved against the request URL, so `</x.md>` is
fine and correct. And each link entry needs exactly one `rel` parameter, though one `rel`
may list several relation types separated by spaces.

Do not add `rel="alternate"` for a markdown file that does not exist; a link pointing at a
404 is worse than no link, because it moves the failure from discovery to fetch.

The whole report, as markdown, is at https://goodforbots.com/r/amazingplugins.com.md?scan=cmv6r9ot300gx01qzsjxpk4d9. 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.

+1 capability

Publish an API catalog

No API catalog published.

Read prompt

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

I need you to: publish an API catalog at /.well-known/api-catalog.

The capability it is missing is "Publishes an API catalog". It carries no points at all: a capability is recorded as a badge on the report and never touches the score. What the scanner saw: No API catalog published.

An agent that wants to call this project's API has to be told where it is by a person
first, unless the site says so itself at a well-known address. That is what the catalog
is for: one document, at one predictable path, pointing at every API here and at the
machine-readable description of each.

Follow RFC 9727. The document must:

- be served at exactly `/.well-known/api-catalog`;
- carry `Content-Type: application/linkset+json; profile="https://www.rfc-editor.org/info/rfc9727"`;
- be a Linkset (RFC 9264): a top-level `linkset` array, each entry with an `anchor`
naming one API and link arrays describing it;
- point at each API's machine-readable description with `service-desc`, its
human-readable documentation with `service-doc`, and optionally a health or status
endpoint with `status`.

A minimal, valid example for a single API:

```json
{
"linkset": [
{
"anchor": "https://amazingplugins.com/api",
"service-desc": [
{ "href": "https://amazingplugins.com/api/openapi.json", "type": "application/json" }
],
"service-doc": [
{ "href": "https://amazingplugins.com/docs/api", "type": "text/html" }
]
}
]
}
```

Add one entry per API or product line if this project exposes several.

Two things to get right, because they are the common failure modes. First, make sure the
path is served by a real route: many frameworks answer every unknown path with the
application shell, which returns 200 and HTML, and to an agent that is worse than a 404
because it gets no signal that the feature is absent. Second, if the project has no
public API at all, skip this and do not publish an empty catalog. A catalog describing
nothing is worse than no catalog, and nothing here is lost by not having one.

Pro

10 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 →

All 36 checks

Evidence for each, in Markdown →

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

Readable base

50 / 50

3.5 of 3.5 points.

robots.txt is valid, with 18 user-agent groups.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 74 URLs.

8.8 of 8.8 points.

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

10.5 of 10.5 points.

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

4.4 of 4.4 points.

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

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

2.6 of 2.6 points.

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

1.8 of 1.8 points.

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

0.9 of 0.9 points.

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

Agent layer

38.8 / 50

11.3 of 11.3 points.

/llms.txt is well formed: 18 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-full.txt serves the site's content as markdown (23 KB).

0 of 10 points.

Asking the homepage for markdown still returns text/html.

5 of 5 points.

States a position on 13 AI crawlers, across 3 purposes (search, user-fetch, training).

2.5 of 2.5 points.

Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.

0 of 1.3 points.

Neither page read passes. The homepage's links are all ordinary page furniture; none point an agent anywhere.

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

Both 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: /blog/10-common-accessibility-issues-on-e-commerce-sites/
The page at /blog/10-common-accessibility-issues-on-e-commerce-sites/ marks its content root, its heading outline and its landmarks.

Extracted words: 692
Headings: 20
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	476	68.79%
Navigation	7	1.01%
Page header	0	0%
Page footer	205	29.62%
Other text	4	0.58%

11 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

H1A house of plugins for WooCommerce.
H2A few store problems, covered.
H3Accessibility Fixer
H3Shipping Rules Tester

16 more headings recorded

Page landmarks

contentinfo
navigation
region

Technical scan data JSON

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

{
  "gaps": [],
  "pages": [
    {
      "url": "https://amazingplugins.com/",
      "reason": "structured",
      "status": "pass",
      "summary": "The homepage marks its content root, its heading outline and its landmarks.",
      "homepage": true
    },
    {
      "url": "https://amazingplugins.com/blog/10-common-accessibility-issues-on-e-commerce-sites/",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /blog/10-common-accessibility-issues-on-e-commerce-sites/ marks its content root, its heading outline and its landmarks.",
      "homepage": false
    }
  ],
  "roots": [
    {
      "words": 479,
      "source": "element",
      "hierarchicallyCorrect": true
    }
  ],
  "reason": "structured",
  "h1Count": 1,
  "headings": [
    {
      "text": "A house of plugins for WooCommerce.",
      "empty": false,
      "level": 1
    },
    {
      "text": "A few store problems, covered.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Accessibility Fixer",
      "empty": false,
      "level": 3
    },
    {
      "text": "Shipping Rules Tester",
      "empty": false,
      "level": 3
    },
    {
      "text": "Stale Order Cleaner",
      "empty": false,
      "level": 3
    },
    {
      "text": "Choose by the problem in front of you.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Make your storefront easier to use.",
      "empty": false,
      "level": 3
    },
    {
      "text": "Investigate a missing shipping rate.",
      "empty": false,
      "level": 3
    },
    {
      "text": "Find the orders worth clearing out.",
      "empty": false,
      "level": 3
    },
    {
      "text": "Useful details, before you install.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Fix common markup issues",
      "empty": false,
      "level": 3
    },
    {
      "text": "Shipping checks are read-only",
      "empty": false,
      "level": 3
    },
    "… 8 more items"
  ],
  "bodyWords": 856,
  "landmarks": [
    {
      "role": "navigation",
      "named": false,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "contentinfo",
      "named": false,
      "source": "native",
      "element": "footer"
    },
    {
      "role": "region",
      "named": true,
      "source": "role",
      "element": "div"
    }
  ],
  "textRatio": 0.0531,
  "truncated": false,
  "articleCount": 0,
  "contentWords": 483,
  "headingCount": 20,
  "headingSkips": [],
  "requirements": {
    "landmarks": true,
    "contentRoot": true,
    "headingOutline": true
  },
  "landmarkRoles": [
    "contentinfo",
    "navigation",
    "region"
  ],
  "hiddenMainCount": 0,
  "textComposition": {
    "words": {
      "main": 476,
      "other": 4,
      "footer": 205,
      "header": 0,
      "navigation": 7
    },
    "shares": {
      "main": 0.6878612716763006,
      "other": 0.005780346820809248,
      "footer": 0.29624277456647397,
      "header": 0,
      "navigation": 0.010115606936416185
    },
    "version": 1,
    "truncated": false,
    "totalWords": 692,
    "analysisLimited": false,
    "mainRegionCount": 1,
    "wordsBeforeMain": 11
  },
  "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://amazingplugins.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://amazingplugins.com/
robots.txt is present and valid
Declared allow · robots.txt
- goodforbotsbot (Site diagnostics)
- * (Default robots group)
- 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)
- mistralai-training (ai-training)
- kimibot (ai-training)
- ai2bot (Unknown)
- webzio-extended (ai-training)
- 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)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: *
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- oai-searchbot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: oai-searchbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claude-searchbot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: claude-searchbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- perplexitybot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: perplexitybot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- gptbot (ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: gptbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claudebot (ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: claudebot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- applebot-extended (ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: applebot-extended
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- chatgpt-user (user-fetch)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: chatgpt-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claude-user (user-fetch)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: claude-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- perplexity-user (user-fetch)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: perplexity-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- google-extended (ai-training, grounding)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: google-extended
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- meta-externalagent (ai-training, product-improvement)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: meta-externalagent
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- amazonbot (ai-training, product-improvement)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: amazonbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- ccbot (open-dataset, ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: ccbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- googlebot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: googlebot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- bingbot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: bingbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- applebot (search, ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: applebot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- bytespider (Unknown)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://amazingplugins.com/
https://amazingplugins.com/robots.txt
```
User-agent: bytespider
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://amazingplugins.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://amazingplugins.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://amazingplugins.com/
The homepage does not block indexing or snippets

Search snippets

No snippet restriction was observed in the supported homepage directives.

Sources and scope: search snippets

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

Search usage

Some declarations have unresolved scope or precedence; inspect their sources.

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)
- applebot (search, ai-training)
- bytespider (Unknown)
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://amazingplugins.com/
Declares AI usage preferences
Unresolved · Content-Signal
These statements have no established crawler-group scope; they are not treated as site-wide permission.
Outside any user-agent group
https://amazingplugins.com/robots.txt
```
Content-Signal: search=yes, ai-input=yes, ai-train=yes
```
Declares AI usage preferences

AI input and use

Some declarations have unresolved scope or precedence; inspect their sources.

Sources and scope: ai input and use

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)
- applebot (search, ai-training)
- bytespider (Unknown)
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://amazingplugins.com/
Declares AI usage preferences
Unresolved · Content-Signal
These statements have no established crawler-group scope; they are not treated as site-wide permission.
Outside any user-agent group
https://amazingplugins.com/robots.txt
```
Content-Signal: search=yes, ai-input=yes, ai-train=yes
```
Declares AI usage preferences

AI training

Some declarations have unresolved scope or precedence; inspect their sources.

Sources and scope: ai training

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)
- applebot (search, ai-training)
- bytespider (Unknown)
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://amazingplugins.com/
Declares AI usage preferences
Unresolved · Content-Signal
These statements have no established crawler-group scope; they are not treated as site-wide permission.
Outside any user-agent group
https://amazingplugins.com/robots.txt
```
Content-Signal: search=yes, ai-input=yes, ai-train=yes
```
Declares AI usage preferences

Read all findings in the Markdown report

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

4th of 33 in Developer Tools & APIs

Whole category →

1Good for Botsgoodforbots.com
2Chrome Goldminechromegoldmine.com
4AmazingPlugins · this reportamazingplugins.com

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

To the prompts ↑

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

Scanned: 13 Oct 2026
Category: Developer Tools & APIs
Tags: Web DevelopmentDevelopersOpen Source

Site profile

Login: Not established
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: 13 Oct 2026
Rubric: 0.9.0
Requests: 22
Fetched: 1.4 MB
Took: 13.1 s
Homepage: 107 ms · direct
Pages read: 2
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
/blog/10-common-accessibility-issues-on-e-commerce-sites/article · from the sitemap · read
/blog/collection · linked from the homepage · from the sitemap · not read: HTTP 429
/about/about · linked from the homepage · from the sitemap · not read: HTTP 429

Similar reports

The whole directory →

More like AmazingPlugins:Developer Tools & APIs Web Development Developers Open Source

Same category

Good for Bots

goodforbots.com

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

Same category

SightRadar

sightradar.com

High-accuracy face recognition API compatible with AWS Rekognition

Same category

Chrome Goldmine

chromegoldmine.com

Database of expired Chrome extensions with proven demand and rebuild plans

Same category

HyperGSC

hypergsc.com

Connect Google Search Console to AI tools using a hosted MCP server

Same category

SSHFlow

sshflow.com

SSH client built for developers providing workspaces for terminals, SFTP, and code editing

Same category

Modeinspect

modeinspect.com

AI design tool that runs in your codebase for canvas and code workflows