Skip to content
NinjaMunk

Found and chosen

SEO Optimization

Most SEO problems we are asked to fix are architecture problems. Pages compete with each other, templates emit the wrong markup, and the fastest wins are buried under a site structure nobody planned.

The problem

What this
usually fixes

  • Rankings stalled and the advice you are getting is a monthly list of blog titles.
  • Similar pages compete for the same query, so neither one ranks.
  • Core Web Vitals fail on mobile and the fixes keep getting deprioritised.
  • Nobody can tell you which pages actually produce enquiries versus traffic.

Who it is for

  • Businesses with a working site that is invisible for their commercial searches.
  • Teams planning a rebuild or replatform who want to protect existing visibility.
  • Companies who have paid for SEO retainers and cannot point to what changed.

Benefits

What changes
after launch

  • 01

    Structure before content

    A keyword map tied to a sitemap, so every page has one job and one query family rather than four pages fighting over one term.

  • 02

    Markup that earns richer results

    Schema, semantics and internal linking implemented in components, so correctness scales with the site rather than decaying.

  • 03

    Reporting a director can read

    Rankings, entrances and enquiries in one view, with a plain statement of what moved and what we recommend next.

Deliverables

  • Technical audit
  • Keyword map
  • Schema markup
  • Reporting setup

Outcomes we hold ourselves to

  • — Crawlable structure, clean internal linking, correct canonicals
  • — Structured data that earns richer search results
  • — Core Web Vitals treated as a release requirement

Technology

  • Search Console
  • GA4
  • Screaming Frog
  • Lighthouse CI
  • Schema.org
  • Ahrefs

Tooling is chosen for maintainability, not novelty. You own every account and the repository from day one — see how we work.

Process

How the work runs

  1. 01

    Audit

    Crawl, index coverage, log-level issues, Core Web Vitals and content overlap, prioritised by likely commercial impact.

  2. 02

    Keyword and page map

    Demand research mapped onto a sitemap: one intent per page, with the internal linking plan drawn before anything is written.

  3. 03

    Implementation

    Technical fixes, schema, metadata and performance work implemented in the templates rather than patched page by page.

  4. 04

    Measure and iterate

    Monthly reporting on rankings, entrances and enquiries, with a short prioritised backlog for the following month.

FAQ

Straight
answers

Next step

Tell us what the
site has to do

Send the goal, the deadline and a budget range. You will get a considered reply within one working day — including an honest answer if we are the wrong studio for it.