Contact
Describe the issue
The more concrete the symptom, the easier it is to define the right first sprint.
What happens next
If the issue is sharp enough, the reply should point to a bounded first-step recommendation rather than a vague package.
The best submissions include
- The exact symptom instead of a broad category.
- The page type or affected URLs where the problem is visible.
- What changed just before the issue showed up.
- Any tooling clues already visible in GSC, Cloudflare, PageSpeed, dashboards, or task systems.
The likely path
- Review the issue and the context you send.
- Define the cleanest bounded sprint if the problem is a fit.
- Implement, verify, and hand off the result clearly.