Service

Crawlable by search engines, and quotable by the models people ask instead.

The technical half of search: crawl paths, indexing, structured data, and the Core Web Vitals of the templates that carry traffic. Then the newer half, which is whether an answer engine can parse a page well enough to cite it. Both come down to markup a machine can read and pages that load.

Start a buildAll services

Technical SEO & GEOIllustrative panel

Focus

Crawl architecture, Schema.org, Core Web Vitals, and AI search visibility.

Crawl architectureSchema.orgAI search visibility

Service: Technical SEO & GEO
Deliverables: Named and scoped below
Bought as: A defined build, or run under management
Ownership: Every account and platform stays in the client’s name

Fig. 01 · Crawled, indexed, and servedIllustrative panel

Crawled, indexed, and served

Sitemaps, robots rules, canonicals, and internal links built so a crawler can reach every page worth having. Pages stuck in Discovered are a plumbing problem, not a content problem.

Fig. 02 · Structured data that describes the real businessIllustrative panel

Structured data that describes the real business

Schema.org markup for the entities that actually exist: the services, the locations, the people, the products. Machines reuse it, so it has to be true.

Fig. 03 · Visible to answer enginesIllustrative panel

Visible to answer engines

Content parseable enough to be quoted, entity details consistent across the places that describe the business, and reporting on citations rather than a single rank number.

Scope

What gets built.

Crawl and index architecture: sitemaps, robots rules, canonicals, pagination

Schema.org markup for the entities the business actually has

Internal linking that connects pages a crawler would otherwise never reach

Core Web Vitals work on the templates carrying the traffic

Answer-engine visibility: parseable content, citations, and consistent entity detail

Measurement in Search Console and server logs rather than a rank-tracker screenshot

DeliverablesScoped in writing before work starts

Outcome

What changes.

Pages get crawled, indexed, and served instead of sitting in Discovered.

Structured data describes the business accurately enough for a machine to reuse it.

Visibility gets reported against queries, pages, and citations rather than one number.

Structural changeNo performance figure is claimed

AI engineering

Agents & retrieval · Extraction · Qualification & routing

Migration & modernization

Content parity · Redirect mapping · Staged cutover

Technical consulting

Architecture review · Technical audit · Written recommendation

Performance engineering

Rendering & caching · Script budget · Field Core Web Vitals

Start

Start with what’s broken.

Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.

Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.

Or email hello@strygon.com

What to send: A paragraph. What broke, and where it shows up.
What comes back: A read on what is likely wrong and what fixing it takes.
Price: The last conversation, not the first