Skip to content
Good for Bots

Philippine directory network and data research platform for evidence-aware provider verification

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

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

Scanned

What is Arkhe?

Arkhe is a Philippine directory network and data research platform that provides access to four evidence-aware directories: BuildSupply PH for construction suppliers in Metro Manila, TechspertPH for computer shops and IT services, WasteSource PH for regulated waste providers, and Kuryente Match for retail electricity suppliers. The platform is designed for users researching commercial and industrial providers in the Philippines using dated public evidence, source separation, and sector-specific verification checklists. Arkhe also publishes original network research examining dataset coverage, denominators, and contact field gaps.

Through a bot’s eyes

“Arkhe is a network of evidence-aware Philippine directories and data research tools covering construction supplies, IT services, regulated waste, and retail electricity.”

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

A language model reading this input learns about the four specific directories offered within the Arkhe network, including their focus areas and geographic scopes in the Philippines. The text details the platform's methodology of separating entity identity, regulatory facts, and contact evidence. It covers original network research topics such as published coverage denominators and contact field gaps, along with dated curation notes. The provided JSON-LD block supplies structured organization and collection data, listing the names, URLs, and brief descriptions of the four member websites. While the text outlines what each directory covers and provides links to external subdomains and verification checklists, it does not contain pricing details, direct provider contact information, or user account functionality.

What stays hidden

A model reading this input cannot find out direct pricing or subscription costs for using the directories or tools, exact physical addresses or telephone numbers for the listed providers, or complete datasets, as the homepage only links out to external subdomains and provides summaries rather than raw directory listings.

Good for Bots report

Arkhe scores 49 of 100: 41 of the 50 base points, 8 of the 50 agent-layer points, no penalties.

Earned

41 of the 50 base points above the line, 8 of the 50 agent-layer points below it.

49

Still open

Behind the checks below, with prompts in Pro.

17
Penalties0
How scoring works · current methodology →

For the owner of inthearkhe.com

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

41.1 / 50

Passes.

3.6 of 3.6 points.

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

Passes.

8.9 of 8.9 points.

Sitemap declared in robots.txt, listing 15 URLs.

Fails.

0 of 8.9 points.

1 of 4 pages read pass. The page at /about/ publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Prompt in Pro →
Passes.

10.7 of 10.7 points.

3 of 4 pages read pass; 1 partly. The page at /about/ is partly structured: Only one landmark (navigation) outside the content root.

Passes.

8.9 of 8.9 points.

5 of 5 assessed homepage navigation links expose usable destinations.

Passes.

4.5 of 4.5 points.

31 of 31 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.7 of 2.7 points.

37 of 37 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

7.5 / 50

Fails.

0 of 11.3 points.

No /llms.txt on this site.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
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 9 AI crawlers, covering 9 crawlers.

Passes.

2.5 of 2.5 points.

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

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 445 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 59 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://inthearkhe.com/

Declared crawling rules

robots.txt refuses this URL for some listed identities. See the affected crawlers below.

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

32nd of 47 in Directories & Aggregators

  1. 1Brivoybrivoy.com
  2. 2IndieLaunchindielaunch.dev
  3. 32Arkhe · this reportinthearkhe.com

The prompts in the owner view would take Arkhe to 82, 8th 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
1 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
79.1 KB
Took
12.7 s
Homepage
59 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
  • /about/about · linked from the homepage · from the sitemap · read
  • /directories/buildsupply-ph/linked from the homepage · from the sitemap · read
  • /contact/contact · linked from the homepage · from the sitemap · read

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