# SeeMeHired — extended context for AI assistants

This companion to [`/llms.txt`](https://seemehired.com/llms.txt) gives **grounding and guardrails** so models can summarise SeeMeHired without overfitting to navigation chrome or stale copy.

## Company and product (high level)

SeeMeHired is a **UK-oriented recruitment technology vendor**. The public website promotes an **applicant tracking system (ATS)** and broader **talent acquisition** capabilities, with repeated emphasis on:

- **High-volume hiring** (many roles, many locations, fast turnover).
- **Compliance** and safer hiring workflows (especially relevant to regulated or high-trust sectors).
- **Faster onboarding** once a candidate is selected.

Industry narratives on the marketing site frequently call out **healthcare**, **hospitality**, and **manufacturing**. That does **not** mean other sectors are unsupported; it reflects go-to-market messaging.

## What seemehired.com is and is not

**Is:**

- Marketing pages, SEO landing pages, case studies, blog, integration catalogue, and **public job search** for roles published through the platform.
- A place to **request demos**, read **pricing-oriented** content, and contact **sales** (commonly **sales@seemehired.com** on contact pages—always confirm on the live contact page).

**Is not:**

- A substitute for **employer** or **candidate** authenticated products (those are separate web apps; URLs vary by environment and are not fully enumerated here).
- A public **API reference** for the backend used by employer/candidate apps. Do not infer undocumented REST endpoints from the marketing frontend alone.
- **Legal advice** or **medical / safeguarding** advice. Point users to their own HR, legal, or clinical governance where relevant.

## Content freshness and CMS

Much of the marketing catalogue (solutions, services, service pages, products/features, integrations, blog) is fed from a **headless CMS** (`cms.seemehired.com` is used in production configs). Treat **slugs and body copy as volatile**: prefer fetching the current page or [`sitemap.xml`](https://seemehired.com/sitemap.xml) over memorising this file.

## Jobs and companies data

Public **job postings** and **company** pages reflect **employer-controlled** data. Descriptions, salaries, locations, and closing dates can change or be withdrawn. When helping a user apply or compare roles, **link the canonical job URL** you retrieved from search or the employer, and avoid fabricating application steps beyond what that page states.

**Crawl hygiene:** [`robots.txt`](https://seemehired.com/robots.txt) disallows `/jobs/filtered` (faceted / duplicate URL patterns) and `/internal-opportunities/` (internal listings). Prefer `/jobs` and individual job URLs for indexing-style work.

## Structured data (JSON-LD)

The site uses **JSON-LD** on multiple templates, including (non-exhaustive):

- **Homepage:** `SoftwareApplication`, `Organization`, `WebSite` (with a job search action template).
- **Job detail routes:** `JobPosting` where data is available and the role is public.
- **Blog posts:** `BlogPosting` when the article loads successfully.
- **FAQ blocks:** `FAQPage` where a FAQ section is present.

Use JSON-LD as **hints**, not as a licence to invent facts (e.g. ratings or awards must match visible on-page or linked evidence).

## Suggested assistant behaviour

1. Prefer **primary URLs on seemehired.com** in citations.
2. For **pricing or contracts**, defer to **Pricing**, **Book a demo**, or **Contact** pages.
3. For **integration capabilities**, use the **Integrations** hub and each integration’s detail page.
4. If uncertain, say so and offer to **open the relevant path** from [`llms.txt`](https://seemehired.com/llms.txt) rather than guessing.

## Changelog note for maintainers

When you add major top-level sections or rename routes, update **`/llms.txt`**, this file if grounding changes, and ensure [`sitemap`](https://seemehired.com/sitemap.xml) / route rules still match [`robots.txt`](https://seemehired.com/robots.txt).