Skip to content
Good for Bots

IndexBoost

indexboost.me

Automatic sitemap-based submission of new and unindexed pages to Google, Bing, Yandex and Yep

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

IndexBoost scores 72 of 100: 48 of the 50 base points, 24 of the 50 agent-layer points, no penalties.

Earned

48 of the 50 base points above the line, 24 of the 50 agent-layer points below it.

72

3 prompts away

Copy them below ↓

25

Still open

Behind the checks below, with prompts in Pro.

3
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“IndexBoost is a search engine indexing service that reads a website's sitemap every 10 minutes and submits new or unindexed pages to Google, Bing, Yandex and Yep through their official APIs, on plans from 15 to 250 dollars per month.”

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

What it can read, and what stays hidden →

What a bot can read

The homepage text covers search engine indexing, sitemap polling every 10 minutes, a four-step setup through Search Console and a service account, a sample feed of URLs with their submission and indexing statuses, and a pricing table with five plans listing site counts, daily page limits and monthly prices. It also contains a short FAQ on why indexing matters, how the process works, why Search Console access is requested, whether multiple sites can be added, typical timing of about 48 hours, and de-indexing. Sign-in links appear throughout. The llms.txt file adds a product list with links to feature pages, a section on when to use the service, a summary that names RSS and Atom feeds, the WordPress REST API and IndexNow, links to a pricing page in Markdown, a blog and a changelog, and a sign-in URL. It also lists an MCP server feature that the homepage does not mention. The JSON-LD blocks describe a web application and an organization, and add a customer support email address and an X profile link.

What stays hidden

A model reading this input cannot tell whether a free trial or free tier exists, what payment or cancellation terms apply, or where the company is based. It does not learn who operates the service beyond an email address and an X profile. The input does not explain what a site and a daily page limit mean for a site with many URLs, or what happens when the limit is reached.

What is IndexBoost?

IndexBoost is a search engine indexing service. According to the input, it reads a website's sitemap every 10 minutes, checks the index status of each URL, and submits pages that are not indexed to Google, Bing, Yandex and Yep through their official APIs.

Read more →

Setup is described as requiring no code: the user signs in with a Google account that manages the site in Search Console and adds a service account. The homepage lists five plans from 15 to 250 dollars per month, each with a number of sites and a daily page submission limit, and states that all four engines and analytics are included on every plan. The service is aimed at website owners, developers and agencies that manage one or more sites.

3 prompts, 25 points

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

+12.5score from 72 to 84

Serve Markdown at its own URL

No /llms-full.txt and no markdown versions linked from llms.txt.

Read prompt

+10score from 84 to 94

Serve Markdown when asked for it

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Read prompt

+2.5score from 94 to 97

Declare AI usage preferences

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

Read prompt

Pro

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

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

Readable base

48.3 / 50

Passes.

3.5 of 3.5 points.

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

Passes.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 53 URLs.

Passes.

8.8 of 8.8 points.

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

Passes.

10.5 of 10.5 points.

3 of 4 pages read pass; 1 partly. The page at /pricing is partly structured: No <h1>, so nothing says what the page is about.

Passes.

8.8 of 8.8 points.

20 of 20 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

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

Not applicable.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

Passes.

2.6 of 2.6 points.

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

Fails.

0 of 1.8 points.

2 of 4 pages read pass. The homepage declares no canonical URL, in a Link header or a <link> element.

Prompt in Pro →

Agent layer

23.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 13 links across 1 section.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links. 3 of 13 descriptions follow the link with something other than ":", the separator the format specifies (`- [name](url): notes`).

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Passes.

5 of 5 points.

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

Fails.

0 of 2.5 points.

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

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 442 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 85 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

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://indexboost.me/

Declared crawling rules

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

Sources and scope: declared crawling rules

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
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

23rd of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 23IndexBoost · this reportindexboost.me

The prompts above would take IndexBoost to 97, 3rd in its category.

To the prompts ↑

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

Scanned

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.

Scan details

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

Scanned
9 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
798.2 KB
Took
25.6 s
Homepage
85 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
  • /blog/why-it-takes-so-long-for-google-to-find-new-pages-and-reindex-updated-contentarticle · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read