seo-technical

1# Technical SEO
2 
3## Input
4 
5A site/page URL, crawl export, source snapshot, response headers, or deployment comparison.
6 
7## Evidence and runtime
8 
9If a skill-resource reader fails to open a linked supporting file, try the
10available file or execution tool using the installed plugin root returned by
11the host or resolved from this skill's location. Do not hardcode a home folder,
12version, or working directory. Distinguish a failed reader call from an absent
13file, and files actually attempted from files not attempted. Report a resource
14as unavailable only after the supported access paths have failed. If no file
15or execution access is available, continue within the evidence you can read
16and state that limit.
17 
18Read [the operating contract](../../references/operating-contract.md) when this
19workflow is selected. Use [runtime and data paths](../../references/runtime-and-data.md)
20when choosing a tool or handling missing data. Recheck relevant
21[search facts and primary sources](../../references/current-search-facts.md)
22before date-sensitive claims. For a quantitative diagnostic, read
23[scoring](../../references/scoring.md); unavailable categories stay unknown.
24 
25## Supporting resources
26 
27Read only the resources needed for the selected part of this task:
28 
29- [technical and performance evidence](../../references/technical-checks.md).
30- [supplied crawl inputs](../../references/dataset-contracts.md).
31 
32- [field and lab CWV report template](../../assets/cwv-report.md).
33 
34## Workflow
35…