In this episode, Pete and Jeff discuss how to implement effective SEO strategies even with limited resources. They break down the essential elements of budget-friendly SEO and provide actionable advice for agencies and clients.

Site Speed Optimization

• Best practices for plugin management
• Implementing proper caching and image optimization
• Importance of quality hosting
• Benefits of using WordPress block editor
• Tips for balancing features vs performance

Site Structure

• Setting up proper permalinks
• Creating effective pillar and cluster pages
• Organizing content hierarchically
• Building strategic internal linking
• Avoiding common structural mistakes

Page Structure

• Proper implementation of heading tags (H1-H6)
• Schema markup basics
• XML sitemap setup
• Common heading tag mistakes to avoid

Budget SEO Strategy for Clients

• Creating comprehensive service pages
• Converting customer questions into content
• Building effective internal linking
• Maintaining regular content updates
• Understanding the time vs money investment

Tools Mentioned

• WP Rocket (caching)
• SEOPress Pro
• Meta SEO Inspector (Chrome extension)
• Headings Map (Firefox extension)
• Google Search Console

Need help implementing these strategies? Contact us at hello@seohive.co

In this episode, Pete and Jeff talk about the practicalities of

running SEO retainers for your clients – the good, the bad, the ugly,

and som tips from their own experiences.

• Monthly retainers shouldn’t mean monthly attention
• Regular monitoring helps catch issues early
• Allows for better tracking of algorithm updates across client portfolio
• Builds stronger client relationships and trust

• Rankings check
• Organic traffic analysis
• Google Search Console error monitoring
• Task progress updates
• Client KPI tracking
• Sales/conversion monitoring

• Dedicate specific days for client reviews (examples given: Mondays or Fridays)
• Can be done in 10-15 minutes per client
• Start with top clients if overwhelmed
• Schedule reviews at least 48 hours before client meetings

• Share highlights and wins immediately
• Don’t go more than two weeks without client contact
• Proactively inform clients about algorithm updates or ranking changes
• Get regular feedback on sales/leads that might not show in analytics

• Easier to spot trends across multiple clients
• More confident client conversations
• Better prepared for monthly reporting
• Opportunity for quick fixes and improvements
• Earlier detection of potential issues

• Use tools that your team will actually engage with
• Focus on implementation rather than perfect tool selection
• Consider client preferences for communication platforms
• Set up regular task reminders for consistency

This episode delves into how the drama may reshape the WordPress ecosystem and its potential business implications for agencies and developers.

• WP Drama Overview: Ongoing tensions between WordPress founder Matt Mullenweg (Automattic) and WP Engine, a major hosting company, have escalated.
• WordPress Plugin Repository Conflict: Automattic blocked WP Engine from the WordPress plugin repository, which raised concerns within the WordPress ecosystem.
• Advanced Custom Fields (ACF) Takeover: Automattic allegedly "hijacked" the free version of ACF from the repository, though WP Engine still manages ACF Pro for paying customers.
• WP Engine's Response: WP Engine downplayed the situation and found a workaround to update plugins despite the block, using VPNs to bypass restrictions.
• Client Concerns: The drama has led to increased client uncertainty, with some questioning the security and viability of WP Engine, despite no immediate risks.
• Impact on Developers: The conflict has made some developers consider alternatives to WordPress and question whether WordPress remains the best solution for certain projects.
• Community Reaction: The drama has sparked discussions about the contributions to the WordPress community, with concerns over profiteering by WP Engine.
• Long-Term Effects: Uncertainty about the future relationship between WP Engine and Automattic, with potential long-term impacts on the WordPress ecosystem.
• Developer Anxiety: Some developers have lost contracts due to client concerns, reflecting the ripple effect of the conflict on business decisions.
• Alternative Solutions: A growing discussion around whether WordPress is the best fit for all projects, with mentions of alternative platforms like Squarespace or Shopify.
• Philosophical Questions: Broader debates on the nature of open source, contribution expectations, and the role of the community in the growth of WordPress.