360 SEO

I rely on the 360 SEO framework when a site needs more than a patch. It forces you to connect technical health, content depth, user behaviour, and backlink profile into a single plan. I saw this play out with a client that lost 35% of organic traffic after a core update. Their technical audit passed, but content was shallow and mobile navigation was broken. We spent three months on topic clusters, structured data, and UX improvements. Traffic recovered 50% in four months. The decision rule I use: if you have over 300 pages and at least two team members, 360 SEO is worth the investment. It prevents you from fixing one thing while another breaks. Counter-argument: some say it's too slow. I'd rather build a sustainable strategy than chase quick fixes that fade. The real value is in cross-functional alignment. When developers understand that page speed affects conversions, not just Lighthouse scores, they prioritise it differently. When writers see that topic clusters outperform isolated blog posts, they change their approach. I track this with a shared spreadsheet that maps each task to an estimated traffic impact. For example, fixing 500 server errors might gain 10% traffic, while rewriting a thin page might gain 5%. That numeric prioritisation is where 360 SEO shines. I also use it during site migrations. Mapping all old URLs to new ones is technical, but you also need to rebuild content clusters and maintain link equity. 360 SEO catches those overlaps.

I used to push 360 SEO on every project. I now think that's a mistake. I learned this the hard way working with a startup that had a great product but no traffic. I recommended a full 360 plan; three months later they'd made no progress. I should have started with a single fix: optimising their category pages. For a local business with ten pages and one owner-operator, a full-circle strategy is overwhelming. I recently advised a plumber in Manchester. Instead of 360, I had them focus on Google Business Profile, local citations, and six service pages. Traffic grew 120% in two months. Counter-argument: you might argue that 360 SEO can be scaled down. In theory yes, but in practice the cognitive load of managing technical, content, and UX simultaneously leads to half-baked work. The decision rule: if your monthly traffic is under 2,000 sessions or your team is just you, pick the biggest gap. Use a tool like Screaming Frog to find crawl errors first, or Ahrefs to find content gaps. Don't try to do everything at once. Edge case: e-commerce sites with 1,000+ products often benefit from 360 SEO even with small teams because technical issues compound quickly. So it's not a hard rule, but a guideline.

If 360 SEO feels too heavy, I start with a focused audit. Use [Screaming Frog](/screaming-frog/) to crawl the site and identify technical issues like broken links, duplicate meta descriptions, and slow pages. That alone can recover 20% of lost traffic. For content gaps, I turn to [Ahrefs](/ahrefs/) content gap analysis: find pages where competitors rank but you don't. Write targeted posts. I saw a 45% traffic increase from just five content gap pages. For user behaviour insights, [Hotjar](/hotjar/) session recordings show where people drop off. I once found a checkout button that was invisible on mobile – fixed it, conversions up 15%. For ongoing monitoring, [Semrush](/semrush/) and a [rank tracker](/rank-tracker/) let me track keyword movements without a full strategy. If you're starting from zero, a [website traffic checker](/website-traffic-checker/) gives you a baseline. My alternative framework: the 'biggest gap first' approach. Pick one area – technical, content, UX, or links – and measure impact. Then expand. This is faster for small sites. Counter-argument: this misses the interactions between areas. True, but if you fix the biggest gap first, you often reveal the next. It's iterative.