Specoria
Menu
TR Free test
← All checks
service_pages

Services described

Why it matters An agent matches a request (“a bookkeeping firm for a small business”) against named services; vague pages lose the match.

Category
Service data
Weight
15 of 100 points (together with the common checks)
Critical blocker
No. If it fails, it only costs its own weight.
Applies to
Service businesses
Effort
2-4 hours · content and developer
Score model
v2.4

How we measure it

We look for Service definitions in structured data or links to service pages on the homepage (“Our services”, /services…). Either passes, neither fails.

What the result page says

These are the sentences in the test result; “…” is replaced by what we found on your site.

  • PassedServices are described in the structured data (Service): ….
  • PassedThe homepage links to … service page(s). Adding Service data would make them easier for agents to compare.
  • FailedNo Service data and no service pages linked from the homepage were found.

How to fix it

Target: One page per service, linked from the homepage, each with Service data pointing to your organization.

Example code

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Service name",
  "description": "What’s included, for whom and how long it takes.",
  "provider": { "@id": "https://example.com/#org" },
  "url": "https://example.com/services/service-name"
}

Example values (example.com, product name, price) are placeholders; replace them with your own.

How to verify it yourself

Each service should have its own page linked from the homepage, ideally with Service JSON-LD (name, description, provider).

Fix it with an AI coding agent

Paste this into Claude Code, Cursor or another coding agent working on your store’s code. Review the change before you deploy it.

You are working on my online store. Specoria’s agent readiness test checks the item below. Fix it so AI shopping agents can read the store and act on it.

## 1. Services described (service_pages)
Target: One page per service, linked from the homepage, each with Service data pointing to your organization.
Example fix (adapt it to this codebase and platform; example values are placeholders):
```
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Service name",
  "description": "What’s included, for whom and how long it takes.",
  "provider": { "@id": "https://example.com/#org" },
  "url": "https://example.com/services/service-name"
}
```
Reference: https://specoria.com/method/checks/service-pages/

## Rules
- First look through the codebase and tell me which files or templates you will change, before editing anything.
- Change only what these checks need, and keep the visible page and the structured data saying the same thing.
- Never invent prices, stock, shipping or return terms, reviews or product identifiers (GTIN): take them from the store’s real data or ask me.
- Don’t block or slow down real visitors and don’t add tracking.
- After deploying, run the free test again at https://specoria.com/ to verify the fix.

Specifications and guidance

The check is based on these open sources; links go to the publisher’s own pages.

Run the free test See the sample report →