employir.com
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
employir.com
Preparing the stored Is Agentic score
employir.com
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 16 applicable checks
Needs work
Weighted across 12 applicable checks
Strong
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
No material issues were found in the applicable checks.
Checks are grouped by relevance for Business sites.
4237 chars, semantic headings (1 H1 + 9 H2s + 2 H3s), 7.9% content ratio
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
employir.com ranks #1 for "Employ International Recruitment" (searched your brand name alone: no main product term from your homepage qualified)
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://www.employir.com/sitemap-index.xml with multiple sitemaps entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (3 blocks)
All metadata signals present: canonical URL, lang="nl-NL", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 7 measured pages fit an agent context budget (largest ~2K tokens)
Name search surfaced no pages on employir.com, although developer resources exist on the site (API docs, OpenAPI spec, MCP server) - weak search indexing or transient search noise
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
MCP server referenced in llms.txt
Full markdown fallback support. Homepage (https://employir.com/index.md) and all 3 sampled content pages return markdown: https://www.employir.com/af/index.md, https://www.employir.com/af/kontak/index.md, https://www.employir.com/cases/van-onderhoudsmonteur-in-zuid-afrika-naar-hoofd-technische-dienst-in-nederland/index.md
Found the llms.txt at https://employir.com/llms.txt.
The llms.txt is well-formatted: 37 lines with markdown links, 3,241 characters in total.
When-to-use guidance found in llms.txt
Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your Wikipedia page, Wikidata entry, GitHub org, and social profiles. This helps AI disambiguate your brand from similarly named entities.
All 5 probed llms.txt links resolve to real content
Frontmatter with title + description on /index.md
Code fences balanced across 1 markdown document
OpenAPI spec found at https://employir.com/openapi.json (version: 3.1.0)
Path-suffix markdown docs served with text/markdown content-type: /index.md
All 4 tools on docs MCP have detailed descriptions (>= 30 chars)
3/4 tools on docs MCP have parameter schemas
How to pass
Define inputSchema with typed properties and required arrays for each tool. Agents need schema info to construct valid tool calls without guessing.
docs MCP exposes 4 tools - consider consolidating to keep agent attention focused on retrieval
How to pass
Expose your tools via your MCP server's tools/list endpoint. A product MCP server scores on breadth: 3 or more tools that cover read, write, and search. A docs MCP server scores on focus: 3 tools or fewer, such as one search tool and one fetch tool. Keep every outputSchema valid and self-contained: a $ref that points outside the schema, such as #/components/schemas/... copied from an OpenAPI file, makes clients built on the official TypeScript SDK 1.x reject your whole tool list.
docs MCP tool names are consistent and descriptive, but none reference content resources (doc/article/page) - agents discovering this server may miss its purpose
How to pass
Use consistent naming conventions (snake_case or camelCase) for all MCP tools. Names should be descriptive (>= 4 chars) and not generic (avoid 'run', 'get', 'do').
REST API documentation found at https://www.employir.com/api/v1/vacatures. Best-of-protocols score: 7/7.
docs MCP is public - correct posture for documentation surface
Verified live: GET https://www.employir.com/api/v1/vacatures answered 200 without credentials (zero-auth access)
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
MCP server connected via Streamable HTTP - employ-ir v1.0.0 (protocol 2025-11-25)
docs MCP returns structured JSON-RPC errors with code and message
docs MCP uses modern Streamable HTTP transport
Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /_astro/Layout.astro_astro_type_script_index_1_lang.HVuFHbvP.js).
API returns JSON error responses (404 at https://employir.com/api/v1/orank-probe-test)
API versioning found (URL versioning (servers or paths)) but no deprecation or sunset policy detected - add Sunset/Deprecation headers or a deprecation policy page
How to pass
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
100% of operations define typed response schemas, 100% use application/json
docs MCP: 4/4 tools have behavioral annotations
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=2).
86 native controls, 0 non-native div-soup affordances (100% native).
86/86 interactive elements have a computable accessible name (100%).
3/3 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (2 operations, 100% with operationIds, 100% documented by description or summary)
Partial compatibility: 2/2 operationIds, 1/2 typed schemas
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
What does employir.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does employir.com do and who is it for? Explain it back to me.
10 steps5 reasoning steps1 search
The agent could not complete the task as requested because the site rate-limited every direct fetch attempt. It assembled a partial answer from a single web search result showing employir.com is a South African–Netherlands recruitment agency, but could not verify pricing, differentiation, or other details from the site's own content.