Step 5 of 8

Write tickets developers act on

Updated 5 min read

Short answer: a developer should be able to fix the ticket without asking you anything. That takes four things: what's wrong, the evidence, how to fix it, and which pages it covers. An audit ticket from SEOSnip has all four filled in; check them and submit.

What a good ticket has

  • What's wrong, in a sentence: "Product page titles are cut off in search results."
  • The evidence: the actual title, its length against the limit, the server HTML that's missing the tag. Not "the SEO tool said so".
  • How to fix it, specific enough to act on: which tag, which template, what it should say.
  • The scope: this page, the product template (48 pages), or every page.
  • A way to check it: the developer, or you, can press Check if fixed instead of eyeballing it.

Ticket an audit issue

  1. In the Issues tab, press Ticket on the issue. The Ticket tab fills in the title, the description (what's wrong, the page, the context, the recommendation), the evidence, the scope and a priority.
  2. Check the scope. For a template ticket, name the template and count its pages.
  3. Add anything only you know: "this changed in last week's release", "the CMS field is called SEO title".
  4. Press Submit Ticket. It lands in the project for that domain, with the page data captured alongside it.

Leave the generated description's layout as it is. The web app reads it to show What's wrong, the evidence and How to fix as separate sections, with a Learn more link to the guide.

Write one by hand

Not everything comes from a check: a broken menu on mobile, a template that's missing a section. Use the Ticket tab directly:

  • What's wrong and How to fix are separate boxes; How to fix is optional if you don't know the fix.
  • + Write a note under Evidence for what you saw and where.
  • On the web app, Polish with AI in the ticket's ⋯ menu tidies the wording into the same headings.

Add screenshots and recordings

When the problem is visual, show it:

  • Screenshot (Alt+Shift+S): drag a box around the part of the page that matters, mark it up, and it's attached.
  • Record (Alt+Shift+R): records the tab after a 3-2-1 countdown. Trim the start and end before you submit.

The ticket also keeps the page data captured with it (head tags, console, network, social previews), which a developer can open under Page data. Pin the part that matters so it shows with the evidence.