SEO as configuration work, not as a promise.

What this involves

• Indexing rules that say what you mean

  robots directives, canonical addresses, handling of pagination and query parameters, so a crawler is not left guessing which of five addresses is the page and which three should never have been reachable.

• Multi-language sites that pair correctly

  hreflang pairs derived from the route table instead of written per page by hand. With translated addresses this breaks silently — one language version missing is enough — and silently is the expensive way.

• Structured data

  schema.org as JSON-LD for the page types your specification names — organisation, service, article — carrying the same statements as the visible text, so the description a machine reads matches the one a person reads.

• Local search, where a location is part of the offer

  Address, opening data and service area stated once in the visible text and once as schema.org markup, identical on every page that names them. Directory and map entries the customer owns are set to those same values on their instruction. The work itself stays remote.

• Sitemaps and redirects

  Generated sitemaps that follow the routes instead of a second list somebody has to remember, and redirect maps in the web server when addresses change, so old links keep resolving instead of ending in an error page.