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.
Turn SEO problems into developer-ready tickets. Site, platform, and stack: [SITE_AND_STACK]. List of SEO problems with affected URLs and counts: [PASTE_PROBLEMS]. Priorities and release process: [PRIORITIES_AND_PROCESS]. Write each ticket like this example. Title: Add canonical tags to paginated category pages Problem: Pages like /shoes?page=2 have no canonical tag, so search engines may treat parameter variants as duplicates. 214 URLs affected (crawl export, 3 Oct). Expected behavior: each paginated page includes a self-referencing canonical to its own URL without tracking parameters. Implementation notes: add in the category template head section; strip utm parameters; do not point page 2 and above to page 1. Acceptance criteria: 1) view source on /shoes?page=2 shows canonical /shoes?page=2. 2) Parameters like utm_source are not in the canonical. 3) No change to page 1. How to test: crawl 20 sample URLs; check the live URL inspection tool after release. Priority and effort: medium, half a day. Risk: low. Owner: front-end. Write a ticket for each problem I listed in that format, group them into sprints by priority and dependency, add a verification checklist for after release, and a note on what not to do (blocking resources, redirect chains). Don't promise ranking effects.
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 ChatGPT, Gemini, Claude or another assistant.