The SEOFOMO State of Technical SEO – Survey Results 2024
Survey
The results of the SEOFOMO Technical SEO Survey are in!
Between September 12 and October 11, 2024, we gathered insights from 282 technical SEO specialists (or SEOs who do tech SEO as part of their day to day tasks) to better understand the challenges and trends when doing technical SEO.
I want to thank all the SEOFOMO newsletter subscribers and friends who participated, and take the opportunity to announce the winner of the SEOFOMO giveaway (winning an SEOFOMO mug and hoodie, a free 1 year license of Screaming Frog SEO Spider and a 1 year license of Sitebulb Pro Desktop Edition: Nikki Halliwell!
Thanks, for taking the survey and participating in the giveaway. I’ll be getting in touch to coordinate the swag delivery and tools access.
Now let’s review the results. This survey offers a comprehensive look at the current state of technical SEO, highlighting common challenges, preferred tools, and anticipated trends for the coming year.
What type of SEO are you?
26 %
Freelance / Independent SEO
73 answers
38 %
In-House SEO
109 answers
32 %
Agency SEO
90 answers
4 %
Other
10 answers
What's your SEO Specialization?
40 %
SEO Generalist / Not Specialized
114 answers
37 %
Technical SEO
104 answers
0 %
Link Builder
1 answers
9 %
Content Focused SEO
24 answers
14 %
SEO Management
39 answers
For how long have you been doing Technical SEO related Activities
14 %
+15 Years
39 answers
24 %
From 10-15 Years
67 answers
30 %
From 5-10 Years
84 answers
24 %
From 2-5 Years
69 answers
8 %
Less than 2 Years
23 answers
What is the typical size of the websites you usually work with?
11 %
Very Big: More than 5M URLs
29 answers
13 %
Big: Between 1M - 5M URLs
38 answers
31 %
Medium: Between 100K - 1M URLs
87 answers
45 %
Small: Less than 100K URLs
128 answers
How impactful are Technical SEO efforts to your SEO projects' goals vs other SEO activities?
7 %
Slightly Impactful
20 answers
42 %
Moderately Impactful
118 answers
42 %
Highly Impactful
120 answers
9 %
Extremely Impactful
24 answers
What percentage of your technical SEO recommendations end up getting implemented in most of your SEO Processes?
4 %
Less than 10%
10 answers
4 %
Between 10% to 20%
10 answers
17 %
Between 20% to 40%
48 answers
29 %
Between 40% to 60%
81 answers
27 %
Between 60% to 80%
77 answers
12 %
Between 80% to 90%
35 answers
7 %
More than 90%
21 answers
What's the average timeframe for a technical SEO recommendation to get implemented?
3 %
Less than a week
8 answers
14 %
Between 1 to 2 weeks
39 answers
21 %
Between 2 to 4 weeks
59 answers
24 %
Between 4-6 weeks
69 answers
18 %
Between 6-8 weeks
52 answers
6 %
Between 8 to 10 weeks
18 answers
6 %
Between 10 to 12 weeks
18 answers
4 %
Between 12-16 weeks
9 answers
4 %
More than 16 weeks
10 answers
What’s the most common reason for technical SEO recommendations execution getting delayed or not implemented?
Based on the responses provided, the main reasons for technical SEO recommendations being delayed or not implemented can be summarized and grouped into the following key categories:
1. Resource Constraints (Development/IT Bandwidth):
The most frequently cited reason is the lack of available developer resources or bandwidth. Development teams are often overburdened with other priorities, leaving little room for SEO implementation.
Many tasks are placed in long development backlogs, with SEO often deprioritized in favor of more immediate or high-visibility projects like new features or bug fixes.
Examples: “Busy developers”, “Dev team backlog”, “Limited developer capacity”, “Developer bandwidth”, “Too much reliance on dev teams”, “No in-house resources”.
2. Prioritization Issues:
SEO recommendations often compete with other business initiatives, and are considered lower priority compared to revenue-generating projects or urgent fixes.
This is exacerbated when SEO is not perceived as critical to immediate business success.
Examples: “Other priorities”, “Conflicting priorities”, “Development roadblocks”, “SEO tasks are last in priority”, “More pressing fixes”.
3. Lack of Understanding or Buy-In (From Stakeholders/Management):
Stakeholders and teams often don’t fully understand the value of technical SEO, leading to skepticism or delayed action.
Getting buy-in from stakeholders, particularly when it involves significant investment or development effort, can be challenging.
Examples: “The client does not see the value”, “Lack of understanding of SEO”, “SEO perceived as less important”, “Need approval from stakeholders”.
4. Budget Constraints:
Financial limitations often delay implementation, as technical SEO can be viewed as expensive, especially if the ROI is not clear.
Examples: “Low budget for devs”, “High cost from web developer”, “Budget or time constraints”, “Cost to the client”.
5. Technical Complexity:
Some technical SEO recommendations are complex and require significant time, effort, and expertise to implement. The complexity can vary depending on the website’s CMS, codebase, or platform.
Examples: “Complexity of the task”, “CMS limitations”, “Technical restrictions”, “Difficult or time-consuming fixes”.
6. Internal Communication & Workflow Issues:
Miscommunication between SEO, development, and other teams can cause delays. Clear communication is often lacking, especially when conveying the technical requirements or importance of SEO tasks.
Examples: “Communication gap”, “Ambiguous briefing”, “Poor communication between teams”.
—
In summary, the top reasons for delays or non-implementation of technical SEO recommendations are primarily due to a lack of development resources, low prioritization compared to other business tasks, and insufficient understanding or buy-in from stakeholders. Budget constraints and the technical complexity of the tasks also play significant roles.
What's the level of difficulty in achieving your expected technical SEO goals compared to a couple of years ago?
32 %
The same
91 answers
31 %
Harder
87 answers
28 %
Easier
80 answers
9 %
I'm not sure
24 answers
How often do you develop whether partial or full technical SEO audits in your SEO processes?
5 %
With every release
15 answers
10 %
Every week
29 answers
28 %
Every month
79 answers
27 %
Every quarter
77 answers
9 %
Every six months
25 answers
4 %
Every year
12 answers
13 %
On demand
37 answers
4 %
Another frequency
8 answers
Do you pre-schedule crawls to automate the validations of your site configurations?
42 %
Usually Yes
119 answers
30 %
Only when the nature/complexity of the project requires it
84 answers
18 %
Usually No, I wish I could but I have constraints
51 answers
10 %
Usually No, I don't think they're as useful
28 answers
Do you use SEO alerting tools to notify you whenever a technical SEO related configuration has changed?
47 %
Usually Yes
132 answers
19 %
Only when the nature/complexity of the project requires it
54 answers
29 %
Usually No, I wish I could but I have constraints
81 answers
5 %
Usually No, I don't think they're as useful
15 answers
What type of SEO crawler do you usually use for your technical SEO audits?
40 %
Desktop Based Crawler
112 answers
15 %
Cloud Based Crawler
42 answers
45 %
A mix of Desktop and Cloud Crawlers
128 answers
How often do you enable JS rendering when crawling Websites?
20 %
Less than 10% of the crawls
56 answers
12 %
Between 10 to 20% of the crawls
34 answers
13 %
Between 20% to 40% of the crawls
38 answers
20 %
Between 40% to 60% of the crawls
57 answers
8 %
Between 60% to 80% of the crawls
22 answers
4 %
Between 80% to 90% of the crawls
11 answers
23 %
More than 90% of the crawls
64 answers
How often do you integrate Google Search Console, Analytics, or any other third-party SEO metrics in your crawls?
11 %
Less than 10% of the crawls
32 answers
7 %
Between 10 to 20% of the crawls
20 answers
10 %
Between 20% to 40% of the crawls
27 answers
15 %
Between 40% to 60% of the crawls
42 answers
13 %
Between 60% to 80% of the crawls
38 answers
12 %
Between 80% to 90% of the crawls
34 answers
32 %
More than 90% of the crawls
89 answers
How many SEO crawlers do you usually use in your technical SEO audits?
27 %
Only 1
77 answers
67 %
2 to 3
190 answers
4 %
3 to 4
11 answers
2 %
5 or more
4 answers
Do you do Web log file analysis as part of your technical SEO analysis?
20 %
Usually Yes
56 answers
37 %
Only when the nature/complexity of the project requires it
104 answers
34 %
Usually No, I wish I could, but I don't get access
97 answers
9 %
Usually No, I don't think they're as useful
25 answers
Do you often use third-party plugins, add-ons or CDN-based solutions for any of these technical SEO implementations?
34 %
JS Rendering
95 answers
30 %
Internal linking
86 answers
17 %
Indexing API integration
48 answers
46 %
Redirects & Rewrites
130 answers
48 %
XML Sitemaps
136 answers
52 %
Structured Data
146 answers
27 %
Hreflang annotations
76 answers
39 %
Canonical tags
110 answers
34 %
Meta robots
97 answers
53 %
Web speed optimization (caching, minification, etc)
150 answers
15 %
Other implementations
42 answers
27 %
I don’t use any
77 answers
Do you validate your site's technical SEO implementations in a test environment before they're released?
44 %
Usually Yes
125 answers
29 %
Only when the nature/complexity of the project requires it
82 answers
19 %
Usually No, I wish I could but I have constraints
53 answers
8 %
Usually No, I don't think they're as useful
22 answers
How do you measure the success of your technical SEO efforts?
Here’s an aggregated summary of how technical SEOs measure the success of their efforts, categorized by key types:
1. Performance and Speed Metrics:
* Page Load Speed: Faster load times after implementation.
* Core Web Vitals: Improvements in LCP, FID, CLS, etc.
* Page Speed Reports: Monitoring via tools like Google PageSpeed Insights, and internal reports.
2. Crawlability and Indexability:
* Indexation Rate: Increased percentage of indexed pages (Google Search Console, GSC reports).
* Crawl Rate: Improved crawling efficiency, fewer errors like 404s, crawl depth reduced.
* Crawl Errors: Reduction in crawl issues/errors monitored through GSC and third-party crawlers (e.g., Screaming Frog, SEMrush).
3. Organic Traffic and Visibility:
* Organic Traffic Growth: Overall increases in traffic from organic sources.
* SERP Rankings: Improvements in keyword rankings, and SERP visibility.
* Impressions and Clicks: Measuring the impact via GSC for impressions and clicks.
4. Technical Error Fixes:
* Error Resolution: Reducing or eliminating technical errors like broken links, 404s, 301s, and structured data issues.
* GSC Error Monitoring: Ongoing tracking of GSC error reports.
5. User Experience Improvements:
* Mobile Usability: Enhancing mobile responsiveness, with better UX.
* Bounce Rate and Engagement: Measuring reduced bounce rates, and better engagement metrics like time on site, scroll depth.
6. KPI Monitoring:
* Pre-Defined KPIs: Meeting KPIs for organic traffic, conversions, and indexation set during project kickoff.
* Revenue and Conversions: For e-commerce, improvements are often tied to increases in revenue and organic conversions.
7. A/B Testing and Experimentation:
Testing Technical Changes: Using A/B testing, or monitoring changes in isolation to track specific impacts, especially for things like crawling/indexation improvements, page speed, and structured data implementations.
8. Site Health and Tool Monitoring:
* Site Health Scores: Monitoring improvements in site health via tools like SEMrush, Ahrefs, or Lumar.
* Audit Comparisons: Comparing before and after results from regular technical SEO audits.
9. Log File and Crawl Data Analysis:
* Crawl Logs: Monitoring crawl budget, crawl depth, and indexing patterns using server logs for in-depth analysis.
* Crawl Activity: Measuring changes in crawl frequency and efficiency.
10. Overall Strategic Objectives:
Meeting Business Goals: Aligning technical SEO improvements with broader business objectives, like visibility gains, organic growth, and revenue impact.
—
This summary reflects that success is usually measured through a mix of KPIs specific to the technical issue being addressed, ranging from basic crawlability to complex A/B testing and business-centric outcomes like conversions and revenue.
What's the biggest Technical SEO challenge you tend to have in your projects at the moment?
Here’s a consolidated summary of the biggest technical SEO challenges SEOs face, categorized by key challenge types:
1. Development and Resource Constraints:
Lack of Developer Resources: Limited availability of developers to implement SEO recommendations or delays in the development queue.
Slow Implementation: Difficulty in getting technical SEO fixes implemented quickly, leading to delays in results.
CMS Bottlenecks: Inflexible content management systems (CMS) that hinder SEO efforts, such as Shopify, Wix, or custom platforms.
Legacy Systems: Dealing with outdated platforms, tech stacks, or poorly coded websites that make technical fixes more challenging.
Cross-Team Collaboration: Difficulty in working with large or distributed teams across time zones, or with teams (IT, dev, marketing) that are resistant to SEO recommendations.
2. JavaScript & Rendering Issues:
JavaScript SEO: Challenges with JavaScript frameworks like React, Next.js, and Single-Page Applications (SPA), which impact rendering and indexation.
JS Rendering & Crawlability: Search engines struggle with crawling and indexing JavaScript-heavy pages, requiring specific optimizations.
Slow Page Load: Issues related to page speed, particularly on JS-powered sites, which are technically demanding and often involve multiple stakeholders.
3. Core Web Vitals and Performance Optimization:
Core Web Vitals (CWV): Difficulty in optimizing key metrics like LCP, CLS, and INP for large or complex websites.
Page Speed: Constant need to improve page loading times, especially when dealing with foundational tech stack limitations or external CMS.
4. Client Communication and Buy-In:
Convincing Stakeholders: Difficulty in explaining the value and importance of technical SEO to clients, management, or other departments.
Budget Constraints: Limited budgets from clients or stakeholders for implementing SEO changes, especially for small businesses or non-technical clients.
Educating Clients: Helping clients understand the technical side of SEO and the necessity of prioritizing it.
5. Site Structure, Indexation, and Crawl Budget:
Crawl Budget Optimization: Ensuring large websites with millions of pages are crawled efficiently, while controlling what gets indexed.
Indexation Issues: Pages not being indexed properly, dealing with improper canonical tags, and handling multiple URL variations.
Site Migrations: Challenges with site migrations leading to traffic loss, improper redirects, or missed SEO recommendations.
Internal Linking: Difficulty in managing or scaling internal linking strategies on large websites.
6. Algorithm Updates & SEO Trends:
Google Algorithm Updates: Adapting to the constant changes in search engine algorithms, such as core updates, and staying updated with new trends like mobile-first indexing.
AI and Automation: The rise of AI-driven search results (e.g., zero-click searches) and dealing with content automation.
7. Specific Technical SEO Issues:
Hreflang Implementation: Challenges with multi-language and multi-regional SEO, particularly in managing hreflang tags and canonicalization.
Structured Data: Implementing structured data at scale, especially for large websites with complex content management systems.
Redirects & URL Management: Improper use of redirects, trailing slashes, and managing duplicate URLs.
8. Other Notable Challenges:
Crawling and Indexing Large Sites: Difficulty in conducting audits and log analysis on websites with millions of pages.
Competing Priorities: Balancing SEO tasks with other business-critical projects, leading to technical SEO being deprioritized.
Dealing with Non-SEO Friendly Tech: Working with platforms or frameworks not built with SEO in mind, requiring custom solutions.
—
These challenges highlight a mix of resource limitations, technical complexity, client communication issues, and the evolving nature of SEO and search engine algorithms.
What are the top 3 tools you use for your Technical SEO tasks?
24.6 %
Google Search Console
159 answers
24.4 %
Screaming Frog
158 answers
12.8 %
Ahrefs
83 answers
12.6 %
Semrush
82 answers
6.3 %
Sitebulb
41 answers
2 %
Chrome Dev Tools
13 answers
1.7 %
Google PageSpeed Insights
11 answers
1.7 %
Botify
11 answers
1.7 %
OnCrawl
11 answers
1.4 %
Webpagetest
9 answers
1.9 %
Sistrix
7 answers
1 %
Google Analytics
6 answers
0.7 %
GTMetrix
5 answers
0.7 %
SE Ranking
5 answers
0.7 %
Moz
5 answers
0.7 %
Lumar
5 answers
0.6 %
Google Sheets
4 answers
0.46 %
Ubersuggest
3 answers
0.46 %
ContentKing
3 answers
Are you leveraging AI / LLMs to automate your technical SEO tasks?
30 %
Yes, for technical SEO analysis / auditing
85 answers
13 %
Yes, for technical SEO implementation
36 answers
15 %
Yes, for technical SEO communication
43 answers
20 %
Yes, for technical SEO reporting
56 answers
51 %
No, I haven’t
144 answers
Have you developed your own tools to help with technical SEO tasks?
23 %
Yes, for technical SEO analysis / auditing
62 answers
6 %
Yes, for technical SEO implementation
16 answers
6 %
Yes, for technical SEO communication
17 answers
18 %
Yes, for technical SEO reporting
50 answers
64 %
No, I haven’t
175 answers
What tools or platforms do you use to coordinate SEO implementation with developers or product teams?
19.8 %
Jira
43 answers
11.52 %
Slack
25 answers
9.22 %
Google Sheets
20 answers
8.76 %
Asana
19 answers
6.91 %
Trello
15 answers
5.99 %
13 answers
3.69 %
Microsoft Teams
8 answers
3.69 %
ClickUp
8 answers
2.76 %
Confluence
6 answers
2.76 %
Monday.com
6 answers
2.30 %
Google Docs
5 answers
2.30 %
Notion
5 answers
1.84 %
Basecamp
4 answers
1.84 %
Ahrefs
4 answers
1.84 %
Google Search Console
4 answers
1.84 %
Semrush
4 answers
1.38 %
GitHub
3 answers
1.38 %
Linear
3 answers
1.38 %
Screaming Frog
3 answers
0.92 %
Azure DevOps
2 answers
What's the technical SEO related functionality you wish tools had but they don't yet?
Here’s a consolidated summary of the new functionalities SEOs wish tools had, categorized by key themes:
1. AI Integration & Predictive Analysis:
AI-Driven Recommendations: Tools that offer real-time, AI-generated SEO solutions, such as fixing technical issues, predicting impacts of changes, and suggesting improvements based on competitor and historical data.
Predictive Impact Analysis: Tools that forecast the potential SEO impact of changes (e.g., schema, structure, URL) before implementation.
AI for Core Web Vitals (CWV): AI suggestions on how to improve CWV metrics based on the website’s CMS or specific technical factors.
Automated Fixes: One-click solutions for issues like redirects, status codes, and SEO bugs.
2. Enhanced Reporting & Visualization:
Real-Time Monitoring: Tools offering real-time detection of SEO issues (e.g., crawl errors, indexation problems, Core Web Vitals) with instant alerts.
Change Tracking & Reporting: Features to track changes over time and compare old vs. new site conditions, helping detect issues faster.
Better Internal Linking Visualization: More intuitive visual representations of internal linking structures, showing architectural issues like orphan pages or broken links.
Content & SEO Change Monitoring: Tools that automatically monitor changes in a site’s structure, content, or technical setup and provide detailed reports on the impact.
3. Log File & Crawl Budget Analysis:
Log File Analysis Integration: Tools that combine log file analysis with crawl data to optimize crawl budget and identify crawl inefficiencies.
Crawl Budget Optimization: Tools that analyze a website and suggest specific improvements to maximize crawl budget, especially for large sites.
4. JavaScript & Rendering Diagnostics:
JS Rendering Analysis: More comprehensive and automated analysis of JavaScript-rendered content, identifying slow-loading scripts and providing actionable fixes.
SSR vs. CSR Insights: Features that analyze and compare server-side rendering (SSR) vs. client-side rendering (CSR) to assess their impact on SEO.
Real-Time JS Issue Detection: Automated detection of JavaScript-related issues and better integration with tools like Chrome DevTools.
5. Core Web Vitals & Page Speed Optimization:
Core Web Vitals Focus: Tools that provide specific, CMS-based recommendations for optimizing Core Web Vitals, with real-time measurement of performance improvements.
Page Speed Analysis at Scale: Tools that provide real-time insights on how page speed optimizations affect Core Web Vitals metrics and page load times.
6. Automation & Task Prioritization:
Task Prioritization: Tools that prioritize SEO tasks based on potential business impact, helping SEOs focus on the most critical fixes.
Automated SEO Issue Fixing: Tools with more automation around diagnosing and fixing common issues like structured data, redirects, and internal linking at scale.
Automated Structured Data: Tools that automatically generate and implement structured data across a website based on content type.
7. Advanced Crawling Capabilities:
Regex or Page-Type Crawls: Ability to limit crawls to specific page types (e.g., blog pages, product pages) or use regex to customize crawls for large sites.
Crawl Simulations: Tools that simulate search engine crawls to better estimate a website’s crawlability and crawl budget.
8. Cross-Tool & API Integration:
Better Tool Integration: Integration across multiple tools (GA4, GSC, etc.) to provide holistic data analysis and save time on merging datasets.
API & Data Warehousing: API integrations to warehouse Google Search Console (GSC) data, with historical records and fewer limitations on data exports.
9. Schema & Structured Data Improvements:
Schema Suggestions: Tools that automatically recommend and implement appropriate schema markup based on a site’s content.
Schema Validation at Scale: More robust validation tools to ensure proper schema markup across large websites, especially for complex structures.
10. Miscellaneous Desired Functionalities:
SEO Collaboration Tools: Real-time collaboration features to streamline communication between SEO, development, and content teams during site audits.
Tech SEO Education & Guides: Tools that provide beginner-friendly guides and explanations for complex technical SEO concepts.
Revenue/Impact Estimation: Tools that estimate the traffic and revenue impact of SEO changes, helping SEOs justify their work to stakeholders.
—
This summary reflects a desire for more AI-driven features, predictive analysis, advanced monitoring, and deeper integrations to make technical SEO tasks more efficient and impactful.