MCP toolsCheck any pageUpdated
Grade a brand’s locations
What does mttr_locations do?
Reads a brand’s location pages together, up to 25 of them found from its home page, its structured data and its sitemap, and grades them on eight checks that only show across them: the brand tied to its locations, a business block on each, no two alike, a share card for each, hreflang both ways, each its own canonical, every one easy to find, and the same details on the page as in its block. Any key may make this call, on any public site.
When to use it
- A business with many offices, stores or service areas wants to know why some places never show up.
- Location pages were made from one template and you want to see how alike they read.
What you ask
You say“Grade the location pages on example.com.”
mttr_locations({ url: "https://example.com/products/linen-shirt" })
| Argument | Type | Needed | What it is |
|---|---|---|---|
url | Text | Yes | The brand's site, such as example.com or https://example.com/. |
What comes back
- A score from 0 to 100, the share of checks passed, and a verdict in words.
- Each check passing or not, with what was found, the locations that fail it and why, and the fix.
- How many locations were found, and how many were read.
- It cannot say whether a business is really at an address.
| Check | Locations passing | First that fails |
|---|---|---|
| A business block on each | 25 of 25 | None |
| No two locations read the same | 3 of 25 | Its words are 71% the same as another location’s |
| A share card for each location | 24 of 25 | No og:title |
| The same details everywhere | 23 of 25 | The street in its block is not on the page |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/check/locations, with your key as a bearer token:
curl "https://mttr.si/api/v1/check/locations?url=https%3A%2F%2Fexample.com%2Fproducts%2Flinen-shirt" \
-H "Authorization: Bearer $MTTR_KEY"When it fails
| When | Status | What to do |
|---|---|---|
| Your assistant has no key yet | 401 over MCP | Sign up with mttr_signup, then connect again with the key it gives. |
| The key has used this hour’s free checks | 429 | The answer says location checks are limited to an hourly allowance. Try again within the hour. |
Every error’s wording is in the API reference.
The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_locations in the API reference.