TECHNICAL / SERVICE SCOPE
Technical SEO.
Find the causes behind crawl, rendering and indexation problems. Define a change at the template level and check what the live page serves.
Explore the scope ↓- Best starting point
- Important pages are difficult to discover, templates produce conflicting signals or a release changes the content search engines can access.
- Working artifact
- URL pattern, Observed behavior and the fields shown below.
- How to evaluate
- Check the output, implementation owner and acceptance evidence.
What the scope produces
- A template-level diagnosis with reproducible evidence
- Requirements for crawl paths, canonical signals and status handling
- A developer handoff with testable acceptance criteria
- A before-and-after release checklist
What the work needs
Website templates, crawl data, server or platform access where relevant and the release process.
A sample working artifact
Illustrative structure, not a client result. A completed record should make the work and its verification clear.
- URL pattern
- A specific value recorded for the engagement.
- Observed behavior
- A specific value recorded for the engagement.
- Root cause
- A specific value recorded for the engagement.
- Change
- A specific value recorded for the engagement.
- Regression check
- A specific value recorded for the engagement.
How the work moves forward
Reproduce the behavior
Observe the URL, response status and served content. Compare the intended page with what a crawler receives.
Trace the cause
Find whether a template, rendering rule or URL policy creates the issue.
Verify the release
Check representative pages and edge cases in production after the change is made.
Scope boundaries
An accessible page can still be excluded from an index. Technical eligibility and a search engine's inclusion decision are separate.