Skip to content
Good for Bots

AI chatbot that answers website visitors from the site's own pages and collects their contact details

Good for Bots: Good, 86 of 100Get this badge →

On your homepage, it turns this report’s link to tailgpt.tailwebs.com dofollow.

Scanned

What is TailGPT?

TailGPT is an AI chatbot product for websites, described as the work of Tailwebs Technology in Bengaluru. It is installed on a site with one script tag and answers visitors only from the web pages and PDF, Word or text documents that the site owner selects. When a question is not covered by that content, the agent says so rather than guessing. When a visitor shows interest, such as asking about a price or a call-back, the agent asks for their name and phone number, and these appear in a leads list with the conversation. The product is presented for businesses such as clinics, coaching institutes, real estate firms and travel agencies. The homepage offers a free trial with no card needed and 20 free preview questions. Pricing is monthly or yearly in Indian rupees, plus applicable taxes.

Through a bot’s eyes

“TailGPT is an AI chatbot for websites that answers visitors only from the site owner's own pages and uploaded documents, then asks interested visitors for their name and phone number.”

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 the product's purpose, how lead capture works, how answers are limited to site content, and sample conversations for clinics, coaching institutes, real estate and travel. It also includes a sample dashboard of visitor questions, a lead-value calculator and some industry statistics about response times and chat. Pricing appears only as a statement that plans are in rupees, monthly or yearly, plus taxes, with no amounts in the text read. The free trial and the 20 free preview questions are stated. Contact details are limited to a support email in the structured data. The llms.txt file adds a summary paragraph and a list of linked pages on setup, installation for many website platforms, pricing, security, and industry use, each with a short description. The JSON-LD adds Organization, WebSite and SoftwareApplication entries with the name, URL, logo and a customer support email. The homepage text was truncated before its final section, and the llms.txt list was also truncated.

What stays hidden

A model reading only this input cannot find the price of any plan, since the pricing figures are not in the text read. It cannot tell how many pages or documents each plan covers, or what the monthly and yearly amounts are. The security page is linked, but its contents on hosting and data retention are not in the input. The homepage FAQ answers, including the one on what the product is, were cut off, so the homepage's own explanatory answers are incomplete. A phone number and street address are not given.

Good for Bots report

TailGPT scores 86 of 100: the whole readable base, 36 of the 50 agent-layer points, no penalties.

Earned

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

86
Penalties0
How scoring works · current methodology →

For the owner of tailgpt.tailwebs.com

3 prompts, 14 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

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

Readable base

50 / 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 162 URLs.

Passes.

8.8 of 8.8 points.

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

Passes.

10.5 of 10.5 points.

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

Passes.

8.8 of 8.8 points.

42 of 42 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

98 of 98 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.

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

Passes.

1.8 of 1.8 points.

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

Agent layer

36.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 107 links across 8 sections.

Passes.

7.5 of 7.5 points.

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

Passes.

12.5 of 12.5 points.

llms.txt points at 64 markdown versions of pages.

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 6 AI crawlers, across 3 purposes (search, user-fetch, training).

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 1864 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 313 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.

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.

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://tailgpt.tailwebs.com/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneUser-agent: oai-searchbot Allow: /
Claude-SearchBotAnthropicAI searchAllowedNoneUser-agent: claude-searchbot Allow: /
PerplexityBotPerplexityAI searchAllowedNoneUser-agent: perplexitybot Allow: /
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
BingbotMicrosoftSearchAllowedNot scoredUser-agent: bingbot Allow: /
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneUser-agent: chatgpt-user Allow: /
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneUser-agent: claudebot Allow: /
Google-ExtendedGoogleAI training, GroundingAllowedNoneUser-agent: google-extended Allow: /
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: oai-searchbot
Allow: /

User-agent: claude-searchbot
Allow: /

User-agent: perplexitybot
Allow: /

User-agent: claudebot
Allow: /

User-agent: chatgpt-user
Allow: /

User-agent: google-extended
Allow: /

User-agent: bingbot
Allow: /

User-agent: *
Allow: /

https://tailgpt.tailwebs.com/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • 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://tailgpt.tailwebs.com/

    robots.txt is present and valid

  • 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://tailgpt.tailwebs.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://tailgpt.tailwebs.com/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

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

5th of 60 in AI Products & Agents

  1. 1Pixelropepixelrope.com
  2. 2Contents Pilotcontentspilot.com
  3. 5TailGPT · this reporttailgpt.tailwebs.com

The prompts in the owner view would take TailGPT to 100, 2nd in its category.

To the prompts →

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

Scan details

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

Scanned
13 Nov 2026
Rubric
0.9.0
Requests
24
Fetched
981.3 KB
Took
18.8 s
Homepage
313 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/after-hours-customer-support-chatbotarticle · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /docs/getting-started/choosing-pagesdocumentation · from the sitemap · read

More like TailGPT:AI Products & AgentsSalesAI & Machine LearningFreemium

Same category

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Same category

contentspilot.com

AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style

Same category

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

Also Freemium

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also AI & Machine Learning

goodforbots.com

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

Also Freemium

brivoy.com

Community site where makers launch new products and early adopters discover them

Do you run tailgpt.tailwebs.com? Open the owner view → Removing the listing is free. Remove →