{"id":2672,"date":"2025-09-30T06:11:26","date_gmt":"2025-09-30T05:11:26","guid":{"rendered":"https:\/\/www.forestsoftware.co.uk\/blog\/?p=2672"},"modified":"2025-09-29T15:45:45","modified_gmt":"2025-09-29T14:45:45","slug":"john-k-mitchell-an-introduction","status":"publish","type":"post","link":"https:\/\/www.forestsoftware.co.uk\/blog\/2025\/09\/john-k-mitchell-an-introduction\/","title":{"rendered":"John K Mitchell – an Introduction"},"content":{"rendered":"Reading Time: <\/span> 11<\/span> minutes : <\/span><\/span>

 <\/p>\n

John K. Mitchell is a pioneer in search engine optimisation (SEO), working on sites long before Google even dominated the web. As he isn’t good at “blowing his own trumpet”, I sat down with John to dig into his journey, his methods, and why he\u2019s still passionate about making sites rank better today and he has published this article on the Forest Softare blog.<\/p>\n

 <\/p>\n

Who is John K. Mitchell?<\/h1>\n

When I first met John, what struck me wasn\u2019t just the decades he\u2019s been doing SEO, but how down-to-earth and curious he still is. He doesn\u2019t talk in jargon; he talks about people, stories, and solving puzzles.<\/p>\n

John is the key person behind Forest Software, a company that helps firms get their websites working harder \u2014 not just pretty, but visible. Over the years, he\u2019s worn many hats: programmer, analyst, system tester, adviser, strategist \u2014 always learning, always adapting.<\/p>\n

Let me take you through his story, where he comes from, what drives him, and what he\u2019s doing now.<\/p>\n

Early Days: programming and curiosity<\/h2>\n

John tells me that his roots are in programming and that he started programming back in 1979 in a large hotel working on their back office system.\u00a0 He then moved into the health area working on diagnostic system at a health authority, then into a tour operator, finally moving into fund management and banking systems after a stint in a timber importer and wholesaler.<\/p>\n

Finally in 1995 he built his own series of webpages, hand-coding the code needed as you might expect from a programmer.<\/p>\n

Long before SEO was a household word, he was already coding, analysing output, and wondering why<\/em> certain results showed up where they did.<\/p>\n

Back in 1997 \u2014 yes, 1997 \u2014 John began experimenting with site optimisation. That\u2019s before Google was the dominant force it is today. In those days, search engines were more primitive, the rules were murky, and everything was more manual. But John saw a pattern: because he understood programming and logic, he could look at a search engine\u2019s output and begin to form educated guesses about what was going on behind the scenes.<\/p>\n

From those early days, John saw something interesting: if you could peek under the hood of search results, you might guess why<\/em> a page ranks where it does. With a programming background, he began making educated guesses, testing tweaks, and seeing what moved the needle.<\/p>\n

That early willingness to poke under the hood, test, adjust, and learn \u2014 that\u2019s a theme that stays true to this day.<\/p>\n

He\u2019s told me that in those early years, many clients were small (or even one-person) websites. John would dive into the code, look at server logs, look at which keywords brought traffic, and tweak things. Sometimes results were small, sometimes bigger. But every experiment taught him more.<\/p>\n

By doing this over and over, he built up a sense of \u201cwhat works, what doesn\u2019t, and why.\u201d That\u2019s partly what now lets him advise confidently on modern SEO \u2014 because he\u2019s seen Google and other engines change, and adapted.<\/p>\n

Joining and growing Forest Software<\/h2>\n

In 1983, John started Forest Software as an \u201cM software consultancy.\u201d (M being a programming language that is still in use today) for the clients that he had at the time.<\/p>\n

Forest Software is the company that John uses to help organisations with web presence, performance, optimisation, and more. The goal: make sites work harder, not just look good.<\/p>\n

John is really the main engine behind that \u2014 someone who brings real experience to the table.<\/p>\n

Within the Forest Software environment, his role is to guide, mentor, lead strategic SEO decisions, and technically supervise. His presence gives stability: you don\u2019t just get someone reading SEO textbooks \u2014 you get someone who lived through its evolution.<\/p>\n

In my conversation with him, I saw how he balances leadership and execution. He doesn\u2019t just give orders \u2014 he\u2019s still hands-on, getting his fingers on code, logs, analytics. He encourages team members to test, fail, iterate. He often says: \u201cIf you don\u2019t test, you\u2019re just guessing\u2014so test responsibly.\u201d<\/p>\n

One thing he emphasises is this: Forest Software isn\u2019t a magic wand. SEO doesn\u2019t deliver overnight miracles. John is realistic: \u201cIf someone promises Page 1 in a week, be skeptical.\u201d He pushes clients to see SEO as a journey, not a one-time event.<\/p>\n

Under his guidance, Forest Software has handled many clients across sectors, each with different challenges (performance, content, structure, links). John\u2019s approach is to treat each client\u2019s website as a unique puzzle: there are principles, but the solution is rarely identical from one case to another.<\/p>\n

What drives him now<\/h2>\n

You might think: after so many years, someone might slow down. But John still gives off that spark of curiosity. In our talk, he described how each Google algorithm update is like a new puzzle to figure out. He doesn\u2019t recoil; he leans in.<\/p>\n

He also cares about teaching and sharing. He often runs internal workshops with the team, explaining how structured data, site speed, mobile signals, content strategy all combine and has run external workshops in the past. He doesn\u2019t just demand results \u2014 he wants people to understand why the results have happened (or not)<\/em>.<\/p>\n

One thing he\u2019s focused on lately is bridging gaps between SEO, content, development, and UX (user experience). He believes that in modern web work, those silos can\u2019t stand. It\u2019s no good optimising keywords if the site is slow, or if the content is off, or if users can\u2019t navigate or if it attracts the wrong type of visitor.<\/p>\n

Another interest he\u2019s expressed to me is future-proofing. Because search engines evolve, John wants\u00a0 clients to build sites that are resilient: adaptable, maintainable, grounded in good architecture and content, not just hacks or tricks.<\/p>\n

A snapshot biography: John K. Mitchell<\/h1>\n

Here\u2019s the biography I pieced together from our talk, his notes, and public bits:<\/p>\n

    \n
  • John K Mitchell\u2019s interest in technology and programming started early – he was working on systems back in 1979 (and had even written computer programmes for a mainframe using paper tape while in school in 1972 !).<\/li>\n
  • In 1997, before Google dominated the landscape, he began delving into site optimisation \u2014 analysing search engine output, server logs, code, and forming hypotheses about what influences ranking.<\/li>\n
  • Over time, John has worked on thousands<\/strong> of websites, many of which achieved solid ranking improvements (organic traffic growth, exposure, and importantly, conversions).<\/li>\n
  • His strength lies not just in applying best practices, but in diagnosing specific issues, combining analytics, technical insight, content strategy, and user behaviour.<\/li>\n
  • He is a senior figure at Forest Software, guiding both strategy and execution.<\/li>\n
  • He teaches, mentors, leads workshops, and stays hands-on.<\/li>\n
  • He has adapted through multiple eras of SEO and search engine evolution \u2014 seeing \u201csearch\u201d shift from simple keyword matching to complex AI, semantic, mobile, voice era.<\/li>\n
  • John\u2019s philosophy: continuous testing, adaptation, understanding underlying systems, not chasing short-term gimmicks.<\/li>\n
  • Personally, he\u2019s modest, curious, and always looking to raise the bar \u2014 both for himself and the team around him.<\/li>\n<\/ul>\n

    Notable challenges & lessons<\/h3>\n

    While I didn\u2019t find many \u201ccelebrity case studies\u201d of John K Mitchell, you can infer the lessons:<\/p>\n

      \n
    1. \n

      Change is constant.<\/strong> The rules of SEO shift (major Google updates, mobile-first indexing, Core Web Vitals). Someone who\u2019s lasted decades has had to adapt or die.<\/p>\n<\/li>\n

    2. \n

      Small is an advantage.<\/strong> John\u2019s focus on smaller businesses means less overhead, less bureaucracy, hands-on work.<\/p>\n<\/li>\n

    3. \n

      Underpromise, overdeliver.<\/strong> By only accepting clients when he believes he can help them meaningfully, he avoids overpromising and underdelivering (a common agency problem).<\/p>\n<\/li>\n

    4. \n

      Programming + intuition = power.<\/strong> John\u2019s background lets him see patterns others miss: odd ranking behaviours, correlations in code, or server quirks.<\/p>\n<\/li>\n

    5. \n

      Holistic web presence matters more than just rankings.<\/strong> A site could rank #1 but bring no leads. John\u2019s approach always keeps the business goal in mind.<\/p>\n<\/li>\n<\/ol>\n

      Anecdotes & insights from our conversation<\/h1>\n

      I\u2019ll share a few moments from our chat that stood out \u2014 because they reveal how John thinks and works.<\/p>\n

      1. The \u201cbroken breadcrumb trail\u201d story<\/h3>\n

      John once described a site where traffic tanked after a site redesign. The culprit? A missing breadcrumb trail (a navigational element) that had linked thousands of pages into a logical structure. After the redesign, the breadcrumbs vanished. This caused issues with internal linking, reduced crawlability, and messed with user paths.<\/p>\n

      Fix the breadcrumb logic, restore internal links \u2014 traffic bounced back. That story stuck with me because it shows that it\u2019s often small structural things, not \u201cthe magic SEO tweak,\u201d that make or break things.<\/p>\n

      John said: \u201cPeople look for big growth hacks. But often your best leverage is in the details \u2014 in making the site coherent, navigable, consistent, clear.\u201d<\/p>\n

      2. \u201cGuess, test, refine\u201d is not a motto \u2014 it\u2019s a habit<\/h3>\n

      John emphasised that much of his early work was built on making consistent guesses (educated ones), testing them, tracking results, refining, then repeating. Over decades, that habit matured.<\/p>\n

      He told me one time he tried tweaking URL structures for a client (removing query parameters, simplifying slugs). The change was modest. But when combined with tweaks to internal linking and page speed, the effect magnified.<\/p>\n

      It\u2019s the compound effect of many small optimisations, each guided by observation and data.<\/p>\n

      3. He still keeps a log of \u201clessons learned\u201d<\/h3>\n

      In his office, John keeps a running log of lessons \u2014 \u201cif you see this scenario, try that,\u201d \u201cthis algorithm update penalised this pattern,\u201d \u201cbe wary when content is low on a deep page\u201d etc. Over years, that log becomes a database of insight. When a new project comes in, he\u2019ll skim through similar patterns in that log.<\/p>\n

      4. Transparent communication with clients<\/h3>\n

      One thing I pressed him about: how he handles client expectations. He said he insists on honesty. He\u2019ll sometimes show clients graphs of site traffic, dips after major algorithm changes, and explain what might be going on (and what he will try). He says clients prefer someone who is forthright, even about uncertainties, than someone promising the moon.<\/p>\n

      One interesting aspect is that he will only take on a client if he thinks it will make a real difference, not just adjust rankings,\u00a0 That\u2019s a rare promise in the SEO world, where many agencies focus solely on metrics like \u201crankings up\u201d rather than business outcomes.<\/p>\n

      He emphasised that SEO is not a box you tick and leave. It\u2019s ongoing. He sees himself partly as a coach, walking alongside the client.<\/p>\n

      The evolution of SEO: John\u2019s perspective<\/h2>\n

      Because John has been in this long enough, I asked him how SEO has changed (and where it might go). Here\u2019s a distilled version of his thoughts.<\/p>\n

      Then vs Now<\/h3>\n
        \n
      • Keyword stuffing vs meaning & context<\/strong>
        \nIn the early days, you could insert the same keyword many times and hope it helps. Now, search engines understand context, synonyms, related phrases, latent semantic indexing. John says you must write content that makes sense<\/em>, not just target phrases.<\/li>\n
      • Links vs quality & relevance<\/strong>
        \nBack then, quantity of backlinks mattered a lot (even low-quality links). Now, relevance and link quality matter more. And the strategy has to be careful, thoughtful.<\/li>\n
      • Speed, mobile, UX<\/strong>
        \nHe says modern SEO is intertwined with site performance (speed), mobile friendliness, user experience. A site that is technically perfect for SEO but slow or ugly to use will struggle.<\/li>\n
      • Algorithm complexity and AI<\/strong>
        \nNow search engines use machine learning, embeddings, semantic analysis. That adds unpredictability. John says we must rely less on hard \u201crules\u201d and more on systems that can adapt.<\/li>\n
      • Structured data, rich snippets<\/strong>
        \nUsing schema, structured markup to give search engines clues on what content means<\/em> \u2014 not just what it says. John sees this as essential for the next era of SEO.<\/li>\n
      • Voice, zero-click, answer boxes<\/strong>
        \nMore searches are voice-based, and search engines often provide answers directly rather than just links. So being the \u201csource snippet\u201d or appearing in featured snippets is a priority.<\/li>\n<\/ul>\n

        What\u2019s next?<\/h2>\n

        When I asked what he\u2019s keeping an eye on, John mentioned:<\/p>\n

          \n
        1. Search generative AI \/ Integration<\/strong>
          \nAs search engines blend generative responses (AI answers) with links, how do you preserve visibility? He\u2019s experimenting with content formats, markup, and signals to try and remain part of the conversation.<\/li>\n
        2. User signals<\/strong>
          \nThings like dwell time and scroll depth \u2014 what do they really signal to the engine? Adjusting how content, layout, navigation encourage engagement.<\/li>\n
        3. Adaptable architectures<\/strong>
          \nHe wants sites designed so they can evolve \u2014 content systems, modular architecture, APIs, flexibility \u2014 to avoid major rewrites when search changes.<\/li>\n
        4. Automation & tooling<\/strong>
          \nHe\u2019s personally interested in semi-automated auditing tools, scripts, monitoring setups that help catch issues early. But always balanced with human judgement.<\/li>\n
        5. Ethics & sustainability<\/strong>
          \nHe\u2019s cautious about black-hat or risky strategies. Over time, he says, you may win short term, but you risk losing long term. He pushes clients toward sustainable SEO that holds up across changes.<\/li>\n<\/ol>\n

          Case glimpses: what John has done (without naming clients)<\/h2>\n

          John can\u2019t always name every client (non-disclosure, privacy etc.), but he shared some general success themes that impressed me.<\/p>\n

            \n
          • Local business uplift<\/strong>
            \nA local trades company (plumbing, heating) had minimal organic reach. Working with John, the site\u2019s structure, content, local signals, reviews, and internal linking were overhauled. Over months, organic leads rose significantly, reducing their dependence on paid leads.<\/li>\n
          • E-commerce revamp<\/strong>
            \nAn online shop with many products was losing ground. The issue was thin product description pages, lack of unique content, duplicated descriptions, slow pages, and poor faceted navigation. John and team restructured product layout, canonical tags, improved imagery, and content \u2014 traffic rose steadily, and revenue from organic increased.<\/li>\n
          • Content-driven authority site<\/strong>
            \nA site positioned as a resource\/news site was struggling to rank in deeper topics. John helped to build content clusters, internal linking hubs, supporting articles, better keyword mapping, and technical cleans to ensure crawlability. Over time, many pages gained visibility, bringing in consistent organic traffic.<\/li>\n
          • Migration \/ redesign rescue<\/strong>
            \nHe once worked on a site redesign that caused a plunge in rankings. By carefully redirecting URLs, preserving link equity, mapping old to new structure, managing canonical tags, cleaning up 404s, and monitoring logs, he recovered much of the lost traffic. He told me that in such rescue jobs, speed, monitoring, and constant iteration are essential.<\/li>\n<\/ul>\n

            Each of these stories reinforces John\u2019s method: diagnose, plan, act, monitor, refine \u2014 not a one-shot fix.<\/p>\n

            How John works with clients<\/h1>\n

            If you become a client, here\u2019s what the experience is likely to be (from what he explained to me).<\/p>\n

              \n
            1. Audit \/ Discovery phase<\/strong>
              \nJohn begins by reviewing analytics, logs, crawl reports, technical health, content gaps, competitiveness. He also wants to understand your business, your goals, your constraints (budget, resources, content team, tech stack).<\/li>\n
            2. Strategic planning<\/strong>
              \nFrom that audit, he plans a roadmap: which technical fixes, content projects, link or outreach work, UX adjustments, performance improvements, prioritised in phases.<\/li>\n
            3. Implementation oversight<\/strong>
              \nJohn often stays involved during implementation \u2014 reviewing code changes, content work, site migrations, or tweaks to templates. He ensures that the plan is executed well, and adjusts as issues arise.<\/li>\n
            4. Monitoring & iteration<\/strong>
              \nSEO isn\u2019t done once; John builds monitoring systems (rankings, organic traffic, logs for errors, crawl stats) and holds regular reviews. If something shifts (e.g. algorithm change, drop in traffic), he dives in to diagnose.<\/li>\n
            5. Reporting & transparency<\/strong>
              \nClients receive accessible reports. John believes in showing clients the data, not hiding behind vague terms: what improved, what needs more work, what experiments are underway.<\/li>\n
            6. Education & collaboration<\/strong>
              \nJohn invites clients to understand the logic, trade-offs, constraints. This helps clients trust decisions, and reduces friction. He sees himself as a partner rather than a vendor.<\/li>\n
            7. Long-term partnership<\/strong>
              \nThe best outcomes often come over months or years. John pushes clients to view SEO as long-term investment, not short-term gain. Over time, compounding improvements can yield strong returns.<\/li>\n<\/ol>\n

              Why John stands out (what sets him apart)<\/h1>\n

              I asked John: \u201cWith many SEO consultants out there, why should someone consider working with you ?\u201d Here\u2019s what I got \u2014 and why I believe it.<\/p>\n

              Deep history and evolving insight<\/h2>\n

              Not many people have continuously navigated SEO\u2019s shifting landscape from the dawn of modern engines to today. John\u2019s seen what works, what fails, and why. That institutional memory matters.<\/p>\n

              Technical + strategic balance<\/h2>\n

              Many SEO folks lean purely content, others purely technical. John blends both. His programming background helps him interpret logs, errors, server behaviour. His content sense helps him advise language, structure, semantic logic and marketing techniques.<\/p>\n

              Testing mindset<\/h2>\n

              He doesn\u2019t push dogma. He says \u201ctest and see.\u201d That humility \u2014 the willingness to try, measure, and adapt \u2014 builds trust and better results.<\/p>\n

              Detail focus<\/h2>\n

              He notices breadcrumbs, canonical chains, schema markup, internal link webs, content typos \u2014 those \u201csmall\u201d things often make big difference. He fights the idea that SEO is only macro strategy \u2014 sometimes the micro matters more.<\/p>\n

              Honest communication<\/h2>\n

              He told me he refuses to promise unattainable gains. He emphasises clarity with clients about uncertainties, timeframes, risk. That builds real relationships.<\/p>\n

              Resilience and ethics<\/h2>\n

              He avoids risky \u201cblack hat\u201d shortcuts. He wants wins that last. He accepts that Google is likely to penalise unconventional tactics later. So he designs strategy that are not risky.<\/p>\n

              What I learned from John that you can use<\/h1>\n

              Talking to John left me with a few takeaways I think are valuable whether you\u2019re an SEO beginner, site owner, or just curious.<\/p>\n

                \n
              • Don\u2019t chase shortcuts<\/strong> \u2014 invest in fundamentals (clean architecture, good content, user experience).<\/li>\n
              • Experiment \u2014 but monitor<\/strong> \u2014 try changes, check how they perform, roll back if needed.\u00a0 Make one change at a time so you know what’s worked and what hasn’t.<\/li>\n
              • Log lessons<\/strong> \u2014 keep a running diary of what patterns worked or backfired.<\/li>\n
              • Cross-discipline thinking<\/strong> \u2014 SEO doesn\u2019t live in a silo. It touches content, dev, UX, performance.<\/li>\n
              • Patience is key<\/strong> \u2014 gains often build day by day.<\/li>\n
              • Client (or stakeholder) communication matters<\/strong> \u2014 explaining reasoning builds trust.<\/li>\n
              • Never stop learning<\/strong> \u2014 algorithms change, user behaviour changes, new formats appear.<\/li>\n<\/ul>\n

                Closing thoughts<\/h1>\n

                My conversation with John K Mitchell gave me a renewed respect for those quietly laying foundations in the SEO world. He\u2019s not chasing flash trends. He\u2019s building durable, sensible, well-reasoned systems. He\u2019s mentoring, executing, adapting.<\/p>\n

                If you engage with John, you won\u2019t get a silver bullet \u2014 what you\u2019ll likely get is steady progress, clarity, strategy built on experience, and a partner who cares about how your site actually works for people and your business, not just for search engines.<\/p>\n

                And in the rapidly changing world of SEO, that\u2019s the kind of partnership that endures.<\/p>\n","protected":false},"excerpt":{"rendered":"

                Reading Time: <\/span> 11<\/span> minutes : <\/span><\/span>  John K. Mitchell is a pioneer in search engine optimisation (SEO), working on sites long before Google even dominated the web. As he isn’t good at “blowing his own trumpet”, I sat down with John to dig into his journey, his methods, and why he\u2019s still passionate about making sites rank better today and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,3],"tags":[],"class_list":["post-2672","post","type-post","status-publish","format-standard","hentry","category-general","category-seo"],"_links":{"self":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts\/2672","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=2672"}],"version-history":[{"count":0,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts\/2672\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=2672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=2672"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=2672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}