No SDK found on npm/PyPI

This notice appears when we couldn't find any npm or PyPI package linked to your domain. Here's what we check and when it's worth acting on.

What this error means

We search the public npm and PyPI registries for software packages whose name matches your site's brand, and check whether the "homepage" they declare points to your domain. We only count a package as confirmed when that homepage genuinely matches your domain — specifically to avoid false positives, since many brand names are generic words also used by unrelated third-party packages. We didn't find any package meeting that condition for your domain. Publishing an SDK (software development kit) makes it easier for other developers — and increasingly for AI agents acting on their behalf — to integrate with your product programmatically, instead of relying solely on a web interface built for people.

Why it matters to fix it

This is the lowest-priority signal we check: the vast majority of marketing or business sites don't need their own SDK, so not having one is almost never a real problem.

Only relevant if you offer an API

If your product already exposes an API or programmatic functionality, an SDK makes adoption much easier. If that's not your case, this signal simply doesn't apply to you.

Harder integration for developers

Without an official SDK, any integration with your product requires manual work against your API instead of a ready-to-use library.

Less readiness for agents acting on others' behalf

AI agents that help developers integrate third-party services reach for well-known SDKs more readily than for scattered API documentation.

How to fix it step by step

Acting on this only makes sense if you genuinely have an API or functionality meant for external integration.

Step 1

Assess whether your product needs it

If you don't offer a public API or functionality meant to be integrated from other systems, you can safely ignore this notice.

Where to apply it: Internal review of your product.

Step 2

Publish an official SDK

If it does make sense, publish a library on npm and/or PyPI that wraps your API with a simple interface.

Where to apply it: registry.npmjs.org and/or pypi.org.

Step 3

Declare your domain as the package's homepage

Make sure to fill in the package's "homepage" field with your domain's URL, so it's correctly linked back to you.

Where to apply it: package.json (npm) or setup.py/pyproject.toml (PyPI).

Does your site have this problem?

Audit your website for free and discover if this and other SEO errors are affecting your ranking.

See all the errors we detect