Slide 1

Slide 1 text

the Language of Devs. Nikki Halliwell Director of TechSEOAudits.com | Technical SEO Consultant | Technical SEO Manager @ Journey Further

Slide 2

Slide 2 text

01 Do you Struggle to Communicate with Developers? Question 1ξ‚’ nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 3

Slide 3 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Communication Between Devs and SEOs is Fundamental in Tech SEO

Slide 4

Slide 4 text

πŸ“Š Shared KPIs require alignment. πŸ“ž Lack of regular comms leads to delays and poor results. πŸ“ˆ THE GOAL: Create workflows that drive mutual success. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com The of Good Dev Comms

Slide 5

Slide 5 text

But itΚΌs not always that easy, right? nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 6

Slide 6 text

Most tech SEO recommendations take 4-6 weeks to get implemented. SEOFOMO nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 7

Slide 7 text

Most SEOs only see 40-60% of their tech SEO recommendations implemented. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com SEOFOMO

Slide 8

Slide 8 text

+ Barriers to Effective Collaboration nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 9

Slide 9 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Speaking Different SEOs have a reputation for speaking in marketing jargon; while developers often use more technical terms.

Slide 10

Slide 10 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Priorities are not Aligned Across Teams While one team prioritises the speed of implementation, the other focuses on completeness and being technically sound.

Slide 11

Slide 11 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com and Lack of Time Developers often have overloaded schedules with huge backlogs of work leaving little time for SEO requests.

Slide 12

Slide 12 text

This is how we can overcome this… nikkihalliwell.com | techseotips.co.uk | techseoaudits.com +

Slide 13

Slide 13 text

The Keys to Dev Comms nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Use Simple and Precise Language πŸ”‘ Avoid jargon. πŸ”‘ Don’t over-explain the solution. πŸ”‘ Get to the point. πŸ”‘ Only include what is necessary.

Slide 14

Slide 14 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com The Keys to Dev Comms Avoid Assumptions πŸ— Clarify technical terminology & abbreviations. πŸ— Be specific with detail & what you need. πŸ— Show examples of the issue. πŸ— Find examples of what β€œgood” looks like.

Slide 15

Slide 15 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com The Keys to Dev Comms Focus on the β€œwhy” πŸ”‘ Emphasise business impact (Β£/$/€) πŸ”‘ What do you want the outcome to be? πŸ”‘ Don't tell developers how to do their job. πŸ”‘ Set a clear priority order.

Slide 16

Slide 16 text

02 How Can We Set Priorities? Question 2ξ‚’ nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 17

Slide 17 text

1. Be transparent in your priority order. 2. Invite them to be part of the process. 3. Agree on a priority that works for all KPIs. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Remember, don’t tell devs what to do

Slide 18

Slide 18 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Red (Critical or Severe) Urgent, high-severity issues that pose significant risks to site functionality or SEO performance, requiring immediate attention. Amber (Moderate) Medium-priority issues that impact the site but are less urgent, with manageable risks that can be addressed in the near future. Green (Low) Low-severity issues that are minor and have minimal impact on the site's performance, to be resolved when resources are available. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com is Widely Understandable

Slide 19

Slide 19 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com 1. High impact, low effort items 2. Quick wins and optimisations 3. Long term and ongoing plans 4. Refinements are low priority. Covers all Tasks+Teams

Slide 20

Slide 20 text

What revenue do they risk losing by not implementing the fixes you recommend? What is the revenue at risk? is a Big Motivator nikkihalliwell.com | techseotips.co.uk | techseoaudits.com PRIORITY NAME REVENUE AT RISK High Issue 1 Β£200,000 High Issue 2 Β£150,000 High Issue 3 Β£100,000 Medium Issue 4 Β£80,000 Medium Issue 5 Β£50,000 Medium Issue 6 Β£45,000

Slide 21

Slide 21 text

Conservative - Potential earnings by improving by an average of 3 positions Forecast Different nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Optimistic - Potential earnings by improving by an average of 5 positions CURRENT CONSERVATIVE (+3) OPTIMISTIC (+5) Non-brand clicks 1,444,955 3,599,135 8,372,356 Non-brand revenue Β£2,037,387 Β£5,074,780 Β£11,805,022

Slide 22

Slide 22 text

+ Internal Communication and Workflow Issues are Common nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 23

