GeminiCLI.com Feedback: `usestring/string-gemini-extension` not indexed in the Extensions Gallery after 12 daily crawls

### URL of the page with the issue

https://geminicli.com/extensions/

### What is the problem?

https://github.com/usestring/string-gemini-extension is not in the gallery. https://geminicli.com/extensions.json has 1,706 entries today and none under `usestring`.

The repo meets the requirements in https://geminicli.com/docs/extensions/releasing/:

- Public GitHub repository, MIT licence
- Topic `gemini-cli-extension` set on 2026-08-26, so twelve daily crawls have passed
- `gemini-extension.json` at the repository root, name `string-web-access`, version `1.0.1`

Current manifest:

```json
{
"name": "string-web-access",
"version": "1.0.1",
"description": "Fetch, search and map any website as clean, LLM-ready Markdown, without getting blocked.",
"contextFileName": "GEMINI.md",
"settings": [
{
"name": "API Key",
"description": "Your String Web Access API key, from portal.usestring.ai",
"envVar": "STRING_API_KEY",
"sensitive": true
}
],
"mcpServers": {
"string-web-access": {
"httpUrl": "https://mcp.usestring.ai/v1/mcp",
"headers": { "Authorization": "Bearer ${STRING_API_KEY}" }
}
}
}
```

The manifest uses `httpUrl`, `headers` and `settings`. Listed extensions use the same fields (github/github-mcp-server has `httpUrl` and `headers`, grafana/mcp-grafana has `settings`), so I doubt a field is the cause. #28890, #28861 and #28900 look like the same symptom.

### What did you expect to happen?

The extension to show up within a day or two of adding the topic, or a validation error I can act on.

### Additional context

Repo topics: gemini-cli-extension, markdown, mcp, web-scraping. No git tag yet; if the crawler needs one, or a different manifest field, say which and I will add it.

Start with the extensions gallery at geminicli.com/extensions/, the generated extensions.json, and the extension releasing documentation. Compare the reported manifest and repository topics with indexed extensions and review related issues #28890, #28861, and #28900. Done means the extension is indexed or the crawler reports a specific actionable validation error.

Written by the indexing model from the issue text.