[shineforever]

Thank you for welcoming GoAnyAPI into the Magpie community plugins and for the careful review of #472. I appreciate the work you put into getting the integration ready and merged.

This small follow-up fixes the GoAnyAPI icon in the Plugins → Discover card, refreshes its English and Chinese summaries, and adds its official website to the card's detail page.

• Remove the raw icon URL from the GoAnyAPI entry in registry.json. The Discover card currently passes that URL to the built-in icon renderer, which treats it as a local icon name and falls back to the generic cube. The plugin's package.json still provides magpie.icon; Magpie's package metadata path fetches and stores that image before displaying it.
• Highlight Google Trends, website traffic, domain rating, keyword suggestions, SERPs, backlinks, and ads statistics in both summaries, with the most-used APIs first.
• Add https://goanyapi.com/ as the package's homepage, which Magpie already displays as a Homepage link in plugin details. Bump the package to 0.1.1 because the community dist branch keeps each packed version immutable.

Validation:

• Parsed the updated registry.json and packages/goanyapi/package.json successfully.
• Confirmed the branch changes only the GoAnyAPI registry entry and package metadata.
• Confirmed the logo URL and Magpie's image proxy both return a PNG.

After merge, the next dist build will make 0.1.1 available to Magpie. An npm first publish is not required for this update.

[yetone]

Merged, thanks. I confirmed the cause in magpie's icon(): an https:// name is read as a bundled icon file and falls back to the cube. Kilo, Search1API and PowerContext's registry icons hit the same fallback, so magpie will draw registry icon URLs itself. 0.1.1 goes out with the next dist build.