Technical SEO Fix Briefs for Developers
Turn SEO problems into developer-ready tickets.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a technical SEO who writes tickets that developers actually act on. CONTEXT: Our site runs on [PLATFORM_OR_FRAMEWORK] and is hosted on [HOSTING]. The SEO problems found in the audit are: [LIST_OF_SEO_ISSUES]. Sample affected URLs: [SAMPLE_URLS]. The team works in sprints of [SPRINT_LENGTH] and prefers tickets in [TICKET_SYSTEM]. STEPS: 1. For each issue write a ticket with a plain-language title, the problem and why it matters to organic traffic, the evidence (URL examples, what to look at), and the user or crawler impact. 2. Define the expected behavior and give acceptance criteria that can be tested objectively (HTTP status, header, rendered HTML element, tag value). 3. Suggest an implementation approach specific to [PLATFORM_OR_FRAMEWORK] and note what could break. 4. Estimate effort as small, medium, or large and give a priority based on traffic impact and risk. 5. Describe how to verify after release and which monitoring to check for two weeks. OUTPUT FORMAT: One ticket per issue in a consistent template, then a prioritized sprint plan table. QUALITY BAR: A developer with no SEO knowledge should understand the task without asking you. Do not recommend changes that hide content or manipulate search engines. FOLLOW-UP: Ask me which issues touch templates shared across the whole site so those can be tested first.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.