Slide 23 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Miscommunication Causes Delays Clear communication is often lacking, especially when conveying the technical requirements or importance of SEO tasks.

Slide 24

Slide 24 text

1. Schedule regular touchpoints and catch ups. 2. Prioritise tasks that align with shared goals. 3. Track progress openly and with transparency. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Dev Comms

Slide 25

Slide 25 text

03 How we Speed Up Tech Ticket Implementation? Question 3ξ‚’ nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 26

Slide 26 text

We need to create clear and actionable tech tickets nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 27

Slide 27 text

What Specific ask or fix. SEO impact or KPIs. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Why Optional, if appropriate. How

Slide 28

Slide 28 text

+ What Does This Look Like? nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 29

Slide 29 text

A concise and actionable request that and clearly outlines the specific task to be completed. It is logged in a project management system like Jira, Trello, or Asana for a developer. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com What is a Tech Ticket?

Slide 30

Slide 30 text

For example: A tech ticket might request the implementation of a canonical tag on a specific page or group of pages to resolve duplicate content issues. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com What is a Tech Ticket?

Slide 31

Slide 31 text

The canonical ticket would include: βž” The exact URL(s). βž” The canonical URL to be used. βž” Why is the change needed? βž” Any supporting links. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com What is a Tech Ticket?

Slide 32

Slide 32 text

A tech ticket should not be a long, multi-page explanation of SEO elements like canonical tags, how they work, or how search engines interpret them. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com What a Tech Ticket is NOT:

Slide 33

Slide 33 text

βž” The key to an effective tech ticket is clarity and precision. βž” Think actionable, not academic! nikkihalliwell.com | techseotips.co.uk | techseoaudits.com What a Tech Ticket is NOT:

Slide 34

Slide 34 text

My Tech Tickets Include βž” Page(s) and Scope βž” Purpose / Issue βž” User Stories βž” Steps to Reproduce the Issue βž” Technical Specs βž” Severity / Priority βž” Success Criteria βž” KPI’s βž” Images of the Issue

Slide 35

Slide 35 text

Clear Clear, concise tickets reduce delays by eliminating back-and-forth. Tickets with specific requests keep tasks easy to implement. Including all necessary details ensures immediate action. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Speed up Implementation Focused Context

Slide 36

Slide 36 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com 50% less time to implement tickets for our clients

Slide 37

Slide 37 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com 70% more likely to be prioritised and completed on schedule

Slide 38

Slide 38 text

04 How Important is it To Work Closely with Devs? Question 4ξ‚’ nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 39

Slide 39 text

As Tech SEOs It is Our Job to Fix Issues and Make Sites Work Better! nikkihalliwell.com | techseotips.co.uk | techseoaudits.com

Slide 40

Slide 40 text

Before… nikkihalliwell.com | techseotips.co.uk | techseoaudits.com - βž” Vague tickets with unclear objectives and insufficient detail. βž” Developers often had to follow up for clarification. βž” Multiple revisions required.

Slide 41

Slide 41 text

After… nikkihalliwell.com | techseotips.co.uk | techseoaudits.com + βž” Requests are clear from the start. βž” The changes align with team goals. βž” Fixes implemented in the first iteration

Slide 42

Slide 42 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com βœ… Reduced total workload, βœ… Accelerated project timelines, βœ… Smoother collaboration.

Slide 43

Slide 43 text

Communication is a 2-way street. Good tickets save time & build trust. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Delivers better results & shared wins.

Slide 44

Slide 44 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com the Language of Devs βž” It’s about understanding what matters to them. βž” What motivates them to do their job? βž” What tickets do they generally focus on and why?

Slide 45

Slide 45 text

βž” Working with devs becomes a lot quicker, βž” Is much more more productive, βž” And causes less headaches. nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Once you nail this…

Slide 46

Slide 46 text

nikkihalliwell.com | techseotips.co.uk | techseoaudits.com Use To Speak the Language of Devs Scan me nikkihalliwell.com/seo-speaker /we-love-seo-2024/ Or visit this

Slide 47

Slide 47 text

Hey, I’m Nikki, I can help you get tech SEO tickets implemented. + Let’s Connect nikkihalliwell.com https://speakerdeck.com/nikkihalliwell

Slide 48

Slide 48 text

No content