Skip to content
Good for Bots

Web design, ecommerce, custom software and AI product development studio based in Gurugram, India

Good for Bots: Fair, 64 of 100Get this badge →

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

Scanned

What is Gigzman?

Gigzman is a web design and development studio in Gurugram, India, according to the homepage title, meta description and llms.txt. The site says it builds websites, eCommerce stores, custom platforms, SaaS products, MVPs, mobile apps, CRM systems and AI products for businesses. The llms.txt file adds that the company also runs four products of its own, and names Real Estate, Healthcare, Education, Professional Services, Retail and Startups as industries it works with. Listed services include SEO and Google Business Profile work, and the site links to a free consultation and a contact page. The legal name given in the structured data is Reverblunt Pvt Ltd.

Through a bot’s eyes

“Gigzman is a web design and development studio in Gurugram, India, that builds websites, ecommerce stores, custom software, mobile apps and AI products for businesses, and runs four products of its own.”

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 web and software development services, grouped into web and commerce, custom software, AI products and conversational AI, plus growth and operations work. It explains the problems of visibility, trust and conversion that the company says it addresses, and lists client projects with short descriptions in several sectors, including travel, fabric trade and real estate. The llms.txt file adds per-service starting prices in rupees and typical delivery timelines, a pricing page reference, case study summaries, three articles and a contact phone number and email address with a street address. The JSON-LD adds an FAQ covering timelines, onboarding, redesigns, integrations, post-launch support and payment milestones, plus organisation details such as telephone, address and areas served. The homepage text itself gives no prices, and its contact details appear only through links.

What stays hidden

A reader of this input cannot tell what the crawled homepage costs beyond the llms.txt starting prices, and cannot see the pricing models named on the pricing page. The input does not describe the four in-house products beyond short case study lines, nor the clients named in the project list beyond one-line summaries. Team size, years in operation and the specific projects behind the review ratings are not stated.

Good for Bots report

Gigzman scores 64 of 100: 45 of the 50 base points, 19 of the 50 agent-layer points, no penalties.

Earned

45 of the 50 base points above the line, 19 of the 50 agent-layer points below it.

64

Still open

Behind the checks below, with prompts in Pro.

8
Penalties0
How scoring works · current methodology →

For the owner of gigzman.com

3 prompts, 27 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

45 / 50

Passes.

3.3 of 3.3 points.

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

Passes.

8.3 of 8.3 points.

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

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as FAQPage, Question, Answer in valid schema.org JSON-LD.

Half passes.

5 of 10 points.

None of the 4 pages read pass fully; 4 partly. The homepage is partly structured: The outline jumps from h2 to h4, which the standard forbids.

Prompt in Pro →
Passes.

8.3 of 8.3 points.

6 of 6 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

13 of 13 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

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

Passes.

1.7 of 1.7 points.

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

Agent layer

18.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 38 links across 5 sections.

Passes.

7.5 of 7.5 points.

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

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.

Fails.

0 of 5 points.

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

Fails.

0 of 2.5 points.

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

Prompt in Pro →

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 3566 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 60 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://gigzman.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 searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
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 trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

https://gigzman.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://gigzman.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://gigzman.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://gigzman.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 8 in Companies & Agencies

  1. 1BuiltToWinWebbuilt2winweb.com
  2. 2WordPress Speed Optimization Servicewordpressspeedoptimizationservice.com
  3. 5Gigzman · this reportgigzman.com

The prompts in the owner view would take Gigzman to 91, 2nd in its category.

To the prompts →

Category average 67. 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
14 Nov 2026
Rubric
0.9.0
Requests
28
Fetched
5.1 MB
Took
19.6 s
Homepage
60 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
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /servicesservice · linked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · from the sitemap · read

More like Gigzman:Companies & AgenciesAI & Machine LearningWeb DevelopmentB2B

Also Web Development

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Also B2B

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes

Also AI & Machine Learning

interviewace.online

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

Also B2B

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Also AI & Machine Learning

goodforbots.com

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

Also Fair

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

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